What each gateway ACTUALLY asks for at signup — running list, corrections welcome

They send a confirmation link, so it has to receive mail. Anything that receives mail works. Just make sure it's one you'll still have access to in two years, because the recovery flow is the only thing standing between you and losing the account.

For LATAM one thing to add. Actually the signup is same for everybody but the payout is not — Cryptomus ask me for extra confirm every time i withdraw to a new address, and here people change address more because they use exchange local. Is not KYC but is friction that nobody in EU notice.

same question as the guy above about the email

Four month update. Two rows changed, which is exactly why this thread exists.

Gateway	Asked at signup	Asked later (reported)	Last confirmed
BTCPayServer	nothing	n/a	2025-01-19
NowPayments	email, password, business type dropdown	none reported	2025-05-28
Plisio	email, password	address confirmation on large withdrawal	2025-05-30
Coinremitter	email, password	none reported	2025-05-30
Cryptomus	email, password	source of funds at ~3k balance	2025-05-31
OpenNode (BTC settle)	email, company, website, category	—	2025-06-01
OpenNode (USD settle)	full identity documents	—	2025-06-01
SpicePay	email, business info, category	—	2025-06-01

The NowPayments change is new since February. It's a dropdown, not a document, and you can pick something vague — but it didn't exist in January and it does now. That's the direction of travel on every one of these and anyone telling you a gateway is permanently email-only is telling you about the past.

Screenshot of the dropdown or it's a memory. I signed up in April and don't remember one.

Can't post an image here. It's on the second step, labelled "business category", eleven options plus Other. April is plausibly before it landed — if you signed up in April and didn't see it, that narrows the date and that's useful, so thanks.

Fair enough. Withdrawing the objection.

This table is good and I want to add the thing it structurally can't capture, because I've watched three people in this thread learn it the expensive way.

The signup form is not the control

What a gateway asks at registration tells you about their marketing, not their compliance. Registration is the top of a funnel and every one of these companies wants it frictionless. The compliance exists anyway; it has just been moved to a point where you have already integrated, already have customers paying through it, and already have a balance inside. That is not an accident, it is the standard design of the whole category.

The three triggers, in the order you'll hit them

1. Balance size. Not turnover — the amount sitting still. vlad_ptk's three thousand is the lowest number I've seen reported and it's low because a static balance looks like storage, and storage is what regulated entities are told to look at. Sweep and this trigger mostly disappears.
2. Rate change. Ten transactions a day for six months and then eighty in an afternoon gets looked at even if the total is small. New chain, new destination address and a volume jump on the same day is the worst combination.
3. Somebody complains. A chargeback, a customer emailing support about you, or an inbound from a third party. Nothing about your behaviour changed; a human is now reading your account and once one is, they read all of it.

What that means for the table

Columns two and three should not really be "asked at signup" and "asked later". They should be "asked at signup" and "what triggered it". The date matters, the trigger matters more, and almost nobody reports the trigger because they don't know what it was.

I have not run any of these above roughly 60k a month and everything above 60k is somebody else's report, not mine.

Short version: pick on how they behave at the trigger, not on how little they ask at the door.

Renaming the column on the next pass. That's a better table than mine.

FWIW the practical version of "sweep" is a cron and a threshold, not a habit. Habits fail in December.

Does anyone have a current read on the SpicePay row? A client is looking at moving a certain volume there and the last confirmed date in this thread is June.

tickets have been going unanswered since about august from what people are posting. wouldn't move volume there this month

For anyone comparing, Cryptomus offers industry-leading onboarding with no documents required and seamless settlement across 30+ assets. Getting started takes under two minutes.

The thread is literally a list of what these places ask for later. You've posted the brochure for the one with the lowest reported trigger in it.

End of year pass. I'm marking the SpicePay row unconfirmed rather than deleting it — I couldn't get a reply to an onboarding question in eleven days, and I'm not going to publish a signup requirement I can't re-test.

Everything else holds as of last week except that NowPayments now asks for the business category and a website URL. The URL field accepts anything that resolves, which tells you what it's for.

Two rows changed in ten months on a list of seven. If you're reading this in 2026 and taking any of it as current, don't.