Get a merchant account when Stripe says no: the 30-day plan

Days 0 to 2: secure what you have

Export everything from the Stripe dashboard before access changes: full transaction history, dispute records, and payout reports. Future underwriters will ask for processing history, and this is it. Note your dispute ratio precisely, because you'll be asked and guessing badly reads as evasive.

Read the rejection or termination notice carefully and identify whether it cites a prohibited category, elevated disputes, or unverifiable information. Each leads to a different application strategy. If you were terminated for cause, ask in writing whether you've been reported to MATCH, the card industry's shared termination list. A MATCH listing lasts five years and shapes everything downstream, so you need to know now, not at your third decline.

Days 2 to 7: build the packet

High-risk underwriters approve complete files and stall incomplete ones. Assemble this before any application goes out:

• Certificate of incorporation and corporate documents
• Government ID for every owner with 25%+ equity
• 3 to 6 months of business bank statements
• Processing history export, including the dispute numbers
• Licenses your vertical requires: gaming license, broker authorization, hemp certificates and COAs
• A live website with visible terms of service, refund policy, company name, physical address, and reachable support

The website matters more than most merchants expect. Underwriters read it like a compliance officer, and a checkout with no refund policy or contact page is what exit scams look like. Fix it before anyone looks.

Days 7 to 14: pick the right doors to knock on

Applying everywhere at once is a mistake, because each declined application creates a record the next underwriter can see. Target processors that already serve your category.

Be honest about the aggregator row: if Stripe rejected your category, PayPal will too, usually after you've built volume on it. Repeating the approve-then-terminate cycle costs more than skipping it.

Days 14 to 30: underwriting, and what to negotiate

Expect follow-up questions and answer them same-day, since slow responses stall files. When an offer comes, the rate is the least negotiable part. Focus on the terms that actually hurt: the reserve percentage and release schedule, the payout delay, the monthly minimum, early termination fees, and what specifically triggers a hold. Get each answer in writing. A processor that won't put reserve terms on paper is telling you the terms are whatever they decide later.

If you have prior processing history with a sub-1% dispute ratio, use it. It's the strongest card you hold and it's worth a reserve reduction if you present it clearly.

In parallel, from day 0: turn on the rail with no application

Everything above takes two to six weeks, and your ads and payroll don't pause for underwriting. Crypto processing has no acquiring bank, which means no application, no underwriting queue, and no category policy. A Flint checkout goes live the same day you sign up and runs beside whatever card account you eventually land.

Merchants who've been through one shutdown usually keep both rails permanently. The lesson isn't that Stripe was the wrong processor. It's that any single processor is a single point of failure, and the industries pages show what that costs vertical by vertical.