D1 API summary
Use this checklist to validate the D1 API endpoints you need to integrate 3DS.
Required APIs
Issuer <- Thales D1
Receive 3DS operation notifications, such as frictionless or challenge outcomes.
Conditional APIs
Use the APIs below depending on which authentication flows you enable.
Support SMS OTP challenges
Issuer <- Thales D1
Provide end user details used for OTP delivery, such as phone number.
Issuer <- Thales D1
Receive an OTP from the D1 backend so the issuer backend can deliver it to the end user (issuer-managed SMS only).
Support OOB enrollment
Issuer -> Thales D1
Delete authentication credentials for an issuer application instance (OOB only).
Issuer <- Thales D1
Receive notifications about end user operations, such as authenticator enrollment.
Support OOB flow with issuer authentication (SCA)
Issuer <- Thales D1
Trigger step-up authentication in the issuer application and return a correlation reference.
Issuer <- Thales D1
Provide the final result of step-up authentication to the D1 backend.
Optional APIs
Use the APIs below depending on which authentication flows you enable.
Secure outbound calls with OAuth 2.0
Issuer <- Thales D1
Provide an OAuth 2.0 access token for D1 outbound calls to the issuer backend.
Retrieve 3DS operation history
Issuer -> Thales D1
Retrieve 3DS operations for a card (single operation or list).
Last updated
Was this helpful?