Processing the decision
D1 processes the Tokenization request and evaluates available signals (including the data you provide) to make a decision on behalf of the Issuer.
Before you begin
To enable D1 to make a decision on behalf of the Issuer, make sure you:
Configure your decisioning preferences during D1 onboarding. For details, see Decision engine.
Provide high-quality, consistent data for:
The card
The End User (called
consumerin the D1 API)
Flow
Sequence diagram
Card verification behavior
D1 manages the Verify card step only if you provide the CVK used to validate the card’s CVV2/dCVV2 during D1 onboarding.
If you do not provide the CVK, D1 calls your issuer backend using the Verify card API and uses your response to determine card eligibility.
Depending on your configuration (this is the default behavior), if the card is not already registered in D1 using the Register card API, the flow fails before calling your issuer backend (for example, due to an unknown card).
End User (consumer) information behavior
To retrieve End User information, D1 follows one of the paths below, depending on how you registered the End User:
If
personalInformationis provided in the payload of the Register consumer API, D1 uses the information stored during registration.If
personalInformationis not provided, D1 calls the issuer backend to retrieve End User (consumer) information.
Decision outcomes
The decision returned by D1 through the Decision engine is aligned with payment network TSP protocols.
D1 can return one of the following outcomes:
GREEN (approve) Full approval of the Tokenization request. The End User does not need to complete additional authentication.
YELLOW (approve with step-up authentication) The Issuer must authenticate the End User using an ID&V method to complete Tokenization.
RED (decline) Tokenization is not approved and the payment network TSP stops the flow.
To understand what happens after each outcome, see Processing the response and the corresponding sections:
Last updated
Was this helpful?