A chargeback is not a refund and it is not a complaint to you. It is a formal demand a cardholder makes to the bank that issued their card, asking that bank to reverse a charge through the card network. Because the dispute travels through the issuing bank, Visa, Mastercard, and Stripe rather than through your inbox, you do not control the outcome, and you often learn about it only after the money has already left your Stripe balance. For a non-resident who runs a Wyoming LLC and sells to US and global customers through Stripe, this is one of the few areas where your residency genuinely does not matter: the network rules, the evidence standards, the response deadlines, and the fees are identical to those a merchant in California faces. What differs is that non-residents are often newer accounts with thinner processing history, which makes the dispute ratio Stripe watches more volatile. This page explains the full mechanics, how to win the disputes that are winnable, and, more importantly, how to avoid most of them in the first place.
What a chargeback actually is
When a cardholder contacts their bank to say a charge is wrong, the bank opens a dispute and, in most consumer-card cases, immediately issues the cardholder a provisional credit. The bank then sends a reason code through the card network to Stripe, your acquiring processor. Stripe debits your account for the disputed amount and adds a fifteen dollar dispute fee. That fee is non-refundable: even if you fight the dispute and win, you get the disputed amount back but never the fifteen dollars. This is the single most important asymmetry to internalize, because it means a losing dispute costs you the sale plus the fee plus your staff time, while a refund you issue yourself costs you only the sale.
The cardholder's bank is the decision maker, not Stripe and not you. Stripe is a conduit that collects your evidence, formats it to the network's requirements, and forwards it. The issuing bank weighs your evidence against the cardholder's claim and rules. This is why a chargeback feels so different from a normal customer-service interaction: you are not persuading the customer, you are persuading a stranger at a bank who will spend perhaps a few minutes on your case and who starts from the cardholder's version of events.
Each dispute carries a reason code that defines what the bank is alleging and, crucially, what evidence will rebut it. A fraud reason code asks a different question than a product-not-received code, and submitting delivery tracking against a fraud claim does little good if the real issue is that the legitimate cardholder never authorized the charge. Reading the reason code first, before assembling anything, is the difference between a targeted rebuttal and a pile of irrelevant documents.
The step-by-step lifecycle
The sequence is predictable, and knowing it tells you exactly where you can act:
- The customer disputes a charge with their card-issuing bank, by phone, app, or letter.
- The bank issues a provisional credit to the customer and sends the dispute through the network to Stripe.
- Stripe debits your account for the disputed amount plus the fifteen dollar dispute fee.
- Stripe notifies you in the Dashboard and by email, showing the reason code and a specific response deadline.
- You have roughly 7 to 21 days, depending on the card network, to submit evidence (the exact deadline is shown in your Dashboard).
- The issuing bank reviews your evidence against the cardholder's claim and decides.
- If you win, Stripe returns the disputed amount to your balance, but the fifteen dollar fee stays gone.
- If you lose, the customer keeps the provisional credit and the debit becomes permanent.
Two things in this list trap merchants. The first is the deadline. It is a hard cutoff; miss it and you forfeit automatically regardless of how strong your evidence was. The second is the order of money movement: the funds are pulled from you up front, so a string of disputes can drive your Stripe balance negative even before you have lost a single case. Stripe will then recover the shortfall from your linked US bank account.
Reason codes and what they demand
The card networks publish dozens of reason codes, but for a typical online seller they cluster into a handful of categories. Matching your response to the category is the whole game.
| Category | What the bank is alleging | What rebuts it |
|---|---|---|
| Fraud / unauthorized | The real cardholder did not make this charge | 3D Secure authentication, AVS/CVC match, prior undisputed orders from the same customer, device/IP evidence |
| Product not received | The customer paid but got nothing | Carrier tracking showing delivery, access/download logs, the delivery email |
| Not as described / defective | The product differed materially from the listing | Your accurate listing, photos, the customer's acceptance, your refund policy |
| Subscription canceled | A recurring charge continued after cancellation | Your cancellation terms, the cancellation record, login/usage during the period |
| Duplicate / credit not processed | They were charged twice, or a promised refund never arrived | Proof the two charges were separate orders, or proof the refund was issued |
The most expensive mistake here is treating every dispute the same. A founder who attaches the same generic PDF of "terms and screenshots" to every case wins the easy ones by luck and loses the hard ones by inattention. Read the code, identify the exact question, and answer only that question with the cleanest possible proof.
Common chargeback reasons in plain terms
Stripe groups the underlying causes into a short list that covers the vast majority of real disputes: unauthorized transaction (true fraud), product not received, product significantly not as described, a canceled subscription that kept billing, a duplicate charge, and a credit that was never processed. Notice how few of these are actually fraud. Industry experience consistently shows that so-called friendly fraud and customer-service breakdowns, not stolen cards, drive most disputes for small online sellers.
That distinction matters because the two problems have different cures. Real fraud is solved at the gate, before the charge clears, with authentication and risk rules. Friendly fraud and service failures are solved after the sale, with fast support, clear billing descriptors, and easy cancellation. If you lump them together and reach only for fraud tooling, you will keep losing the larger category.
A useful habit is to log the reason code of every dispute you receive over a few months. The pattern that emerges tells you where to invest. A cluster of product-not-received codes points at a shipping or delivery-email problem. A cluster of subscription-canceled codes points at a confusing cancellation flow. A cluster of unauthorized codes points at a genuine fraud exposure that authentication will fix.
How to dispute and actually win
When a dispute is worth fighting, the process runs through the Stripe Dashboard, and the quality of your submission decides the outcome. Work the deadline first, then assemble proof that maps to the reason code:
- Open the dispute in the Stripe Dashboard and submit your response before the stated deadline.
- For physical goods, provide carrier tracking and delivery proof to the cardholder's billing or confirmed shipping address.
- Provide customer email or chat communication showing they received and accepted the product or service.
- Provide your refund and cancellation policy exactly as it was displayed at checkout.
- For digital goods, provide access logs, download timestamps, IP addresses, and the issued license key.
- Provide the signed agreement, accepted proposal, or terms-of-service acceptance for services.
- Configure Stripe Radar rules ahead of time to pre-block known fraud patterns so fewer disputes ever reach this stage.
The strongest submissions are tight, not voluminous. A bank reviewer does not want forty pages; they want the three documents that directly contradict the cardholder's specific claim. Lead with the single most damning piece of evidence, the delivery signature, the usage log timestamped after the customer claims they got nothing, the cancellation that never happened, and let the supporting documents fill in around it.
Building winning evidence by product type
The proof that wins a dispute depends entirely on what you sell, so build your evidence kit around your own product before you ever receive a dispute. For physical goods, that means carrier tracking that shows delivery to the cardholder's address, a signature or delivery photo where available, and the order and shipping confirmation emails. For digital downloads, it means access and download logs with timestamps and IP addresses, the license key you issued, and the delivery email. For SaaS and subscriptions, it means login and usage logs proving the customer actually used the product, the signup record, and the cancellation terms they agreed to at signup. For services, it means the signed agreement or accepted proposal, the deliverables you sent, and any messages where the client approved the work.
In every category, three pieces of evidence are universal and should accompany the product-specific proof: the customer's IP address and email captured at the moment of purchase, your refund policy as it appeared at checkout, and any messages where the customer acknowledged the purchase. These three establish that a real, identifiable person knowingly bought from you under terms they could see.
The practical implication is that evidence is collected at sale time, not at dispute time. If your checkout does not record IP and email, if your fulfillment does not log delivery, if your app does not store usage timestamps, then when a dispute arrives weeks later you will be reconstructing a case from memory and losing. Instrument the systems now so the evidence exists automatically when you need it.
The worked example: the unanswered-email dispute
Consider a customer who buys a one hundred and twenty dollar annual SaaS plan, cannot find the login link, emails support, and hears nothing for five days. Frustrated, they file a chargeback for services not received. Stripe immediately debits the one hundred and twenty dollars plus the fifteen dollar fee, so you are out one hundred and thirty-five dollars before you have done anything. The founder logs in to fight it and pulls the usage records, only to discover that the customer never actually logged in. That fact, which feels like it should help, actually weakens the case, because it corroborates the customer's claim that they never received the service.
The lesson is that this dispute was manufactured by a slow support reply, not by a dishonest customer or a stolen card. A reply within twenty-four hours that simply resent the login link would have cost nothing and produced an active, happy user whose own usage logs would later defeat any spurious dispute. Instead, silence converted a solvable onboarding hiccup into a one hundred and thirty-five dollar loss and a permanent ding to the dispute ratio that Stripe monitors.
Generalize the example and you arrive at the central truth of chargeback management for small merchants: most non-fraud chargebacks are customer-service failures in disguise. The cheapest dispute defense you can buy is a fast, human support reply. It costs less than the fifteen dollar fee, it preserves the sale, and it keeps your ratio clean.
Refund versus dispute versus Stripe tooling
These three are constantly confused, and the confusion is expensive. A refund is money you voluntarily return to the customer through Stripe; it carries no dispute fee and it is always cheaper than a chargeback the customer would have won anyway. A dispute or chargeback is the customer going to their bank instead of to you; the bank pulls the funds and Stripe charges the non-refundable fee, and you then have to fight to recover the principal. Stripe's own tooling, including Radar and smart dispute features, sits on top of both, blocking likely fraud before it clears and helping auto-assemble evidence when a dispute does land.
The decision rule that follows is simple and saves real money: if a customer is genuinely unhappy and would win a chargeback, refund them first. A voluntary refund avoids the non-refundable dispute fee entirely and, just as importantly, it keeps the dispute off your ratio. Your dispute rate, not your refund rate, is the number Stripe and the card networks watch, so converting a would-be dispute into a refund is a strictly better outcome on every axis.
Only fight disputes you can actually win on the evidence. Spending hours assembling a rebuttal for a case you will lose is worse than doing nothing, because you still pay the fee and the loss while burning your own time. Triage every dispute honestly into win it, refund it, or let it go, and act fast on the winnable ones.
Prevention is cheaper than any dispute
Prevention works on two fronts at once. To stop fraud before it clears, use 3D Secure on higher-value transactions, which authenticates the cardholder with their bank and, for many fraud reason codes, shifts liability to the issuing bank rather than you. Layer Stripe Radar rules on top to block known fraud patterns, mismatched country and IP signals, repeated failed attempts, and high-risk profiles. Together these address the genuine unauthorized-charge category that authentication is designed for.
To stop the larger friendly-fraud and service-failure category, the levers are operational rather than technical. Honor your refund policy quickly the moment a customer asks, because a fast refund almost never becomes a chargeback. Write product descriptions that match exactly what you deliver, so there is no gap for a not-as-described claim. Reply to support email fast, ideally within a day, since slow replies are the leading cause of the unnecessary disputes described above. Use a clear, recognizable billing descriptor so customers see your business name on their statement and do not file an unauthorized claim simply because they did not recognize the charge.
The unifying metric behind all of this is your dispute rate. Stripe puts accounts on risk review above roughly a one percent dispute rate, and persistent high rates can lead to reserves, holds, or account closure. Every prevented dispute protects that ratio, and the ratio protects your ability to keep processing at all.
Card-network monitoring programs and account risk
Stripe's roughly one percent guideline is not the only threshold you answer to. The card networks run their own excessive-dispute programs, and Visa and Mastercard each monitor merchants whose dispute ratios cross network-defined limits. Landing in one of these programs is serious: it can mean fines passed through to you and pressure on Stripe to restrict or close your account. These programs operate independently of Stripe's internal review, so a merchant can satisfy Stripe's headline number and still trip a network program if the trend is bad.
For a non-resident, the only honest framing is that there is no separate, harsher standard for you. The network rules, thresholds, fees, and evidence requirements are identical regardless of where the owner lives. Winning or losing a dispute turns entirely on the quality of your delivery and your evidence, never on your passport. Where non-residents do face extra exposure is account fragility: newer accounts, thinner history, and a single bad month can push the ratio up sharply, which makes disciplined prevention even more valuable for you than for an established US merchant.
Treat the dispute ratio as a core operating number, reviewed monthly alongside revenue. If it drifts toward one percent, diagnose the dominant reason code, fix that one process, and watch the ratio recover before any program or review is triggered. Defensive habits, refund early, deliver clearly, answer fast, authenticate high-value charges, keep both Stripe and the networks satisfied at the same time.
Putting it together
Chargebacks reward preparation and punish improvisation. The merchants who lose are the ones who first think about evidence when a dispute arrives, who treat every reason code the same, who let support email sit, and who fight cases they cannot win. The merchants who win are boring on purpose: they instrument checkout and fulfillment to capture evidence automatically, they read the reason code before assembling anything, they refund genuine unhappiness before it becomes a dispute, and they reserve the fight for cases their logs can actually prove. Do those four things and your dispute rate stays low, your Stripe account stays healthy, and the fifteen dollar fees stay rare.
If you have not yet set up the entity behind your Stripe account, forming a Wyoming LLC gives you the US business identity, EIN, and structure that Stripe and US banking partners expect from a non-resident seller. We handle the full formation for $397 all-inclusive, so you can get your account, your descriptor, and your dispute defenses in place from day one.