10 min read ·

Stripe alternatives for high-risk stores, and when to keep Stripe

Picture a research-use-only (RUO) peptide store whose only payment account closes on a Tuesday. The payout in transit is held. Stored cards for repeat customers are stuck with the old provider, and checkout throws errors by lunch.

Work out your own number: take your monthly card sales and divide by 30. That is roughly what every day without a working route costs, and with a single account the owner has no second route to switch to.

That is why stripe alternatives are a stack design problem, not a fee comparison. Our view is simple. Keep Stripe where it fits, add a separately underwritten second route, and set up automatic fallback between them. Peptide Marketing HQ builds that setup for RUO stores, and the rest of this post shows how to compare the pieces by role, written approval, reserves and termination terms.

Keep Stripe where it fits, add a second route

The decision most founders face is not Stripe versus everything else. It is where Stripe fits your catalog and where a second route should sit beside it. Stripe can be the right primary route for some stores, and the only answer that counts is its written answer for your catalog. Read Stripe's restricted businesses page yourself, save a dated copy, and judge your own catalog against it.

Our recommendation is direct. If Stripe has approved your exact catalog and claims in writing, use it as a primary route and add a backup anyway. If its page names your category, or support will not give you a written answer, skip it as your primary and build around a provider that will.

A closure costs more than the lost sales. Funds can sit for a while after an account closes, because card disputes can arrive well after a sale and providers often hold money against that window. Check your provider's own terms for how long they hold funds.

Subscriptions stop taking payments, since stored payment methods belong to the provider, and moving them needs the old provider's cooperation. Then comes the new application, which takes days at best. So ask which route is underwritten for your actual products and claims.

A checkout API with the lowest headline rate means nothing if the account is closed in month four.

The target setup has three parts:

  1. A primary route that fits your category.
  2. A second route that is separately underwritten, with its own approval.
  3. Automatic fallback between the two on decline or outage.

We build this for peptide stores on peptide payment processing, including the orchestration layer that switches routes.

If you have already been shut down, read what to do after PayPal or Stripe drops a peptide store. This post covers planning the stack, not recovering from a closure.

Four types of Stripe alternatives, compared by policy

Policy pages change, so read each provider's page on the day you apply and keep a dated copy. We do not quote specific reserve percentages, payout delays or chargeback thresholds here, because those terms differ by provider and by merchant. Treat your written quote and the provider's own policy page as the only numbers that count.

Payment stack options compared by role: mainstream processor, high-risk merchant account, gateway, ACH and backup route

  • Rolling reserve: some quotes hold back a share of processed volume for a set period. The percentage and the length of the hold are written into your quote, so get both in writing and compare them across providers.
  • Payout delay: standard accounts often pay faster than high-risk accounts, and a new high-risk account can start slower. Ask each provider for the payout schedule in writing.
  • Chargeback ceilings: card network monitoring programs flag merchants once their dispute ratio passes a set threshold, and the exact figures depend on the program and the date. Acquirers often set an internal limit lower than the network's, so ask for yours in writing.

Mainstream processors are the first type. WooPayments' prohibited and restricted products page lists "Peptides and other research chemicals" (page updated August 21, 2026, checked November 18, 2026), so that one is a named ban. Stripe's restricted businesses page (updated September 22, 2026), PayPal's acceptable use policy, Square's payment terms and the Shopify Payments eligibility page do not name peptides. Their lists cover research chemicals, prescription products or high-risk goods in broad terms, and whether RUO peptides fall inside is the provider's call. Search each restricted-business or acceptable-use page for "peptide," "research chemicals" and "unapproved drugs," then ask for a written answer.

Shopify deserves its own warning. Changing platforms does not by itself give you an independent route, so ask any platform's built-in payments team which processor sits behind it before you count it as a second route.

Option type Named examples Role in the stack Who underwrites the risk Ask for in writing
Mainstream processor Stripe, Square, Braintree, PayPal, WooPayments Bundled gateway and acquiring The provider, against its published restricted list Your exact catalog accepted, not just "ecommerce"
High-risk merchant account via an ISO See our processors guide Acquiring relationship The acquiring bank, reached through the ISO Named approval for RUO peptide sales, reserve and notice terms
Other gateway NMI, Authorize.net Technical connection to an acquirer Not the gateway; the merchant-account provider behind it Which acquirer sits behind it and who holds funds
ACH or eCheck Specialist ACH providers Bank-debit payment rail The ACH provider and its originating bank Return handling, authorization records, category acceptance
Second processor behind orchestration Any approved acquirer from the rows above Backup route A second, separate acquirer Its own approval, fallback rules, refund mapping

We name no ISOs in the table on purpose. ISO acceptance is decided per application by the acquirer, so a brand name beside "accepts peptides" would be a claim we cannot source. The vendor shortlist and how to compare quotes live in our guide to the best high-risk payment processors. This post stays on option types.

What are you really signing with a high-risk account?

Gateway versus acquiring bank

A gateway is the technical connection between your checkout and the card networks. The acquiring bank takes the underwriting risk. Authorize.net and NMI are gateways, so neither one approves your product category by itself. The merchant-account provider behind the gateway makes that call.

An ISO is a sales and servicing layer between you and the bank. It can be a fine route. The questions that matter are whose name is on the merchant account, who holds your reserves, and what the contract says about leaving. Those terms matter more than the quoted percentage.

