"Your credit card is about to expire"?

I use the SDK to capture user’s credit card info.
Just got a support call: user’s card submission failed with message “Your credit card is about to expire. Please use a different card” – or words to that effect.

This isn’t a message from my code - is it a part of the Square SDK?

It sounds fishy to me? Card in question had expire date of 12/28 which makes this more confusing? Malware maybe?

:waving_hand: I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:

Additional Documentation

Troubleshoot In-App Payments SDK Problems
Reader SDK Quickstart
Reader SDK

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.

The message you’re encountering, “Your credit card is about to expire. Please use a different card,” is not directly generated by the Square SDK itself. However, it is possible that this message is being triggered by the card issuer or the payment processing system when the card is nearing its expiration date.

Square’s systems, including the Cards API, do have mechanisms to handle card expiration updates. For example, Square can automatically update the expiration date of cards on file when notified by the issuing bank. However, if a card is close to its expiration date and hasn’t been updated yet, it might trigger a warning or error message during a transaction attempt.

Given that the card in question has an expiration date of 12/28, it should still be valid. If the message is not coming from your code, it might be worth checking with the card issuer to ensure there are no issues with the card itself. Additionally, ensure that your application is handling card expiration dates correctly and that there are no other factors, such as incorrect date handling, that might be causing this issue.

If the problem persists, it might be helpful to log the transaction attempt details and consult with Square support to investigate further.

This answer was reviewed by @Bryan-Square.