BitSettleA Bitcoin Lawyer service

Sources and verification

Know what the evidence proves.

A source can confirm an asset identifier or explain a protocol. Confirming that a merchant can accept a payment requires evidence from the actual setup.
On this page

Asset and protocol sources

Verify the payment method

Bitcoin on-chain

Match the receiving address and amount, inspect the transaction with your node or an explorer, and apply the agreed confirmation policy. Check the invoice record before fulfilment.

Lightning

Verify the invoice and payment hash against the connected wallet or node and the recorded invoice state. An individual Lightning payment is not an on-chain transaction you can verify in a Bitcoin block explorer.

Token payments

Match the network, exact contract or mint, destination, and amount in the correct decimal precision. Then confirm the required network evidence and invoice reconciliation. An explorer label alone does not establish the asset’s issuer or bridge dependencies.

Contract and mint reference

The entries below retain the project’s reference configurations. An address check is not a deployment test or an assurance of availability. Polygon, Arbitrum One, and BNB Smart Chain need a separate provenance review before activation.

These are token identifiers, not payment destinations. Use the receiving details on the correct invoice.

TRON

TRC-20 · 6 decimals

Exact address listed in Tether issuer registry

TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t
Issuer address reference checked 26 October 2026; deployment not verifiedView on explorer for TRON (opens in a new tab)

Ethereum

ERC-20 · 6 decimals

Exact address listed in Tether issuer registry

0xdAC17F958D2ee523a2206206994597C13D831ec7
Issuer address reference checked 26 October 2026; deployment not verifiedView on explorer for Ethereum (opens in a new tab)

Polygon

ERC-20 · 6 decimals

Issuer and bridge provenance requires review

0xc2132D05D31c914a87C6611C10748AEb04B58e8F
Legacy reference; do not enable without asset and deployment checksView on explorer for Polygon (opens in a new tab)

Arbitrum One

ERC-20 · 6 decimals

Issuer and bridge provenance requires review

0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9
Legacy reference; do not enable without asset and deployment checksView on explorer for Arbitrum One (opens in a new tab)

BNB Smart Chain

BEP-20 · 18 decimals

Issuer and bridge provenance requires review

0x55d398326f99059fF775485246999027B3197955
Legacy reference; do not enable without asset and deployment checksView on explorer for BNB Smart Chain (opens in a new tab)

Avalanche C-Chain

ERC-20 · 6 decimals

Exact address listed in Tether issuer registry

0x9702230A8Ea53601f5cD2dc00fDBC13d4dF4A8c7
Issuer address reference checked 26 October 2026; deployment not verifiedView on explorer for Avalanche C-Chain (opens in a new tab)

Solana

SPL Token · 6 decimals

Exact address listed in Tether issuer registry

Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB
Issuer address reference checked 26 October 2026; deployment not verifiedView on explorer for Solana (opens in a new tab)

Confirm your deployment

  1. Confirm that the software supports the selected configuration.
  2. Confirm that the method is enabled with the intended asset and wallet controls.
  3. Record the result of an authorized test invoice, including failures and reconciliation.
  4. Confirm merchant availability and operating responsibilities in the agreed scope.

Use the onboarding checklist to agree those steps. The technical reference explains the configuration and its limits.