A store can keep a low chargeback rate and still get a termination notice. When the notice cites product claims, or a label that does not match the product page, the store does not have a fraud problem. It has a records problem, and no scoring tool would have caught it.
That is the thesis of this checklist. Ecommerce fraud prevention for a WooCommerce peptide store is one system: fraud controls, store compliance and payment evidence have to agree with each other. No fraud tool can fix misleading claims or sloppy records. No backup payment route should ever be used to hide anything from a processor.
This is the checklist we use at Peptide Marketing HQ. It follows the order from checkout to dispute, and it shows where each control lives in WooCommerce.
Sort the problem before you buy a tool
Fraud in a high-risk store is a set of different problems. Each one needs a different response, and a single score or plugin covers none of them well. Sort the problem first, then pick the control.
A plain decision tree
- Stolen-card order: AVS or CVV mismatch, a brand-new account, a high first-order value, rush shipping. First move: hold the order before capture and review it.
- Account takeover: a login from a new device followed by an address change or a saved-card purchase. First move: lock the account, email the owner on file and re-verify.
- Refund abuse: repeat refund requests, or "not received" claims on orders with a delivery scan. First move: pull the order log and apply the written refund policy.
- Reshipper: a mailbox-style address, billing and shipping far apart. First move: ask a plain question and review.
- Friendly fraud: the customer ordered, then disputed. First move: contact them before the dispute lands, then build the evidence file.
- Fulfillment problem: late or lost parcels and repeated "where is my order" tickets. First move: fix shipping. A better score will not help.
- Processor closure over policy: a notice that cites claims, labels, terms or descriptors. First move: preserve records and fix the site.
Why low chargebacks do not protect you
A processor can drop a store with a low chargeback rate. The cause is often product claims, labels, terms or descriptor problems, not fraud volume. Fraud tools do not see any of that.
What fraud prevention cannot fix
Run this audit before you add any scoring:
- Human-use language anywhere on the site, in emails or in ads.
- Labels that do not match the product pages.
- Vague refund terms, or terms that differ from what staff actually do.
- Weak fulfillment records and slow support.
Fix the site first, then add controls. We hold one line: we do not help anyone hide product types from a processor or dress up sales as something they are not. Cost is part of the case for fixing the basics.
One dispute costs you the order, the product that already shipped and your processor's dispute fee. It also adds to the dispute ratio your acquirer watches, which feeds the ratio in Visa's acquirer monitoring program. That should shape a decision: when a customer contacts you first on a small order, refund proactively.
Fight only when you hold strong evidence, such as a delivery scan or a successful 3-D Secure result. Our chargeback prevention post goes deeper on the dispute side.
Checkout settings that catch stolen-card orders
Most stolen-card orders show their problem at checkout. The settings below turn those signals into a review queue instead of a guess.

