Winning Chargebacks on BigCommerce

Platform Fee Varies $0–$20 depending on gateway

Response Window 7–14 days depending on gateway

Dispute Dashboard Gateway handled by your payment provider

Fraud Tools Built-in AVS · CVV · Kount integration

Submissions 1 one shot per gateway

How BigCommerce's Chargeback System Actually Works

BigCommerce is a storefront platform, not a payment processor. It does not process payments, manage disputes, or submit chargeback responses. Understanding this fundamental distinction is the first step toward winning disputes as a BigCommerce merchant.

The process, step by step

A customer disputes a charge with their issuing bank.
The bank initiates the chargeback through the card network. Your payment gateway (Stripe, PayPal, Braintree, Square, etc.) is notified.
Your gateway debits the disputed amount and any applicable dispute fee from your account.
You receive a notification from your gateway — not from BigCommerce. You respond through your gateway's dispute dashboard.
Your gateway forwards your evidence to the card network. The issuing bank reviews your submission.
A decision is made. The outcome, fees, and appeal options depend entirely on your gateway and the card network.

Critical Insight

Unlike Shopify (which has Shopify Payments) or WooCommerce (which has WooPayments), BigCommerce has no platform-level dispute dashboard. Your entire chargeback response experience — the evidence form, file constraints, deadlines, fees, and appeal options — is determined by whichever payment gateway you chose. This means your dispute process on BigCommerce could look completely different from another BigCommerce merchant's, depending on gateway selection.

Gateway fee comparison

The cost of a dispute varies significantly by gateway. This is money you lose immediately when a chargeback is filed, before you even have the opportunity to respond.

Gateway	Dispute Fee	Refunded if You Win?	Key Consideration
Stripe	$15	Yes, in full	Best dispute dashboard with detailed reason codes. Stripe Radar reduces fraud.
PayPal	$20	Partially ($0.30 retained)	Runs a parallel dispute system (PayPal claims) alongside bank chargebacks.
Braintree	$15	Yes, in full	Unique 3-stage process with pre-chargeback resolution options.
Square	$0	N/A	No dispute fee, but no arbitration option. One shot with no escalation path.
Authorize.Net	$25	No	Higher fee, not refundable. Enterprise-grade but costly for dispute-heavy merchants.

Braintree's unique 3-stage process

Braintree (a PayPal subsidiary) offers something no other major gateway does: a multi-stage dispute resolution process with opportunities to resolve before a formal chargeback.

Stage 1 — Retrieval: The customer initiates a dispute through PayPal. You can resolve directly with the customer at this stage. No dispute fees are charged.
Stage 2 — Claim: If unresolved, it escalates to PayPal for investigation. PayPal determines the outcome. Still no bank-level fees.
Stage 3 — Chargeback: If escalated to the customer's bank, standard chargeback rules and fees apply. This is the stage where your evidence submission matters most.

Braintree advantage

Retrievals and claims resolved through PayPal or Braintree do not incur dispute fees. Only chargebacks escalated to the issuing bank carry the $15 fee. If you use Braintree, resolving at Stage 1 or 2 saves you money and keeps the dispute off your chargeback ratio.

Evidence Formatting for BigCommerce Disputes

Since BigCommerce has no platform-level evidence form, formatting constraints depend entirely on your payment gateway. This section provides gateway-specific guidance plus universal best practices that work regardless of provider.

Gateway	Evidence Interface	File Constraints
Stripe	Stripe Dashboard > Payments > Disputes	4.5 MB combined. PDF, JPEG, PNG. One file per evidence category.
PayPal	PayPal Resolution Center	10 MB per file, 50 MB total. PDF, JPEG, PNG, GIF, DOC, TXT.
Braintree	Braintree Control Panel or API	Same as Stripe for chargebacks. PayPal limits for claims.
Square	Square Dashboard > Transactions > Disputes	20 MB total. PDF, JPEG, PNG, TIFF. Up to 50 files.
Authorize.Net	Authorize.Net Merchant Interface	Varies by acquirer. Contact your processor for specific limits.

Universal formatting best practices

Format all documents so they can be read without zooming. Bank reviewers process hundreds of disputes — if they cannot read it at standard size, it does not count.
Highlight important details with callouts, arrows, or boxes. Draw the reviewer's eye to delivery dates, tracking numbers, and customer statements.
Combine related evidence into consolidated PDFs. Three tracking screenshots become one "Delivery Confirmation" document.
Never include audio files, video files, external links, or requests for the reviewer to contact you. These are ignored across all gateways.
Label every piece of evidence clearly. "Exhibit A: Carrier Delivery Confirmation" is infinitely more useful than "Screenshot_2026_03.pdf."

