Chargebacks and Processor Redundancy for Peptide Stores

Written by

in

Peptide chargebacks are the most common reason a research-use-only (RUO) peptide store loses its ability to take cards. A few dozen disputes in a month can move a small merchant from normal processing to a reserve, a monitoring programme or a closed account. This guide is for owners and marketers of RUO peptide stores. It explains why the category is underwritten as high risk, how the Visa and Mastercard monitoring programmes count disputes in 2026, what causes disputes, how to prevent and contest them, and how to build a backup payment stack that every provider knows about. It is general information, not financial or legal advice.

Key takeaways
  • The networks count, they do not judge. Visa and Mastercard programmes are triggered by ratios and counts. Winning a dispute later does not remove it from the count.
  • Visa now counts fraud reports too. The Visa Acquirer Monitoring Program (VAMP) adds fraud reports and disputes together. The merchant “Excessive” line is 1.5% in the US, Canada, the EU and Asia Pacific since 1 April 2026.
  • Mastercard’s line is also 1.5%, with at least 100 chargebacks in the month, measured against the previous month’s transactions.
  • Your processor will act long before the network does. Most small stores never reach the network minimums. They meet their processor’s own risk limits first.
  • Most prevention is plain operations: a recognisable descriptor, prompt order and shipping emails, a refund policy people can find, and fast refunds.
  • A backup processor is sensible. A hidden one is not. Every provider should get the same accurate description of what you sell.

1. Why peptide merchants are underwritten as high risk

A payment processor is financially responsible for the merchants it boards. If a store cannot cover its chargebacks or network assessments, the processor and its acquiring bank pay. Underwriters therefore price two things: how likely disputes are, and how likely the business is to breach a rule the processor answers for. RUO peptides score poorly on both.

  • The product category is written into restricted lists. Stripe’s restricted businesses list does not name peptides, but it prohibits incorrectly labelled research chemicals, card-not-present prescription-only products and pharmaceuticals, and pseudo-pharmaceuticals that are unsafe or make harmful claims. PayPal’s Acceptable Use Policy prohibits products that present a risk to consumer safety. Shopify Payments lists pseudo-pharmaceuticals. An underwriter reads your site and decides which side of those lines you fall on.
  • The card networks treat nearby categories as high risk. Visa’s Merchant Data Standards Manual lists card-absent merchants under the drug category codes 5122 and 5912 as high-integrity risk. Mastercard’s Security Rules and Procedures require acquirers to register non-face-to-face pharmaceutical merchants. Neither document mentions research peptides. The point is that acquirers are cautious about anything that sits close to those categories.
  • Regulatory action is visible. The FDA has sent warning letters to peptide sellers in 2026, and processors read the same letters you do. Our RUO website compliance checklist summarises what those letters cited.
  • Sales are card-not-present and shipped. Every order can be disputed as fraud or as not received.
What this means in practice

Expect a longer application, requests for supplier documents and certificates of analysis, a review of your website, higher fees than a low-risk store pays, and possibly a reserve. Those terms are the cost of an account that knows what you sell. An account opened under a vaguer description is cheaper only until its first review.

2. How Visa and Mastercard monitoring works in 2026

Both networks run programmes that identify merchants with too many disputes. They work differently, and both changed recently.

Visa: the Visa Acquirer Monitoring Program (VAMP)

Visa’s VAMP fact sheet describes one global programme that consolidates the earlier Visa Dispute Monitoring Program and Visa Fraud Monitoring Program. Three features matter to a merchant.

  • One combined ratio. The VAMP ratio is the count of fraud reports (which Visa calls TC40) plus the count of disputes (TC15), divided by the count of settled card-not-present transactions. It is based on counts, not value.
  • Fraud is counted even without a chargeback. A fraud report from an issuer adds to the numerator on its own. Stripe’s documentation notes that a payment with both a fraud report and a dispute is counted twice.
  • The merchant line dropped in 2026. A merchant is “Excessive” at a ratio of 1.5% or more with at least 1,500 fraud reports and disputes in the month. In the US, Canada, the EU and Asia Pacific that line was 2.2% until 1 April 2026.

