Skip to main content
The example values are placeholders. Obtain a real token from Request checkout token or Get payment card. Send the complete token in the JSON body using the same agent bearer key. Never include it in a URL or query string. The body must contain only checkout_token, use Content-Type: application/json, and be at most 4 KB.

​
Successful response

A 200 response contains a card_checkout_details resource in data, identified by the assigned card’s ID:
This response contains actual payment-card details. Handle it only in a trusted checkout client. Do not return it to a language model, print it to logs, send it to analytics, or persist it in browser storage. It is private and not cached.
The response does not authorize a purchase or guarantee that a merchant accepts the card. The owner may need to enter CVC directly at the merchant or complete bank authentication. Credential retrieval itself makes no charge.

​
Token lifecycle and access changes

Tokens expire within 60 seconds and are consumed atomically once. The database stores token hashes, not reusable plaintext tokens. A second redemption fails, including after a lost response or a downstream failure; request a new token when appropriate. Redemption verifies the current agent key, active status, linked-card binding, ciphertext snapshot, and Transfer access. Revoking or replacing a key, pausing an agent, disabling access, or removing or replacing its card blocks outstanding-token redemption. Another agent’s key cannot redeem the token. After the actual card details have been returned, Transfer cannot recall a client’s copy or restrict where it is entered. Freeze or replace the bank card to stop bank-side spending. Local sandbox mode permits only public test cards; live storage requires an approved deployment following security and PCI review. See Errors and rate limits for failure handling. This endpoint has no simulation-card redemption flow.