Processing the response

After D1’s decision engine evaluates a Tokenization request, D1 returns a decision to the payment network TSP (for example, MDES or VTS). The TSP then completes the Tokenization flow with the token requestor and, when applicable, provisions and activates the digital card.

Avoid TSP decision overrides

Some payment networks can be configured to override the Issuer Tokenization decision at the TSP level. Thales does not recommend this because it can cause D1 and the payment network TSP to get out of sync.

Decision outcomes

D1 can return one of the following outcomes:

• GREEN (approve) The Tokenization request is approved and no additional End User authentication is required.
• YELLOW (approve with step-up authentication) The Tokenization request is conditionally approved. The End User must complete an additional authentication step (an ID&V method) before the digital card can be activated.
• RED (decline) The Tokenization request is declined and the payment network TSP stops the flow.

Each outcome has specific implications for the digital card state and the End User experience.

Notifications

During and after Tokenization, D1 can generate notifications that you manage in your issuer backend. Optionally, D1 can also send informational notifications to the End User.

TSP notification delays

The TSP might delay sending notifications. These delays are outside D1’s control.

Notifications to the issuer backend

D1 notifies your issuer backend of Tokenization outcomes and life cycle events (depending on what you enable during D1 onboarding).

For the APIs involved, see:

• API summary

End User notifications

End User notifications are informational messages sent by SMS or email (when enabled). D1 can send these notifications on behalf of the Issuer in the following cases:

• Approval with no conditions
• Approve with step-up authentication
• Tokenization cancelled
• Card replacement and card renewal
• Digital card deletion

For configuration options and message templates, see End User notifications.

• If the Issuer sends OTP by SMS/email (instead of D1), D1 does not send End User notifications.
• If End User notifications are enabled, D1 may call your issuer backend to retrieve the latest End User contact information using Get consumer information API.