VAMP also measures the acquirer’s whole portfolio. Visa’s fact sheet sets “Above Standard” at 0.5% and “Excessive” at 0.7% for acquirers. This is why your processor cares about your ratio long before you reach 1,500 items: every dispute you receive counts against its own number. Stripe’s documentation, for example, describes a lower tier at a ratio of 0.5% that may attract fees.

Visa’s fact sheet says disputes resolved through pre-dispute solutions are excluded from the ratio. Processors describe the details differently, so ask yours exactly which resolutions it excludes. Visa does not publish its fees in the fact sheet. Checkout.com’s VAMP article reports a fee of USD 8 per fraud or dispute item for Excessive merchants. Your own processor’s pass-through may differ.

Mastercard: the Excessive Chargeback Program (ECP)

Mastercard’s Security Rules and Procedures define the ratio: chargebacks received in a month divided by Mastercard transactions in the preceding month. Mastercard keeps the thresholds in a manual that is not public, so the figures below come from Stripe’s documentation.

Programme and tierRatioMinimum monthly countWhat is counted
Visa VAMP, merchant Excessive (US, Canada, EU, Asia Pacific, Latin America)1.5% or more1,500 fraud reports plus disputesFraud reports plus disputes, over settled card-not-present transactions in the same month
Visa VAMP, merchant Excessive (Central Europe, Middle East and Africa)2.2% or more150, and at least USD 75,000As above
Mastercard Excessive Chargeback Merchant (ECM)1.5% to 2.99%100 to 299 chargebacksChargebacks this month over transactions in the previous month
Mastercard High Excessive Chargeback Merchant (HECM)3% or more300 or more chargebacksAs above
Mastercard Excessive Fraud Merchant (EFM)Fraud chargebacks above 0.50%1,000 e-commerce transactions and more than USD 50,000 in fraud chargebacksFraud chargebacks only, where few payments use 3-D Secure

Sources: Visa VAMP fact sheet and Stripe monitoring programmes documentation, read 16 November 2026. Some countries have different figures. Confirm the current numbers with your processor.

Stripe’s page lists Mastercard assessments that start at USD 1,000 in the second month in the programme and rise the longer a merchant stays. It also says a merchant leaves after three consecutive months below the thresholds, and that refunds and dispute wins do not reduce the count.

A change to watch

A Checkout.com merchant notice dated 19 August 2026 says Mastercard will introduce a Global Merchant Audit Program on 1 April 2027, with new dispute monitoring for merchants. We did not find a public Mastercard document confirming the detail. Ask your processor what will apply to your account.

The MATCH list

If an acquirer closes your account for certain reasons, it must add you to Mastercard’s MATCH Pro database. The Security Rules say acquirers must check it before signing a merchant, and that records stay for five years. Excessive chargebacks is one listing reason. Transaction laundering is another. A listing makes a new card account very hard to get, which is the practical reason to manage disputes early.

3. What causes chargebacks in this category

In the US, a cardholder can dispute a billing error within 60 days of the statement, and the FTC’s consumer guidance lists goods not delivered as agreed as one such error. Network rules give issuers longer. Stripe says networks typically allow 120 days. Most peptide disputes fall into three groups.

Unclear billing descriptors

The buyer sees a name on the statement that they do not connect with your store. This often happens when the legal entity name differs from the brand, or when a store deliberately uses a vague name. The buyer, or a partner who shares the account, reports it as fraud. Under VAMP that single event can produce a fraud report and a dispute.

Shipping delays and silence

Stock gaps, cold-chain holds, customs and carrier delays are routine in this category. A late parcel becomes a dispute when the buyer hears nothing. The FTC’s Mail, Internet, or Telephone Order Merchandise Rule also applies to US sellers: you need a reasonable basis for your stated shipping time, or for shipping within 30 days if you state none, and if you cannot ship on time you must tell the buyer and offer a cancellation and refund.

Friendly fraud

Friendly fraud is a dispute from the real cardholder for a purchase they made. Causes include buyer’s remorse, a forgotten order, a family member’s purchase, or a wish to avoid the return process. Buyers in this category may also be reluctant to explain a purchase to someone else who sees the statement, which makes “I don’t recognise this” an easy answer.

True fraud and card testing

Stolen cards are used on any store with high-value, easily resold goods. Card testing, where a bot runs many small authorisations, is tracked separately by Visa as enumeration.

4. Prevention: descriptors, emails, refunds, alerts and 3-D Secure

Use a descriptor the buyer recognises

Stripe’s statement descriptor rules are a good reference even if you use another processor: 5 to 22 characters, reflecting the name you do business as, because clear descriptors can reduce chargebacks. Use your store’s brand name, and add a support phone number or URL where the processor allows it. Repeat the descriptor in the order confirmation email: “This charge will appear on your statement as…”.

A descriptor that hides the business from the cardholder or the bank causes disputes and is a form of misdescription. Do not use one.

Send order and shipping emails that answer questions before the bank does

  • Order confirmation within minutes: items, total, descriptor wording, expected dispatch date and a reply-to address someone reads.
  • Dispatch email with carrier and tracking link.
  • Delay email as soon as you know, with a new date and a one-click option to cancel for a refund.
  • Delivery confirmation, with the support contact repeated.

These are transactional messages and should stay free of product claims. Our peptide email marketing page covers how we build these flows within RUO framing.

Publish a refund policy people can find, and honour it quickly

State what can be returned or refunded, in what condition, within how many days, and how to ask. Link it in the footer, at checkout and in the confirmation email. When a customer is clearly heading for a dispute, a prompt refund is usually cheaper than the dispute: Stripe’s US pricing, for example, charges USD 15 for a dispute received and a further USD 15 if you contest it, and the dispute counts toward your ratio whether or not you win.

Use alert and order-detail tools

  • Verifi Rapid Dispute Resolution (RDR) is a Visa service that automatically refunds a pre-dispute according to rules you set, before it becomes a chargeback.
  • Verifi Order Insight shares order details with the issuer so the cardholder can recognise the purchase.
  • Ethoca Alerts, from Mastercard, notifies the merchant of a dispute early so it can refund first.
  • Ethoca Consumer Clarity shows recognisable purchase details in banking apps.

These tools cost money per alert and they trade a dispute for a refund. Check with your processor whether it supports them, and which resolutions it excludes from your VAMP count.

Turn on 3-D Secure where it makes sense

3-D Secure asks the issuer to authenticate the cardholder. Stripe’s documentation says that when an authenticated payment is disputed as fraudulent, liability typically shifts to the issuer. It does not cover other reasons, such as a product not received. Stripe also notes that Mastercard still counts liability-shifted chargebacks in its programme ratios. 3-D Secure adds a step at checkout, so many stores apply it by risk rule, for example to first orders above a set value.

Screen for obvious fraud

Require the card security code, use address verification, review orders where billing and shipping addresses differ, limit repeated attempts from one device, and consider signature on delivery for high-value parcels.

Marketing affects disputes too

A buyer who was promised an outcome and did not get it is a dispute waiting to happen, and outcome claims are a compliance problem in their own right. Accurate, claim-free product pages and ads produce buyers who know what they ordered. See our pages on Google Ads for peptides and Google Shopping for peptides, and Merchant Center recovery if a listing problem is already affecting orders. Earlier guides in this series cover claim-free product feed titles and recovering a suspended Google Ads account.

5. How to fight a dispute with evidence

Contesting a dispute means sending evidence through your processor to the cardholder’s bank. Stripe’s description of the process is typical: you usually have 7 to 21 days to respond, you get one submission, and the outcome is at the discretion of the cardholder’s bank. Deadlines vary by processor and network, so use the date shown on the dispute itself.

Match the evidence to the reason given. Stripe’s dispute categories guide recommends:

Dispute reasonEvidence that answers it
Product not receivedShipping address that matches a verified billing address, carrier name, tracking number, shipping date and delivery confirmation. Or proof that a refund was already issued.
FraudulentAddress and security-code match results, delivery proof and signature, and a history of earlier undisputed orders from the same customer.
Credit not processedThe refund policy text, how it was shown before purchase, and why the customer was not entitled to a refund. Or proof the refund was sent.

Visa Compelling Evidence 3.0

For Visa fraud disputes, Visa’s merchant readiness document sets out a specific test. You show two earlier transactions from the same customer, each between 120 and 365 days old and neither reported as fraud. At least two data elements must match the disputed order, from user ID, IP address, shipping address and device ID, and one of the two must be the IP address or device ID. Stores with customer accounts and repeat buyers can meet this if they log those fields. Visa’s fact sheet says fraud reports that qualify are excluded from the VAMP ratio.

