Self-custodial · Multi-chain · Atomic splits

Crypto payments, fully self-custodial.

The system runs in your own environment, and payments settle from the payer's wallet directly to your addresses. No third party holds funds at any point.

How it works

A payment in four steps

01

Create an order

Through the API or the console

02

The payer pays

Token, network and wallet of choice

03

Atomic settlement

Split by rule; reverts on any failure

04

Confirm and notify

Delivered as a signed webhook

Checkout

The payment page your payers see

The payer selects a token and a network, connects a wallet and pays. The page works on desktop and mobile, in English and Chinese, in light and dark themes.

Browser extensionsOpen in walletQR connectionGas sponsorshipEmbeddable
Desktop checkout: merchant and amount on the left; token, network and payment on the right
Wallet selection sheet of the mobile checkout
Capabilities

Everything payment acceptance requires, in one system

Payments and atomic splits

One payment is divided among up to 10 payees within a single transaction.

Fiat pricingPayment linksRatio or fixed amountRefunds

Subscription billing

Signed once by the payer, immutable, and charged at most once per period.

TrialsRetriesPlan changesCancel any time

Checkout and wallets

Mainstream desktop and mobile wallets, with redundant connection channels.

Gas sponsorshipEmbeddableLight and darkEnglish and Chinese

Address risk screening

Screened before quoting and again at booking; a flagged payment is frozen.

OFAC listThird-party providersCustom listsPayee checks
Supported networks

EVM, TRON and Solana

EthereumEVM
BNB Smart ChainEVM
BaseEVM
Arbitrum OneEVM
OP MainnetEVM
PolygonEVM
Avalanche C-ChainEVM
X LayerEVM
LineaEVM
ScrollEVM
GnosisEVM
CeloEVM
TRONTVM
SolanaSVM
Other EVM networksAdded from the console
Stablecoins: USDT · USDC · DAI · PYUSD · EURCNative coins: ETH · BNB · POL · AVAX · TRX · SOLOther tokens can be listed
Security model

Funds remain under the merchant's control

Contracts hold no fundsNo withdrawal function; zero balance after each transaction
No administrator, not upgradeableThe deployer holds no privileges
Authorization covers the full termsAmount, payees and deadline are signed by the payer
Merchant keys cannot move fundsKMS custody and rotation supported

Contract sources and audit reports are published with the documentation; mainnet deployment will follow an external audit. Read the security model

Console

Operations, configuration and audit in one place

Console overview: received today, pending payments, orders confirmed over 7 days, chain connection status and recent orders
Passkey sign-inMulti-node failoverEmail · Telegram · Slack alertsComplete audit log
Developers

One request creates an order

REST API · OpenAPISigned webhooksEvent streamIdempotency keysTest modePostman collection
POST /v1/orders
curl -X POST $BASE/v1/orders \
  -H "Authorization: Bearer $KEY" \
  -H "Idempotency-Key: ord-SO-10023" \
  -d '{
    "merchant_order_no": "SO-10023",
    "amount": "100.00",
    "currency": "usd"
  }'

→ checkout_url
→ webhook: order.paid
Single binaryCheckout, API and console together
PostgreSQL onlyDeployed from a Docker image
Data stays with youSensitive data encrypted with a master key
ObservableHealth checks and Prometheus metrics

Complete a first payment on a testnet

Quick start