SHORT ANSWER
A gateway account is not the decision that matters. Authorize.net describes itself as the technology in the middle; the merchant account that actually settles card sales is underwritten by an acquiring bank, and its underwriter reviews your industry. Whether a peptide store can process depends on that bank’s category policy and Visa’s acquirer rules, not on the gateway.
This material is general educational information as of the “last reviewed” date. It is not legal advice and may not reflect later developments or facts specific to your business. Links are provided so readers can inspect the primary or official sources.
01 / THREE PARTIES
Gateway, merchant account, and acquirer are different things
Authorize.net’s own explainer lists the parties in a card sale: the customer, the merchant, the issuer, the acquirer, and the gateway. It describes the gateway as the piece that “sits in the middle” and “connects all the key players.” The acquirer is “the bank where you have your merchant account.”
Its pricing page draws the same line. A gateway is “the technology that securely transmits payment data”; a merchant account is “the bank account that holds your funds after a transaction is approved.” Two products, two decisions.
The distinction matters for a peptide seller because the gateway carries the data and the merchant account carries the risk. Only one of them has an underwriter.
03 / THE ACQUIRER’S RULES
The bank answers to Visa’s acquirer rules
Authorize.net is a Visa company, and the bank behind any merchant account it arranges operates under Visa’s acquirer requirements. Visa’s Online Pharmacy Guide for Acquirers (June 2016) states that Visa “requires that acquirers register with Visa Inc. to receive a High Brand-Risk Acquirer license” before boarding a card-not-present internet pharmacy merchant.
The same guide tells risk teams not to judge these merchants by dispute history: “the absence of an intellectual property violation or chargeback does not establish its legitimacy.” That is the bank’s instruction from the network, and it explains why a clean processing record does not settle the category question.
The guide is written for pharmacies, not peptides. It is cited here for what it shows about how acquirers are told to think: category first, evidence of legitimacy second, chargebacks last. A storefront that sells peptides with human-use context on the page is the kind of merchant that guidance was written to catch.
- The acquirer assigns the merchant category code, and Visa can require it to be corrected (see the merchant category codes guide).
- High brand-risk registration is the acquirer’s obligation, and it is a cost and a review burden the bank weighs before boarding.
- The gateway does not change any of this; it transmits whatever the merchant account is permitted to process.
04 / RESELLER CLAIMS
“Authorize.net accepts peptides” is half a sentence
Payment resellers and high-risk brokers often advertise Authorize.net integration as though the gateway were the approval. Read against Authorize.net’s own description, the claim only says the gateway can be connected to a merchant account. It says nothing about which acquirer will open that account for a peptide storefront, on what terms, or for how long.
The honest version of the sentence is: Authorize.net’s Gateway Only plan can sit in front of a merchant account from a bank that has agreed to board the business. Whether such a bank exists for a given storefront depends on the storefront, the bank’s category policy, and the network registration the bank must carry.
The same logic applies to any gateway. The three-party structure is not an Authorize.net quirk; it is how card processing works.
05 / BEFORE YOU APPLY
Make the underwriter’s first factor easy to answer
The underwriter looks at your industry first, and it reads your industry off your storefront. Product names, descriptions, imagery, bundled supplies, and testimonials are what a bank sees when it decides which category you are in. That review happens before, and independent of, any gateway setup.
- Confirm which merchant account will sit behind the gateway and which bank underwrites it.
- Ask that bank, not the gateway, whether research-use peptide sales are within its category policy.
- Review the storefront for human-use context before any application is filed.
- Keep the evidence of what was changed, so the application describes the business as it is.
QUESTIONS
Related questions
Is a gateway account the same as being approved to process?
No. In Authorize.net’s own terms, the gateway transmits payment data and the merchant account holds funds. The merchant account is the one that an acquiring bank underwrites, and that underwriting includes your industry.
Does Authorize.net publish a list of prohibited businesses?
Not on its public site as of September 3, 2026. The Terms of Use defer to a service agreement that is not posted. Category restrictions are applied by the acquiring bank under its own policy and Visa’s acquirer rules.
If a broker says Authorize.net works for peptides, is that true?
It can be true of the gateway and still say nothing about the merchant account. Ask the broker which acquiring bank will underwrite the account and what that bank’s written category policy says.
SOURCES
Sources cited
Each source is listed with its class so government authority, agency guidance, enforcement examples, and private policy are never blended into one rule.
Defines the gateway, the acquirer, and the underwriting factors an acquirer considers, beginning with industry. Read September 3, 2026.
Distinguishes gateway from merchant account, describes All-in-one and Gateway Only plans, and the Merchant Service Provider’s role. Read September 3, 2026.
Site terms; states that the applicable Service Agreement governs in a conflict. No public restricted-business list. Read September 3, 2026.
High Brand-Risk Acquirer license requirement for card-not-present pharmacy merchants; absence of chargebacks does not establish legitimacy. Cited as acquirer guidance, not a peptide rule.