Skip to main content

​
Payout

There is no payout address to enter. You are paid to the wallet you sign in with, and it is fixed once your settlement pool is provisioned. Sign in with the wallet you actually want paid.
Settings has no Payout section. When your settlement pool is provisioned you sign a one-off proof-of-control message from the connected wallet — an off-chain signature, not a transaction, so there is no gas for you to pay. That commits your pool’s address, computed from that proven wallet, and the server ignores any recipient a client tries to submit. The Pool tab shows the result read-only: locked to your sign-in wallet — actually deploying the contract on each chain you want is a separate step, one signature and one wallet-paid transaction per chain, done in that same tab. That is what makes the check your customers’ browsers run meaningful: the destination is derived from a wallet you proved you control, not from a row in our database.

Choose the wallet before you provision

The recipient is immutable per account and per chain family — one EVM wallet, one TRON wallet. To be paid into a multisig or treasury, sign in and provision from that wallet itself. EVM smart-contract wallets are supported (EIP-1271); TRON sign-in verifies plain key signatures only, so a TRON contract or multisig payout wallet is not supported today.

Sign the proof of control

One off-chain signature from the connected wallet, prompted during pool setup.

Confirm before real payments

Check your deployed pool and its recipient at /verify before taking real payments.
Never sign in with, or try to route payouts to, an exchange deposit address. You could not provision from one in any case — you cannot sign with it — and exchanges rotate and retire those addresses without warning, so funds sent to a dead one are unrecoverable. Use a wallet you hold keys to.
There is no rotation path. Once your pool is committed the recipient cannot be changed, so decide before you provision.

​
Currency and tokens

Display currency

EUR or USD. What prices are quoted in. Purely presentational — settlement is in your chosen token.

Settlement token

USDC, USDT, or EURC. Sets which token the checkout opens on by default. There is no swap today, so you are paid in whichever enabled (token, chain) pair the customer picks.
In Tokens you enable each (token, chain) pair individually, so you can take USDC on a chain without taking EURC on that same chain. Enforced server-side, not just hidden in the UI. Coverage is not uniform across networks, and it is not a rule you can extrapolate from — it is a fixed list of contracts per network. Across the eight networks live today: USDC on all seven EVM testnets but not on TRON; EURC only on Ethereum Sepolia, Base Sepolia and Avalanche Fuji; USDT only on TRON Nile. Networks we add later will not necessarily carry the same tokens. The Tokens tab shows exactly which pairs you can turn on, and Chains and tokens has the full matrix.

​
Minimum payment size

You set your own minimums in Per-network minimums, on the Pool tab rather than in Settings. It is one number field per network and per way of paying — an absolute amount in your settlement currency, blank or 0 meaning no minimum. Below a minimum, the checkout hides that way of paying for that network and offers the customer another one; when every option on a network is gated, the network itself disappears. Sending to a pay-to-address invoice is available on every network; connecting a wallet is available on EVM networks only. Coming A percentage-based version — cap settlement cost as a share of order value, with the implied per-network minimum shown live as you move it — is designed but not shipped. Limits · Roadmap.

​
Compliance

Merchant screening

Always on, platform-level. The wallet you sign in with is screened at sign-in, and your account’s registered wallet is re-scanned daily. A second wallet linked for another chain family is screened at that chain’s sign-in only — not at link time, and not by the daily re-scan.

Payer screening

Off until you switch it on. Switching it on reveals a mode selector, already set to Enforce — a sanctioned payer’s payment is refused. Change it to Monitor to let the payment through and log the decision instead. Sanctions.

​
Webhooks

Endpoint URL and your signing secret. The delivery log — response codes and bodies — lives on the Webhooks tab, which links back here to edit the URL.
Every account has a signing secret. Reveal it once in Settings → Integration → Webhook sender check (or on the Webhooks tab) and store it where your server reads it. It cannot be shown a second time; if you lose it, or think someone else has it, rotate it there — the old secret stops working immediately.
The Webhooks tab has a Send test payload button. It signs exactly like a real delivery — same header, same envelope, same signed content. Its event is payment.test and its data.test is true, so route it away from fulfilment. If your handler verifies the test, it verifies production.

​
Confirmation thresholds

How deep a payment must be confirmed before you’re told it’s final. Depth is computed per network, scales with order value, and accounts for each network’s reorg behaviour. We set it, not you — there is no control for it in Settings. A per-merchant override exists in the backend, so if you sell something instantly consumable, where a reversal can’t be recovered by withholding shipment, ask support to raise your thresholds. Deeper confirmation costs conversion, so it is a genuine trade-off. Finality.

​
Referral

If a partner referred you, their code is bound here. While your account isn’t linked to a partner yet, you can enter a code in this section at any time to link it yourself. Once a partner is linked the binding is permanent, and only platform support can change it. A referral costs you nothing extra — the partner’s share is carved out of the platform fee you already pay, never added to it. That fee is 1% flat, all-in, so you keep 99% on the connect rail: 0.75% to us, 0.25% to your partner, and nothing else. Fees.
The read-only fee card in Settlement & display, “1.00% flat — you keep 99.00%”, is the number to price against. The deposit rail nets you slightly less than that on any given order, by whatever small network fee the forwarder held back on that specific payment (capped at 10%, shown per order) — Fees has the breakdown.

​
Account

Your registered wallet, any linked wallets, and your session. Your wallet is your login; there’s no password to change or reset.

​
Linking a second wallet

An EVM key can’t sign for TRON, and a TRON key can’t sign for the EVM networks, so accepting on both needs two wallets on one account — one per chain family. Sign in with either one and Linked wallets offers to attach the other; the direction simply follows the wallet you are signed in with. Attaching is a co-signature — one signature from each wallet — and both have to be given in one sitting. Close the tab, reload, or dismiss one of the prompts and nothing is attached. No harm done, but you start again from Account. Once it succeeds, both addresses show under Linked wallets and in the wallet menu in the header, which is how you confirm at a glance that the second one is really attached.
Don’t sign in with the second wallet before you have linked it. It belongs to no account yet, so signing in creates a new, empty one — no payments, no pool, as though your data had vanished. It hasn’t. Sign back in with your first wallet and run the link, and that empty account is folded into yours automatically. That only holds while it is untouched: once it has taken a payment, had a pool provisioned, or been through setup, linking is refused and merging the two is not something you can do yourself — contact support.