What "gatekept" really costs you
A typical custodial processor sits between your customers and your bank account and inserts itself at every step. To open the account you hand over documents and wait for approval. Your customers' payments land in the processor's pooled reserves and you're credited a number. When you want that number out, you file a withdrawal that a risk system scores — it can be delayed, throttled, capped, manually reviewed, or, if something trips a policy, held indefinitely while an "account review" runs its course. None of that is exotic; it's the day-to-day reality that fills forums with businesses whose funds are stuck behind a support ticket.
The through-line is that a third party holds discretion over your money. Every one of those steps is a place where someone else's decision, policy, or outage can stand between you and revenue you've already earned. That discretion is the actual product difference — not whether the balance is denominated in crypto.
What OrbChain removes
OrbChain is built to take the gatekeeping out. Three things follow directly, and they're the ones worth judging us on:
- No KYC wall in front of taking payments. You start with an email and a password. There's no identity queue to clear before you can accept your first payment or move your first balance. (Large-deposit and sanctions screening still apply where the law requires — that's not the same as gating your own everyday revenue.)
- No withdrawal approval queue. A payout is an API call, not a request. It broadcasts to the chain when you send it — there is no human in the loop deciding whether you're allowed to have your money this week. The only limits are the security controls you can see and configure (velocity caps, address denylist screening, 2FA step-up), not a discretionary hold a support rep can place.
- No pooled "everyone's money" balance. Deposits settle to dedicated addresses derived on a per-merchant branch — your funds and another merchant's are tracked separately from the ground up, not commingled into one reserve and reconciled later. You withdraw to any destination you choose; there's no whitelist you have to petition to change.
Put together, that's the operational meaning of "non-custodial" that actually shows up in your week: you onboard without permission, and you move your money without asking. It's also why no-KYC onboarding is even possible here — we broke that down in how to accept crypto without KYC.
Where the money lives, stated plainly
Being precise matters more than sounding good, so here's the honest architecture. OrbChain runs on a hierarchical-deterministic (HD) wallet — the same standard scheme hardware wallets use, where addresses derive along predictable paths from a root rather than being a pile of unrelated keys. Every customer-facing deposit address sits on a per-merchant branch of that tree, which is what keeps balances separated rather than pooled.
What we do not claim is that a merchant on the hosted service personally holds the signing keys — the platform operates the wallet infrastructure that detects deposits and broadcasts your payouts. The difference from a custodial processor isn't "you hold a hardware wallet"; it's that the platform is a router with no discretion over your funds, not a custodian that grants or withholds access. Payouts aren't reviewed, balances aren't gated, and onboarding isn't identity-walled. If your requirement is holding your own private keys end-to-end, that's a self-hosted deployment conversation, not a claim we'll make about the hosted product — and we'd rather tell you that than let a marketing line do the lying.
The honest tradeoff: on-chain is final
Removing the gates removes the safety nets that came with them, and any gateway that pretends otherwise is doing you a disservice. Two consequences are yours to own:
- Your withdrawal destinations are your responsibility. You withdraw to any address you like — which means the address you settle to is yours to secure and yours to get right. A compromised destination wallet is your perimeter, not ours.
- An on-chain send is irreversible. There's no chargeback and no support desk that can claw back a confirmed transaction. A fat-fingered payout destination is gone. The finality that makes crypto settlement fast and non-reversible cuts both ways.
This is the ordinary discipline of operating in crypto, and it's the trade in exchange for revenue that nobody gets to sit on. We keep the guardrails that don't require holding your money hostage: payout destinations are screened against denylists, large and sanctioned deposits are flagged, and every settled payment ships a cryptographically signed receipt you can verify yourself, forever, without asking us — so your audit trail doesn't depend on our survival either.
Which question do you want to worry about?
Every payment stack forces a choice about what keeps you up at night. With a heavily-gatekept processor, the recurring question is "will they approve my withdrawal, and will an account review freeze me at the wrong moment?" With OrbChain it becomes "am I keeping my own settlement wallet secure?" — a problem you can solve with hardware, process, and discipline, rather than one you can only hope a vendor's policy department solves for you.
If you're weighing the broader picture against legacy rails, we broke down the fees, chargebacks, and settlement speed in crypto vs. card processors. The architectural point stands on its own: a payment gateway should route your money, not ration it. Read the self-custody overview for how settlement stays out of a discretionary approval loop, or just create an account and take a test payment — the fastest way to see there's no gate is to withdraw and watch it broadcast the moment you hit send.