Every merchant settles to a dedicated BIP-44 derivation branch — never mixed into a pooled reserve with anyone else's funds. Turn on auto-sweep and every payment is forwarded to an external wallet only you hold keys to, minutes after it confirms. No KYC to onboard, no approval queue to withdraw. The best custody is the balance you've already moved out — so we make leaving the default.
m / 44' / coinType' — standard SLIP-44. BTC = 0', ETH = 60', LTC = 2', TRX = 195', SOL = 501'.coin/ merchantIndex' — atomically assigned at signup from the MerchantCounter singleton. Index 0 is reserved for platform hot wallet.merchant/ 0 / userIndex — external chain. userIndex per-user for static addresses, per-invoice for fresh-address invoices.addressm / 44' / 501' / merchantIndex' / userIndex'.sol// Move your balance out whenever you want — there is no human // in the loop deciding whether you're allowed to have your money. curl -X POST https://orbchain.io/v1/payout \ -H "payout_api_key: $ORBCHAIN_PAYOUT_KEY" \ -H "content-type: application/json" \ -d '{ "coin": "USDT_TRC20", "address": "T…your-own-wallet", "amount": "500.00" }' // → { "payout_id": "po_…", "status": "PENDING", "coin": "USDT_TRC20" } // The worker signs and broadcasts on the next tick. The only limits // are the security controls YOU can see and set — velocity caps, // destination denylist screening, 2FA step-up — not a support hold.
On the hosted service, no — OrbChain operates the wallet infrastructure and holds the master seed (KMS-sealed, non-exportable). We won't pretend otherwise. What you do control is where the money ends up: auto-sweep every settlement to an external wallet whose keys only you hold, and in steady state your funds live there, not here. If you need to hold the signing keys end-to-end from day one, that's a self-hosted deployment, not the hosted product — ask us about it.
Two ways that are literally true. First, the platform is self-custodial infrastructure: funds are never parked with a third-party custodian who could freeze the whole platform in one motion — OrbChain runs its own keys. Second, and more useful to you: auto-sweep means your revenue lands in a wallet you custody within minutes of settling, so the platform is a pass-through, not your bank. The custody that matters is the balance you've already moved out.
We hold the seed, so the honest answer is guardrails, not cryptographic impossibility: separation-of-duties on the platform side, audit logs, per-coin signing limits, velocity caps, admin IP allowlists, and destination denylists. The strongest protection is structural — you can sweep on every settlement and withdraw on demand with no approval, so you're never asked to leave a large balance sitting here in the first place.
No. Every merchant sits on its own BIP-44 branch (merchantIndex'), and deposits land on addresses derived under that branch. Balances are tracked separately from the ground up rather than commingled into one reserve and reconciled later. Index 0 is reserved for the platform hot wallet; no merchant gets it.
Yes. Each settled payment carries an Ed25519-signed receipt you can verify against our published public key, offline, forever — no API call to us required. So your proof of what you were owed doesn't depend on our uptime or our goodwill. See signed receipts.
Non-pooled settlement, auto-sweep to a wallet only you control, and on-demand withdrawal with no approval queue. No lock-in, ever.