AVS and CVV
AVS compares the billing address and postal code with what the issuer holds. CVV checks the code on the card. Neither proves the buyer is the cardholder.
A mismatch should route to review, not auto-decline every time. Typos, new addresses and international cards cause plenty of honest mismatches. Log both results in an order note, for example "AVS: street no match, zip match. CVV: match." You will want that line later.
3-D Secure
Use risk-based triggers. Step up authentication on first orders, high values and mismatched signals, and leave clean repeat customers alone. Liability shift can move responsibility for certain fraud-coded disputes to the issuer when authentication succeeds. It does not cover every dispute type. A "not received" claim or a complaint about the product is still yours to answer. It also does nothing for a compliance problem.
Velocity and value rules
Cap orders and failed attempts per IP, email, device and card inside a set window. Add a first-order value threshold that sends the order to manual review. Here is an illustrative starting point, not a standard. Say a store's average first order is $120.
It might hold any first order over $350, any third attempt from one IP within 15 minutes, and any second card used on one account within 24 hours.
To find your own baseline, export orders from WooCommerce under Analytics, then Orders, as a CSV. Filter to first-time customers and read the median order total and the 90th percentile. Set the review threshold just above the 90th percentile. Then check the queue after a month. If most held orders turn out to be honest buyers, raise the number.
What the gateway’s own tools do
Gateway fraud tools differ by vendor, but they tend to sit in the same categories: AVS and CVV rules, 3-D Secure triggers, velocity or rate limits, risk-score thresholds, and block or allow lists. Switch on the categories your gateway offers and write each setting in your runbook. Gateway pages change, so note the date you read the documentation.
In WooCommerce, the gateway plugin's settings screen holds the AVS, CVV and 3-D Secure options. Many gateway plugins also offer an authorize-only mode, so the card is approved but not captured until you release it.
Core WooCommerce gives you the On hold order status and order notes, which is where your review record lives. We track chargeback rate, approval rate, false-positive rate, dispute win rate and response time together, so a falling fraud number does not hide lost sales. Write down the date you read any gateway fraud tool documentation you rely on.
Card testing is its own problem with its own fixes. We cover it in our card testing post, so we will not repeat it here.
Last, make the charge recognizable. A clear billing descriptor and honest checkout terms are fraud controls. A customer who recognizes the charge does not dispute it.
Account takeover, reshippers and refund abuse
Account takeover
Takeover starts with a stolen password and ends with a saved card. We close that path in four steps:
- Throttle logins and lock after repeated failures.
- Send an alert on every email change and address change.
- Re-check the customer before a saved card is reused.
- Give a new shipping address on an old account a second look.
Reshippers and freight forwarders
Signs include mailbox-style addresses, shipping far from billing and rush requests. Be fair about it, because plenty of legitimate buyers use a forwarder. One signal alone should not stop an order. Hold it when a forwarder or mailbox-style address appears together with at least one of these: a first order, an AVS mismatch, or a value above your first-order threshold.
For held orders, send a short, neutral email:
Thanks for your order. As a routine security check, please reply to confirm the billing name and the shipping address on order #[number]. We will release the order as soon as we hear from you, usually within one business day.
If the buyer does not reply inside your window, cancel and refund. Write that rule down so staff apply it the same way every time.
Refund abuse and friendly fraud
Write a refund policy you can enforce. Keep an order log that records what was bought, what shipped and when it was delivered. Add a rule for repeat refund requesters, such as a manual look at the third request. For the pattern behind these disputes, read why peptide stores lose friendly fraud disputes.
Block or review?
Should we block international orders, VPN users or billing and shipping mismatches outright? Usually no. Treat each as a review trigger. For a store doing $5k to $100k a month, every false decline is a real buyer lost, and a small store feels that more than a large one. Block only on a rule you can defend in writing.
Research-use-only stores and clinics
The two models need different evidence. A research-use-only store has to show accurate research-use-only wording, catalog records and labels that match. A clinic or telehealth brand needs patient identity and consent workflows, accurate clinical claims and clean recurring billing. A research store should not borrow clinic language because it converts better. The same rule will not fit both.
Run a manual review playbook a small team can hold
A small team needs a short queue. Keep the triggers few and tied to the checks above.