The quote-comparison checklist

Put these items side by side for every quote:

  • Rolling reserve size and release schedule
  • Payout timing
  • Termination and notice language
  • Chargeback thresholds and fees
  • Personal guarantee requirements
  • Early termination fees
  • What happens to unsettled funds if the account closes

Reserves, rolling terms, chargeback history, ticket size and fulfillment model all change quotes. A higher rate with clear terms can cost less than repeated shutdowns and forced migrations.

Ask the plain question

Ask every provider whether they will underwrite RUO peptide sales. Get the answer in writing. We never obscure the product type from a processor, a platform or an underwriter, and we do not help anyone who wants to. A friend's merchant account is not an option either.

Where ACH and a second route earn their place

ACH and eCheck are an extra rail, not a workaround. Specialist acceptance, return handling and authorization records still apply. Bank-debit returns still arrive. The provider still underwrites you.

Checkout routing diagram with a primary card route, a second underwritten route and automatic fallback

How a second route behaves on WooCommerce

On a WooCommerce store, the primary route takes the order first. If it declines for a technical reason or goes down, the order retries on the second route. Four things need care:

  • Tokens and subscriptions. Stored payment methods usually belong to one provider, so recurring orders need a plan for each route.
  • Webhooks. Each route sends its own events, and your store must handle both.
  • Refunds. A refund has to go back through the route that took the payment.
  • Reconciliation. Your books need to match payouts from both routes.

Limits you should accept

More routes do not fix a bad chargeback ratio. Visa's VAMP ratio and the other network monitoring programs still apply to every route you run. Splitting volume to dodge monitoring is off the table, and we refuse to build it.

Fallback logic breaks in predictable places: mismatched billing descriptors, missing refund mapping and duplicate captures when a retry fires after a slow response. We test each of these in sandbox before a store goes live.

What do underwriters ask for before they approve you?

Expect an application pack. Have these ready:

  • Product catalog with labels
  • A claims review of the whole site
  • Ownership documents
  • Bank statements
  • Fulfillment evidence
  • Refund and shipping terms
  • Chargeback controls

A compliant store clears this faster. Clear RUO positioning, no human-use claims, consistent billing descriptors and accurate policy pages give the underwriter fewer reasons to hesitate. That is why we run a compliance review and a descriptor audit before an application goes out. Peptide website design and payment setup are one job for us, not two.

Build the dispute file early

Disputes arrive eventually, and a backup processor is only half the plan. Keep this evidence for every order:

  • Label and lot or COA records
  • Delivery proof
  • Customer communications
  • The refund policy the customer accepted
  • Authorization records

Use AVS, CVV and 3-D Secure where your provider supports them. Store the file by order number so you can answer a dispute without hunting.

The clinic and telehealth branch

Clinics and telehealth brands follow a different path. LegitScript preparation, licensed clinicians, disclosures and state coverage form a separate underwriting route from RUO supply. LegitScript is for clinics and telehealth brands, not for RUO suppliers. Certification also does not guarantee approval from every processor. RUO suppliers and clinics should not share one generic processor list.

Choose your stack and migrate safely

Match the plan to your situation:

  • Stripe already fits your catalog. Stay, and add a second route as insurance.
  • You sit in a restricted category. Add a second underwritten route before you need it.
  • Your catalog falls outside what mainstream providers accept. Build a primary high-risk account plus a backup, and treat Stripe as optional.

The migration order for a WooCommerce store is:

  1. Get written approval first.
  2. Set up the gateway.
  3. Test checkout, failed payments and refunds in sandbox.
  4. Run both routes in parallel.
  5. Move traffic over gradually while you watch declines.

Four mistakes come up repeatedly. People move everything in one weekend. They rely on a single new account. They skip written confirmation. They run orders through someone else's merchant account.

There is no universal best among stripe alternatives. There is only a stack whose providers have approved your actual business. We cover the whole chain with one accountable team: a compliant site built for underwriting review, high-risk payment processing with a backup route, SEO, email, labels and packaging.

If you want a second pair of eyes first, request our free store audit, or read how we set up peptide payment processing with automatic fallback.

Research notes last updated November 18, 2026.

Frequently asked questions

What is the best Stripe alternative for a high-risk store?

There is no single best option. The right one is whichever provider has approved your specific catalog in writing, with reserve and termination terms you can live with. Compare by role (acquirer, gateway, rail, backup) before you compare rates.

Can I just switch to Shopify Payments instead of Stripe?

Not automatically. Shopify Payments has its own eligibility rules, and the processor behind it may be one you already use. Ask which processor sits behind it, and get written approval for your catalog, before you count it as an independent route.

Is a gateway the same as a merchant account?

No. The gateway is the technical connection to the card networks. The merchant account sits with an acquiring bank, which takes the underwriting risk. Authorize.net or NMI will not approve your category on their own.

Can ACH replace card payments for my peptide store?

It can add a rail, not remove every problem. Returns, authorization records and provider underwriting still apply. Most stores use ACH or eCheck beside a card route.

Do clinics and RUO suppliers use the same processors?

They should not assume so. Clinics and telehealth brands follow a healthcare-focused path with licensing, disclosure and state coverage questions. RUO suppliers need written approval for research-use-only sales.

Free store audit

Find out what is putting your store at risk.

Payments, website, compliance and rankings reviewed by a person, with a written fix list and a 30-minute call.