Skip to main content
When the customer has completed filling in their card info, the return_url and callback_url will receive a request. When you get this request, the payment token will be stored on the transaction. Use get transaction details to retrieve the transaction, with the query-param includes to include the cards tokens example:
  • ?includes=card.payment_token
  • ?includes=card.recurrence_token
The token will then be included in the card details, e.g. card.payment_token. The card data contains expiry_date (format MM/YYYY). When tokenization is used, card.expiry_date will be the expiration date of the card itself if available. If the card’s expiration date is unavailable, card.expiry_date will fall back to the token’s expiration date.
Store the token internally in a secure manner.

​
Fetching a card token

You can look up a stored token directly with get card token, which returns the token’s current status and card details without needing to go through a transaction.

​
Token status

A card token has one of the following statuses:

​
Attempting payment with a token

A newly created token isn’t synced immediately, so get card token can return a 404 for a token that was just created even though the token itself is valid.

​
External references for imported tokens

When importing cards from another PSP/acquirer, we store the reference you used there as an external token reference. You can use this reference the same way you’d use a Dintero-issued token:
  • Pass it as token_id to get card token to look up the token using the old PSP’s reference.
  • Pass it as the payment_token or recurrence_token value when creating a payment, instead of the Dintero-issued token — see use a stored card token.
Note that if the same card appeared multiple times in the imported cards, these will refer to a single payment token within our system. It is also recommended to switch to using the token’s actual ID and payment token values instead of the old reference.
Last modified on July 14, 2026