Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
⌘Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Register cards via API
Card registration is a backend-to-backend flow between your issuer backend and the D1 backend.
You can run it at any time before the card is used in a D1 service.
You can also combine card registration with card creation for the same end user.
As part of registration, your issuer backend provides:
cardId: A unique technical identifier used in the D1 API and D1 SDK. It must not be the PAN or derived from the PAN.
cardProductId: The identifier of the card product.
PAN and expiry date: Encrypted using JWE.
consumerId: Your issuer backend identifier for the end user who owns the card.
If the end user is not registered in D1, D1 can implicitly register the end user from the provided consumerId. When D1 needs personal information, it calls your issuer backend using Get consumer information.
Unlike card creation, card registration does not require an account list.
Sequence diagram
Card registration flow between the issuer backend and the D1 backend.
After registration, you can use the card across other D1 services, for example:
