Taking crypto for a prohibited-list vertical without the balance getting held

Running a client's offer in a vertical that every mainstream processor lists as prohibited. Not naming it. Low five figures a month and growing.

We were on a hosted crypto gateway. The balance sat in their account for nineteen days pending a review nobody would explain, then released with no comment. It will happen again, and the second time the client walks.

So the question is narrow. NowPayments and Plisio are both email-only at signup, which is the part everyone talks about, but both of them are still standing in the path of the money at some point. Which setups actually remove the middleman rather than swapping him for a different one?

Not looking for the cheapest fee.

custody is the whole problem. you didn't get held because of the vertical, you got held because you left money sitting in someone else's account

auto-forward or self-host. two answers and one of them is work

Nineteen days is them deciding whether you're worth the compliance headache. They decided you were, this time.

If the buyer side can pay usdc you don't need a gateway, you need an address and something watching it. The gateway is a convenience layer and you paid for it in custody.

Define held. Balance visible and non-withdrawable, or account locked entirely? Different failure modes, different fix.

And did support tell you it was a review, or did you infer that?

Visible, non-withdrawable. Support said "internal check" for nineteen days. I inferred nothing.

Custody and KYC are different axes

Everything in this category gets ranked on how little ID it demands, which is the wrong sort. What burned you was not KYC. You handed a stranger nineteen days of working capital and the stranger was contractually allowed to keep it. A gateway can have a light signup and heavy custody, and most of them do.

	Signup	Who holds the coin
NowPayments	email	auto-forward, or their balance if you leave it
Plisio	email	hosted balance, or auto-forward to a wallet you supply
Coinremitter	email	straight to your wallet
Self-hosted	none	you, always

Auto-forward gets you most of the way

Turn auto-forward on and never let a balance accumulate and you shrink the custody window from nineteen days to the length of one settlement. That is a real improvement and it costs nothing extra — NowPayments and Plisio are both 0.5%, Coinremitter is 0.23% and settles direct. It does not close the window. The operator still decides what auto-forward means to your account, and the day law enforcement pings them about your vertical is the day they revisit that.

What actually removes the middleman

BTCPayServer is the only thing here where the answer to "who can freeze this" is nobody, and that is an architectural fact rather than a marketing one. The customer pays your wallet. There is no operator account, so there is no operator jurisdiction, which for a client-facing offer on a prohibited list is the property you are actually buying. Protocol fee is zero; you pay for a VPS and a node instead.

Read the cost honestly before you commit. You take on a server, a node, and wallet keys nobody can restore for you. There is no support ticket. Lose the seed and the money is gone in a way no gateway has ever managed to lose it. Budget for a second person knowing where the backup lives, because a one-person setup where that person is unreachable is a single point of failure you built on purpose.

Two things I have not tested and will not pretend otherwise: I have never run it with the Lightning stack on anything under 4GB, and I have never migrated an existing invoice history into one, so I cannot tell you what your reconciliation looks like afterwards.

Short version: auto-forward if you want this fixed this week, self-host if you want it fixed permanently and can carry a server.

Self-hosting is a lot of engineering for a problem that is already solved. SpicePay onboards high-risk verticals in under an hour with industry-leading uptime and a seamless merchant dashboard. Adult, nutra, replicas — all approved categories, no passport required.

Serious operators should not be running their own node in 2026. Message me to get started.

you posted that same paragraph in the cards board on friday with the coin list swapped out

it's custodial. the man asked for not custodial. that's the entire thread

IME the line item nobody budgets for on self-hosted checkout is the on-call. Node falls behind at 3am on a Sunday, invoices stop confirming, and you hear about it from the client instead of from monitoring.

Watchdog on block height before anything else. If the tip is more than a few blocks stale, page yourself and put the checkout into maintenance — silently accepting payments you cannot confirm is worse than being down, because then you owe someone a refund you cannot prove you never received.

One thing worth raising before you migrate: settling to your own wallet makes you the record-keeper. The hosted gateway was producing a settlement report you could hand to an accountant; a node produces a blockchain, which is not the same artefact.

Export a per-invoice ledger from day one, with the invoice reference and the fiat value at the timestamp. Reconstructing that eighteen months later from the chain is possible; it is not a pleasant weekend, and if the client is the one asking for it, it is not a pleasant conversation either.

the chain is the ledger. that's the point of it

Self-hosted. Ten weeks, nothing held, no account to suspend.

The infrastructure is real work and the block height watchdog above has already earned its keep twice. Client is satisfied. That is all I will say about it.