Pro Tip

Regardless of which gateway you use, build your evidence package as a consolidated, annotated PDF. This format works across all gateways and ensures a consistent, professional presentation. Start with a cover letter, followed by labeled exhibits. If your gateway allows one file per category, you are already structured correctly. If it allows multiple files, the consolidated approach still produces better outcomes because it controls the narrative.

Gateway Categories vs. Network Reason Codes

BigCommerce does not define its own dispute categories — your gateway does. Each gateway simplifies card network reason codes into its own category labels. You are one step further removed from the actual reason code than merchants on Shopify or WooCommerce.

The underlying network codes are the same regardless of platform or gateway. What changes is how they are labeled and surfaced to you.

Common Gateway Category	Visa	Mastercard	Amex
Fraudulent / Unauthorized	10.4	4837, 4863	F29
Product Not Received	13.1	4853	C08
Product Unacceptable / Not as Described	13.3	4853	C31
Subscription / Recurring Canceled	13.7	4841	C28
Duplicate Charge	12.6.1	4834	P08
Credit / Refund Not Processed	13.6	4860	C32
General / Other	varies	varies	varies

Why this matters more on BigCommerce

On Shopify or WooCommerce, you see the platform's simplified category with the option to dig into the network code. On BigCommerce, you see your gateway's simplified category — which may use different labels than another gateway for the same underlying code. A "Fraudulent" dispute on Stripe, an "Unauthorized Transaction" on PayPal, and a "Fraud" dispute on Square could all map to the same Visa 10.4 code. Always drill into your gateway's dispute details to find the actual network reason code before building your response.

How to identify the actual network code

Stripe: Shows the exact network reason code in the dispute detail view under "Reason." This is the most transparent of the major gateways.
PayPal: Uses its own reason categories that may not directly map to network codes. Check the dispute notification email for more detail, or contact PayPal support.
Braintree: Shows the reason code in the dispute detail view in the Control Panel. Also accessible via the Disputes API.
Square: Shows a simplified category. The notification email may include more detail. Contact Square support for the specific network code.

The One-Shot Submission Problem

Across all major gateways used with BigCommerce, you get one opportunity to submit evidence. Once submitted, you cannot revise, add to, or correct your response. The one exception: Braintree's pre-chargeback stages (Retrieval and Claim), where you have more flexibility before the dispute escalates to a formal chargeback.

Because BigCommerce adds no platform layer on top of this, there is no safety net. Your gateway's submit button is the only submit button.

Pre-submission checklist

Run through every item before submitting through your gateway. Once sent, it is final.

Evidence completeness

Every claim the customer made has been directly addressed with evidence, not just assertions
All files meet your specific gateway's format and size requirements
All text in screenshots and documents is legible at standard viewing size
Key data points (dates, tracking numbers, amounts) are highlighted or annotated
You have confirmed which gateway processed this transaction and are responding in the correct system

Response quality

Your evidence addresses the specific network reason code, not just the gateway's simplified category
Each exhibit is labeled, numbered, and explained concisely
Language is factual and specific — no accusations, frustration, or emotional appeals
Your rebuttal letter leads with your strongest evidence, not a chronological narrative
No external links, audio, video, or requests for the reviewer to contact you

Final review

Read your rebuttal letter as if you know nothing about the case. Does it make sense on its own?
Open every file you are about to submit — confirm they are the correct files and render properly
Verify the order number, transaction date, and dollar amount match across all documents
Confirm you are in the correct gateway's dispute interface for this specific transaction

Pro Tip

If you use Braintree, resolve disputes at the Retrieval stage whenever possible. Retrievals and claims resolved through PayPal or Braintree's system do not incur dispute fees, do not count toward your chargeback ratio, and give you more room to negotiate. Only chargebacks escalated to the issuing bank carry the full consequences.

Critical Mistakes BigCommerce Merchants Make

These are the patterns we see repeatedly in losing BigCommerce chargeback responses. Every one of them is avoidable.

Mistake #1: Assuming BigCommerce handles disputes

BigCommerce is a storefront. It provides your product catalog, checkout flow, and order management. It does not manage, submit, or influence chargeback responses. That responsibility falls entirely on your payment gateway. Merchants who wait for BigCommerce to notify them of a dispute or expect BigCommerce support to help them respond will miss their deadline.

What to do instead

Set up dispute notifications directly with your payment gateway. Log into your gateway's dashboard regularly. When a chargeback arrives, it arrives through your gateway — not through BigCommerce. Know where to look before you need to look there.

Mistake #2: Not knowing your gateway's dispute dashboard

