Skip to main content
Two ways into the same pool. Your customer picks; you don’t have to choose.

​
Side by side

​
Connect

The customer’s wallet talks to your pool directly. Fastest to settle, exact attribution, and it costs us nothing — which is why it has no minimum order value. Available on all seven EVM chains. TRON support is built and shipping.

​
Deposit

The customer gets an address and a QR code. They can pay from a phone wallet, a hardware wallet, or by withdrawing straight from Binance, Coinbase, or Kraken.
This rail is why the product works commercially. A large share of real crypto payments come straight off an exchange, where the customer has no connected wallet at all. Processors that only support wallet connection quietly turn those customers away.
We pay to deploy the forwarder and sweep it. Because that cost is fixed per invoice while our fee is a percentage, very small orders on expensive chains aren’t viable — hence a per-chain minimum. Below it, the checkout offers the connect rail instead of refusing.

​
What decides what’s shown

You can also set your own minimum per chain in Settings, expressed as a percentage of order value — a cap on how much settlement cost you’ll tolerate.

​
Which should you steer customers to

You don’t need to. But if you’re designing your own flow:

Prefer connect for small orders

No minimum, faster settlement, and exact attribution with no sweep step.

Prefer deposit for reach

It’s the only option for customers paying from an exchange, which is a large share of crypto buyers.

​
A third rail, coming

For repeat customers — subscriptions, balance top-ups, marketplaces — a per-customer address is in development. One permanent address per customer instead of one per invoice, which makes repeat deposits dramatically cheaper on TRON. The trade-off is attribution: the address identifies who, not which order, so matching relies on amount and timing. Good for balance models, wrong for one-shot e-commerce. It’ll be opt-in. Roadmap.