Production CreateCard fails with INVALID_CARD_DATA on source_id (Web Payments token)

Hi,

we need help with a production card-on-file issue.

Setup

  • Environment: Production
  • Web Payments SDK + Cards API (CreateCard)
  • App ID: sq0idp-...
  • Location ID: LACA9AZM...
  • source_id token format: cnon:...
  • verification_token: present

Problem

CreateCard fails consistently with:

  • category=INVALID_REQUEST_ERROR
  • code=INVALID_CARD_DATA
  • field=source_id

What we already verified

  • App ID in rendered form matches configured app ID.
  • Access token/location/app are from same production setup.
  • Connection check to location succeeds (ACTIVE).
  • We tested docs-correct CreateCard flow with minimal payload:
    • source_id
    • card.customer_id
    • optional verification_token
  • Still same error.

Question

Can Square check backend/account capability for this merchant/location and explain why valid production cnon token is rejected for card-on-file save?
Also please confirm whether any account/location-side enablement or policy restriction is blocking this flow.

Thanks.

If you are creating a card on file, remember to put in the Payment ID as the source_id in the request, not the payment token generated from the WPSDK. See details here: Create a Card on File from a Payment ID .

If that still leads to errors, there may be a few reasons that include risk rules and card issuers denying the storage of the card. Be sure to check these:

  • billing_address.postal_code in the CreateCard request must match the postal code entered when the card was tokenized. A mismatch returns exactly this error on source_id.
  • The buyer verification (3DS) behind verification_token has to be completed.
  • Repeated save attempts on the same card in a short window can trip an abuse-prevention rule. It lapses after a while, and the retry needs a fresh tokenization from the customer.
  • Try a different card from a different issuer to rule out an issuer-side decline.

If it still fails, reply with the idempotency key and timestamp of the failed request.

Thank you!

I followed the production-location and credential checks. The production Application ID, access token, and location ID all belong to the same application and merchant. A fresh form submission generated a new cnon: token, buyer verification completed, and the exact billing postal/address data was included.

The request still fails at POST /v2/cards with INVALID_CARD_DATA on source_id. Sandbox succeeds. Location: LACA9AZMZ22AS. Production Application ID: sq0idp-fZr...X7Q. Reference: c9ba2eaa3f68. No square_request_id was returned.

Because the connection check also succeeds for the correct active production location, can you inspect whether Square risk controls, seller configuration, card geography, or this production token are preventing card-on-file creation?

I’m testing this from Slovenia with a Slovenian CC (Visa and MaterCard) for a US Client…