No-KYC vs KYB in crypto payments

Layer one: what the platform collects from the merchant

This is the layer no-KYC marketing is about. A custodial gateway typically runs KYB before a business can accept a single payment: incorporation documents, a director's passport, proof of address, sometimes bank statements and a working website. A non-custodial gateway often asks for an email address and a receiving wallet. Both behaviors follow from regulation rather than temperament. Holding client funds is the activity that pulls a platform into licensing categories, money transmission in the United States, crypto-asset service provision under the EU's MiCA framework, and licensed firms owe identification duties to their regulators. A platform that never takes possession of client funds sits outside the trigger in many jurisdictions, though the exact line differs by regime, which is why careful gateways explain their reasoning instead of promising a legal conclusion for every country.

Layer two: what the platform collects from your customers

Separate question, often missed until it costs a sale. Some custodial processors require the paying customer to hold a platform account, and in some cases to complete identity verification, before an invoice can be paid. The compliance logic is the same custody logic one layer down: the platform is briefly holding the payer's funds too. Non-custodial checkouts generally ask the customer for nothing, because the customer is paying the merchant directly. When evaluating a gateway, read the payer flow in its documentation, not just the merchant onboarding, and count the steps between your customer and a completed payment.

Layer three: your own obligations, which no gateway changes

A no-KYC gateway does not make a regulated business unregulated. If your industry or country requires you to identify your customers, sell only to verified adults, keep transaction records, or file tax reports, those duties bind you identically whether your gateway asked for your passport or not. Sanctions law binds everyone regardless of payment rail. The honest framing of a no-KYC gateway is narrower and still valuable: it removes the platform's onboarding queue, its document reviews, and its ability to gate your money on a verification demand, for merchants whose own obligations are already in order. Merchants shopping for a way to escape obligations that genuinely apply to them will find that the gateway was never where those obligations lived.

Reading a no-KYC claim critically

Two questions sort the field. First, is the claim structural or revocable? A custodial platform with document-free signup still holds your revenue in a balance, and its terms almost always reserve the right to request documents later and hold the balance while you comply. The promise is real until the policy changes. A non-custodial platform holds nothing, so a future policy change has nothing to gate: the property survives management. Second, does the claim cover the payer side too? A checkout that makes your customers verify identity moves the friction rather than removing it. The test for both questions is the same one that settles custody claims generally, covered in how to tell if a gateway is actually non-custodial.

Common questions

If a gateway skips KYB, does its compliance burden shift onto me?

No burden transfers, because none is being dodged. KYB duties in payments regulation attach to platforms that hold client funds, and a watcher-style gateway holds none, so there is no unmet obligation moving anywhere. What stays with you is what was always yours: customer identification where your industry requires it, taxes, and sanctions compliance, none of which depend on which gateway you pick.

Why do some gateways verify businesses and others do not?

Custody. A platform holding client funds falls under licensing regimes that require identifying its clients, so custodial gateways run KYB as a legal necessity. A platform that only watches chains and derives addresses from merchant-supplied material holds nothing those regimes attach to in many jurisdictions, so it can onboard with an email and a wallet.

Does no-KYC mean my payments are anonymous?

No. On-chain payments are public by nature, the gateway knows your email and receiving wallets, and your customers may know much more. No-KYC describes the absence of a document-verification step at the platform, not anonymity. Merchants needing payment privacy should look at which chains they accept rather than at onboarding policy.

Can a no-KYC gateway start requiring KYC later?

A custodial one can, and its held balances make the new policy enforceable immediately. A non-custodial one can change its policy too, but past revenue already sits in merchant wallets, out of the policy's reach, and there is no balance to gate future compliance on. That difference between revocable and structural is the one worth checking before you rely on the promise.