I have a client that is integrated into our platform through oath. When they try to add a card through our integration they are getting this INVALID_CARD_DATA error below.
It only seems to be affecting them and no other client. Is there a way to diagnose better what the cause is or look into maybe their account has an issue?
Square\Models\Error::__set_state(array(
‘category’ => ‘INVALID_REQUEST_ERROR’,
‘code’ => ‘INVALID_CARD_DATA’,
‘detail’ => ‘Invalid card data.’,
‘field’ => NULL,
)),
Have they verified that the information they are inputing is what the bank has on file? 
Yes, we even tried a card in hand and didnt work.
Do you have the payment_id for the failed payment or is this error happening when trying to save the card on file?
It happens when we try to save the card on file, so there is no payment id
Okay, do you have the source_id that you generated with the Web Payments SDK?
Hi. We have not upgraded to the latest API yet, we are still using [2020-10-28 ]. I dont believe that is part of the API
What is the token/nonce you’re passing to the API?
most recent one is
cnon:CBESEKHdajsfm3Q9QtAo47xg4Js
I have a related production case, but the causes identified in this thread have been ruled out. The source is a newly authorized buyer-present card payment, not a sandbox test card, digital wallet, Square Pay, or existing card on file. The retrieved payment shows status: APPROVED, card_details.status: AUTHORIZED, entry_method: KEYED, with AVS and CVV accepted. Customer, application and location match, and CreateCard was called before the authorization was voided. Nevertheless, CreateCard returns INVALID_CARD_DATA on the payment ID.
Application ID: sq0idp-v8_NJqzh9rfsf2wIskNHjA
Payment ID: LtWPjintPTFfpauXPp2E20fyusTZY
Could Square please inspect this payment and determine why it is ineligible for card creation despite satisfying the documented payment-ID workflow?
@QFPA - Thanks for the additional details. We reviewed the recent attempts and confirmed this isn’t a card-field formatting issue. The card-storage verification was blocked by security controls, and several repeated attempts were also being throttled. We also found that the referenced payment had already been voided by the time of the recent attempts, and the customer associated with those requests did not match the payment’s customer. Please try again with a fresh buyer-present authorization associated with the same customer, then call CreateCard once while the authorization remains active. If that attempt fails, please provide its timestamp and request ID so we can trace that specific request.