D1 API summary

Overview

This page provides a checklist of the D1 API endpoints typically required to integrate 3DS.

Direction indicates who calls the endpoint:

• Inbound: your issuer backend calls the D1 API.

• Outbound: the D1 backend calls your issuer backend.

Required APIs

API	Inbound/Outbound	Description
Get authorization token	Issuer -> Thales D1	Get an OAuth 2.0 access token to call the D1 backend.
Order card	Issuer -> Thales D1	Order a physical card
Order cards	Issuer -> Thales D1	Order several physical cards

Optional APIs

API	Inbound/Outbound	Description
Register card	Issuer -> Thales D1	Register a card with corresponding cards credentials.
Card order status notifications	Issuer <- Thales D1	Receive card order status real time
Get card order status	Issuer -> Thales D1	Get the status of a card order
Pull & Change	Issuer -> Thales D1	Pull a card and request to apply a change
Track card	Issuer -> Thales D1	Request to track the shipment of a card