Crypto payment gateways without KYC

What this page can honestly claim#

It reports what each provider publishes about merchant verification, and nothing more. Most of this category publishes nothing at all, and a provider that says nothing is recorded here as undisclosed rather than counted as no-KYC.

That distinction is the entire value of this page. A silent provider is not a permissive one; it is a provider that has not told you, and merchants who read silence as permission discover the requirement after building the integration.

Four providers state it outright#

CoinRemitter states that registration requires an email address and no identity verification. BTCPay Server has no verification because it has no company in the payment path at all, OxaPay advertises signup with no documents, and GoUrl publishes simple registration with no verification process. Four published claims, each checkable in a way that inference from silence never is.

A handful out of the whole catalogue is still the exception rather than the pattern, and half of those are non-custodial, which is the property doing the work. Every other provider on this list either requires business verification, requires business and personal verification, or declines to say.

KYB and KYC are different requirements#

Business verification means the company provides incorporation documents, ownership details and often a bank reference. Identity verification means named individuals provide personal documents. A provider can require one without the other, and several here do.

Speend, B2BINPAY and 0xProcessing publish business verification only. BitPay and Coinbase Commerce publish both. The KYB and KYC guide sets out what each side actually asks for, and the glossary entry covers the term itself.

The payer side is a separate question entirely#

Merchant verification and customer verification are unrelated, and merchants conflate them constantly. A provider can verify you thoroughly and ask your customers for nothing, which is the common arrangement and the one most merchants actually want.

Speend is built around exactly that split: the business passes verification and the payer opens no account and faces no check. If your concern is checkout abandonment rather than your own onboarding, that is the property to shop for, and it is not what "no KYC" usually means.

Why so many providers publish nothing#

Because the answer depends on jurisdiction, vertical and volume, and publishing a single policy would be wrong for most applicants. That is a defensible reason and it still leaves a merchant unable to plan, which is why this index records the silence rather than excusing it.

It also means the requirement can change without notice, including after you integrate. A provider with no published policy has committed to nothing, and a merchant relying on light onboarding has no recourse when it tightens.

Non-custodial changes what there is to verify#

A provider that never holds your funds has structurally less regulatory exposure than one that does, and several non-custodial providers here ask correspondingly less at signup. That is a reason rather than a guarantee, and none of them publishes a policy either.

If light onboarding is the priority, the non-custodial list is the better starting point than this one, because the property that produces light onboarding is custody rather than any stated policy.

What to ask, and when#

Ask what verification applies to a business in your jurisdiction, in your vertical, at your expected volume, and ask before you build. Those three variables are what move the answer, and a support reply naming all three is worth more than any published policy.

Ask also what triggers a review after onboarding. Several providers verify lightly at signup and revisit at a volume threshold, which is the version that hurts: the request arrives when you are already dependent on the integration.

The honest summary#

There are four providers on this list documented as requiring no identity check, a handful that publish a clear requirement, and a majority that publish nothing. Any page presenting a longer list of no-KYC providers is inferring from silence, and this one will not.

Verification is also the criterion this index can verify least well, which is why it is reported as what providers publish rather than as what they do. The methodology page sets out where that line sits across every criterion.

Why this page cannot be longer#

Because listing providers as no-KYC on the strength of their silence would be inventing a claim, and it is exactly the claim a merchant would act on. Four providers on this page state it; the rest publish a requirement or publish nothing.

Pages elsewhere that name a dozen no-KYC gateways are reading silence as permission. That is a costly reading for anyone who builds an integration on it and then meets a verification request at a volume threshold.

What changes after onboarding#

Several providers verify lightly at signup and revisit when volume crosses a threshold. That is the version that hurts, because the request arrives once you are already dependent on the integration.

Ask what triggers a later review, not only what is required today. It is a different question and it produces a different answer at most providers on this list.

The question that actually gets answered#

What verification applies to a business in your jurisdiction, in your vertical, at your expected volume. Those three variables move the answer more than any published policy would.

A support reply naming all three is worth more than a page like this one, and it takes a day to obtain.