Most peptide processors will decline you. Their websites won't tell you that.
The RUO Payment Processing Field Guide
We screened ~28 payment processors for a research-use-only catalog: WHOIS records, ISO/MSP disclosures, BBB profiles, live application flows, card-network documentation. Here is what actually underwrites RUO, what quietly auto-declines it, and the three questions that end a dead-end conversation in one email.
What's in it
- Why “peptide-friendly” almost always means prescription peptides and how to tell which one you are looking at in 30 seconds.
- The merchant category code that is correct for RUO and why the “safer” codes are how merchants end up MATCH-listed.
- The one-line disclosure card-brand rules require and how many of the ~28 processors we screened actually publish it.
- When LegitScript is genuinely required and when you are being upsold something your model cannot use.
- A ten-minute screening method, with the exact commands so you can run it yourself on any processor before you take a call.
- The storefront conditions sponsor banks enforce at review as a pre-application checklist, including the two that catch people out.
- Reserve, funding, and contract benchmarks including the two terms to get in writing every time.
No processor named in this guide sponsored, reviewed, or endorsed it. No referral relationships with any vendor discussed. Every claim was verified against primary sources on 11 August 2026, and section 5 shows you how to re-verify all of it yourself.
Already past the processor question? What your processor needs before they will approve you goes deeper on the file itself, and rolling reserves covers what the hold does to working capital.