> For the complete documentation index, see [llms.txt](https://docs.txn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.txn.io/payouts/validating-addresses.md).

# Validating addresses

<mark style="color:green;">`POST`</mark> `/api/public/v1/addresses/validate`

Validates a wallet address before you create a payout. The endpoint checks that the address is well-formed for the specified network and screens it against sanctions and high-risk wallet lists. A `200` response means the address passed both checks at the time of the call and can be used in a [Create Payout](https://docs.txn.io/payouts/creating-payout.md) request.

{% hint style="info" %}
This endpoint uses `Content-Type: application/json`, not `application/vnd.api+json`.
{% endhint %}

### What the format check does and does not cover

The format check confirms that the address is a syntactically valid address on the specified network. It does not confirm that the address was issued by the recipient's wallet or exchange for that network, and it cannot tell whether the recipient is actually watching that address.

Tron and EVM networks (Ethereum, BNB Smart Chain, Polygon) derive addresses from the same key material, so a `0x` Ethereum-style address can be re-encoded as a Tron address (`T...`). Since 6 October 2026 the format check rejects any Tron destination that is not a Base58 address with a valid checksum: a `0x` or `41` hex form submitted with a Tron network code returns `422 invalid_address` with the detail `Address is not in Tron (TRC20) format; expected a Base58 address starting with T`. The check cannot tell Ethereum, BNB Smart Chain and Polygon apart, because the same `0x` address is valid on all three, and a payout sent on the wrong one cannot be recalled by Txn.

{% hint style="danger" %}
Always submit the address exactly as shown in the recipient's wallet or exchange for the network you are paying out on. Never convert an address from one network's format to another, and check the prefix on your side before calling the API: a Tron address always starts with `T`, an EVM address always starts with `0x`. If the prefix does not match the network, or the recipient gave you the address for a different EVM network, ask them for the correct address instead of submitting it.
{% endhint %}

### Expected address format by network

Use this table to reject mismatched addresses in your own integration before you call the API. Sandbox network codes carry a `t` prefix (for example `ttrx:usdt`) but use the same formats.

<table><thead><tr><th width="220">Network</th><th width="260">Network codes</th><th>Expected format</th></tr></thead><tbody><tr><td>Tron</td><td><code>trx</code>, <code>trx:usdt</code></td><td>Base58, 34 characters, starts with <code>T</code>, with a valid checksum. <code>0x</code> and <code>41</code> hex forms are rejected.</td></tr><tr><td>Ethereum</td><td><code>eth</code>, <code>usdt</code>, <code>usdc</code>, <code>link</code>, <code>shib</code></td><td><code>0x</code> followed by 40 hexadecimal characters (42 characters total).</td></tr><tr><td>BNB Smart Chain</td><td><code>bsc</code>, <code>bsc:usdt</code></td><td><code>0x</code> followed by 40 hexadecimal characters.</td></tr><tr><td>Polygon</td><td><code>polygon</code>, <code>polygon:usdt</code>, <code>polygon:usdcv2</code></td><td><code>0x</code> followed by 40 hexadecimal characters.</td></tr><tr><td>Solana</td><td><code>sol</code>, <code>sol:usdt</code>, <code>sol:usdc</code></td><td>Base58, 32 to 44 characters.</td></tr><tr><td>XRP</td><td><code>xrp</code></td><td>Starts with <code>r</code>, 25 to 35 characters, followed by the destination tag as <code>?dt=tag</code>. See <a href="https://docs.txn.io/payouts/creating-payout.md#xrp-destination-tag">XRP destination tag</a>.</td></tr><tr><td>Bitcoin</td><td><code>btc</code></td><td>Starts with <code>1</code>, <code>3</code> or <code>bc1</code>.</td></tr><tr><td>Litecoin</td><td><code>ltc</code></td><td>Starts with <code>L</code>, <code>M</code> or <code>ltc1</code>.</td></tr><tr><td>Dogecoin</td><td><code>doge</code></td><td>Starts with <code>D</code>.</td></tr><tr><td>Bitcoin Cash</td><td><code>bch</code></td><td>CashAddr (<code>q...</code> or <code>bitcoincash:q...</code>) or legacy format starting with <code>1</code>.</td></tr><tr><td>Cardano</td><td><code>ada</code></td><td>Starts with <code>addr1</code>.</td></tr></tbody></table>

The same EVM address is valid on Ethereum, BNB Smart Chain and Polygon. The format check cannot tell these networks apart, so make sure the recipient gave you the address for the network in `network` and that their wallet supports receiving that asset on that network.

**Headers**

| Name          | Value              |
| ------------- | ------------------ |
| Content-Type  | `application/json` |
| Authorization | `Bearer <api_key>` |

**Request Body**

<table><thead><tr><th width="126">Name</th><th width="111">Type</th><th width="105">Required</th><th>Description</th></tr></thead><tbody><tr><td>address</td><td>string</td><td>Yes</td><td>Wallet address to validate.</td></tr><tr><td>network</td><td>string</td><td>Yes</td><td>Network code for the address. Use the same value you intend to pass as <code>payNetwork</code> in Create Payout. See <a href="https://docs.txn.io/api-basics/supported-currencies.md">Supported Currencies</a> or <a href="https://docs.txn.io/payouts/listing-payout-currency-pairs.md">Listing Payout Currency Pairs</a>.</td></tr></tbody></table>

**cURL**

```json
curl -X "POST" "https://api.sandbox.txn.io/api/public/v1/addresses/validate" \
     -H 'Content-Type: application/json' \
     -H 'Authorization: Bearer <api_key>' \
     -d '{
  "address": "TTbGTMwUwA3mncLP7xqCZei1ekaNSgeAJe",
  "network": "ttrx:usdt"
}'
```

**Response**

{% tabs %}
{% tab title="HTTP 200" %}

```json
{
  "data": {},
  "status": "ok",
  "jsonapi": {
    "version": "1.0"
  }
}
```

Address is well-formed for the network and not flagged by risk screening. It can be used in a Create Payout request. This does not confirm that the recipient's wallet or exchange issued the address for this network; see [What the format check does and does not cover](#what-the-format-check-does-and-does-not-cover).
{% endtab %}

{% tab title="HTTP 422" %}

```json
{
  "errors": [
    {
      "status": 422,
      "title": "Invalid address",
      "code": "invalid_address",
      "detail": "The address is not valid for the selected network",
      "source": {
        "pointer": "/data/attributes/address"
      }
    }
  ]
}
```

Address is not a valid address on the specified network: a malformed string, a failed checksum, or another network's format, such as a Bitcoin address submitted with `trx:usdt` or a `0x` address submitted with a Tron network code. For Tron networks `detail` reads `Address is not in Tron (TRC20) format; expected a Base58 address starting with T`. The same `0x` address is valid on every EVM network, so a mismatch between Ethereum, BNB Smart Chain and Polygon is not caught; see [What the format check does and does not cover](#what-the-format-check-does-and-does-not-cover).
{% endtab %}

{% tab title="HTTP 422" %}

```json
{
  "errors": [
    {
      "status": 422,
      "title": "We couldn't send funds to this address, please try another address",
      "code": "address_has_high_risk_score",
      "detail": "",
      "source": {
        "pointer": "/data/attributes/address"
      }
    }
  ]
}
```

Address failed risk screening. Do not proceed with a payout to this address.
{% endtab %}

{% tab title="HTTP 404" %}

```json
{
  "errors": [
    {
      "status": 404,
      "title": "Record not found",
      "code": "network_not_found",
      "detail": "Network not found"
    }
  ]
}
```

Network code not recognised. Check the value against [Supported Currencies](https://docs.txn.io/api-basics/supported-currencies.md) or [Listing Payout Currency Pairs](https://docs.txn.io/payouts/listing-payout-currency-pairs.md).
{% endtab %}
{% endtabs %}


---

# 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.txn.io/payouts/validating-addresses.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.
