D1 API summary

Overview

This page provides a checklist of the D1 API endpoints typically required to integrate Transaction Control.

Direction indicates who calls the endpoint:

• Issuer backend → D1 backend: your issuer backend calls the D1 API.
• D1 backend → issuer backend: the D1 backend calls your issuer backend.

Required APIs

​Get authorization token​	Issuer backend → D1 backend	Get an OAuth 2.0 access token to call the D1 backend.
​Create card or Register card​	Issuer backend → D1 backend	Create or register a card in the D1 backend.
​Renew card​	Issuer backend → D1 backend	Renew a card.
​Replace card​	Issuer backend → D1 backend	Replace a card.
​Delete card​	Issuer backend → D1 backend	Delete a card from the D1 backend.
​Notify 3DS card operation​	D1 backend → issuer backend	Receive 3DS operation notifications (for example, frictionless or challenge outcomes).