These codes are possible values for the tokenization recommendation reason codes inside the tar_info object of the Auth API.
Mastercard codes
These codes are possible values for the tokenization_recommendation_reason_code_parsed field.
| Code | Reason |
|---|---|
| 01 | Wallet ID was created 40 days or fewer prior to launch. |
| 02 | Wallet ID was created 40 days or fewer prior to provisioning request. |
| 03 | Wallet ID/Card pair is fewer than 20 days old. |
| 04 | Changes have been made to the account settings for the wallet ID in prior 20 days. |
| 05 | Suspicious transactions linked to this account. |
| 06 | The account has not had activity in the last year. |
| 07 | Suspended cards in the secure element. |
| 08 | The phone was put in lost mode in the last 7 days for longer than the duration threshold (1 hour). |
| 09 | The number of provisioning attempts for this card on this device in 72 hours exceeds the threshold (3 attempts). |
| 0A | There have been more than the threshold number of different cards attempted at provisioning to this phone in 24 hours (5 different cards). |
| 0B | The card-provisioning request contains a distinct name in excess of the permitted threshold (2 distinct names). |
| 0C | Device score is less than 3. |
| 0D | Account score is less than 4. |
| 0E | Device-provisioning location outside of wallet ID home country. |
| 0F | Model rules not available at this time (in cases where backend systems time out). |
| 0G | Wallet algorithm identified high fraud risk. Wallet recommendation is DECLINE. |
| 0H | Phone number score is less than 3. |
Visa codes
These codes are possible values for the tokenization_recommendation_reason_code field for Visa transactions.
| Code | Reason |
|---|---|
| 01 | Cardholder’s wallet account is too new relative to launch. |
| 02 | Cardholder’s wallet account is too new relative to the provisioning request. |
| 03 | Cardholder’s wallet account card pair is newer than the date threshold. |
| 04 | Changes made to account data within the date threshold. |
| 05 | Suspicious transactions linked to this account. |
| 06 | Account has not had activity in the last year. |
| 07 | Suspended cards in the secure element. |
| 08 | Device was put in lost mode in the last 7 days for longer than the duration threshold. |
| 09 | The number of provisioning attempts on this device in 24 hours exceeds the threshold. |
| 0A | There have been more than the threshold number of different cards attempted at provisioning this phone in 24 hours. |
| 0B | The card-provisioning request contains a distinct name in excess of the permitted threshold. |
| 0C | The device score is less than 3. |
| 0D | The account score is less than 4. |
| 0E | Device-provisioning location outside of the cardholder’s wallet-account home country. |
| 0G | Suspected fraud. |
| 0H | Phone score is less than 3. |
| AG | Issuer preferred to defer ID and decision to token-creation time. |
| AH | Issuer-encrypted payment-instrument data has expired. |
| AI | User/device that was intended to receive the encrypted payment instrument data is different from the one that is provisioning the token. |
| AL | Sending and receiving devices are different. Passcode was included in the issuer's encrypted payment-instrument data, then it matched the user-provided value. |
| AM | Pushing to a different user than the cardholder. Passcode was included in the issuer's encrypted payment instrument data, then matched the user-provided value. |
| AN | Sending and receiving devices are the same but without up-front authentication or passcode verification. |
| AO | Sending and receiving devices are the same but unsuccessful up-front authentication passcode verification. |