Create device binding
Mastercard Token Authentication Framework (TAF) starts with device binding.
Prerequisites:
The card has already completed tokenization. The merchant already has a
srcDigitalTokenIdfrom the Thales backend.The device supports device authentication, such as fingerprint or Face ID.
Before binding the token to the device, the issuer backend authenticates the end user (ID&V). The issuer backend sends an OTP to the end user. The end user enters the OTP in the merchant application.
The merchant application triggers the create binding flow

1-2
The end user (through the merchant application) triggers the ID&V flow by calling the Thales SDK with tokenId and a fresh correlationId (for troubleshooting).
3-7
The Thales SDK calls the Thales backend, which reaches Mastercard to retrieve the available ID&V methods.
8-9
The merchant application displays the available ID&V methods and asks the end user to select one. The options are SMS or email.
You can retrieve the list of ID&V methods from the IDVSession object.
Use the IDVSession object to call getIdvMethods to get the list of supported ID&V methods.
Use the IDVSession object to call idvMethods to get the list of supported ID&V methods.
End user selection and OTP sending

1-2
The end user selects an ID&V method. The merchant application provides the selection to the Thales SDK.
3-7
The Thales SDK calls the Thales backend, which reaches Mastercard, to generate an OTP. The issuer backend then sends the OTP to the end user through the selected channel.
The SDK returns the binding activation result through onSuccess or onIssuerAuthenticationError. If activation fails, keep the IDVSession instance returned in onIssuerAuthenticationError. Use it to retry the ID&V flow.
OTP verification

1-2
The end user enters the OTP in the merchant application, which sends it to the Thales SDK.
3-7
The SDK securely conveys the OTP to Mastercard for verification, then returns the result to the merchant application.
Last updated
Was this helpful?