> 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/central-issuance/implement-central-issuance/address-validation.md).

# Address validation

The **Address validation** service checks the delivery address of each card before production. Its goal is simple: reduce the number of cards returned because of an undeliverable address.

* Valid address → the card is produced and shipped.
* Invalid address → the card order is rejected, and you are notified so you can correct the address and reorder.

{% hint style="info" %}
The validation is performed automatically during the order flow. No additional API call is required from issuer backend.
{% endhint %}

### How it works

<figure><img src="/files/U38VfYPWBY6KzED27tCY" alt=""><figcaption></figcaption></figure>

1. Issuer backend submit a card order, including the end user's delivery address.
2. D1 acknowledges the order (HTTP 202), address validation is done later.
3. D1 validates inputs (format, length, allowed characters).
4. D1 submits the address to the validation service
5. D1 evaluates the response against the thresholds from issuer configuration.
6. Outcome:
   1. Valid → the card moves to production; a notification is sent.
   2. Invalid → the card is rejected; a notification is sent with the reason (and optionally a suggested corrected address).
7. Issuer order again the card with a corrected address if needed.

### Choosing validation mode

One mode is selected at onboarding. It applies to all card orders.

<table><thead><tr><th width="120.199951171875">Mode</th><th>What happens</th><th>When to use it</th></tr></thead><tbody><tr><td><strong>disabled</strong></td><td>No validation. All cards go to production.</td><td>You don't want the service.</td></tr><tr><td><strong>statistics</strong></td><td>Validation is performed, but the card is <strong>always produced</strong>. </td><td>To measure the impact before turning on enforcement.</td></tr><tr><td><strong>enabled</strong></td><td>Validation is performed. Invalid addresses are <strong>rejected</strong>.</td><td>Standard production use.</td></tr><tr><td><strong>premium</strong></td><td>Same as <em>enabled</em>, plus a <strong>suggested corrected address</strong> is returned when available.</td><td>You want help fixing rejected addresses.</td></tr></tbody></table>

### What you need to configure

Only a few parameters matter for you:

<table><thead><tr><th>Parameter</th><th>Description</th><th width="146">Recommended</th></tr></thead><tbody><tr><td>addressValidation</td><td>Mode: disabled / statistics / enabled / premium</td><td>enabled</td></tr><tr><td>addressValidationMatchScoreThreshold</td><td>Minimum quality score (0–100). Below this, the address is rejected.</td><td>95</td></tr><tr><td>addressValidationOnReorder</td><td>If true, the address is re-validated when you reorder a previously rejected card. If false, the reorder skips validation.</td><td>false</td></tr><tr><td>addressValidationOutageFallback</td><td>What to do if the validation service is temporarily unavailable: produce (accept the card) or reject (refuse the card).</td><td>produce</td></tr></tbody></table>

{% hint style="info" %}
All other technical parameters (provider, retry strategy, postal-code thresholds, etc.) are managed internally and don't require any action from you.
{% endhint %}

### Notifications you will receive

#### Address valid – card goes to production

```json
{
  "operation": "PRODUCE",
  "status": "PENDING",
  "details": {
    "status": "CARD_PROD_REQUESTED",
    "addressValidation": {
      "status": "valid",
      "matchScore": 95
    }
  }
}
```

#### Address invalid – card rejected

```json
{
  "operation": "PRODUCE",
  "status": "FAILED",
  "errorCode": "INVALID_ADDRESS",
  "details": {
    "status": "DATA_EXCEPTION",
    "addressValidation": {
      "status": "invalid",
      "matchScore": 55
    }
  }
}
```

#### Address invalid – with a suggested correction (premium mode)

```json
{
  "operation": "PRODUCE",
  "status": "FAILED",
  "errorCode": "INVALID_ADDRESS",
  "details": {
    "status": "DATA_EXCEPTION",
    "addressValidation": {
      "status": "invalid",
      "matchScore": 55,
      "suggestedAddress": {
        "line1": "221B Baker Street",
        "line2": "Flat 2",
        "city": "London",
        "postalCode": "NW1 6XE",
        "countryCode": "GB"
      }
    }
  }
}
```

### What happens when a card is rejected?

1. You receive a PRODUCE / FAILED notification with errorCode = INVALID\_ADDRESS.
2. In **premium** mode, a corrected address may be suggested.
3. You **correct the address** and **reorder** the card.

### Service availability & reliability

* The validator is called in real time for every card order.
* If the provider is temporarily unreachable, the service retries automatically.
* After all retries, the configured **fallback** (produce or reject) is applied.
* Country coverage and accuracy depend on Loqate's reference data — see [Loqate country coverage](https://docs.loqate.com/data-coverage/introduction).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/central-issuance/implement-central-issuance/address-validation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.