Red Path for third-party wallet
Conditions
| Type | Value |
|---|---|
| Token service provider | Visa Token Service |
| Issuer decision | Red path as DECLINED |
| Check eligibility (Visa specific) | Issuer behalf |
| Token type | Belongs to third-party wallet as CLOUD or EMBEDDED_SE |
| Provisioning type | Manual Provisioning |
Sequence diagram
Sequence steps description
| Step | Description |
|---|---|
| 1 | Consumer initiate digitization as manual provisioning from third-party wallet |
| 2 | Wallet as Token Requestor check if card is eligible for digitization |
| 3 | 3.1. MTP I-TSP receive digitization eligibility request from Visa Token Service. 3.2. MTP I-TSP passthrough digization eligibility request to the issuer according to the configuration. |
| 4 | Issuer validate if card is eligible for digitization |
| 5 | Issuer response contains confirmation for card digitization eligibility and provide product identifier to the Visa Token Service |
| 6 | 6.1. Visa Token Service return T&C to the wallet according to the product identifier. 6.2. Wallet display T&C to the consumer. |
| 7 | Consumer review and accept T&C. |
| 8 | Wallet as Token Requestor send digitization request to the Visa Token Service |
| 9 | 9.1. Visa Token Service send token authentication request to MTP I-TSP. 9.2. MTP I-TSP passthrough token authentication request to the issuer as Authorize Service request. |
| 10 | Issuer review token authentication request and DECLINE provisioning due to the security checks failure. |
| 11 | Issuer send token authentication response to the Visa Token Service through MTP I-TSP. |
| 12 | Visa Token Service delete previously generated token. |
| 13 | 13.1. Visa Token Service notify wallet about digitization failure. 13.2. Wallet notify consumer about digitization failure. |