The gateway holds the authorization. WooCommerce holds the order. The support inbox holds a message from the same customer asking about returns. When that customer files an "unauthorized" dispute, nobody owns one joined record, and the clock is already running.
Response windows vary by network and processor, and some processors also place a reserve on the account while a dispute is open. Confirm the exact deadline and any hold terms with your own processor, and ask for the date on every case.
By the time someone has exported the gateway data and searched the mailbox, the store has lost a case it should have won. The evidence was there all along: earlier undisputed orders from the same customer and a signed delivery are exactly the kind of proof that wins, but only if someone assembles it before the deadline.
Visa calls this pattern first-party misuse, and we use that term and "friendly fraud" interchangeably. A customer gets the order, keeps it, and then tells the bank something else happened. Our position is simple. Friendly fraud is an operations, evidence and processor-continuity problem.
Build the record at checkout, refund honestly when the fault is ours, and fight only when the records match the claim. Never change a product page or a disclaimer to win a case.
At Peptide Marketing HQ we build WooCommerce stores and payment routes for research-use-only suppliers, so this is the process we hand founders.
Friendly fraud or something else?
Friendly fraud is a cause of disputes, not another word for chargeback. A chargeback is the mechanism. The cause might be a stolen card, our own mistake, or a customer who received the order and disputes it anyway.
A dispute costs more than the order. There is the dispute fee your processor charges, the staff time to build a response, and the effect on your dispute ratio. We come back to that cost when we decide between refunding and fighting.
A decision tree before any evidence
Ask these in order. Stop at the first yes.
- Did a stranger use the card? That is stolen-card fraud. We accept it or investigate it. A matching AVS or CVV result does not prove the cardholder placed the order.
- Did we ship the wrong item, ship late, or not ship? That is merchant error. We refund and fix the process.
- Was one order charged twice? That is duplicate billing. We refund.
- Did a cancelled subscription bill again? That is our billing error. We refund.
- Is the complaint about the product or delivery, and is it reasonable? That is a valid complaint. We handle it through support.
- Did we fulfill correctly, bill once, and do the records show the buyer made or accepted the order? Only this one is first-party misuse.
If the cause is on our side, evidence is not the fix. We cover general chargeback basics in our earlier post on peptide chargeback prevention and do not repeat them here.
The patterns that show up in peptide stores
Think of these patterns as a diagnostic tool. Each one looks different in the order record, and that difference tells us what to do. The example records below show which fields expose each pattern.

