The one-sentence version
Your customer pays into a contract that can only pay you, and you withdraw from it whenever you want.The full flow
Step by step
You deploy a pool
A pool is a small contract that belongs to you. When it’s created, your payout address is baked into it permanently.You sign the deployment and pay the network fee, which is what makes it yours rather than ours. One pool per chain you want to accept on.
A customer reaches checkout
You call our API for a quote, or the embedded widget does it for you. The quote locks a price for a short window and produces a payment identifier.
The checkout verifies us
Before showing a single payment option, the widget reads your payout address directly from the blockchain and re-computes what your pool address should be.If that doesn’t match what our servers said, the checkout stops and tells the customer not to pay. This is the mechanism that means a breach of our database still cannot redirect your money. How the verification works.
The customer pays
Either by connecting a wallet and signing, or by sending a plain transfer to a one-time address we show them. The two rails.
We confirm and tell you
We watch the chain. Once the payment is final — not merely seen — you get a
payment_confirmed webhook. That is your signal to ship. Finality.You claim
Payments accumulate in your pool. Press Claim in the dashboard and the balance splits and pays out. Claiming.
Who controls what
Nobody can block your withdrawal, including us — the function that releases funds is callable by anyone. That’s deliberate. A processor that could freeze your funds is a custodian, with everything that implies.
Things that surprise people
There are no chargebacks — in both directions
There are no chargebacks — in both directions
Nobody can reverse a payment against you. You also cannot reverse one yourself. Refunds are something you send manually, from your own wallet, to an address the customer gives you. Refunds.
Money accumulates rather than arriving per order
Money accumulates rather than arriving per order
Payments pile up in your pool and you claim in batches. This keeps network fees low — one withdrawal for a hundred orders instead of a hundred withdrawals. You choose the cadence.
A payment that arrives late is still honoured
A payment that arrives late is still honoured
Quotes expire, but the payment address does not. If a customer’s exchange withdrawal takes six hours, the money still arrives and still gets credited. The chain is the source of truth, not our timer.
You pay the network fee to deploy and to claim
You pay the network fee to deploy and to claim
Two small on-chain costs are yours: deploying your pool once per chain, and each claim. Both are transactions you sign. Everything in between is on us. Fees.
Now build it
The quickstart takes about 15 minutes.