The technical reference behind the managed service.

BitSettle is a managed service: we provision, configure, and monitor the entire settlement stack for you. There is no plugin to install, no server to restart, and nothing to patch on your side.

Once you're onboarded, we enable the exact rails your business wants to accept and wire up dedicated RPC, chain API, and Solana endpoints so you never depend on fragile public defaults.

You never hand over signing keys during setup. You only ever provide the receive-side wallet details (addresses or an account-level public key) that settlement should point at.

The managed rail supports nine networks: native Bitcoin and Lightning, plus USDT on seven 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 run on native BTCPay-based payment rails alongside the seven USDT networks.

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 sits 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.

This adapter split, along with the RPC and endpoint configuration behind it, is ours to run and monitor. You get the outcome (nine reliable rails) without operating any of the underlying infrastructure.

Invoice settlement matches exact token contracts or Solana mints. We never settle by token symbol alone.

Avalanche defaults to the canonical USDT contract. Legacy USDT.e is 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.

Every setup is receive-only and watch-only: BitSettle only ever needs public information about where your money should land, never a private key.

Manual address pools are the safest fallback for wallets that don't export an account-level xpub.

EVM xpub mode derives receive addresses below m/44'/60'/0'/0/n from an account-level xpub you provide. 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 is handled as chain-specific; EVM address derivation semantics are never assumed to carry over to SPL Token flows.

BitSettle never asks for, stores, or needs merchant seed words, private keys, or signing keys, during onboarding or at any point afterward.

EVM payment links use the EIP-681 ERC-20 transfer form with the configured chain ID, destination address, and base-unit amount.

Solana and non-EVM checkout behavior favor explicit destination details unless wallet payment-link support is validated.

If a wallet or exchange doesn't support token payment links, checkout falls back to a plain destination-address QR code.

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

RPC and Solana endpoints can be rate-limited, unavailable, or inconsistent during high traffic on public infrastructure, which is exactly why dedicated, monitored endpoints are part of what we run for every managed account.

TRON transactions are treated as final only after roughly 19 blocks of solidification; other networks carry their own network-specific confirmation policy, which we apply automatically per chain.

Outgoing USDT refunds are out of scope for BitSettle because refunds require signing keys, and BitSettle is intentionally receive-only. Refunds go out from the wallet you control.