Retrieve tokenization data

Retrieve tokenization data

Use these APIs after D1 notifies your issuer backend of a Tokenization event.

Start from the operationId included in the notification.

Then retrieve the digitalCardId and, if needed, digital card details and credentials.

Retrieve operation details

Call Get operation with the operationId.

This returns the processed operation and, when available, the digitalCardId.

Retrieve operation details and, when available, the digitalCardId

Use the digitalCardId

The operation response includes the digitalCardId when the payment network TSP created (or is creating) the digital card.

If the operation status is SUCCESSFUL or PENDING:

• Retrieve non-sensitive data with Get digital card information.
• Retrieve sensitive credentials with Get digital card credentials.

Digital card credentials are encrypted with your issuer encryption certificate provided during D1 onboarding.

Decrypt them in your issuer backend.

Store only what you need.

Search a digital card

Use this flow when you do not have digitalCardId.

You can start from the digital card PAN (DPAN) observed in authorization traffic.

Common use cases:

• Link a digital card to an End User, funding card (FPAN), or device.
• Investigate fraud signals raised by your authorization host.

1. Call Search digital card to resolve the DPAN to a digitalCardId.
2. Optionally, call Get digital card information to retrieve details for that digitalCardId.

Pass the digital card PAN (DPAN).

You typically receive it in authorization requests from the Acquirer via the payment network.

Search a digital card by DPAN and optionally fetch digital card details