Practical rules

  • Keep the response short and factual. A one-page summary followed by labelled evidence.
  • Send only your own records. Never alter a document or invent a delivery record.
  • Do not contest what you cannot evidence. If the parcel was lost, accept the dispute.
  • Do not refund a payment after it has been disputed unless your processor tells you to. The bank has usually already returned the money.
  • Log every dispute by reason, product, carrier and traffic source. The pattern is more useful than any single win.

6. Rolling reserves and what they do to cash flow

A reserve is money the processor holds back to cover future disputes and refunds. Stripe’s reserves FAQ describes it as a temporary hold on part of a business’s funds and lists reasons that include long delivery windows, elevated dispute activity and sudden unexplained growth in volume.

PayPal’s reserves article explains the common types:

  • Rolling reserve. A percentage of each day’s sales is held and released on a schedule. PayPal’s example is 10% held for 90 days.
  • Minimum reserve. A fixed balance must be kept. PayPal’s example is 5% of daily volume until USD 5,000 is reached.

Those are illustrations, not quotes for your account. High-risk agreements often carry larger percentages or longer periods, and the terms are set in the merchant agreement.

Planning for a reserve

Read the reserve clause before you sign: the percentage, the hold period, whether the processor may raise it without notice, and how long funds are held after the account closes. Model your cash flow with the reserve in place, including the cost of inventory you must buy while money is held. A sudden jump in sales after a promotion is a common trigger, so tell your processor before a large campaign.

7. Building a backup payment stack, honestly disclosed

No processor is permanent in this category. A portfolio review, a change of acquiring bank or a policy update can end an account that has done nothing wrong. Redundancy means a second account is already approved when that happens.

One accurate business description, given to every provider:
what you sell, RUO terms, website, volumes, dispute history
Store checkoutOne brand, one descriptor family, one refund policy
1. Primary processor
Card acquiringHigh-risk account underwritten for RUO peptides
  • Takes most card volume
  • Alerts and 3-D Secure enabled
  • Reserve terms known
2. Backup processor
Card acquiringSecond approved account with a different acquiring bank
  • Takes a steady share of volume
  • Told that a primary exists
  • Ready to take more
3. Alternative rails
Non-card paymentsEach within the provider’s own terms
  • ACH or bank transfer
  • Invoice for lab accounts
  • Crypto, where permitted
Monitor each account separately: dispute ratio, fraud reports, refund rate, reserve balance

How to build it

  • Apply to the backup while the primary is healthy. An application made after a termination is weaker, and you must answer truthfully if asked about one.
  • Use a different acquiring bank. Two sales agents that board to the same bank are one point of failure.
  • Tell both processors. Disclose that you hold another account and how you split volume. Give both the same product list, website and processing history.
  • Keep the backup active. Route a steady, modest share through it. An account that goes from nothing to full volume overnight invites a review and a reserve.
  • Do not use a second account to dilute a problem. Each merchant account is measured on its own. Fix the cause of the disputes.

Alternative rails

  • ACH or bank transfer. There is no card chargeback, but ACH debits can be returned. Nacha’s rules set an unauthorised return rate threshold of 0.5%, so ACH has its own monitoring.
  • Invoicing for institutional buyers. Labs and universities often prefer purchase orders and bank payment.
  • Cryptocurrency. The FTC notes that crypto payments are typically not reversible. That removes chargebacks but also removes a protection buyers expect, so your refund policy carries more weight. Use a provider whose terms allow your business, and take tax and legal advice.
What we will not help with

Describing the business to a processor as something else, such as supplements or cosmetics. Running sales through another company’s merchant account or a separate “clean” website. Splitting one business across shell entities to reset a dispute count. Mastercard’s rules require a merchant to submit only its own transactions, Visa’s Acceptance Risk Standards define transaction laundering as an unknown business using an approved merchant’s credentials, and MATCH has a listing code for it. These routes end in terminated accounts, held funds and a five-year listing. Our peptide payment processing page describes how we approach applications openly.

8. The monthly chargeback checklist

