Can't save a debit card after an in-person payment (INVALID_CARD_DATA)

Questions
1

Can’t save a debit card after an in-person payment (INVALID_CARD_DATA)

We’re getting INVALID_CARD_DATA on CreateCard with a buyer-present payment and would appreciate a look.

Flow: Mobile Payments SDK on an iPad + Square Stand takes a delayed-capture payment (autocomplete: false). About 6 seconds later, while the payment is still APPROVED, we call POST /v2/cards with the payment ID as source_id to save the card for a subscription.

Response:
{“category”:“INVALID_REQUEST_ERROR”,“code”:“INVALID_CARD_DATA”,“detail”:“Invalid card data.”,“field”:“source_id”}

Example payment: aGNGfM6Xc7ga8wXBaD5bFcpVyaaZY

  • CreateCard called at 2026-10-11 17:54:52 UTC
  • Card: Mastercard DEBIT, not prepaid, entry_method CONTACTLESS
  • application_name “US DEBIT”, application_identifier A0000000042203
  • The payment had no customer_id attached. We saved the card to an existing customer found by email.

Every failure we’ve seen is a debit card read through the US Common Debit AID (5 attempts, including one chip insert). Credit cards with the same flow always succeed.

Questions:

  1. Was this blocked by card-storage security controls, or by throttling from the donor’s earlier attempts (same card on Oct 5)?
  2. Would attaching the customer to the payment (PaymentParameters.customerID) before the tap fix this? We’re making that change now.
  3. Can a card be saved from a payment processed through the US Common Debit AID at all?

Application ID: sq0idp-kt-6g2MHFsJB4J8uT5P-Fw