Merchant account for SARMs startup

Opening a merchant account for a SARMs startup is harder than CBD, harder than peptides, and about the same as kratom. The vertical is legal-adjacent — SARMs are not FDA-approved for human consumption, so compliant operators sell for "research use only" with appropriate disclaimers. That distinction matters to acquirers. Here's what SARMs founders actually need to know before they sign the first merchant agreement.

Who won't underwrite SARMs

Stripe, Square, PayPal, Shopify Payments, Authorize.net direct, Braintree. Do not try to hide SARMs under a generic "supplements" MCC or route SARMs transactions through a CBD MID. Both get caught, and both results in MATCH listing within 60-90 days. MATCH stays on your record five years and follows you personally (the signer) to every future application. The single fastest way to destroy your SARMs startup before it exists is to try to sneak it past Stripe.

See our alternative to Stripe write-up for the full "why not Stripe" framing; SARMs follows the same logic with tighter reserves.

Who will underwrite SARMs

The realistic shortlist for a SARMs startup in 2026: Corepay (most active SARMs book among specialist ISOs), Durango Merchant Services (broader high-risk, takes SARMs with compliance docs), PayKings (good for subscription SARMs), Easy Pay Direct (moderate SARMs book, heavier reserves), High Risk Pay (takes operators coming off closures, most expensive). See best high-risk merchant account for SARMs for the full ranking.

Realistic expectations for a first-year SARMs startup: 4.5-5.5% effective rate, 15-20% rolling 180-day reserve, $25 monthly fee, Authorize.net or NMI gateway layer, 2-3 week underwriting timeline if docs are clean.

What docs you actually need

Formation docs (LLC or C-corp articles; SARMs operators typically form an LLC with a non-obvious DBA — "Research Supply Co" rather than "SARMs King"), EIN letter, bank account + voided check, driver's license for each signer over 20% ownership, personal credit check authorization, three months of processing history if transitioning from another account (rare for true startup), COA from your lab partner for each SKU, and site screenshots showing research-only disclaimers in place.

The disclaimer language matters. Acquirers want to see "For research use only. Not for human consumption." on the product page and in the cart/checkout flow. They want an age gate (21+ typical for SARMs). They want a clear terms of service that restricts purchases to research entities. This is not legal cover — it's the acquirer's underwriting checklist. Miss any of them and you'll be declined.

Personal credit and signer history

SARMs underwriting pulls personal credit on the signer. A 650+ FICO is generally fine; below 600 you'll need a second signer or higher reserve to compensate. Acquirers also check the signer against MATCH — if you've been MATCH-listed before from a prior business, you're declined regardless of the new operation's quality. One MATCH, five years, no exceptions.

For co-founders, the signer with the cleaner credit and no MATCH history signs the merchant agreement. The entity stays the LLC; personal liability stays with the signer. Structure accordingly.

Gateway + integration reality

Most SARMs specialist ISOs pair with Authorize.net or NMI. Both integrate with WooCommerce, Shopify (via plugin, not Shopify Payments), BigCommerce, and most headless stacks. Budget 1-2 days of engineering to wire the gateway correctly: tokenization flow, 3DS enrollment, descriptor configuration, webhook handling for captures/refunds/disputes. The gateway doesn't determine approval; it determines how the integration will feel to run long-term.

Avoid custom-built payment forms for SARMs. Use hosted tokenization (Authorize.net Accept.js or NMI CollectJS) to keep PCI scope at SAQ-A. A SARMs startup running PCI-DSS Level 2 audits because they built custom card capture is burning $15-20K/year unnecessarily. See PCI scope reduction for high-risk operators.

When to think about multi-brand structure

If your startup plan is one SARMs brand, one MID is fine. If you're planning 2-3 brands (one for retail, one for wholesale, one for a related vertical like peptides), set up the parent account + orchestration structure from day one. Adding brand #3 to a single-brand MID is painful; starting with parent-account architecture lets you add brands in days instead of weeks. We build this for operators reaching 3+ brands. See the multiflow architecture.

Talk to the underwriting desk

If you're launching a SARMs startup and want the clean path to a first merchant account, submit an application with basic info on your operation, product line, and projected volume. We'll map you to the right specialist ISO for a single-brand startup, or onboard you to the multiflow parent architecture if you're planning multi-brand from day one. Free consult, no contract.

See also SARMs operator playbook.