Run this every month
  1. Calculate both ratios per account. Visa: fraud reports plus disputes, divided by settled transactions this month. Mastercard: chargebacks this month divided by last month’s transactions.
  2. Compare against your processor’s limits, not only the network thresholds. Ask for those limits in writing if you do not have them.
  3. Sort disputes by reason. Fraud, not received, not as described, credit not processed.
  4. Check the descriptor. Look at a real statement or a test charge and confirm it shows your brand and a contact.
  5. Test the emails. Place an order and confirm that the confirmation, dispatch and delay emails send, and that replies reach a person.
  6. Measure support response time and refund turnaround. Set a target and record misses.
  7. Review late shipments. Confirm every delayed order received a notice with a cancellation option.
  8. Review alert and 3-D Secure performance. How many alerts arrived, how many were refunded in time, and what authentication did to approval rates.
  9. Reconcile the reserve. Confirm amounts held and released match the agreement.
  10. Check the backup. Confirm it processed volume this month and that its details on file are current.
  11. Confirm disclosures are still accurate. If your catalogue, website or volumes changed, tell each processor.
  12. Write down one cause to fix before next month, with an owner.

9. FAQ

What chargeback rate is too high for a peptide store?

Visa’s merchant Excessive threshold is 1.5% of card-not-present transactions, counting fraud reports and disputes together, in most regions. Mastercard’s Excessive Chargeback Merchant tier starts at 1.5% with at least 100 chargebacks. Processors usually set stricter limits of their own, so ask yours.

Why are peptide chargebacks treated more seriously than in other niches?

Processors already classify the category as high risk because it sits close to restricted product lists and has seen regulatory action. A dispute ratio that a low-risk store might survive can prompt a reserve or a closure for a peptide merchant.

Does winning a dispute remove it from my ratio?

No. Stripe’s documentation on the network programmes says refunds and dispute wins do not reduce the counts. Prevention and pre-dispute resolution matter more than representment for staying under thresholds.

Does 3-D Secure stop chargebacks?

It typically shifts liability for fraud disputes to the card issuer on authenticated payments. It does not cover disputes such as product not received, and Mastercard still counts liability-shifted chargebacks toward its programme ratios.

What is a rolling reserve?

A processor holds a percentage of each day’s sales and releases it after a set period. PayPal’s published example is 10% held for 90 days. Your percentage and period are set in your merchant agreement.

Can I have two payment processors at the same time?

Yes, and it is sensible in this category. Tell each processor about the other, give both the same accurate description of the business, and keep real volume on both. Do not use a second account to hide or dilute disputes.

Can I describe my store as supplements to get approved?

No. Misdescribing the business breaches the merchant agreement and can lead to termination, held funds and a MATCH listing that lasts five years. We do not assist with it.

Is this guide financial or legal advice?

No. It is general information about card-network programmes and processor policies. Thresholds and fees change, and your merchant agreement governs your account. Take advice from a qualified professional.

Need a second opinion?

Talk through your dispute numbers and payment setup

Peptide Marketing works only with research-use-only peptide brands. We will look at your dispute reasons, your descriptor and order emails, and the marketing that brings in your buyers, and tell you what to fix first. We do not help misdescribe a business to a processor.

Book a 15-min call

Prefer email? Write to hello@peptidemarketing.info.

Sources

This guide is general information for businesses selling research-use-only products. It is not financial, legal or regulatory advice. Sources were read on 16 November 2026. Card-network thresholds, fees and processor policies change, and your merchant agreement governs your account. Check the linked pages and take professional advice before you act.

Comments

3 responses to “Chargebacks and Processor Redundancy for Peptide Stores”

  1. […] Google’s cross-domain measurement can join two domains into one session, but it needs the same Google tag on every domain involved. You rarely control a processor’s hosted page, so for most stores the practical tools are the unwanted-referrals list and a confirmation page on your own domain. For how processor choice shapes the checkout, see peptide payment processing and our guide to chargebacks and processor redundancy. […]

  2. […] Payment failed, bank-transfer instructions sent, password changed. See peptide payment processing and our guide to peptide chargebacks […]

  3. […] chargebacks guide covers dispute thresholds and backup processors, and our peptide payment processing page explains […]

Leave a Reply

Your email address will not be published. Required fields are marked *