Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › eStore – authorize.net declines
- This topic has 19 replies, 4 voices, and was last updated 12 years, 6 months ago by tiger.
-
AuthorPosts
-
May 23, 2012 at 5:33 am #29591adminKeymaster
Thank you for the details. The following is your issue (it explains why authorize.net declined this transaction).
Authorization with the card issuer was successful but
the transaction was declined due to an address or ZIP code mismatch
with the address on file with the card issuing bank based on the settings in the Merchant Interface.If the payment gateway (in this case authorize.net) declines a payment due to an issue with the credit card details then the plugin can’t do anything. You will need to use a valid credit card and use correct details so the payment gateway accepts it.
May 23, 2012 at 7:03 am #29592tigerMemberThank you… However, I’m not concerned with the
transaction declining. I’m only concerned with
the form returning to the same page; allowing
my customer the opportunity to correct the issue.
When the customer realizes that he/she inadvertently
plugged in the wrong address or zip code, they can
easily correct the mistake because the form has returned
letting them know their error(s).
Please provide a solution to a very simple issue.
I’m merely asking that my customer be given a second
opportunity to input the correct information.
Please help.
Thank you, kindly!
May 23, 2012 at 7:12 am #29593tigerMemberAre you telling us that your plugin gives “only”
one opportunity to input information on the form
correctly, or you’re out of luck?
May 23, 2012 at 7:50 am #29594adminKeymasterThere maybe a slight misunderstanding here. Are you referring to the standard authorize.net gateway where the credit card data is entered on the authorize.net site or are you referring to the AIM integration via the gateway bundle?
I am guessing you are referring to the standard authorize.net gateway. This is what happens when you are using the standard authorize.net gateway:
1) Your customer hits the “Buy” button on your site
2) Item gets added to the shopping cart
3) The customer hits the checkout button to checkout
4) The customer is sent to authorize.net’s payment page (from this point onward the plugin has no more control… authorize.net takes control of the checkout)
5) The customer enters the credit card details on authorize.net payment page.
6) Authorize.net will give error until a correct credit card details is entered.
7) Once the payment is accepted authorize.net will redirect the customer to the “Thank You” page.
The payment won’t even be accepted on the authorize.net’s payment page in “step 6” until a valid credit card details is entered (your customer can try as many times as they want).
Now, in your case authorize.net is accepting the card details on step 6 then declining it which is something that never happens in normal situation. Does that help you see why it’s not the plugins fault because the card details is entered on authorize.net site (not in a form created by eStore)?
There is most likely something not configured correctly in your authorize.net merchant profile which is why the gateway is behaving this way. Contact authorize.net and ask them the following question and they will be able to sort it out:
Why is the payment getting declined after it accepts the credit card on the authorize.net checkout page?
May 23, 2012 at 3:39 pm #29595tigerMemberThanks for the information… I understand now. All is well.
Thanks again!
-
AuthorPosts
- You must be logged in to reply to this topic.