We've emailed Adyen about this one.

Email subject is 'Unexpected 'Expired Card (54 : Expired card)' response for non-expired cards.'

Adyen came back to us with:

Thank you for contacting Adyen.

Indeed, you are right that the card expiry date was future date.

This refusal reason is coming from the issuer- it's possible the card is refusing on their end for some other reason, but are sending the response code that we normally map to "expired card". I recommend that the shoppers contacts their issuer to request more information on why the card is being refused, as Adyen do not have further insights on this.

Hope this clarifies!

Thanks @jgleeson! I've let the donors know. :)

Have another one that I think may be the same issue. Donor in Zendesk #1829484/CID 47129803 attempted to donate a total of 3 times on 01/20 and 01/21. All three attempts are declined with the response "expired card". However, the expiration date provided for each of the transactions is a future date.

Transaction id's at Gr4vy:

• 5dcbd608-abae-4028-b3dd-7343a55b6d2c
• d14a2949-7f7c-412f-9f30-ed7e712f71f4
• b7f1d8c8-0075-4f50-bd1f-28cb4645e009

Ideally if it's not an expired card it won't note that at the PSP and say it's just a general decline. Without this extra checking that I happened to do this time we would have provided the donor with incorrect information as we have special messaging if it's actually an expired card informing them of that.

Not sure if we can ask them if there is a way to look into improving the mapping on their end? Or possibly there is just no fix for this one. 😅

@AMJohnson My search results suggest that some issuers will show 'expired card' errors for the old card if the buyer has gotten a replacement card (i.e. due to losing the old one), even before the old card's expiration date. So maybe some of these folks have gotten replacements but still have the old card info saved in a browser?

Interesting thanks @Ejegg! Luckily we have a workaround for now. If we notice we can just use our standard decline messaging.

Sounds good @AMJohnson, I'll move this ticket to 'Done' on our tracking board.

To confirm, it sounds like there is nothing we can do to improve this on our end? If so I'll let the team know. :0)

Right @AMJohnson, we don't have any better information available to us on the form, so we're stuck trusting the codes we get back on the response.

Gotcha. Thank you for looking into it, @Ejegg!