Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Card life cycle

Using the D1 API, your issuer backend can suspend, resume, and delete cards (see API summary for details).

Suspending or resuming a card does not affect related digital cards. For example, an End User can keep using digital cards after you suspend a lost card.

Deleting a card deletes all related digital cards.

Card replacement

Replace cards when they are lost or stolen.

To trigger a replacement, call Replace card.

D1 notifies the payment network TSP to keep existing digital cards linked to the replaced card.

Flow overview:

Card replacement: D1 updates the payment network TSP and the Token requestor

Card renewal

Cards are renewed when they expire. For cards created by D1, D1 triggers renewal automatically. Your issuer backend can also trigger renewal using Renew card.

Note:

For cards registered in D1, your issuer backend must notify D1 by calling Renew card.

D1 notifies the payment network TSP so existing digital cards keep working after renewal.

This uses the same flow as card replacement.

End User notifications (optional)

D1 can also send notifications to the End User for some renewal scenarios. This is optional. See End User notifications.

Last updated

Was this helpful?