> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-decision/decision-engine/data-validation-codes/verification-codes.md).

# Verification codes

## Verification codes

Verification codes describe the checks D1 performs on data provided by the token requestor and the Issuer.

### Code groups

D1 groups verification codes into the following categories:

* **Token requestor**: checks data provided by the token requestor.
* **End user name**: checks the end user name against the cardholder name.
* **End user billing address**: checks the billing address provided by the wallet against the billing address provided by the Issuer.
* **End user phone number**: checks the phone number provided by the wallet against the phone number provided by the Issuer.
* **End user language**: checks the language provided by the wallet against the language provided by the Issuer.
* **End user localization**: checks the localization provided by the wallet, including coordinates and IP address, against localization data derived from the billing address provided by the Issuer.

The following table lists all verification codes.

### Code structure

A verification code uses a prefix to identify the data source:

* `TR_`: the data is provided by the token requestor.
* `ISS_`: the data is provided by the Issuer.
* No prefix: D1 compares data provided by both the token requestor and the Issuer.

A verification code uses a suffix to identify the result:

* `UNAVAILABLE`: the data is not available.
* `MATCH`: both values are provided and match.
* `NO_MATCH`: both values are provided and do not match.
* `PARTIAL_MATCH`: both values are provided and only part of the data matches.
* `INVALID`: the data is available, but its format is invalid.

<table><thead><tr><th width="436.272705078125">Verification code</th><th width="302.4544677734375">Category</th></tr></thead><tbody><tr><td><p>TR_RECOMMENDATION-UNAVAILABLE</p><p>TR_DEVICE_SCORE-UNAVAILABLE</p><p>TR_ACCOUNT_SCORE-UNAVAILABLE</p></td><td>Token requestor</td></tr><tr><td><p>NAME-MATCH</p><p>NAME-NO_MATCH</p><p>NAME-PARTIAL_MATCH</p><p>TR_NAME-UNAVAILABLE</p></td><td>End user name</td></tr><tr><td><p>ADDRESS-MATCH</p><p>ADDRESS-NO_MATCH</p><p>ADDRESS-PARTIAL_MATCH</p><p>ADDRESS_LINE1-NO_MATCH</p><p>ADDRESS_LINE2-NO_MATCH</p><p>ADDRESS_ZIPCODE-NO_MATCH</p><p>ADDRESS_COUNTRYCODE-NO_MATCH</p><p>TR_ADDRESS-UNAVAILABLE</p><p>TR_ADDRESS-INVALID</p><p>ISS_ADDRESS-UNAVAILABLE</p><p>ISS_ADDRESS-INVALID</p></td><td>End user billing address</td></tr><tr><td><p>PHONE_NUMBER-PARTIAL_MATCH</p><p>PHONE_NUMBER-MATCH</p><p>PHONE_NUMBER-NO_MATCH</p><p>TR_PHONE_NUMBER-UNAVAILABLE</p><p>TR_PHONE_NUMBER-INVALID</p><p>ISS_PHONE_NUMBER-UNAVAILABLE</p><p>ISS_PHONE_NUMBER-INVALID</p></td><td>End user phone number</td></tr><tr><td><p>LANGUAGE-MATCH</p><p>LANGUAGE-NO_MATCH</p><p>TR_LANGUAGE-UNAVAILABLE</p><p>TR_LANGUAGE-INVALID</p><p>ISS_LANGUAGE-UNAVAILABLE</p><p>ISS_LANGUAGE-INVALID</p></td><td>End user language</td></tr><tr><td><p>LOCALIZATION-MATCH</p><p>LOCALIZATION-NO_MATCH</p><p>LOCALIZATION-PARTIAL_MATCH</p><p>TR_LOCALIZATION-UNAVAILABLE</p><p>TR_LOCALIZATION-INVALID</p><p>ISS_LOCALIZATION-UNAVAILABLE</p><p>ISS_LOCALIZATION-INVALID</p><p>TR_IPADDRESS-UNAVAILABLE</p><p>TR_IPADDRESS-INVALID</p></td><td>End user localization</td></tr></tbody></table>

{% hint style="warning" %}
The quality of the verifications depends on the data made available by both the wallet and the Issuer.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-decision/decision-engine/data-validation-codes/verification-codes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.