Step 3 – present terms and conditions

Present the terms and conditions to the end user. Capture their consent before Tokenization.

What happens in this step

The token requestor presents the terms and conditions.

The payment network TSP provides them (for example, VTS or MDES).

The end user reviews and accepts them in the wallet application or issuer application.

Who does what

• Token requestor

  • Display the terms and conditions to the end user.
  • Capture an explicit accept/decline action.
  • Stop the enrollment flow if the end user declines.
• Issuer backend

  • Ensure the right configuration is used in step 2 (for example, by returning productId).
  • Do not approve the digitization request until consent is captured.

Implementation notes

• The token requestor defines the rendering rules.
• The payment network TSP defines the content format.
• Treat consent as a required precondition for the digitization approval step.

Next step

After consent is captured, continue to Step 4 – approve the digitization request.