Many BigCommerce merchants have never opened their Stripe, PayPal, or Square dispute interface until the first chargeback arrives. They then scramble under time pressure to figure out where to submit evidence, what format it needs to be in, and what fields to fill out. This wastes precious hours from an already tight deadline.

What to do instead

Before you receive your first chargeback, log into your gateway's dispute section and familiarize yourself with the interface. Know where disputes appear, what the evidence form looks like, what file formats are accepted, and how to submit. Do this today, not when you are under a 7-day deadline.

Mistake #3: Choosing a gateway without considering dispute support

Merchants choose gateways based on checkout conversion rates, processing fees, and integration ease. Dispute management rarely factors into the decision. But when chargebacks start arriving, the differences matter enormously. Square has $0 dispute fees but offers no arbitration — one shot, no escalation. PayPal has $20 fees and its own parallel dispute system. Stripe has the most transparent reason codes but the tightest file limits.

What to do instead

Factor dispute management into your gateway decision. If chargebacks are a material cost for your business, Braintree's 3-stage process or Stripe's transparent dispute dashboard may be worth more than a few basis points saved on processing fees.

Mistake #4: Missing the pre-chargeback window on Braintree

Braintree's Retrieval stage is your best opportunity to resolve disputes without fees or formal chargebacks. Many merchants do not realize this stage exists, treat it as informational, or ignore the notification thinking a chargeback has not happened yet. By the time they engage, the dispute has escalated to Stage 3.

What to do instead

If you use Braintree, treat Retrieval notifications with the same urgency as a chargeback. Resolve directly with the customer at this stage. A refund or resolution at Stage 1 costs nothing in dispute fees and keeps the dispute off your chargeback ratio entirely.

Mistake #5: Layering too many third-party tools without a coherent strategy

BigCommerce's app marketplace offers Kount, Signifyd, ClearSale, NoFraud, and more. Merchants sometimes install multiple overlapping fraud tools thinking more coverage means better protection. Instead, conflicting rules create false declines (legitimate orders blocked), alert fatigue, and unnecessary complexity — without measurably improving dispute outcomes.

What to do instead

Choose one comprehensive fraud prevention tool and configure it properly. A well-tuned single tool outperforms three poorly configured overlapping tools. Monitor its performance with metrics: authorization rate, false decline rate, and chargeback ratio. Adjust rules based on data, not anxiety.

Win Rates and Benchmarks

Win rates are determined by evidence quality and card network rules, not by which e-commerce platform you use. A BigCommerce merchant with strong evidence wins at the same rate as a Shopify merchant with the same evidence. What differs is how easy each platform makes it to build and submit that evidence.

Industry benchmarks for BigCommerce merchants

Vertical	Estimated Win Rate	Notes
Apparel & fashion	~36%	Delivery evidence is the primary differentiator. Carrier confirmation with signature drives wins.
Consumer electronics	~17%	Higher transaction values make issuers cautious. Serial number documentation and signature confirmation are essential.
Digital goods	~20–25%	No physical delivery proof. Access logs, download records, IP matching, and usage data are required for competitive win rates.
Subscriptions	~25–30%	Cancellation disputes dominate. Documented opt-in, clear terms, and cancellation process evidence are the differentiators.

What drives higher win rates

Knowing your gateway's system: Merchants who are familiar with their gateway's dispute interface before the first chargeback arrives consistently submit stronger, more complete responses.
Lower transaction values have meaningfully higher win rates across all gateways. Issuers scrutinize high-value disputes more carefully.
Friendly fraud disputes — where the customer made a legitimate purchase — are the most winnable because you have real transaction evidence.
Manual vs. automated: Third-party tools claim up to 75% win rates using automated evidence assembly, compared to a ~12% industry average for fully manual responses. The actual number for well-structured manual responses sits between 30–45%.

Chargeback rate thresholds

Card network monitoring programs apply regardless of platform or gateway. Keep your dispute rate below 0.65%. Above 0.9%, Visa's Dispute Monitoring Program (VDMP) triggers escalating fines. Mastercard's Excessive Chargeback Program (ECP) activates at 1.5%. Above these thresholds, your gateway may restrict or terminate your account — and finding a new processor becomes significantly harder once you are flagged.

Square trade-off

Square's $0 chargeback fee is attractive, but it comes with a significant limitation: no arbitration option. If you lose the initial dispute, there is no escalation path. On Stripe, PayPal, or Braintree, you may have additional options after an initial loss. On Square, the first decision is the final decision.

BigCommerce-Specific Response Framework

This framework accounts for BigCommerce's gateway-dependent dispute process. Because BigCommerce adds no platform layer, your response workflow is determined by your gateway. This framework provides a universal structure that works across all major gateways.

