Skip to content
ZeroKYC Pay
Get started
DocsPricingBlogSign in

Transit checkout guide

How the 1% transit checkout works: payout address, auto-sweep, batching and what your customers see.

Coming soon: the transit checkout is not open to new merchants yet — it is shown in the console for preview only. Meanwhile, the direct checkout is fully available.

The transit checkout is the "familiar" mode: payments arrive on ZeroKYC Pay platform addresses, and an automated sweep keeper forwards them to your payout address after confirmations. You price it at 1% of confirmed volume + the network fee, both deducted at sweep. No subscription, no minimums.

When transit fits

  • You want payment ops fully off your plate — no wallet hygiene, no address exclusivity rules.
  • You pay out to an exchange deposit address, a cold-wallet rotation or a treasury.
  • You accept volatile assets (BTC, XMR) and don't want to manage rate refresh yourself.

Setup

  1. Open the console → Checkout → type Transit.
  2. Paste your payout address per chain (any valid address — an exchange deposit works).
  3. Enable the assets you want; copy your pk_test_… and create an invoice.

There is nothing else to configure: the platform issues payment details from its own pool (unique-amount addresses for account-based assets, its own xPub addresses for BTC, subaddresses for XMR).

How money moves

  1. Invoice created — the buyer gets an address and a crypto amount quoted from public market rates.
  2. Payment confirmed — after the asset's confirmation threshold (see the table) the invoice flips to confirmed and the webhook fires.
  3. Sweep — the keeper transfers amount − 1% − network fee to your payout address:
    • EVM and TON: immediately after confirmation, gas is negligible.
    • TRON, BTC, XMR: batched — by a $50 threshold or hourly — so network fees never eat small payments.

The 1% platform fee accumulates separately and is settled by the treasury batcher once a day. Your console shows confirmed volume and held fees in real time, and every sweep appears in the Sweeps page with its tx hash.

Operational details worth knowing

  • Transit hot keys are isolated from treasury keys; addresses leave rotation after a sweep, and sweeps auto-pause on anomalies.
  • If a sweep fails (e.g. no TRON energy), the keeper retries with backoff — the funds stay on transit and an alert fires. Your customers' invoice states are unaffected.
  • Underpaid payments sweep too: the buyer's observed amount lands in your wallet, and the payment.underpaid webhook tells you what happened.
  • A transaction seen in the mempool before invoice expiry stays valid even if its confirmation lands later.

What your customer sees

The standard hosted checkout: amount, address, QR, TTL timer. Nothing in the flow hints at transit vs direct — the difference is purely on the settlement side.