“I don’t recognize this charge”
Three causes sit behind this line, and the order record separates them.
- Descriptor problem. The statement shows a name the buyer does not connect to our brand. The account email, billing name and shipping address all match, and the buyer has no prior support contact. Example record: first order on the account, a descriptor that shows only a parent company name, and no device match to any other account. This is partly our failure.
- Shared household card. The cardholder name differs from the customer account name, or someone else in the home placed the order. Example record: billing name differs from the account name, shipping address matches the cardholder's address, and no support contact exists. This is a gray area, and we should not call it fraud by the buyer without proof.
- Buyer's remorse. The buyer asked about returns or changes before the dispute, or has ordered before from the same device. Example record: same device fingerprint as three prior orders, plus a support email asking about returns two days before the dispute. Contact history is the giveaway.
“Item not received” when tracking says delivered
Porch loss, a family member who signed, and a genuine misdelivery all produce this claim. Example record: delivery scan with a signature, a ship-to address that matches the billing address, and a photo at the door. That file supports a fight. A misdelivery is not fraud at all.
If the carrier's scan data points to a different address or a bad location, we reship or refund and file with the carrier.
Cancelled-recurring and duplicate charges
These are usually our own billing mistakes. A renewal ran after cancellation, or a retry fired twice. Example record: a cancellation timestamp that sits before the renewal charge. We refund them and fix the cause.
Every pattern lands in a dispute reason category, such as unauthorized use, goods not received, cancelled recurring transaction or duplicate processing. Exact codes and names vary by network, so check each network's published list. What matters is that our evidence answers the exact allegation. Delivery proof does nothing on its own against an unauthorized-use claim, because the buyer is not saying the box never came.
Build the evidence file at checkout
The record has to exist when the order happens. Rebuilding it weeks later from a gateway export and a mailbox search is how cases get lost.
One case file per order
In WooCommerce, we want one record that joins these fields:
- Order ID and the gateway transaction ID
- Authorization result, plus AVS and CVV outcomes where lawfully available
- Customer account and order history
- IP and device signals captured at checkout
- Fulfillment event and tracking, including the delivery scan
- Support history and any refund record
- Accepted policy version and the timestamp of acceptance
Installing a random fraud plugin and hoping is not the plan. The processor, gateway, store database, fulfillment system and inbox need to produce one coherent file. Our WooCommerce builds write these fields to the order at creation, and our peptide payment processing work makes sure the gateway IDs line up with them.
What each claim needs
- Unauthorized: authentication result, account history, device and IP match, and prior undisputed orders. Tracking is irrelevant here.
- Item not received: tracking, delivery scan, address match and carrier proof. Authentication data adds little.
- Cancelled recurring: consent record, renewal notice, cancellation timestamp and refund history.
- Duplicate processing: two separate order IDs and two separate fulfilled shipments. If we cannot show that, we refund.
Peptide-specific records to freeze
Preserve a snapshot of the product page as it stood on the order date. Keep the research-use-only disclaimer, the terms accepted at checkout, the label or packaging representation, the shipping policy and the compliance version in force. Never edit the site after a dispute to improve the evidence. An edited page is a worse exhibit than an imperfect one, and it can read as concealment to an acquirer.
Visa's guidance says 3-D Secure can create a useful authentication trail. It does not guarantee a win. Delivery confirmation alone is also thin when the buyer disputes the address.
Should we refund, accept, or fight the dispute?
We triage every case with one question. Did our process contribute? If shipping, billing, cancellation or compliance played any part, we refund or accept. If the evidence matches the claim and the order was ours to defend, we consider fighting.

