BitSettlea Bitcitizen company

For developers & self-hosters

The technical track behind the managed service.

BitSettle is a fully managed payment service, but it runs on an open BTCPay Server plugin you can read, host, and verify yourself. This is the reference for that layer: install, the nine networks, the adapter model, canonical USDT assets, watch-only address modes, payment links, and the risk boundaries we name out loud.

Not technical? We host and configure everything for you →

Canonical assets

Nine rails, one dollar, matched by contract, never symbol.

Native Bitcoin and Lightning run on BTCPay's own rails. The seven USDT networks below are receive-only, each pinned to an exact token contract or mint and a fixed decimal precision.

Bitcoin

Native rail

The original. Settles natively.

Lightning

Native rail

Bitcoin in about a second.

TRON

USDT-TRON

StandardTRC-20
Contract / mintTR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t
Decimals6
ConfirmationChain API confirmations

Ethereum

USDT-ETHEREUM

StandardERC-20
Contract / mint0xdAC17F958D2ee523a2206206994597C13D831ec7
Decimals6
Confirmation2 to 64 confirmations

Polygon

USDT-POLYGON

StandardERC-20
Contract / mint0xc2132D05D31c914a87C6611C10748AEb04B58e8F
Decimals6
Confirmation64 to 256 confirmations

Arbitrum One

USDT-ARBITRUM

StandardERC-20
Contract / mint0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9
Decimals6
Confirmation1 to 60 confirmations

BNB Smart Chain

USDT-BSC

StandardBEP-20
Contract / mint0x55d398326f99059fF775485246999027B3197955
Decimals18
Confirmation5 to 30 confirmations

Avalanche C-Chain

USDT-AVALANCHE

StandardERC-20
Contract / mint0x9702230A8Ea53601f5cD2dc00fDBC13d4dF4A8c7
Decimals6
ConfirmationConfigurable confirmations

Solana

USDT-SOLANA

StandardSPL Token
Contract / mintEs9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB
Decimals6
ConfirmationConfigurable commitment

BNB Smart Chain is the important edge case at 18 decimals; every other USDT network uses 6. Settlement matches the exact contract or mint above. Wrapped or look-alike tokens never settle as real dollars unless explicitly allowlisted.

Get started

Install the plugin

Install BitSettle USDT from BTCPay Server > Settings > Plugins > Available Plugins, then restart BTCPay Server.

The BTCPay technical plugin identifier remains BTCPayServer.Plugins.USDt for loader compatibility.

Production stores should configure dedicated RPC, chain API, or Solana endpoints before accepting meaningful volume.

Coverage

Networks we support

The BitSettle release offers seven receive-only USDT chains: TRON, Ethereum mainnet, Polygon PoS, Arbitrum One, BNB Smart Chain, Avalanche C-Chain, and Solana.

The EVM set is Ethereum, Polygon, Arbitrum, BNB Smart Chain, and Avalanche C-Chain. TRON and Solana are the non-EVM rails.

TRON, Ethereum, Polygon, Arbitrum, Avalanche, and Solana use 6 decimals. BNB Smart Chain remains the important edge case at 18 decimals.

Bitcoin and Lightning remain native BTCPay payment rails alongside the USDT plugin release.

Architecture

How each rail is wired

Ethereum, Polygon, Arbitrum, BNB Smart Chain, and Avalanche C-Chain share the EVM adapter family: JSON-RPC, contract allowlists, Transfer log detection, and EIP-681-style payment links.

Avalanche belongs in the EVM path because canonical Avalanche USDt is an ERC-20-style token on C-Chain.

Solana should stay in a separate adapter lane because USDt on Solana is an SPL mint with associated token accounts, slot commitments, and non-EVM payment-link behavior.

Safety

Matching the real dollar

Invoice settlement should match exact token contracts or Solana mints. Do not settle by token symbol alone.

Avalanche defaults to the canonical USDt contract. Legacy USDT.e should be ignored unless a merchant explicitly enables an alias mode.

Solana defaults to the canonical USDt mint. Wrapped mints require an explicit allowlist and separate destination token accounts.

Receiving

How addresses are generated

Manual address pools are the safest fallback when a wallet does not export an account-level xpub.

EVM xpub mode derives receive addresses below m/44'/60'/0'/0/n from an account-level xpub. Only public keys are used, and this mode applies to EVM chains only.

For Solana, the lowest-risk receive model is a pool of pre-created canonical USDt associated token accounts reserved one invoice at a time.

Solana receive configuration should be treated as chain-specific; do not assume EVM address derivation semantics carry over to SPL Token flows.

BitSettle never needs merchant seed words, private keys, or signing keys.

Honesty

What the rails can and can't do

USDT is centrally administered. Issuer controls can include freezing, blacklisting, pausing, or burning balances.

Public RPC and Solana endpoints can be rate-limited, unavailable, or inconsistent during high traffic.

Public test networks should use mock tokens unless an official Tether-issued testnet asset is verified for that environment.

Outgoing USDT refunds are out of scope because refunds require signing keys, and BitSettle is intentionally receive-only.

Configuration

Explicit, configurable, and receive-only.

The settings that keep the rail deterministic. Server-side keys are public-only; signing keys never leave your wallet.

EVM account path

Public keys only
account xpub: m/44'/60'/0'
receive path: m/44'/60'/0'/0/n
server keys:  public only

EIP-681 payment link

EVM checkout
ethereum:{contract}@{chainId}/transfer
  ?address={destination}
  &uint256={amountInBaseUnits}

Adapter split

EVM vs SPL
EVM:  ETH, POL, ARB, BSC, AVAX
TRON: chain API adapter
SOL:  SPL / ATA adapter

Settlement policy

Allowlists
match:         contract or mint
symbol-only:   never
wrapped asset: explicit alias only

Solana token mint

6 decimals
method: USDT-SOLANA
mint:   Es9vMFrza...wNYB
decimals: 6

Risk boundary

Receive-only
refunds:       out of scope
issuer freezes: possible
public RPC:    trial only

Ready to ship, or want it run for you?

Follow the quickstart to self-host, or get early access and we host, configure, and monitor the whole stack: dedicated RPC and all nine rails included.

The settlement engine is built on open BTCPay Server, so the rails are auditable rather than a black box you take on trust.