Skip to main content

​
Settlement

Pool

Your contract, one per chain. Receives payments and pays only you. Immutable — its payout address is fixed at creation and cannot be changed by anyone, including us.
A path by which money reaches your pool. There are two: connect and deposit.
The customer connects a browser wallet and signs one transaction into your pool. They pay their own network fee.
The customer sends a plain transfer to a one-time address. Works from any wallet or an exchange withdrawal. We front the network fee to create that address and sweep it into your pool, and recover it by holding back a small network fee — capped on-chain at 10% of what arrived, fixed into that address before the customer is ever shown it, and verified by their own browser before they pay. It comes off that one payment, not out of your settlement share.
The one-time contract behind a deposit address. Sweep-only — it can send funds to your pool and nowhere else.
Moving funds from a deposit address into your pool. Automatic for a deposit that lands as paid or overpaid — and, on the EVM chains, expired_paid_late. An underpaid or wrong_token deposit is not swept for you: the money waits at the deposit address, which can only ever pay your pool, until someone calls the sweep. On TRON, a late payment and any top-up arriving after a sweep has already run also wait.
Splitting your pool’s balance and crediting each share to a pull-claim ledger. Callable by anyone. The 1% platform fee (0.75% treasury, 0.25% partner) comes off the gross; the rest is credited to you in full — no separate reward paid to whoever sent the transaction. You are credited 99% of the gross — an all-in cost of 1%.
The deposit rail’s committed network fee. Fixed into the one-time address when it’s created, before the customer sees it; verified by their browser before they pay; capped on-chain at 10% of what arrives. Taken at the forwarder, not from your settlement share — intent.surchargeUnits in the API response.
Moving your distributed share to your payout address.

​
Money

​
Trust

Your payout address, pinned in the embed code on your site. The root of the verification chain — it lives somewhere our database can’t reach.
The on-chain registry slot that says where an address wants to be paid. Each slot is writable only by the address that owns it, so our database can never author one. There is no dashboard control that writes one today, and where nothing has been written the registry answers with the address itself — which is the normal case, since your payout address is the wallet you sign in with.
The browser recomputing your pool address from the chain-read payout address and checking it matches what our servers served. The load-bearing check.
Re-derivation failed. The checkout blocks signing and hides the payment address. Verification.
The integrity attribute on the SDK script tag. If the file changes by one byte, the browser refuses to run it.

​
Payment states

​
Chains

​
Integration