At each step of the Tokenization process, information will be sent between the Network and CLOWD9.

Following the outcome, CLOWD9 will send you the event notification. These messages can be used to provide support to your Customers, especially in the event of an unsuccessful outcome, preventing their card from being Tokenized.

As a result of the Customer requesting their PAN and associated card_id to be tokenized either via your App or the Wallet Provider, the following event notifications will be received:

Tokenization Initiation

Following the request from the Network, CLOWD9 will validate the PAN is held on our platform and the status.

Providing the card is valid and in an active status, CLOWD9 will provide a succesful response to the Network. In turn, the Network will return the associated card art, Terms & Conditions together with required data to the Wallet Provider.

The outcome message you will receive is detailed herehttps://docs.clowd9.com/docs/tokenization-initiation

VCMM has to be configured within Visa before this step can take place.

Approve Provisioning

Following the Tokenization Initiation and the acceptance of the Terms and Conditions by the Customer, the Network will request approval from CLOWD9.

Using the risk criteria configured at Product level, one of the three reason codes will be returned to the Network:

• Approved (reason code 00): This will result in the token creation in an inactive status via the Network, known as the Green Flow. Further verification is not required and the next step will be Token Activation

• No Reason to Decline (response code 085): The Network will progressing with the token creation in an inactive status; however further Customer Verification will be required. This is known as the Yellow Flow and will require Cardholder Verification methods to be provided as per the next step

• Declined (response code will depend on the reason for the Decline): As a result of the decline, the Customer will not be able to tokenize their card. They will be required to re-start the process

Cardholder Verification Methods

Where CLOWD9 have responded to the Approve Provisioning with No Reason to Decline (085), the Network will request the Card Verification Methods, also known as Step-up Authentication.

CLOWD9 will return one or more of the following Method(s) based on your configuration to the Network. The Method(s) will be displayed to your Customer who will be required to chose how to complete the Verification:

• One Time Passcode generated by the Network. CLOWD9 will transmit this you via a configured endpoint to communicate to the Cardholder via SMS or Email
• In-app notification, also known as a push notification whereby the requestor authenticates via their mobile application
• Customer Services whereby the Cardholder calls direct to your Customer Services and verifies their identify

Where the Authentication method is In-app Notification or Customer Services, the DPAN status is changed to Active either by API or Vista.

Token Activation

The Network will provide confirmation the token activation has been successful either as a result of the Green Flow or following succesful Customer (Cardholder) verification.

The token is now active and ready for use via the Wallet Provider and token lifecycle management will now apply.