15005 problem -> user needs to get a notification

Hey,

whenever a user tries to use a card that does not get accepted by pp pro (15005), the user gets from payer_auth_frame(step4) to checkout_payment(step2) without a confirmation. is there a way to improve that? this is very confusing for some of my customers, especially for new ones.

thanks in advance

Do you have an example of a card that does not get accepted? ie: what exactly is being rejected? Is it the card type? the card number? the CVV? the amount? the password? or just insufficient funds? or something else?

OK, so usually I get this mail:

Problem occurred while customer #xxx -- username -- was attempting checkout. (Classis 15005 error)

Then some of my customers told me they got a mail from their bank cause they think the shop is a fraud (I guess cause they try to checkout multiple times).

I couldn't reproduce this error, but according to 2 of my customers Zen doesn't say what's wrong, it just redirected them from payer_auth_frame to checkout_payment again.

It would be great if I could parse the 15005 on the payer_auth_frame and open a popup so the user actually knows what has happened.

Card used was a Visa.

p1lot:

OK, so usually I get this mail:

Problem occurred while customer #xxx -- username -- was attempting checkout. (Classis 15005 error)
Is that exactly what the email says?
... cuz I don't recognize how it would say "(Classis 15005 error)".

15005 is the response code PayPal issues when the credit card is rejected by the customer's bank.
When Zen Cart gets such a response it stuffs the error message into the messageStack and redirects the customer to the checkout_payment page where the messageStack outputs any error messages that have been generated.

Perhaps your template has been altered and no longer properly shows messageStack messages on the checkout_payment screen?

Sorry, I wanted to add "(classic 15005 error)" and made a typo. I know, and that's what I told the uses. But they said there was no error message or anything.

I didnt remove the error stack on my page or anything.

Anyway, as always Dr. Byte, thanks for your help!

What other payment modules do you have enabled?

PP Express and PP Pro are the only modules that are enabled.

I asked 6 customers now and all of them said that there was no error displayed when they experienced a 15005. I think I really lose some customers because of this error.

Just a thought ... are you suggesting that somehow a message saying "Sorry, your bank is rejecting your credit card" is going to magically "save" those customers?
If they don't have the money, then they're not going to buy anyway. If their bank is denying them to use the card, they can't buy. The only option is for them to use a different card, which is what they're directed to do anyway (by being taken back to the payment options page).

Further, it's VERY unwise to say anything about why the card is rejected ... otherwise you become a target for thieves who use your site just to attempt to validate stolen card numbers, while racking up transaction fees for you.

Would it be possible to just display something like: "Sorry, your card has been rejected for unknown reasons".

p1lot:

OK, so usually I get this mail:

Problem occurred while customer #xxx -- username -- was attempting checkout. (Classis 15005 error)
What's the subject-line of that email?
Did the body actually say "(Classic 15005 error)", or did you add that part when you posted it?
Was there anything else other than that one line in the body of the email?

Hey,

1. not sure, deleted the 15005 mails

2. Nope, I added that "(Classic 15005 error)"

3. Nothing else was in the body of that mail

Zen Cart Version 1.3.9h

Updated recently from 1.3.9g

Using PayPal Website Payments Pro.

Text of email from my site to me:

Subject: ALERT: PayPal Direct Payment Error (15005)

Problem occurred while customer #<xx> - <name> - was attempting checkout.

No message displayed on page. Other declination messages display.

This just seems to have started.

http://thescannerstore.com

Do you have PayPal Debug Logging enabled? The logs will be useful. ref: http://www.zen-cart.com/forum/showthread.php?t=61199

• turn them on
• recreate the problem
• zip the logs
• upload the zip to your server
• send me a PM with a link to the zip file so I can analyze the logs

I'm having the same problem with my site. When paypal rejects the card, it just goes back to the checkout page without any error message (yet an email is sent to us with the error as described in this posting ).

Has anyone found a fix for this? Thanks!

• using version 1.3.9h

Zen-cart v1.3.9h Checkout without an account.
This customer only showed up as a 'new customer', not as a 'new order'.
We received this email:
ALERT: PayPal Direct Payment Error (15005)
Problem occurred while customer #436 -- Ciro -- was attempting checkout.
When we contacted the customer, Ciro said he didn't know if it took or what happened. He was taken back to the home order page each time he attempted to pay. He didn't receive notification from Zen-cart that his credit card was declined. When we took his credit card over the phone, and entered it into the pay-pal virtual terminal, we were told that it was declined. He had another card that he would have used if he had been notified of the decline.
Is there a way to:
(1) check the customer page to seen the reason for the lack of an order, and
(2) make sure that the customer gets notification of the card decline, so he can use another card.

I just checked v1.3.9h and v1.5.0 and v1.5.1, and they all give an error message of "Card rejected by the bank. Your IP address has been recorded" when a 15005 response is returned.

Most likely, the reason why the above zen-cart users in the past have not been getting the error message stacks appropriately displayed to their customers whose cards get 15005 rejections are due to this: http://www.zen-cart.com/showthread.php?198451-Fixed-v1-5-1-PayPal-WPP-Processor-Decline-Fails-to-Show-Error-Message&highlight=paypal

They need to make sure that debugging is enabled in the paypaldp payment module settings.

This appears to have been addressed in 1.5.1