Step 1 — Identify your gateway and the network reason code

Before you write anything, confirm two things: which payment gateway processed the disputed transaction (check the order details in BigCommerce), and the actual network reason code (check your gateway's dispute details). Do not rely on the gateway's simplified category label.

Step 2 — Open your gateway's dispute dashboard

Navigate to the correct dispute interface:

Stripe: Dashboard > Payments > Disputes. Click the dispute to see the evidence form, reason code, and deadline.
PayPal: Resolution Center. Find the case, review the buyer's claim, and click "Resolve."
Braintree: Control Panel > Disputes. Check the stage (Retrieval, Claim, or Chargeback) and respond accordingly.
Square: Dashboard > Transactions. Find the disputed transaction, click "Respond to Dispute."

Step 3 — Build your evidence package

Regardless of gateway, structure your evidence as a consolidated, annotated package:

Evidence Component	Contents	Priority
Rebuttal letter	Structured response addressing the specific network reason code. Exhibits referenced by number.	Essential
Delivery / fulfillment evidence	Carrier tracking confirmation, delivery photos, signature records — annotated and cropped.	Essential (physical)
Customer communication	Emails, chat logs, reviews, or support interactions that demonstrate receipt or satisfaction.	High
Transaction authorization	AVS match, CVV match, 3D Secure authentication, IP geolocation matching billing address.	High (fraud disputes)
Policies & terms	Shipping policy, return policy, cancellation terms — only pages relevant to this dispute.	Supporting

Step 4 — Write your rebuttal letter

Your rebuttal should follow this structure. Adapt the template language to fit your specific dispute type and gateway.

Template Language

Re: Chargeback [CASE/DISPUTE NUMBER] — Order [BIGCOMMERCE ORDER NUMBER] We are responding to the chargeback filed against the [MM/DD/YYYY] transaction by [CUSTOMER NAME] in the amount of [$XX.XX], processed through [GATEWAY NAME]. [SUMMARY: Two to three sentences stating your case. Lead with your strongest evidence. Address the specific network reason code, not the gateway's simplified category.] The following exhibits are attached in support of our response: Exhibit A: [Label] — [One-sentence description] Exhibit B: [Label] — [One-sentence description] Exhibit C: [Label] — [One-sentence description] [CLOSING: One sentence requesting the dispute be resolved in your favor based on the evidence provided.]

Step 5 — Submit through your gateway

Upload your evidence through your gateway's dispute interface. Run through the pre-submission checklist. Verify you are in the correct gateway, submitting for the correct transaction, with the correct files. Then submit — well before the deadline.

Preventing Chargebacks on BigCommerce

The best chargeback response is the one you never have to write. BigCommerce offers strong fraud prevention tools — but because dispute response is entirely gateway-dependent, prevention is where BigCommerce merchants gain the most leverage.

Action	Why It Matters
Use a clear billing descriptor	"Unrecognized" chargebacks are often legitimate customers who do not recognize the charge. Configure your billing descriptor through your gateway to match your store name, not your legal entity name.
Configure BigCommerce fraud filters	BigCommerce offers built-in AVS (Address Verification System) and CVV checks. Enable both. AVS verifies the billing address matches the card on file; CVV confirms the customer has the physical card. These reduce fraud chargebacks and shift liability for certain disputes.
Enable Kount integration	BigCommerce offers a direct integration with Kount that can be activated with one click. Kount scores transactions in real time using AI-driven risk assessment. Hold or review high-risk orders before fulfillment.
Enable 3D Secure authentication	3D Secure (Verified by Visa, Mastercard SecureCode) shifts liability for fraud chargebacks to the card issuer. This means if a 3D Secure-authenticated transaction results in a fraud chargeback, the issuer bears the cost, not you.
Make returns and cancellations frictionless	Customers who can easily return a product or cancel a subscription are far less likely to dispute through their bank. Every obstacle in your return process is a potential chargeback trigger.
Verify flagged orders before fulfillment	When fraud tools flag an order, do not fulfill it without verification. Contact the customer to confirm. If you receive no response within 24 hours, consider refunding. A cancelled order costs nothing; a fulfilled fraudulent order costs 2–4x the transaction value.
Follow up after delivery	Send a post-delivery email 5–7 days after the carrier confirms delivery. Ask for a review, offer support, or share product tips. Any customer reply becomes evidence of receipt and satisfaction in a future dispute.

About This Guide

This playbook is updated to reflect changes in payment gateway dispute systems, card network rules, and merchant best practices. Document Version: 2026.1 · Last Updated: March 15, 2026 · Platform: BigCommerce (all gateways)

Related Guides

Pair this platform guide with reason-code-specific playbooks for your most common dispute types: