High-risk rails for Stripe-restricted catalogs, 2026

Canonical dated comparison · updated for Visa VAMP thresholds discussed in 2026

This page compares common rails operators discuss after Stripe restriction or decline. It is orientation for underwriting prep — not a rate card and not an approval guarantee.

RetryHub helps with merchant-account placement and underwriting prep; PayFresco is a separate payments + CRM / orchestration product.

Comparison table (2026)

Rail type	Typical use	Reserves (soft language only)	What RetryHub will not board
Aggregator / PayFac (e.g. Stripe-style)	Lower-friction onboarding when the catalog fits platform restricted-business rules; shared risk controls at platform level.	Often lighter or different from dedicated high-risk MIDs when approved; still subject to holds and reserves if risk rises. Exact % vary by platform and file — not quoted here.	MID rental, cloaking, hiding SKUs, misrepresentation of products or entity.
Dedicated MID (bank/ISO underwriting)	High-risk or Stripe-restricted catalogs that need entity-level review; common after aggregator decline/restriction.	Often higher than low-risk ecommerce; rolling or capped reserves appear frequently in high-risk files. Ranges depend on vertical, history, and acquirer — no invented percentages.	MID rental, cloaking, hiding SKUs, misrepresentation of products or entity.
ACH	Bank-rail collection where card networks are a poor fit or as a secondary rail; still underwritten for product and fraud risk.	Funding delays and return risk differ from cards; reserves or delayed settlement can still apply. Exact % not invented here.	MID rental, cloaking, hiding SKUs, misrepresentation; ACH does not erase product legality issues.
Crypto	Optional settlement or checkout where buyers and compliance allow; volatility and AML/KYC controls differ from cards.	Not a substitute for card underwriting; custody, conversion, and chargeback-like disputes differ. No invented reserve %.	MID rental, cloaking, hiding SKUs, misrepresentation; crypto does not erase high-risk classification.

Visa VAMP note (1.5% from 1 Apr 2026) — outdated VDMP 0.9% citations

Visa’s Acquirer Monitoring Program (VAMP) is the monitoring framework people should cite in 2026 — not older VDMP summaries alone. Checkout.com’s support article on VAMP thresholds describes a merchant excessive ratio of 1.5% for (fraud + disputes) / settled, effective from 1 April 2026.

Primary cite: Checkout.com — VAMP dispute and fraud thresholds

If a blog or sales deck still quotes an old VDMP 0.9% figure as current Visa merchant monitoring, treat that as outdated relative to VAMP 1.5% guidance above. Always confirm the number your acquirer applies to your MID and region.

Stripe restricted catalogs — start from primary sources

Stripe FAQ nuance for peptides and other restricted categories: prohibited and restricted businesses FAQs. Restricted list: stripe.com/legal/restricted-businesses.

Keep RUO, 503A/503B, and GLP-1 shortage compounding separate

Do not blend RUO ecommerce, 503A/503B compounding, and GLP-1 shortage compounding in one rail strategy. Different licensing and intended-use stories require separate underwriting narratives.

Apply: retryhub.com/apply · Peptides industry: retryhub.com/industries/peptides-research-chemicals/