Review triggers:
- AVS or CVV mismatch combined with a first order.
- Order value above your first-order threshold.
- Velocity rule hit on IP, email, device or card.
- New shipping address on an old account.
- Forwarder or mailbox-style address.
Service levels. Pick targets one person can keep, for example a decision within one business day. While an order is on hold, tell the customer that a routine security check is under way and when to expect an answer. Do not accuse anyone.
Questions. Acceptable: confirm the order, the billing contact and the shipping address. Over the line: asking for a full card number or CVV by email, or coaching a customer on what to say about intended use. If a buyer indicates human use, we cancel and refund.
What to keep. Keep order notes, customer acknowledgments, and IP and device information where you lawfully collect it and disclose it in your privacy policy. Never store raw card data. Leave card handling to the gateway and its PCI DSS scope.
The ship-or-cancel rule. Cancel and refund instead of shipping when the mismatch stays unresolved past your window, contact details fail, a forwarder will not confirm, or the buyer signals human use. Record the reason in an order note using a short fixed code.
In WooCommerce, this runs on order notes, a custom "on hold, review" status and a filtered order list as the queue. The custom status takes a short code snippet: register it with register_post_status as wc-review, then add it to the wc_order_statuses filter.
Staff add notes from the order screen, and a plugin or snippet can write the AVS and CVV lines automatically with add_order_note. The rules drift as plugins update and staff change. Our website care plans keep those flags and notes maintained.
What goes in the evidence file?
Build the file at authorization and fulfillment, not after the issuer files a dispute. Historical transaction, device, IP, account and delivery records are the evidence that answers a card-not-present fraud dispute, so keep them from the first order. Which evidence programs apply depends on the dispute type, your processor and current network rules, so ask your acquirer which ones apply and confirm their cutoffs. Processor deadlines can be earlier than scheme deadlines.
The file for a card-not-present dispute holds:
- The order payload and the AVS/CVV and 3DS results.
- Fulfillment scans and delivery confirmation.
- Support emails and refund decisions.
- Customer acknowledgments, plus login records where relevant.
Answer each dispute by reason code. A generic receipt rarely wins.
Pre-underwriting records
Keep these on hand before any processor asks: legal entity, owner information, catalog, labels, testing documentation where applicable, terms, refund and shipping policies, and a working support contact. They are the same records merchant underwriting will ask for.
Content and packaging audit
Check that research-use-only wording is accurate. Remove human-use and therapeutic language. Make sure labels match product pages, and that shipping and refund language matches practice. Our compliance review covers this, and we never describe what any peptide does.
The first 72 hours after a drop
- Preserve every record, including notices and order exports.
- Pause risky traffic and ads.
- Find the actual policy issue named in the notice.
- Fix the site and documents.
- Approach a new acquirer truthfully, with your real catalog.
The processing side lives on our peptide payment processing page. Our free store audit checks your site against these records.
Ecommerce fraud prevention needs backup routes without shortcuts
A second gateway or an orchestration layer is for resilience. It keeps you taking orders when one provider has an outage. It is not a way around an acquirer's decision. We reject descriptor manipulation, account hopping and hiding product types, and a new gateway does nothing if the same claims and labels stay on the site.
Governance for a failover route
- Every provider approved with the full catalog disclosed.
- Written routing rules that say which orders go where, and why.
- Tokenization or a vault, where supported, so cards need not be re-entered.
- Reconciliation across routes, matched to orders each week.
- Customer messaging that keeps one clear descriptor and one set of terms.
Stop conditions
Pause or remove a route on any policy flag, rising dispute ratios or a provider objection. Write these in advance so nobody argues about them mid-crisis.
Can we open a second gateway after Stripe or PayPal closes an account?
Yes, with a provider that has reviewed your real catalog. We will not describe any processor's peptide policy here, because that belongs on the vendor's own page. Read it there and note the date.
Fraud controls, store records and payment evidence only protect you when they agree with each other. The next step is to run your store against the records in this checklist. If you would rather have someone else do the checking, our free store audit compares your claims, labels, refund terms and order records against what a processor or a dispute reviewer would actually read.
Frequently asked questions
What is ecommerce fraud prevention for a high-risk store?
It is a set of controls matched to different problems: stolen cards, account takeover, refund abuse, reshippers and friendly fraud. For a peptide store it also covers claims, labels and records that processors review. No single plugin covers all of it.
Should we decline every AVS mismatch?
No. Route mismatches to manual review, especially on repeat customers and international cards. Decline only when a mismatch combines with other signals you can defend.
Does 3-D Secure stop chargebacks?
It can shift liability for certain fraud-coded disputes when authentication succeeds. It does not cover every dispute type, and it does not fix a compliance problem.
Can we add a second gateway after a closure?
Yes, with a provider that has reviewed your real catalog. Fix the underlying policy issue first, or a new account will hit the same problem.
What should we keep for disputes?
Keep the order payload, AVS/CVV and 3DS results, fulfillment scans, delivery confirmation, support emails, refund decisions and acknowledgments. Never keep raw card data.

