Worth separating the two failure modes, because they need different fixes and this thread is mixing them.
Failure mode one: onboarding disclosure
You tell them the category, an underwriter reads it, and the account is dead before it processes anything. Annoying, cheap, fast. You lose a week.
Failure mode two: post-hoc MCC review
The account opens, processes, and then something — a volume threshold, a chargeback cluster, a complaint, occasionally just an audit cycle — puts a human in front of your transaction history. They see what you actually sell, and now they are holding funds they have already accepted. This is your 41-day story, and it is the expensive one.
The mistake is optimising against mode one. Every "no KYC, email only signup" recommendation solves mode one and makes mode two worse, because the lighter the onboarding the later the review happens and the more of your money is inside when it does.
What I'd actually run
- A primary rail that has already said yes to your category in writing. Slower to open, boring, survives the review because the review is behind you.
- A self-hosted fallback that cannot be reviewed at all. BTCPayServer on a box you control, wired into the same checkout, dark until you need it. It will not save your average order value — a chunk of buyers will not use it — but it means "account closed" is a bad afternoon rather than a dead business.
- A sweep schedule measured in hours, not weeks. Whatever is in a custodial balance when the review lands is the amount you are gambling.
I have not run this at above 60k a month and I would not assume it holds at 300k — at that point you are a large enough account that someone negotiates with you instead of closing you, which is a different game entirely.
Short version: stop shopping for a processor that won't review you. Shop for one that already did.