AcceptUSDToneverychainthatmatters

Real-time detection, screening, and double-entry settlement for USDT across ten blockchains. Self-custodial, with keys that never leave your HSM.

  • Self-custodial
  • Ten chains
  • Double-entry
Read the docs
0Networks
0 sFastest finality
0 yrImmutable audit
$0Custody vendor fees
One integration, ten chains

Every network the engine settles on

Tron, Ethereum, BNB Chain, Solana, Polygon, Arbitrum, Base, Optimism, Avalanche, and TON, behind a single API surface, each confirmed on its own finality clock.

NetworkTickerConfirmationsFinality
AvalancheAVAX8~2 sec
TONTON1~5 sec
SolanaSOL32~13 sec
BNB ChainBSC15~45 sec
TronTRX19~1 min
EthereumETH12~3 min
PolygonPOL256~10 min
ArbitrumARB64~12 min
BaseBASE64~12 min
OptimismOP64~12 min
01Double-entry core

Every movement, balanced to the cent

Value never appears or vanishes: each deposit, sweep, and payout is recorded as balanced debits and credits in an append-only ledger. Balances are derived, never hand-edited, and held as integer smallest-units, so there are no floating-point rounding surprises.

One chain-adapter interface means Tron, the seven EVM chains, Solana, and TON all post to the same ledger: add a chain, not a codebase. Reconciliation against on-chain reality runs continuously.

02Chain-adapter core

One interface. Every network.

Tron, the seven EVM chains, Solana, and TON all sit behind a single adapter interface, so every deposit runs the same path: detect, confirm to each chain's own threshold, screen against sanctions and the Tether blacklist, settle to the ledger, and sweep to treasury.

Adding a network is a configuration change, not a rewrite, and each chain keeps its real confirmation clock, from TON's seconds to Polygon's checkpoint depth.

deposit settled · double-entry balanced

Integrate, operate, supported

Simple to integrate. Yours to operate.

One REST API with idempotent endpoints and signed webhooks, a merchant console for every tenant, and direct access to the team that built the engine.

Easy integrationREST · WEBHOOKS
# create a payment intent
POST /v1/payment_intents
{ "amount": "1000.00", "network": "tron" }
201 Created
{
  "id": "pi_a1b2c3d4",
  "address": "TR7NH…Lj6t",
  "status": "requires_payment"
}
# webhook  payment_intent.settled  ✓

Idempotent endpoints, signed webhooks, and one API surface for all ten networks.

Merchant consolePREVIEW
Settled · last 24h
12,480.00 USDT
  • + 250.00 USDTjust now settled
  • + 1,000.00 USDT2m settled
  • + 480.00 USDT11m settled

Per-tenant balances, deposits, and webhook logs in one console.

SupportEngineering

Talk to the people who built it.

  • A shared channel with the engineers who built the engine
  • Integration reviews, key-ceremony and incident runbooks
  • Public status page and honest incident comms

Self-custodial by design

You hold the keys. Or we seal them in the HSM.

Either way, there's no third-party custodian: no Fireblocks, no Cobo, no BitGo. Pick the mode below to see how the keys are held.

enginepublic keys · xpub
sign
signer-svcisolated · NATS
pkcs#11
YubiHSM 2private key sealed

Keys derived in the HSM. Only signatures cross back, and the crypto-vault has no egress.

  • No third-party custodian
  • Managed HSM or self-custody
  • Public-key-only app layer

BuiltforUSDT.Builttobeowned.

Ten chains, one integration, and a signing key that stays yours.