Step 4 – approve the digitization request

Approve (or reject) the digitization request. Return the step-up authentication options when needed.

What happens in this step

The TSH backend asks the issuer backend to approve Tokenization for a card.

The request includes signals to support your decision:

• Device information (not provided for e-commerce)

• Scoring information

You return one of these decisions:

• green: Approve without step-up authentication.

• yellow: Approve with step-up authentication. Return an ID&V method list.

• red: Decline Tokenization.

Digitization approval flow.

See requestCardDigitization in the API reference.

Request parameters

Parameter	Required	Description
x-correlation-id	Required	Correlates the enrollment session. Use the same value received in requestCardEligibility (step 2).
cipheredCardInfo	Required	Same value received in requestCardEligibility (step 2).
authenticationValue	Optional	Contains CVV2 when provided by the token requestor. Encrypt it with cipheredCardInfo using the issuer public key (PKCS#7). In practice, token requestors provide it when the end user entered card details manually or captured them from a photo.

Response parameters

Parameter	Required	Description
levelOfTrust	Required on success	Decision for this digitization request: green, yellow, or red.
idvMethodList	Conditional	Return only when levelOfTrust is yellow. The list defines the available ID&V methods for step-up authentication.

Decisioning guidance

• Use the device and scoring signals to select green, yellow, or red.

• When returning yellow, include only the step-up methods you can support end-to-end.

• Stop the enrollment flow when returning red. Show a decline message to the end user.

Next step

Continue to Step 5 – activate the token.

If you returned yellow, the end user completes step-up authentication using one of these paths:

• Option B: activate with SMS or email OTP

• Option C – activate in the issuer application

• Option D – activate via customer service