// layer 5 — the gateway
Payment gateways where the operator (you) signs up without ID, organised by what the customer pays in.
Visa and Mastercard publish merchant-category-code restrictions. Gambling, adult, supplements-with-claims, replicas, crypto — entire MCCs that Stripe, PayPal, Shopify Payments, Square and the rest refuse outright. They don't care that your specific offer is legal; the category is on a list.
Visa and Mastercard pull merchant accounts that breach 1% chargeback ratio. Some sensitive verticals run 2-5% just from buyer's-remorse refunds. A no-KYC gateway either eats the chargeback risk itself or settles in crypto so Visa rules don't apply.
Card-acquiring is a regulated banking activity. The acquirer must KYC the merchant — name, address, beneficial owner, source of funds. Skipping this is fraud, not freedom. The legitimate workaround is to receive crypto and never touch the card-acquiring rail at all.
Pick the gateway by what your customer is going to pay with, not by what's cheapest. Cheap-but-wrong gateways collapse on the first chargeback wave.
Customer pays in BTC/USDT/XMR → crypto-native gateway. Customer pays card → card-crypto workaround. Customer pays PIX → honest answer is "you need CPF, sorry". Don't pick a gateway because its signup is easy if it doesn't match how money actually arrives.
Open source, runs on your VPS, payments land directly in your wallet. Zero third-party. The only true no-KYC option. Trade-off is infra: you maintain the server, node and wallet keys yourself.
Hosted gateways with the lightest signup short of self-hosting — email and password, no docs. Auto-forward to your wallet. They reserve the right to ask for KYC on large volume — real risk for high-risk verticals.
Customer types Visa/MC, processor charges, gateway converts at the rail, you receive crypto. You skip merchant-acquiring KYC because the gateway is the merchant of record on the card side. Trade-off: high decline rates on some BINs, chargeback exposure on the gateway, MCC suspensions still possible.
Fiat off-ramp triggers full KYC on the receiving end. Keep settlement in BTC/USDT/USDC and only convert when you actually need to cash out — at a separate non-KYC venue like ChangeNOW or SideShift.
Custodial gateways (Cryptomus, SpicePay) can freeze balance on a complaint. Daily or weekly withdrawal to your own wallet caps the freeze window. Gateways also suspend MCCs, get acquired, change policy — know the next gateway you'd switch to with the account already created.
Customer pays in cryptocurrency, you receive cryptocurrency. The cleanest no-KYC profile — no card rail in the loop, no fiat banking, just on-chain settlement. BTCPayServer (self-hosted) is the strongest option; the rest are hosted operators that ask only for an email at signup.
| Gateway | Merchant KYC | Accepts | Settles in | Fee | Rating | Visit |
|---|---|---|---|---|---|---|
BTCPayServer OSS Self-hosted, open-source, truly zero KYC | none | BTC · BTC-LN · LTC +2 | Your wallet directly | 0% protocol fee. VPS + node infra costs only. | 4.8 | Visit |
NowPaymentsHR-OK Hosted crypto checkout, email-only signup | BTC · ETH · USDT +3 | Your wallet (auto-forward) | 0.5% (0.4% with NPM token discount) | 4.2 | Visit | |
PlisioHR-OK Crypto gateway with merchant tools and APIs | BTC · ETH · USDT +4 | Hosted balance | 0.5% | 4.0 | Visit | |
CryptomusHR-OK Heavy in CIS and Asia affiliate ecosystems | BTC · ETH · USDT +4 | Hosted balance | 0.4% to 0.8% depending on coin | 4.0 | Visit | |
CoinremitterHR-OK Cheapest fee in hosted crypto checkout | BTC · ETH · USDT +4 | Direct wallet | 0.23% | 3.8 | Visit | |
SpicePayHR-OK Explicitly accepts categories others ban | light | BTC · ETH · USDT +1 | Hosted balance | 1% (lower with volume) | 3.7 | Visit |
Customer pays crypto, you settle into fiat. The fiat leg triggers some form of KYC almost everywhere — OpenNode's USD payout, NowPayments' bank withdrawal — because cashing into a bank account is a regulated activity in every Western country. Crypto-in / crypto-out and then converting yourself on a no-KYC swap is usually cleaner.
| Gateway | Merchant KYC | Accepts | Settles in | Fee | Rating | Visit |
|---|---|---|---|---|---|---|
OpenNode Lightning-first Bitcoin payments | light | BTC · BTC-LN | BTC | 1% | 3.6 | Visit |
Customer enters a Visa/Mastercard at your checkout, the processor charges the card, and you receive crypto. The closest thing to a no-KYC card-acquiring product — the merchant of record on the card side is the gateway, not you. Trade-off: high decline rates, chargeback exposure, and the gateway can suspend specific MCCs.
| Gateway | Merchant KYC | Accepts | Settles in | Fee | Rating | Visit |
|---|---|---|---|---|---|---|
NowPayments Card CheckoutHR-OK Customer pays card, you receive crypto | Visa · Mastercard | BTC | ~3.5% card processing + 0.5% gateway | 3.8 | Visit |