When fighting makes sense
The order was fulfilled, the claim conflicts with credible records, and the file answers the allegation directly. A buyer who disputes as unauthorized after a signed delivery, a matching device, and three earlier undisputed orders is the clearest example.
When a refund comes first
The best time to decide is before any chargeback exists, when a customer complaint or a pre-dispute alert reaches you first. Use one rule. If our process contributed, refund. If it did not and the order value is below your own cost to respond, refund anyway. Above that line, let the case go to a dispute only when you have real evidence, such as proof of delivery and a clear policy the customer accepted.
Your cost to respond is staff time plus the dispute fee your processor charges. Pull that fee from your processor's fee schedule and write the number down.
For many stores, a low-value order costs more to defend than to refund.
Pre-dispute alert programs are the mechanism that makes an early refund work. Verifi's Cardholder Dispute Resolution Network (CDRN) and Rapid Dispute Resolution (RDR), and Ethoca Alerts, tell the merchant or act on its rules when a cardholder questions a charge, before a chargeback exists.
The merchant refunds, the issuer closes the inquiry, and no chargeback is created. That means the case never enters your chargeback count. The provider charges a per-alert or per-resolution fee instead, and your processor sets that fee, so ask for it in writing.
These programs are enrolled through your processor or gateway, so ask which ones it supports.
Once the chargeback is filed, a refund no longer ends the matter. The funds have already been debited, and the chargeback sits in your count with its fee. A separate refund on top can leave the buyer paid twice. So after filing, we have two options: accept the dispute, or respond with evidence through the processor.
We never fight a legitimate refund, duplicate charge or fulfillment failure. We never disguise what was sold, and we never soften a disclaimer to help a case. Evidence cannot repair a misleading transaction.
What a good response looks like
Write one clear page tied to the specific reason code, with exhibits numbered in the order the page cites them. No padding, no screenshots of unrelated chats, and no argument about the customer's character. Here is a skeleton for an unauthorized-use claim:
- Rebuttal, one sentence. "The cardholder's account placed this order from a device and IP address seen on three earlier orders, and the order was delivered with a signature."
- Exhibit 1. Authorization record with AVS and CVV results.
- Exhibit 2. Device and IP match between this order and the account's history.
- Exhibit 3. Three prior undisputed orders on the same account, with dates and amounts.
- Exhibit 4. Signed delivery scan with the ship-to address.
- Exhibit 5. The refund policy version accepted at checkout, with the acceptance timestamp.
Response deadlines differ by network and processor, and some processors set an earlier internal cutoff. Ask your processor for the exact date on every case, and file before it.
Stop friendly fraud before it starts
Most of the work happens before anyone calls a bank. This is the sequence we set up:
- A recognizable billing descriptor. It should match the brand on the site and the packing slip. We cover this in our post on the billing descriptor.
- Order and shipping notifications. Confirmation, fulfillment notice, tracking and a delivery message.
- Signature or photo delivery for larger orders. The cost is small next to a lost non-receipt case.
- Easy cancellation. No hunting for a hidden link.
- 3-D Secure where it fits. It adds an authentication trail for unauthorized claims.
- A refund policy accepted at checkout and logged with the order. The policy version becomes evidence later.
Early-resolution tools
Visa publishes pre-dispute guidance that urges merchants to resolve issues before they become chargebacks. Tools such as Verifi Order Insight share order details with the card issuer so a cardholder can recognize a purchase before disputing it. These are network and enterprise tools, and they are not automatically open to every small merchant. We ask the acquirer or payment provider what is actually enabled and on what terms.
A customer who can reach us in two minutes does not call the bank. So we publish a support email, a contact form and a stated response time, and we keep them. A buyer who waits three days for a reply has already started the dispute.
How disputes affect your payment account
For a high-risk peptide merchant, rising disputes cost more than the orders. They bring reserves, closer monitoring, underwriting reviews and, in the worst case, termination.
Two network programs set the outer limits, and each network publishes its own thresholds. Visa's Acquirer Monitoring Program (VAMP) counts fraud reports plus disputes against settled card-not-present transactions and rates a merchant against a ratio and a minimum monthly count. Visa's VAMP fact sheet lowered the US merchant threshold from 2.2% to 1.5% on April 1, 2026, and the threshold applies only at 1,500 or more fraud reports and disputes in a month. Our post on Visa VAMP explains how the ratio works.
Mastercard runs its own Excessive Chargeback Program, with a monthly chargeback count and a ratio that flag a merchant, and higher tiers above that. Its thresholds also change, so ask your acquirer for Mastercard's current figures in writing rather than relying on a number quoted second-hand.
A store at $5k to $100k a month rarely reaches Visa's 1,500-a-month floor. Your acquirer's contract bites first. Find three clauses in your merchant agreement: the chargeback ratio or "excessive chargebacks" clause, the reserve clause that says what triggers a rolling or fixed reserve, and the termination-for-cause clause.
Track against the ratios written in those clauses, and ask your underwriter in writing at what ratio the reserve is raised. We track dispute count, dispute rate, refund rate, fulfillment exceptions and representment results by processor and by month.
A remediation pack that gets read
If the processor asks questions, we send a pack, not an excuse. It contains:
- Dispute counts by cause, split into first-party misuse, merchant error and valid complaints
- Root-cause fixes already made
- Descriptor and policy changes, with dates
- Sample case files, one per claim type
A backup route through payment orchestration has specific parts. It means a second merchant account at a different acquirer, a second gateway connection, and a routing rule. The usual rule sends traffic to the primary route until a hold or a decline spike, then fails over to the second.
Setup takes real effort, including a second underwriting application and test orders on both routes. Both underwriters are told the product category, and every processor in the chain knows what we sell. The route exists so one account review does not stop the store.
It is never a way to spread disputes across accounts to avoid monitoring.
Before signing with any provider, ask these questions:
- Are the merchant accounts in our company's name, and who holds the gateway credentials?
- What exactly triggers failover, and can we see and change the rule?
- Do both routes show the same billing descriptor?
- How are fees, disputes and reserves reported for each route?
- What happens to held funds if one account closes?
A dispute file only holds up when the evidence record, the billing descriptor and the processor route are built together, so we work as one accountable team for the whole chain a peptide store needs to stay live.
If you want a second set of eyes on your checkout records and dispute process, our free store audit covers both.

