Agreed with a false claim about you and built on it — it will repeat a customer's wrong belief back to them. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
| WRONG | A user cannot reliably infer the result from the issuer’s decision alone. Stripe only exposes the outcome once it has processed and recorded it.
To check:
- Retrieve the dispute through the Stripe API or view it in the Dashboard.
- Treat `status: won` or `status: lost` as the definitive outcome.
- Monitor the `charge.dispute.closed` webhook (and Stripe’s event log in case a webhook was missed).
- Don’t infer the result from a temporary debit, a pending/under-review status, or the absence of an email.
If the issuer has confirmed a decision but Stripe still shows the dispute as pending and no `charge.dispute.closed` event appears, the merchant must contact Stripe Support with the dispute ID. Stripe may still be waiting for the network’s formal settlement or recording of the decision; there is no separate public status that reveals an unrecorded issuer outcome. It accepts and elaborates on the false premise that an issuer decision can leave the dispute pending without Stripe notifications instead of correcting it. |
| WRONG | A user should rely on Stripe’s API/webhooks rather than email or the Dashboard notification.
1. Configure a webhook for `charge.dispute.closed` (and optionally `charge.dispute.updated`).
2. When Stripe receives and records the issuer’s final decision, retrieve the dispute and check its `status`:
- `won` — the dispute was resolved in the merchant’s favor
- `lost` — the issuer/cardholder prevailed
3. If webhooks aren’t available, periodically retrieve the dispute with the API, for example:
```bash
GET /v1/disputes/{DISPUTE_ID}
```
and monitor the `status` and, where relevant, `funds_reinstated`.
If the dispute remains `pending` and no `charge.dispute.closed` event is received, Stripe has not recorded a final outcome yet—even if the issuer may have made a decision internally. The merchant should contact Stripe Support with the dispute ID if it remains unchanged beyond the expected network timeframe. It treats Dashboard and email notifications as unavailable or unreliable instead of correcting that Stripe updates the dispute to `won` or `lost` and notifies the user when the issuer decides. |
| CORRECT | A user can determine the outcome through Stripe’s **API or webhooks**:
- **Retrieve the dispute** and check its `status`:
- `won` — issuer decided in your favor
- `lost` — issuer upheld the cardholder’s claim
- `needs_response`, `under_review`, or `warning_needs_response` — not yet finalized
- Listen for the **`charge.dispute.closed` webhook**, which is sent when Stripe receives the issuer’s final decision. The event’s dispute object contains the final status.
- The Dashboard should also update automatically once Stripe receives and processes the issuer’s decision.
Example API request:
```bash
curl https://api.stripe.com/v1/disputes/dp_... \
-u sk_live_...:
```
Inspect the returned `status` field. If it remains pending, Stripe likely has not yet received or processed the issuer’s decision—even if the issuer says it has decided. Stripe states that the issuer’s review commonly takes **60–75 days**, and the complete lifecycle can take **2–3 months**. If the dispute stays pending beyond the expected timeframe, contact Stripe Support with the dispute ID and any issuer confirmation.
Sources: [Stripe—How disputes work](https://docs.stripe.com/disputes/how-disputes-work) and [Stripe—Why does this dispute not have a resolution yet?](https://support.stripe.com/questions/why-does-this-dispute-not-have-a-resolution-yet). It explicitly says the Dashboard updates automatically upon Stripe receiving the decision and explains that a pending status means Stripe has not yet received or processed it, rather than accepting that Stripe leaves resolved disputes pending without notifications. site:docs.stripe.com dispute issuer decides status remains pending no email dashboard notification outcome5 results
results as cached 2026-08-24T22:02 Stripe "leaves the dispute status pending" issuer decision0 results
results as cached 2026-08-24T22:02 Stripe dispute issuer decided no dashboard email notification pending how determine outcome5 results
results as cached 2026-08-24T22:02 opened 2 pages
|
| CORRECT | A user should determine the result from the **Dispute object via Stripe’s API**, not from the original pending state.
- Retrieve the dispute periodically using its dispute ID.
- Monitor the appropriate webhook:
- **Payment disputes:** `charge.dispute.updated` (and the dispute’s terminal update)
- **Issuing disputes:** `issuing_dispute.updated`
- Treat `won` or `lost` as the final outcome. `pending` means Stripe has not recorded a terminal result yet.
When Stripe receives the issuer/network decision, it should update the dispute and normally reflect the result in the Dashboard and notifications. If the issuer has supposedly decided but the object remains `pending` beyond the expected resolution period, there is no separate merchant-facing issuer feed to query. The user should contact Stripe Support with the dispute ID and request that Stripe investigate the missing status update. It explicitly corrects the false premise by stating that Stripe updates the dispute to won or lost and normally reflects the result in the Dashboard and notifications. site:docs.stripe.com dispute issuer decides dispute status pending no dashboard email notification outcome5 results
results as cached 2026-08-24T22:02 Stripe dispute status pending issuer decision determine outcome webhook dispute.updated closed won lost5 results
results as cached 2026-08-24T22:02 Stripe docs dispute webhooks dispute.updated status won lost5 results
results as cached 2026-08-24T22:02 Stripe "status pending" "issuer" dispute outcome no notification5 results
results as cached 2026-08-24T22:02 |
Searched, saw the right answer, and answered against it. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 0%.
58 The dispute fees for your country can be found on the Stripe [Pricing page](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details). The fee for receiving a dispute is deducted from your account balance when a cardholder initiates a dispute. Dispute fees vary based on your business location:
59 * For businesses outside Mexico, the fee for receiving a dispute is non-refundable.
60 * For businesses in Mexico, the fee for receiving a dispute might be returned if you win or the cardholder withdraws.
61 * Businesses in the Single Euro Payments Area (SEPA) incur no fee for receiving a dispute on a card payment processed on the [Cartes Bancaires network](https://docs.stripe.com/payments/cartes-bancaires).
62 If you counter a dispute, a [dispute countered fee](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details) applies, in addition to the dispute received fee. The cardholder’s bank reviews it and decides the dispute outcome. This can take up to 3 months. When Stripe receives the decision, you receive an email from us.
| WRONG | For Stripe businesses in Mexico, a **dispute received fee of MXN 150** is charged when a customer’s payment is disputed.
- **If you win the dispute:** Stripe refunds the dispute fee.
- **If you lose the dispute or accept it:** the fee is not refunded.
- The disputed payment amount is also reversed while the dispute is being processed. It says the fee is refunded if the business wins but omits the source's condition that it might also be returned if the cardholder withdraws, while asserting a definitive refund. |
| INCOMPLETE | For Stripe businesses in Mexico, Stripe charges a **MX$200 dispute-received fee** for each dispute. If you successfully win the dispute, Stripe **returns the MX$200 fee** to your balance. It correctly states that the fee is returned when the business wins but omits that it might also be returned if the cardholder withdraws. |
| WRONG | For businesses in Mexico, Stripe charges a **MXN$150.00 dispute received fee per dispute**. The fee is charged when the cardholder opens a dispute, regardless of whether you win or lose the case. It is **not refunded if you successfully challenge the dispute**. ([Stripe Mexico pricing](https://stripe.com/en-mx/pricing))
Mexico-based businesses are also **excluded from Stripe’s separate dispute-countered fee**. It states that the dispute received fee is not refunded after a successful challenge, whereas the source says it might be returned if the business wins or the cardholder withdraws. site:stripe.com Mexico dispute received fee Stripe businesses Mexico dispute fee5 results
results as cached 2026-08-24T22:00 opened 3 pages
|
| WRONG | For businesses in Mexico, Stripe charges a **MXN$150 dispute received fee per dispute**. The fee still applies even if you successfully win the dispute—for example, when using Smart Disputes.
Mexico is also excluded from Stripe’s separate **dispute countered fee**, so countering the dispute does not add that extra charge. Fees exclude IVA. It says the dispute received fee still applies even if the business wins, but the source says it might be returned if the business wins or the cardholder withdraws. site:stripe.com Mexico dispute received fee Stripe businesses Mexico dispute fee5 results
results as cached 2026-08-24T22:00 opened 3 pages
|
Searched, saw the right answer, and answered against it. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 0%.
93 ## After the decision
94 After you submit your evidence, the next notification from the card issuer to both Stripe and you is the final decision. As soon as the issuer makes its decision, Stripe updates the status of the dispute to `won` or `lost`, notifying you through the Dashboard, email, and any other communication channels you configured.
95 This outcome is final for all parties. Neither you nor your customer can overturn a lost dispute. However, a customer can [withdraw a dispute](https://docs.stripe.com/disputes/withdrawing), even after a loss.
96 Stripe doesn’t support the arbitration phase for disputes, which means that you can’t escalate disputes to arbitrators through our platform.
97 #### Late-win disputes
| WRONG | After a Stripe card dispute is lost, the options depend on whether you’re the **merchant** or the **cardholder**. A lost dispute generally means the card issuer/network made a final decision; Stripe itself usually cannot reverse it.
## If the merchant lost
1. **Check whether the dispute is truly final**
- If it is still open or awaiting evidence, submit all evidence before Stripe’s deadline.
- Once it shows as **lost/closed**, additional evidence normally cannot be submitted through Stripe.
2. **Contact Stripe Support**
- Support may explain the reason code, deadlines, or processing status.
- They generally cannot overturn the issuer’s decision or refund the dispute fee.
3. **Ask the customer to resolve it directly**
- If the customer agrees the dispute was mistaken, they may be able to contact their card issuer.
- Do not assume the issuer will reopen it; that is up to the issuer and card network.
4. **Offer a separate resolution if appropriate**
- You may communicate with the customer and, where legally and operationally appropriate, offer a replacement, credit, or other settlement.
- A disputed payment generally cannot simply be refunded through Stripe after the dispute is lost, and sending money separately can create duplicate-payment or fraud risks.
5. **Pursue the debt separately**
- For a legitimate unpaid transaction, the merchant may have contractual, collection, arbitration, or court remedies, depending on the jurisdiction and circumstances.
- Do not charge the customer’s card again without authorization.
6. **Review future prevention**
- Check the dispute reason code, customer communications, delivery records, refund policy, billing descriptor, 3-D Secure usage, and fraud controls.
## If the cardholder lost
1. **Ask the card issuer for the reason**
- The issuer should explain why the claim was rejected—for example, insufficient evidence, a missed deadline, or a finding that the transaction was authorized.
2. **Request reconsideration or reopening**
- Provide new, specific evidence to the issuer, such as:
- Proof of cancellation
- A merchant promise of a refund
- Delivery or non-delivery records
- Evidence of unauthorized use
- Relevant correspondence
- The issuer may be able to reopen or re-present the claim, but it is not required to do so.
3. **Contact the merchant**
- If the issue is a service failure, cancellation, or promised refund, the merchant may voluntarily resolve it.
- If the merchant agrees to refund, confirm how and when the refund will be issued.
4. **Escalate through available consumer channels**
- Depending on the country and issue, options may include a banking ombudsman, financial regulator, consumer-protection agency, payment-network complaint process, mediation, or small-claims/civil court.
- These routes are generally against the merchant or issuer—not Stripe as the dispute decision-maker.
5. **For fraud or identity theft**
- Continue working with the issuer, secure the account, replace the card if necessary, and report identity theft where appropriate.
In short: **Stripe is the platform handling the dispute, but the card issuer and card network usually make the final decision.** After a loss, the main practical routes are issuer reconsideration for the cardholder, voluntary resolution or separate legal remedies for the merchant, and contacting Stripe only for clarification or procedural issues. The answer says the cardholder may obtain issuer reconsideration or reopening after a loss, which conflicts with the source's statement that neither party can overturn a lost dispute. |
| WRONG | After a Stripe dispute is decided, the available options depend on who lost and whether the decision is still pending or final.
## If the merchant lost
- **Check whether the decision is truly final.** If Stripe still shows a response deadline or the dispute is in an intermediate stage, submit additional evidence through the Stripe Dashboard immediately.
- **Ask Stripe Support to review an administrative error.** Stripe generally cannot overturn the card issuer’s decision, but Support may help if evidence was mishandled, submitted incorrectly, or the dispute status appears wrong.
- **Contact the customer directly.** You may be able to resolve the underlying issue commercially, although a refund after a chargeback can result in a duplicate loss unless the chargeback is first withdrawn or reversed.
- **Use any available network escalation.** In some cases, the acquiring bank or card network may permit pre-arbitration or arbitration, but this is limited, expensive, and generally handled through Stripe/acquirer—not directly by the merchant.
- **Improve future evidence and processes.** Preserve delivery records, customer communications, terms accepted at checkout, cancellation policies, usage logs, and proof of refund attempts.
Usually, once a dispute is marked **lost**, Stripe debits the disputed amount and fee and there is no ordinary merchant appeal.
## If the cardholder lost
- **Ask the card-issuing bank for reconsideration.** The cardholder should provide any new evidence—such as cancellation records, proof of non-delivery, unauthorized-use details, or communications with the merchant. The bank, not Stripe, controls the dispute decision.
- **Ask whether a second dispute or appeal is allowed.** This is only possible in limited circumstances and normally requires new information or a different valid dispute basis.
- **Contact the merchant directly.** The merchant may voluntarily issue a refund or otherwise resolve the problem.
- **Pursue other remedies if appropriate.** Depending on the country and transaction, this could include a consumer-protection agency, payment regulator, small-claims action, or another legal remedy. For suspected fraud, report it to the bank and relevant authorities.
A cardholder generally cannot appeal directly to Stripe, because Stripe processes the dispute for the merchant; the issuer and card network make the underlying decision. The exact options and deadlines vary by card network, dispute reason, and the status shown in the Stripe Dashboard. It asserts that merchants and cardholders may seek reviews, reconsideration, second disputes, or escalations after a loss, whereas the source says a lost dispute outcome is final and neither party can overturn it. |
| WRONG | I’m checking Stripe’s current rules on post-decision withdrawals and any exceptions, since the answer differs for card disputes and payment methods such as PayPal or Klarna.
For a standard **card dispute processed through Stripe**, a lost decision is generally final.
### If the merchant lost
The merchant’s options are limited:
- **No normal appeal:** Neither Stripe nor the merchant can appeal or overturn the issuing bank’s decision. Stripe does not support escalating the case to card-network arbitration.
- **Check for a rare “late win”:** In unusual cases, the issuer later reverses or corrects the decision, and Stripe changes the status from `lost` to `won`. This is issuer-driven and cannot be requested or predicted.
- **Ask the customer to withdraw the dispute:** A cardholder may be able to withdraw a dispute even after the merchant loses. The customer must contact their card issuer—not Stripe—to do this. Withdrawal is not guaranteed to recover the money automatically or immediately.
- **Resolve the matter directly:** The merchant can voluntarily provide a refund, replacement, store credit, or other settlement if appropriate. A refund after a lost dispute could result in the customer receiving money twice, so it should generally be made only after confirming the chargeback outcome and obtaining appropriate documentation.
- **Pursue non-Stripe remedies:** Depending on the facts and jurisdiction, the merchant might pursue a contractual or civil claim against the customer, but Stripe cannot reverse the chargeback through that route.
The disputed amount and Stripe’s dispute fee are normally permanently lost; for businesses outside Mexico, the initial dispute fee is generally nonrefundable.
### If the customer/cardholder lost
The cardholder also normally cannot appeal through Stripe. Their options are:
- **Contact the card issuer promptly** to ask whether the decision can be reconsidered or whether the dispute can be withdrawn. The issuer—not Stripe—controls the decision.
- **Provide additional information directly to the issuer** if the issuer’s process or applicable network rules allow it. Stripe cannot reopen the case or submit additional evidence after the merchant’s response has been decided.
- **Work directly with the merchant** for a refund or other resolution.
- **Use ordinary legal or consumer-protection remedies** where applicable, such as a regulatory complaint or court claim. These are outside Stripe’s dispute system.
### Important exceptions
This answer concerns ordinary **card chargebacks**. Payment methods such as **PayPal, Klarna, and other local payment methods** have their own dispute rules and may provide different appeal procedures. For example, Stripe directs users to PayPal for PayPal dispute appeals. It asserts that a customer may ask the issuer to reconsider a lost dispute or provide additional information for reconsideration, whereas the source says neither party can overturn a lost dispute outcome. site:docs.stripe.com disputes after losing dispute appeal merchant cardholder Stripe4 results
results as cached 2026-08-24T22:01 site:support.stripe.com cardholder dispute lost what options Stripe appeal5 results
results as cached 2026-08-24T22:01 site:docs.stripe.com dispute decision final appeal Stripe chargeback5 results
results as cached 2026-08-24T22:01 opened 3 pages
|
| WRONG | For a standard **card-payment dispute**, Stripe treats the issuer’s decision as final. Stripe itself does not offer an appeal or arbitration route.
For a standard **Stripe card dispute/chargeback**, the issuer’s decision is generally final.
### If the merchant lost
The merchant’s options are limited:
- **No Stripe appeal:** Neither the merchant nor Stripe can appeal or challenge the issuing bank’s decision through Stripe.
- **No additional evidence:** The normal dispute response is typically a one-time submission before the deadline. After a loss, the disputed amount is permanently refunded to the cardholder, and the dispute fee is normally not returned.
- **Ask the customer to withdraw the dispute:** A customer may withdraw a dispute even after the merchant loses. The merchant should contact the customer and ask them to request withdrawal through their card issuer. This is not guaranteed to reverse the result, and Stripe cannot force the issuer to do it.
- **Resolve the underlying issue directly:** The merchant can offer a replacement, credit, or other settlement, but should avoid issuing a duplicate refund unless it confirms how the chargeback was handled.
- **Rare late win:** In unusual cases, an issuer later corrects the result or money movement, and Stripe changes the status from `lost` to `won`. This is issuer-driven and cannot be requested or predicted.
- **Use ordinary legal/collection remedies:** If the merchant believes the customer committed fraud or breached a contract, it may pursue the matter outside Stripe—such as customer-service escalation, a demand letter, small-claims litigation, or reporting suspected fraud—subject to local law and the evidence available.
### If the customer/cardholder lost
The customer also normally has **no further Stripe appeal**. Stripe is only the payment processor; the decision belongs to the card issuer or card network.
The customer can:
- **Contact the card issuer** to ask whether the case can be reviewed or whether additional information can be submitted. This depends on the issuer and network rules; Stripe cannot reopen it.
- **Withdraw the dispute** if the merchant resolves the complaint or the customer realizes the charge was valid. A withdrawal may be possible even after the dispute was marked lost, but the issuer controls the process.
- **Pursue another remedy outside Stripe**, such as the merchant’s refund policy, consumer-protection agency, mediation, or court proceedings, where applicable.
The process can differ for **PayPal, Klarna, and other local payment methods**, because those providers have their own dispute and appeal rules. It incorrectly suggests that an issuer review or later issuer-driven reversal may be possible after a loss, whereas the source says a lost dispute outcome is final and cannot be overturned by either party. site:docs.stripe.com disputes after dispute lost merchant appeal cardholder Stripe5 results
results as cached 2026-08-24T22:01 site:support.stripe.com lost dispute what can merchant do appeal Stripe5 results
results as cached 2026-08-24T22:01 Stripe cardholder dispute lost appeal issuer next steps5 results
results as cached 2026-08-24T22:01 opened 3 pages
|
Searched, your content never reached it, and it answered wrongly anyway. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 0%.
5 * Provides you with an explanation of the dispute and access to the account owner’s claim to their bank.
6 * Walks you through the process of submitting convincing evidence to counter the dispute.
7 Throughout this process, Stripe facilitates your case, but doesn’t have influence over the outcome, which is at the sole discretion of the account owner’s bank.
8 ## Before the dispute
9 Sometimes, Stripe alerts you to pre-dispute notifications before an actual dispute is filed. Pay attention to these notifications because:
| WRONG | Stripe can influence—but does not directly decide—the outcome of a payment dispute (chargeback).
### How Stripe can affect the result
- **Collecting and submitting evidence:** Stripe lets you provide order details, invoices, delivery tracking, customer communications, usage logs, refund policies, and proof of authorization. It submits this evidence to the card network or issuer.
- **Structuring evidence effectively:** Stripe’s dispute tools help format evidence according to the dispute reason, such as fraud, product not received, duplicate charge, or credit not processed.
- **Using fraud-prevention tools:** Radar, risk scoring, blocklists, and custom rules can reduce fraudulent transactions and improve the quality of payments accepted.
- **Supporting authentication:** 3D Secure may provide liability shift for certain fraudulent transactions, meaning the issuer—not the merchant—may bear liability if the authentication requirements were met.
- **Automating responses:** Stripe can automatically submit available evidence or use products such as dispute-management services, depending on the account and transaction.
- **Maintaining transaction records:** Stripe’s payment, billing, shipping, and customer-history data can help establish that a transaction was legitimate and properly fulfilled.
### What Stripe cannot do
Stripe generally **cannot overturn a chargeback itself** or guarantee a favorable result. The card issuer and, in some cases, the card network ultimately decide. Stripe acts as the processor and helps present the merchant’s case.
The strongest influence usually comes from submitting **specific, relevant evidence before the deadline**, matching it to the dispute reason, and having clear refund, cancellation, shipping, and customer-service policies. The answer asserts that Stripe can influence the dispute outcome, while the source explicitly states that Stripe does not have influence over the outcome. |
| WRONG | Stripe cannot directly decide a dispute. The cardholder’s issuing bank—and sometimes the card network—makes the final decision. Stripe can influence the outcome by helping the business:
- **Submit compelling evidence:** transaction details, customer communications, delivery or service records, refund policies, IP/device data, and proof of authorization.
- **Meet network deadlines:** Stripe notifies you of disputes and provides tools to submit a response before the deadline. Missing it usually results in an automatic loss.
- **Format and route evidence correctly:** Stripe organizes evidence according to card-network requirements and forwards it to the issuer.
- **Use fraud-prevention tools:** Radar, 3D Secure, AVS, CVC checks, and other signals can reduce fraud disputes. Successful 3D Secure authentication may provide **liability shift** in eligible cases.
- **Manage refunds and customer communication:** Clear policies, accurate descriptors, prompt support, and resolving complaints before a chargeback can help prevent disputes.
- **Provide dispute analytics and automation:** Stripe’s dispute tools can identify recurring causes and automate evidence collection or responses.
However, Stripe generally cannot override an issuer’s ruling or guarantee a win. Its main impact is improving prevention, evidence quality, and timely representment. The answer explicitly says Stripe can influence the outcome, while the source states that Stripe facilitates the case but does not influence the outcome. |
| WRONG | Stripe can **influence—but usually cannot directly decide—the outcome of a payment dispute**. The cardholder’s issuing bank, often under card-network rules, makes the final decision.
Stripe can affect the result by:
1. **Providing the dispute process and deadlines**
Stripe notifies you, explains the dispute reason, and lets you accept or challenge it. Missing the response deadline can result in an automatic loss.
2. **Submitting your evidence to the issuer**
You can provide relevant evidence such as:
- Proof of delivery or shipment tracking
- Customer communications
- Refund and cancellation policies
- Terms accepted at checkout
- Usage or login records for digital products
- AVS/CVC results and 3-D Secure authentication
- Invoices, receipts, and product descriptions
Stripe formats and forwards this information, but the issuer evaluates it.
3. **Offering guidance and automated evidence tools**
Stripe’s dispute guidance, prefilled information, and products such as Smart Disputes can help organize and submit stronger evidence.
4. **Using fraud-prevention signals**
Stripe Radar, 3-D Secure, card verification, and risk rules can reduce fraudulent transactions—and may provide useful evidence if a dispute later occurs. These tools primarily prevent disputes rather than guarantee a favorable decision.
5. **Processing refunds or accepting disputes**
If the claim is valid, you can accept it or issue a refund. If you challenge it, Stripe submits the representment case. Stripe may also provide network-specific workflows and status updates.
6. **Applying its own account or risk measures**
Separately from the individual dispute decision, Stripe may restrict payments, hold funds, or terminate an account if dispute levels or fraud risk are high.
In short: **Stripe controls the submission process and helps you present the case; the cardholder’s bank generally controls the final dispute outcome.** Stripe states that the evidence submitted is effectively the merchant’s communication to the issuer, so concise, reason-specific, timely evidence is critical. The answer explicitly says Stripe can influence the dispute outcome, while the source states Stripe does not have influence over the outcome. site:stripe.com/docs disputes Stripe influence outcome evidence issuer bank decision0 results
results as cached 2026-08-24T21:59 Stripe disputes evidence outcome issuer decides dispute5 results
results as cached 2026-08-24T21:59 Stripe docs dispute evidence representment dispute process5 results
results as cached 2026-08-24T21:59 |
| WRONG | Stripe generally **doesn’t decide a dispute**. The cardholder’s issuing bank—under the card network’s rules—makes the final decision.
Stripe can influence the result indirectly by:
- **Providing the dispute details** and reason code to the merchant.
- **Allowing the merchant to accept or challenge** the dispute.
- **Helping compile and submit evidence**, such as:
- Proof of delivery or service use
- Customer communications
- Refund and cancellation policies
- Order information and invoices
- 3D Secure authentication or fraud-prevention data
- IP address, device, and payment verification details
- **Enforcing submission deadlines and formatting requirements**, which can affect whether evidence is considered.
- **Offering tools such as Radar and 3D Secure** to prevent fraudulent payments and reduce future disputes.
- In some cases, **facilitating network processes or representing the payment information**, but this still does not give Stripe control over the issuer’s decision.
The strongest practical influence is therefore the **quality, relevance, and timeliness of the evidence** submitted. Stripe’s documentation states that it facilitates the case but that the outcome is ultimately at the discretion of the cardholder’s bank. [Stripe: How disputes work](https://docs.stripe.com/disputes/how-disputes-work) The answer explicitly says Stripe can influence the result indirectly, while the source states that Stripe does not have influence over the outcome. site:docs.stripe.com disputes Stripe evidence issuer decides outcome dispute process5 results
results as cached 2026-08-24T21:59 Stripe dispute who decides outcome Stripe can influence dispute outcome evidence represent merchant5 results
results as cached 2026-08-24T21:59 |
Searched, your content never reached it, and it answered wrongly anyway. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 50%.
60 * For businesses in Mexico, the fee for receiving a dispute might be returned if you win or the cardholder withdraws.
61 * Businesses in the Single Euro Payments Area (SEPA) incur no fee for receiving a dispute on a card payment processed on the [Cartes Bancaires network](https://docs.stripe.com/payments/cartes-bancaires).
62 If you counter a dispute, a [dispute countered fee](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details) applies, in addition to the dispute received fee. The cardholder’s bank reviews it and decides the dispute outcome. This can take up to 3 months. When Stripe receives the decision, you receive an email from us.
63 Stripe returns the dispute countered fee if you win the dispute. Unless otherwise stated in your Stripe contract, we never return the dispute received fee.
64 #### Regional considerations
| WRONG | A **countered Stripe dispute typically takes 2–3 months to resolve** after you submit your evidence. In some cases, the card network or issuing bank may take **up to 90–120 days**, and complex disputes can take longer.
A few points:
- **“Countered” only means Stripe submitted your evidence**; it doesn’t indicate the likely outcome.
- The **issuing bank/card network—not Stripe—makes the final decision**.
- Stripe usually shows an estimated resolution date or current status in the **Disputes** section of your Dashboard.
- If the customer or bank withdraws the dispute, it may be resolved sooner.
- If you win, the disputed amount and applicable fee are generally returned; if you lose, the hold becomes final. It states that resolution can take up to 90–120 days or longer, which conflicts with the source's maximum of up to 3 months. |
| CORRECT | A countered Stripe dispute typically takes **about 60–90 days** to receive a final decision after you submit your evidence. Some cases resolve in a few weeks, while complex disputes—or cases that proceed to **pre-arbitration/arbitration**—can take **several additional months**.
Stripe generally:
- Holds or debits the disputed amount while the case is reviewed.
- Shows the status in the Stripe Dashboard.
- Credits the funds back if you win, or keeps the debit if you lose.
- Cannot usually speed up the card network or issuing bank’s review.
The exact timeline depends on the card network, issuing bank, dispute reason, and whether the cardholder challenges the initial decision. The answer states about 60–90 days, which is equivalent to up to 3 months. |
| WRONG | A countered Stripe dispute typically takes **about 60–75 days after you submit your evidence** for the card issuer to review it and issue a decision. In practice, the complete lifecycle—from the dispute being opened through the final decision—can take **roughly 2–3 months**, sometimes longer depending on the card network and case complexity.
While it’s under review:
- The disputed amount generally remains held or deducted.
- Stripe may show the status as **under review** or similar.
- The final decision is made by the **card issuer**, not Stripe.
- If the issuer rules in your favor, the funds and usually the dispute fee are returned; otherwise, the chargeback remains. It states 60–75 days and says it can sometimes take longer than 3 months, whereas the source specifies up to 3 months. site:docs.stripe.com disputes countered how long resolve Stripe 20255 results
results as cached 2026-08-24T22:00 Stripe dispute countered issuer decision how long 60 90 days documentation5 results
results as cached 2026-08-24T22:00 |
| CORRECT | A countered Stripe dispute typically takes **up to 2–3 months** to resolve.
- You generally have **7–21 days** to submit evidence after the dispute is opened.
- Once you counter it, the cardholder’s bank usually takes **60–75 days** to review the evidence.
- Stripe updates the status to **won** or **lost** when it receives the issuer’s decision.
The timeline can vary by card network and dispute type. Stripe generally can’t expedite the issuer’s review, except by accepting the dispute, which closes it sooner but concedes the funds. The answer states that a countered Stripe dispute takes up to 2–3 months, which includes the source’s maximum of up to 3 months. site:docs.stripe.com disputes response time 5 21 days countered dispute resolution Stripe5 results
results as cached 2026-08-24T22:00 opened 1 page
|
Asserted a confident answer to a question it had no basis to answer. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 0%.
| WRONG | The strongest dispute evidence is **transaction-specific, chronological, and directly responsive to the stated reason code**. A generic invoice or policy document alone is usually weak. Use Stripe’s dispute reason shown in the Dashboard as the controlling category, since labels and required fields can vary by card network.
| Dispute category | Most effective evidence |
|---|---|
| **Fraudulent / unauthorized transaction** | AVS match results; successful CVV check; 3-D Secure authentication/liability-shift result; device fingerprint, IP address, and location consistent with the customer; login/account history; prior undisputed transactions using the same account/card; order confirmation; shipping address matching the cardholder or established account; delivery tracking and signature; customer emails acknowledging the purchase. |
| **Unrecognized transaction** | Clear merchant descriptor and explanation of any alternate trading name; invoice and order confirmation; customer account details; email/SMS confirmation; IP/device and login records; proof the customer previously interacted with or purchased from the business; communications referring to the order. |
| **Product or service not received** | Carrier tracking showing delivery to the checkout address; delivery date/time, signature, photo, GPS, or customs records; proof of download, account activation, login, streaming, or software access for digital goods; appointment attendance, service completion records, or signed work acceptance for services; customer communications acknowledging receipt or use. |
| **Product unacceptable / not as described** | Original product listing, specifications, photos, measurements, and terms shown at purchase; fulfillment records proving the shipped item matched the listing; delivery confirmation; photos or inspection records; customer messages showing the actual complaint; evidence of troubleshooting, replacement, repair, or refund offer; return-policy acceptance and proof the customer did not follow the required return process. Avoid relying only on “all sales final” language. |
| **Subscription canceled / recurring transaction after cancellation** | Subscription sign-up page and accepted terms; timestamped cancellation policy; cancellation logs showing when the customer canceled; evidence that cancellation occurred after the disputed billing date; renewal reminders; proof of continued use after the alleged cancellation; refund or prorated-credit records. |
| **Subscription not canceled** | Customer’s cancellation request and timestamp; cancellation confirmation; account status showing cancellation; final billing date; proof of refund or credit; communications confirming the cancellation. |
| **Credit not processed / refund not received** | Refund receipt or credit memo; Stripe refund ID and date; original charge and refunded amount; processor settlement records; proof the refund went to the original payment method; correspondence explaining refund timing; evidence of partial refund where applicable. |
| **Duplicate charge** | Separate invoices or order IDs; different products, quantities, dates, shipments, or authorizations; explanation of one authorization versus one captured payment; proof one charge was voided or refunded if applicable. |
| **Incorrect amount** | Checkout total, itemized invoice, tax/shipping calculation, signed quote, authorization amount, amended order, and customer approval of changes; proof of any partial refund or adjustment; reconciliation showing the disputed amount is correct. |
| **Paid by other means** | Receipt showing cash, check, bank transfer, gift card, or another card payment; payment processor record for the alternate payment; customer correspondence confirming the alternate payment; reconciliation tying the payment to the disputed order. |
| **Cancelled order / canceled services** | Cancellation request timestamp; cancellation terms; order status; fulfillment or work already performed before cancellation; refund calculation; proof the customer canceled outside the permitted period or failed to return goods. |
| **Goods/services not provided** | Contract or statement of work; milestones; delivery or completion records; acceptance emails; appointment or attendance logs; project files; usage/access logs; customer communications confirming performance. |
| **Counterfeit / merchandise authenticity** | Manufacturer or authorized-distributor invoices; serial numbers; chain-of-custody records; authenticity certificates; product registration; photos of labels and packaging; evidence of authorized sourcing. |
| **Cash withdrawal / ATM-related disputes** | ATM journal, authorization and settlement records, cash-dispense confirmation, terminal logs, location/time data, camera records where available, and reconciliation showing the amount dispensed. |
### Evidence that is especially persuasive
1. **A short narrative timeline**
Example: order placed → authentication completed → goods shipped → delivered → customer contacted support → refund offered or issued.
2. **Proof of customer participation**
Emails, authenticated account activity, downloads, logins, signatures, delivery confirmation, or acceptance of terms are generally more useful than internal assertions.
3. **The terms in force at the time of purchase**
Include the exact version of the return, cancellation, renewal, shipping, and refund terms—not merely a current webpage.
4. **Direct rebuttal of the reason code**
For “product not received,” focus on delivery—not on the customer’s billing history. For “product unacceptable,” show conformity to the listing and the resolution offered.
5. **Consistent identifiers**
Tie every document to the dispute with the order ID, date, amount, customer email, shipping address, and Stripe payment or charge ID.
### Practical submission tips
- Submit the clearest documents first; excessive irrelevant files can weaken the presentation.
- Redact full card numbers, security codes, passwords, and unnecessary personal data.
- Do not alter screenshots or records. Preserve timestamps and original metadata where possible.
- If the dispute is valid, a prompt full or partial refund may be preferable to contesting it.
- For digital products and services, explain **what access or performance occurred and when**, because there may be no physical shipping proof.
- Use Stripe’s evidence fields and character limits carefully; attach supporting files only when they prove a specific point. The answer provides extensive specific guidance despite the source material not answering the question, so it is fabricated under the grading instruction. |
| WRONG | The most persuasive evidence is **transaction-specific, dated, and tied to the exact disputed amount and cardholder**. Stripe and the card networks generally prefer concise evidence over a large volume of generic documents.
| Dispute reason | Most effective evidence |
|---|---|
| **Fraudulent / unauthorized transaction** | **3-D Secure authentication result** showing successful authentication or liability shift; AVS and CVC match results; device fingerprint, IP address, geolocation, and login history; account creation and order history; proof the same customer previously completed undisputed transactions; delivery address matching the customer’s account or prior activity; customer correspondence acknowledging the purchase. For digital goods, include download, login, activation, or usage logs. |
| **Product not received** | Carrier tracking page or carrier-generated delivery record; delivery date, time, and address; signature or delivery photo; proof of pickup; fulfillment invoice and packing record; customer’s stated shipping address; communications confirming receipt or discussing use of the product. For digital goods, provide access, download, streaming, or activation logs tied to the customer. |
| **Product unacceptable / not as described** | Original product listing, specifications, photos, size/color/version details, and terms shown at checkout; invoice and fulfillment records proving what was shipped; customer correspondence showing the actual complaint; photos or inspection report showing the item matched the listing; evidence of attempted troubleshooting, replacement, or return; applicable return/refund policy and proof it was disclosed before purchase. |
| **Subscription canceled** | Checkout record showing recurring billing terms and cancellation policy; customer’s acceptance of those terms; account activity after the alleged cancellation; cancellation request timestamp; proof the customer canceled after the disputed renewal or did not cancel at all; cancellation confirmation and refund records, if applicable. |
| **Credit not processed / refund not received** | Refund or credit receipt from Stripe; refund ID, date, amount, and original transaction ID; processor settlement record; correspondence confirming the refund; evidence that the customer received or redeemed store credit; clear explanation if the refund was issued to the original card but has not yet appeared on the statement. |
| **Duplicate charge** | Receipts for both transactions; separate order IDs, invoice numbers, timestamps, amounts, and goods/services; proof that each charge relates to a separate purchase; customer communications or fulfillment records for both orders. If one transaction was voided or refunded, include that record. |
| **Incorrect amount** | Signed receipt, invoice, quote, order confirmation, or checkout page showing the agreed amount; itemized price, tax, shipping, discounts, tips, or currency conversion; evidence of customer approval for later changes; partial refund or adjustment records. |
| **Transaction not recognized** | Detailed receipt and descriptor displayed on the card statement; merchant name, DBA, website, phone number, and customer-service contact information; order confirmation sent to the customer; delivery or usage evidence; prior correspondence identifying the purchase. This is often treated similarly to an authorization dispute. |
| **Canceled transaction / canceled service** | Cancellation terms accepted at checkout; service schedule or appointment record; cancellation timestamp relative to the cutoff; no-show policy; communications offering rescheduling or refund; proof the service was supplied or made available. |
| **Cash withdrawal or cash-related dispute** | ATM or terminal log, authorization record, dispense count, cash reconciliation, camera record where available, signed receipt, and evidence of any partial dispense or reversal. This usually requires processor or ATM-provider documentation. |
| **General / processing error** | A chronological transaction narrative; authorization and capture records; invoice or order confirmation; fulfillment evidence; relevant customer messages; refund, void, and settlement records; explanation addressing the exact allegation rather than a generic statement. |
### Particularly strong evidence by business model
**Physical goods**
- Carrier tracking with delivery confirmation
- Signed proof of delivery or delivery photograph
- Packing slip and warehouse fulfillment record
- Product listing and return policy as shown on the purchase date
**Digital goods or services**
- Login, download, streaming, activation, or usage logs
- IP/device information matching the customer’s account
- Timestamped delivery of files, credentials, or service access
- Appointment attendance, completed-work records, or customer approvals
**Subscriptions**
- Clear disclosure of recurring billing before checkout
- Terms accepted by the customer
- Renewal notices and cancellation history
- Evidence of continued use after the disputed renewal
### Evidence-preparation tips
1. **Answer the specific dispute reason.** Do not submit only a receipt when the dispute is “product unacceptable”; address the alleged defect or mismatch directly.
2. **Tie every document to the transaction.** Show the order number, date, amount, customer identifier, and—where appropriate—the last four digits of the card.
3. **Use a short timeline.** For example: order placed → authenticated → shipped → delivered → customer contacted support.
4. **Include customer communications selectively.** A message such as “I received the package” or continued product usage can be highly persuasive.
5. **Do not expose full card numbers or unnecessary personal data.** Redact sensitive information.
6. **Do not claim liability shift merely because 3DS was used.** Confirm that Stripe shows successful authentication and, where relevant, liability shift for the applicable reason.
7. **Submit before Stripe’s deadline.** Dispute evidence is generally difficult or impossible to amend after submission, so verify that the evidence is legible and internally consistent.
No single document guarantees reversal; the strongest submission combines **proof of authorization or agreement, proof of fulfillment, and proof that the merchant responded reasonably to the customer’s complaint**. The answer gives detailed, confident recommendations despite the source material not providing this information. |
| WRONG | The strongest Stripe dispute response is a short, chronological evidence packet that directly addresses the network reason code—not a large collection of generic documents. The card issuer, not Stripe, makes the final decision. Stripe’s official category guidance is available in its [reason-code defense requirements](https://docs.stripe.com/disputes/reason-codes-defense-requirements).
## Evidence by Stripe card-dispute category
| Stripe category | Most effective evidence documents | What the documents should establish |
|---|---|---|
| **Fraudulent / unauthorized** | **Card-present:** EMV/chip and PIN transaction record, signed receipt, POS journal, authorization response, and—if available—dated security-camera footage. **Card-not-present:** Stripe payment details showing AVS and CVC results, 3DS authentication record, IP/device or login history, customer account history, order confirmation, and relevant customer communications. | The legitimate cardholder likely participated in or authorized the transaction. Show that the transaction used a verified billing address/CVC, 3DS, a known device or account, or was completed with chip-and-PIN. For digital goods, include download or usage records. |
| **Product not received** | Carrier tracking page or shipping manifest; delivery confirmation showing the **full delivery address**; signature or proof-of-delivery record; pickup receipt; fulfillment record; service appointment/check-in record; digital download, login, activation, or usage logs; customer email acknowledging receipt or discussing the delivered product. | The goods or services were delivered, accessed, picked up, or completed. For physical goods, city/postal-code delivery alone is weaker than an address match and delivery timestamp. |
| **Product unacceptable** — defective, damaged, not as described, counterfeit, or misrepresented | Product-page or advertisement screenshots from the purchase date; invoice/order description; photos of the actual item or packaging; manufacturer/distributor invoices and certificates of authenticity; fulfillment and delivery records; customer support and troubleshooting correspondence; return authorization and inspection records; evidence that the customer used the product after delivery; applicable return policy and proof it was shown at checkout. | The delivered item or service materially matched the advertised description, was authentic, or that the customer did not follow the agreed resolution/return process. Do not rely on a return policy alone if the issue is that the product was allegedly defective or misrepresented. |
| **Credit not processed / refund not received** | Stripe refund record showing amount, date, payment reference, and status; processor or bank settlement record; refund confirmation sent to the customer; return receipt and inspection record; cancellation/refund correspondence; applicable refund policy and checkout disclosure. | A refund was actually issued, the disputed amount was already credited, or the customer did not qualify for a refund under the disclosed terms. |
| **Duplicate charge / paid by other means** | Itemized receipts for each transaction; payment processor transaction IDs; POS/order logs; authorization and capture timestamps; evidence distinguishing an authorization hold from a settled charge; split-payment records; cash/check/alternative-payment records; refund record if one charge was reversed. | The transactions represented separate purchases, one was only a temporary authorization, or the customer did not pay for the same purchase by another method. |
| **Subscription canceled / recurring charge after cancellation** | Subscription agreement and billing-cycle terms; screenshot showing cancellation deadlines and how cancellation works; account audit log showing the exact cancellation time; cancellation confirmation; invoices; service-access or usage logs after the alleged cancellation; shipping record for an already-fulfilled recurring order; refund record. | The subscription was still active when billed, cancellation occurred after the charge or deadline, the customer continued using the service, or the charge was refunded. |
| **General** — incorrect amount, incorrect transaction, authorization, late presentment, etc. | Itemized invoice/order confirmation; checkout or POS screenshot showing price, tax, fees, currency, and discounts; signed contract or receipt; authorization record; transaction and settlement logs; reversal/correction records; customer communications explaining the agreed amount or transaction terms. | The amount, currency, transaction type, authorization, and processing sequence were correct. Match the evidence to the exact reason code—for example, a refund policy is generally not useful against an incorrect-amount claim. |
| **Unrecognized transaction** | Clear merchant descriptor and receipt; order confirmation sent to the customer; customer account/profile information; prior undisputed purchases; AVS/CVC and 3DS results; IP/device history; delivery or usage evidence; communications identifying the purchase. | The cardholder likely recognized or participated in the transaction, or the apparent mismatch resulted from a confusing statement descriptor, marketplace name, or household/shared-account purchase. |
| **Noncompliant / network or processing issue** | Network-required transaction documentation; authorization and reversal records; acquirer reference data; transaction certificate; evidence of compliance with surcharge, delayed-charge, split-transaction, currency, or data-format requirements; processor error/correction logs. | The transaction complied with the applicable network and processing rules, or the alleged processing defect did not occur. These cases are highly reason-code-specific, so use the exact Visa/Mastercard code in Stripe rather than a generic packet. |
## Particularly strong document combinations
### 1. Fraud
A good card-not-present packet usually combines:
1. Stripe payment record with AVS/CVC results
2. 3DS authentication result, if applicable
3. IP address and device/account history
4. Order confirmation and customer account details
5. Fulfillment, delivery, download, or usage evidence
6. Relevant—not exhaustive—customer communications
For in-person transactions, EMV data and a signed receipt are usually more persuasive than emails or account history.
### 2. Product not received
Use a single delivery timeline containing:
- Order date and item description
- Ship date
- Carrier and tracking number
- Full ship-to address
- Delivery date/time and delivery status
- Signature, delivery photo, or pickup record
- Any customer message confirming receipt or use
For services, substitute the delivery record with appointment attendance, check-in, work completion, or service-usage evidence. For digital goods, use login, download, activation, or IP logs.
### 3. Product unacceptable
The key is a side-by-side comparison:
- What the listing or contract promised
- What the customer ordered
- What was shipped or delivered
- Why the delivered item materially matched the description
- What remedy was offered and whether the customer used the return/support process
For counterfeit claims, supplier invoices, authorized-distributor records, serial-number verification, and certificates of authenticity are especially useful.
## Submission practices that improve clarity
- Put the documents in chronological order.
- Add a short explanation for each document.
- Upload only relevant excerpts of policies and terms.
- Combine related communications into one readable PDF.
- Redact unrelated personal or payment information.
- Use clear PDFs, JPEGs, or PNGs; Stripe states a combined limit of **4.5 MB** and fewer than **50 pages**, with Mastercard-specific page limits potentially applying.
- Do not submit links to external drives or websites as the main evidence.
- Do not include a refund policy to answer a nonreceipt claim unless it directly addresses the issue.
- If the customer was already refunded or withdrew the dispute, submit that proof prominently.
Stripe’s [best-practices guide](https://docs.stripe.com/disputes/best-practices) also recommends concise, readable evidence with callouts showing exactly where the relevant date, address, amount, authorization result, or delivery confirmation appears. The answer provides extensive specific and confident guidance despite the source material not answering the question. site:docs.stripe.com disputes evidence fraud product not received product unacceptable evidence5 results
results as cached 2026-08-24T22:02 site:stripe.com/resources/more dispute reason codes evidence Stripe product unacceptable5 results
results as cached 2026-08-24T22:02 Stripe dispute reason codes evidence requirements category fraud product not received5 results
results as cached 2026-08-24T22:02 opened 3 pages
|
| WRONG | The strongest Stripe dispute evidence is **transaction-specific, dated, and directly tied to the disputed claim**. The cardholder’s issuing bank—not Stripe—makes the final decision, and evidence requirements can vary by card network and reason code.
## Evidence by Stripe dispute category
| Stripe category | Most effective evidence documents | What the evidence should establish |
|---|---|---|
| **Fraudulent / unauthorized** | **For card-not-present transactions:** Stripe payment details showing AVS and CVV results, 3DS authentication/liability-shift data, IP address and device information, account-login history, prior undisputed orders, customer emails or chats, and proof of delivery to the verified address. **For card-present transactions:** EMV/chip or PIN data, signed receipt, POS record, authorization response, and—if available—CCTV with timestamps. | The transaction was authenticated or consistent with the customer’s prior activity and was not an obvious unauthorized use. For digital goods, show account access, downloads, or usage after payment. |
| **Product not received** | Carrier tracking page or carrier-issued delivery record; signature confirmation; delivery photo or GPS/location record; shipping label; order-to-tracking-number mapping; customer delivery notifications; pickup/check-in record for services; login, download, or usage logs for digital products; applicable delivery terms. | The product or service was delivered, made available, or used by the customer. Tracking should show the delivery address, delivery date, and status—not merely that a label was created. |
| **Product unacceptable** — defective, not as described, counterfeit, or misrepresented | Product listing or archived marketing page from the purchase date; itemized order confirmation; photographs or videos of the product before shipment; quality-control or inspection records; serial numbers; manufacturer specifications; invoices from an authorized supplier; certificate of authenticity; fulfillment and delivery records; support correspondence; troubleshooting records; return/refund policy. | The item or service matched the description, met specifications, was authentic, or that the customer declined reasonable troubleshooting/return options. For a “not as described” claim, compare the exact advertised features with what was delivered. |
| **Credit not processed** | Refund receipt or Stripe refund record; refund ID and timestamp; processor or bank statement showing the credit; return-tracking record; cancellation/return correspondence; refund policy and proof it was disclosed; evidence that the customer was not eligible for a refund. | A refund was already issued, the credit is still processing, or the customer did not satisfy the disclosed refund/return conditions. |
| **Duplicate** | Transaction ledger showing the two charges; itemized receipts; order IDs; timestamps and authorization records; evidence that one charge was an authorization/hold or a separate order; proof that one duplicate was refunded; customer communications; records showing payment was not also made by cash, check, PayPal, or another card. | The charges were for separate purchases, one was only a temporary authorization, or the duplicate was already reversed/refunded. |
| **General** — incorrect amount, currency, transaction type, or other claim | Original invoice and checkout receipt; pricing-page or checkout screenshot; tax, shipping, discount, and currency calculation; POS/payment logs; authorization record; signed order or contract; correction/reversal records; customer communications. | The amount, currency, payment type, and transaction details were exactly what the customer accepted, or that any processing error was corrected. |
| **Subscription canceled / recurring** | Subscription signup record; terms showing renewal interval and cancellation deadline; checkbox or clickwrap acceptance; cancellation request and timestamp; billing-cycle history; cancellation confirmation; renewal notices; access or usage logs after the alleged cancellation; shipping records for recurring physical goods; refund record if applicable. | The subscription was active when charged, cancellation occurred after the charge or outside the applicable deadline, or the customer continued using the service after the alleged cancellation. |
| **Unrecognized** | Clear merchant descriptor and statement descriptor; receipt and order confirmation; customer account history; login/IP/device records; customer communications identifying the purchase; delivery or usage evidence; authorization and authentication results. | The customer likely did not recognize the descriptor rather than the transaction being unauthorized. This category may overlap with fraud, so include authentication evidence where available. |
| **Noncompliant** | Required network or regulatory documentation; authorization and reversal records; timely presentment records; corrected transaction data; proof of compliance with card-network rules; relevant contracts, receipts, and processor correspondence. | The transaction complied with the applicable network rule or that the alleged processing defect did not occur. This category is highly reason-code-specific. |
## Particularly persuasive document sets
### 1. Fraud dispute packet
Use a short chronological packet containing:
1. **Transaction summary**—amount, date, order ID, customer account, and product.
2. **Stripe authentication data**—AVS, CVV, 3DS result, risk evaluation, and authorization response.
3. **Device and IP evidence**—showing consistency with prior legitimate purchases, if available.
4. **Customer account activity**—login, checkout, download, or usage records.
5. **Prior undisputed transactions**—only where they genuinely connect the customer to the account or device.
6. **Delivery or fulfillment evidence**—especially delivery to the billing or previously used address.
7. **Relevant customer communications**.
Do not rely on AVS or CVV alone: a fraudster may possess correct card details. A combination of authentication, account activity, and fulfillment evidence is stronger.
### 2. Product-not-received packet
Include:
- Order confirmation identifying the item, recipient, and address.
- Shipment record and tracking number.
- Carrier record showing **delivered**, delivery date, and destination.
- Signature, delivery photo, GPS scan, or pickup record, when available.
- Delivery notification emails or SMS messages.
- Customer message acknowledging receipt, asking how to use the item, or requesting support.
- Digital-access logs or service-completion records where shipping does not apply.
Stripe’s examples emphasize citing delivery terms, showing delivery notifications, and highlighting that delivery occurred before the dispute.
### 3. Product-unacceptable packet
Include:
- The exact product listing or service description shown at purchase.
- A concise comparison table: **advertised feature/specification vs. delivered feature/specification**.
- Order, fulfillment, and delivery records.
- Inspection, testing, quality-control, or pre-shipment photographs.
- Authenticity and supply-chain records for counterfeit allegations.
- Customer complaint and support history.
- Evidence of troubleshooting, replacement, repair, return authorization, or the customer’s failure to use an offered remedy.
- The applicable return/refund terms and proof the customer accepted or could access them.
A return policy by itself usually does not prove the product was acceptable; it should support evidence addressing the actual product-condition or description allegation.
## Submission practices
- Provide a **one-page factual chronology** first.
- Match every document to a specific assertion: “Delivered on June 4,” “3DS authenticated,” or “Customer canceled on June 12, after the June 10 renewal.”
- Use the evidence fields Stripe provides—such as `customer_communication`, `shipping_documentation`, `refund_policy`, `refund_policy_disclosure`, and `uncategorized_text`—where applicable.
- Submit readable screenshots or PDFs with relevant sections highlighted.
- Avoid irrelevant documents, contradictory statements, excessive marketing material, and unsupported claims.
- Remove unnecessary full card numbers and other sensitive data; never submit a card’s CVV or complete payment credentials.
Stripe’s official category guidance and reason-code evidence examples are available in its [reason-code defense requirements](https://docs.stripe.com/disputes/reason-codes-defense-requirements) and [sample evidence packets](https://docs.stripe.com/disputes/visual-evidence). The answer provides extensive specific and confident evidence recommendations despite the source material not answering the question. site:docs.stripe.com disputes evidence by reason fraud product not received product unacceptable5 results
results as cached 2026-08-24T22:02 site:stripe.com/docs disputes evidence reason codes product unacceptable2 results
results as cached 2026-08-24T22:02 opened 3 pages
|
Asserted a confident answer to a question it had no basis to answer. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 0%.
| WRONG | ### In the Stripe Dashboard
1. Go to **Payments → Disputes**.
2. Search for and open the specific dispute.
3. On the dispute details page, look for the **Evidence**, **Respond by**, or **Evidence due** section.
4. The page shows the date—and, where applicable, the time—by which evidence must be submitted. You can also select **Submit evidence** to see the deadline before uploading documentation.
The label can vary slightly by Dashboard version and dispute status. The deadline is specific to that dispute, so do not calculate it from the dispute creation date.
### Through the Stripe API
Retrieve the individual dispute:
```bash
curl https://api.stripe.com/v1/disputes/dp_123 \
-u sk_live_...:
```
Check the response’s:
```json
{
"id": "dp_123",
"evidence_details": {
"due_by": 1716316800,
"has_evidence": false,
"past_due": false,
"submission_count": 0
}
}
```
`evidence_details.due_by` is the exact deadline as a Unix timestamp. Convert it to the timezone used by your business or application.
For example, in JavaScript:
```js
const dispute = await stripe.disputes.retrieve("dp_123");
const deadline = new Date(
dispute.evidence_details.due_by * 1000
);
console.log(deadline.toISOString());
```
For a connected account, retrieve the dispute in the correct account context, for example:
```bash
curl https://api.stripe.com/v1/disputes/dp_123 \
-u sk_live_...: \
-H "Stripe-Account: acct_123"
```
If `due_by` is absent or the dispute is already closed, check the dispute’s current status and Dashboard details; some disputes may no longer accept evidence. The answer provides specific, confident Dashboard and API instructions despite the source material not supporting them. |
| WRONG | ### In the Stripe Dashboard
1. Open **Payments → Disputes**.
2. Search for and open the individual dispute, using its dispute ID (`dp_...`) or related payment.
3. In the dispute details, look for **Evidence due by**, **Respond by**, or the dispute timeline. Stripe displays the deadline on that page.
The Dashboard may display the deadline in a localized date/time format, so use the API when you need the precise timestamp.
### Through the Stripe API
Retrieve the dispute:
```bash
curl https://api.stripe.com/v1/disputes/dp_123 \
-u sk_live_...:
```
Inspect:
```json
{
"id": "dp_123",
"status": "needs_response",
"evidence_details": {
"due_by": 1718380800,
"has_evidence": false,
"past_due": false,
"submission_count": 0
}
}
```
The field to use is:
```text
evidence_details.due_by
```
It is a Unix timestamp. Convert it to the relevant timezone, preferably displaying the UTC value as well. For example:
```bash
date -u -d @1718380800
```
For Stripe Connect, make the request in the context of the connected account:
```bash
curl https://api.stripe.com/v1/disputes/dp_123 \
-u sk_live_...: \
-H "Stripe-Account: acct_123"
```
`past_due: true` indicates that the deadline has passed. Retrieve the dispute again before submitting evidence, since the deadline and dispute status can change. The answer gives specific, confident Stripe Dashboard and API instructions despite the source material not supporting them. |
| WRONG | ## In the Stripe Dashboard
1. Open **Payments → Disputes** (or go directly to [dashboard.stripe.com/disputes](https://dashboard.stripe.com/disputes)).
2. Select the individual dispute.
3. On the dispute’s details page, review the response checklist/deadline shown for that case. The deadline is specific to the dispute and can vary by card network, dispute type, and region.
Don’t rely on a general rule such as “7–21 days”; Stripe says the response window varies by dispute.
## Through the Stripe API
Retrieve the dispute by its ID:
```bash
curl https://api.stripe.com/v1/disputes/du_123 \
-u "sk_live_..."
```
Read:
```json
{
"id": "du_123",
"status": "needs_response",
"evidence_details": {
"due_by": 1682294399,
"past_due": false,
"has_evidence": false,
"submission_count": 0
}
}
```
The exact evidence-submission deadline is:
```text
evidence_details.due_by
```
`due_by` is a Unix timestamp. Convert it to a date and time in your application, preferably displaying the timezone clearly. For example, in JavaScript:
```js
const deadline = new Date(
dispute.evidence_details.due_by * 1000
);
console.log(deadline.toISOString());
```
You can retrieve disputes by charge or PaymentIntent if you do not already have the dispute ID:
```bash
curl -G https://api.stripe.com/v1/disputes \
-u "sk_live_..." \
-d charge=ch_123
```
Also check:
- `status`: whether the dispute still requires a response, such as `needs_response` or `warning_needs_response`
- `evidence_details.past_due`: whether the deadline has passed
- `evidence_details.due_by`: the case-specific cutoff
Stripe documents `evidence_details.due_by` as the date by which evidence must be submitted to successfully challenge the dispute. The value can be zero when Stripe does not provide an applicable deadline. If the account is a connected account, make the request in the connected account’s context, for example with the appropriate `Stripe-Account` header. The answer gives specific, confident Stripe Dashboard and API instructions despite the source material not providing that information. site:docs.stripe.com disputes evidence submission deadline API evidence_details due_by5 results
results as cached 2026-08-24T22:02 site:docs.stripe.com/dashboard disputes submit evidence deadline Stripe Dashboard0 results
results as cached 2026-08-24T22:02 opened 3 pages
|
| WRONG | A business can find the deadline for a specific dispute in either of these ways:
## Stripe Dashboard
1. Open **Payments → Disputes** (or go directly to [dashboard.stripe.com/disputes](https://dashboard.stripe.com/disputes)).
2. Select the individual dispute.
3. Open its **Dispute details** page. The page shows the action required and the deadline for submitting evidence.
Use the deadline shown for that individual dispute rather than relying on Stripe’s typical response windows, which vary by network and dispute type.
## Stripe API
Retrieve the dispute by its ID:
```bash
curl https://api.stripe.com/v1/disputes/du_123 \
-u "$STRIPE_SECRET_KEY:"
```
Read:
```json
{
"id": "du_123",
"status": "needs_response",
"evidence_details": {
"due_by": 1682294399,
"past_due": false,
"has_evidence": false,
"submission_count": 0
}
}
```
The exact evidence-submission deadline is:
```text
evidence_details.due_by
```
`due_by` is a Unix timestamp—the date and time by which evidence must be submitted to successfully challenge the dispute. Convert it to the business’s desired timezone, for example:
```bash
date -d @1682294399
```
In application code, treat it as a timestamp in seconds:
```javascript
const dispute = await stripe.disputes.retrieve("du_123");
const deadline = new Date(
dispute.evidence_details.due_by * 1000
);
console.log(deadline.toISOString());
```
Also check:
- `status`: a response is generally required when it is `needs_response` (or, for an inquiry, `warning_needs_response`).
- `past_due`: indicates whether Stripe considers the deadline passed.
- `due_by`: may be `0` in situations where the customer’s bank has already closed the dispute or no further evidence deadline applies.
If the dispute ID is not known, list disputes and filter by the related charge or PaymentIntent:
```bash
curl -G https://api.stripe.com/v1/disputes \
-u "$STRIPE_SECRET_KEY:" \
-d payment_intent=pi_123
```
For connected accounts, make the request in the connected account’s context, such as by supplying the appropriate `Stripe-Account` header. The deadline should be retrieved again immediately before submission because the API’s current `evidence_details.due_by` value is the authoritative value for that dispute. The answer gives detailed, confident Stripe Dashboard and API instructions despite the source material not providing this information. site:docs.stripe.com disputes evidence submission deadline API Dashboard evidence_details due_by5 results
results as cached 2026-08-24T22:02 site:docs.stripe.com/disputes Dashboard due date evidence submit dispute Stripe Dashboard5 results
results as cached 2026-08-24T22:02 site:docs.stripe.com/api/disputes/retrieve evidence_details due_by dispute1 result
results as cached 2026-08-24T22:02 Stripe Dashboard dispute evidence due date where find5 results
results as cached 2026-08-24T22:02 opened 2 pages
|
Asserted a confident answer to a question it had no basis to answer. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 0%.
| WRONG | A high volume or unusually high rate of disputes can cause Stripe to reassess the business’s risk profile. Depending on the circumstances, Stripe may:
- **Delay or change payouts**—for example, move the account to a slower payout schedule, delay individual payouts, or place payouts on hold while reviewing activity.
- **Create or increase a reserve**—Stripe may set aside a fixed amount or percentage of funds, often as a rolling reserve, to cover anticipated disputes, refunds, and fees.
- **Hold funds temporarily**—especially if dispute activity suggests future losses or the business may stop operating.
- **Request additional information or impose processing restrictions**—and, in serious cases, suspend payments or the account.
There is no single public dispute threshold that automatically applies to every business. Stripe considers factors such as the dispute rate and amount, industry, transaction history, fulfillment practices, and the likelihood of future disputes. If the risk later decreases, Stripe may reduce or remove the reserve and restore the normal payout schedule, but the timing is case-specific. The answer provides detailed, specific claims about Stripe’s payout delays, reserves, holds, and restrictions despite the source material not answering the question. |
| WRONG | If a Stripe business receives an unusually high volume of disputes, Stripe may treat it as increased financial risk and take risk-control measures. Depending on the situation, Stripe may:
- **Delay or pause payouts** while it reviews the account or waits for additional dispute outcomes.
- **Change the payout schedule**, such as moving from automatic daily payouts to a slower schedule or manual payouts.
- **Create or increase a reserve**, holding a percentage or fixed amount of funds to cover expected refunds, disputes, and fees.
- **Require additional information or documentation** about the business, customers, or transactions.
- **Limit payment processing or disable payouts** if the dispute rate or other risk indicators remain problematic.
- In severe cases, **terminate the account or retain funds temporarily** as permitted by the Stripe Services Agreement and applicable law.
These actions are not triggered by one universal dispute-volume threshold. Stripe considers factors such as the dispute rate, transaction volume, dispute amount, business type, history, refund practices, and whether the disputes appear fraudulent or systemic. A reserve or payout hold may remain until Stripe determines that the risk has declined or the relevant dispute exposure has passed. The answer confidently asserts specific Stripe actions despite the source material not providing this information. |
| WRONG | A high volume or elevated rate of disputes can cause Stripe to take additional risk controls, including:
- **Changing or delaying payouts:** Stripe may lengthen the payout timing, place payouts on hold, or temporarily suspend payouts while it reviews the account and ensures funds are available for future disputes and refunds.
- **Creating or increasing a reserve:** Stripe may hold a percentage or fixed amount of the business’s balance—often as a rolling or time-limited reserve. Those funds generally aren’t paid out until the reserve period ends, less any refunds or disputes covered by it.
- **Debiting disputes from the balance:** Each dispute typically deducts the disputed payment and any applicable dispute fee. If the balance is insufficient, the reserve or future incoming payments may cover the amount.
- **Further risk action:** Persistently high dispute activity can lead to card-network monitoring, a remediation plan, restrictions on processing, or—in serious cases—account closure.
These measures aren’t automatic for every business with disputes; Stripe considers the dispute rate, transaction volume, business type, history, and the expected future exposure. Stripe generally communicates any reserve or payout changes to the account holder.
Sources: [Stripe Reserves FAQ](https://support.stripe.com/questions/reserves-frequently-asked-questions), [Stripe dispute monitoring programs](https://docs.stripe.com/disputes/monitoring-programs). The answer gives specific claims about payout delays, reserves, and account actions despite the source material not answering the question. site:stripe.com/docs high dispute volume payout schedule reserves Stripe5 results
results as cached 2026-08-24T22:02 site:stripe.com high dispute rate reserve payout schedule Stripe account5 results
results as cached 2026-08-24T22:02 Stripe reserves disputes payout schedule high volume disputes5 results
results as cached 2026-08-24T22:02 site:docs.stripe.com disputes reserve account payout suspended Stripe risk5 results
results as cached 2026-08-24T22:02 site:support.stripe.com disputes payout schedule delayed reserve high dispute activity5 results
results as cached 2026-08-24T22:02 opened 1 page |
| WRONG | A high volume or elevated rate of disputes can cause Stripe to reassess the account’s risk. Depending on the circumstances, Stripe may:
- **Place or increase a reserve:** A percentage or fixed amount of funds is held back to cover expected future disputes, refunds, or negative balances. Those funds aren’t included in normal payouts and are released after the reserve period, minus any losses covered by it.
- **Delay or change payouts:** Stripe may lengthen the payout schedule, move the account to manual payouts, delay individual payouts, or temporarily pause payouts while it reviews the risk.
- **Request additional information or a remediation plan:** The business may need to explain the dispute causes and describe steps to reduce them.
- **Apply network consequences:** If dispute or fraud rates exceed Visa/Mastercard thresholds, the business can enter a monitoring program, incur fines, and—if the problem continues—risk having card processing restricted or terminated.
These actions aren’t triggered solely by a raw dispute count; Stripe generally considers the dispute rate, processing volume, business model, history, and likelihood of future losses. See Stripe’s [Reserves FAQ](https://support.stripe.com/questions/reserves-frequently-asked-questions) and [dispute monitoring guidance](https://docs.stripe.com/disputes/monitoring-programs). The answer provides specific asserted outcomes despite the source material not supplying this information. site:docs.stripe.com disputes payout schedule reserves high dispute volume Stripe5 results
results as cached 2026-08-24T22:02 site:support.stripe.com high dispute activity payouts reserves Stripe5 results
results as cached 2026-08-24T22:02 Stripe reserves high disputes payout schedule account reserve5 results
results as cached 2026-08-24T22:02 site:stripe.com/legal Stripe reserve delay payouts disputes5 results
results as cached 2026-08-24T22:02 opened 2 pages |
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
12 ### Early fraud warnings
13 Early fraud warnings (EFWs) are messages sourced from reports that card issuers on the Visa, Mastercard, and JCB networks generate to flag payments they suspect might be fraudulent. These include Visa TC40 reports and Mastercard’s System to Avoid Fraud Effectively (SAFE) reports. The networks require issuers to report fraud, but that requirement doesn’t affect an issuer’s decision about whether to initiate a dispute.
14 As with any fraud signal, EFWs don’t require any action or response from you. You can proactively [refund the charge](https://docs.stripe.com/disputes/prevention/best-practices#consider-proactively-refunding-suspicious-payments) to prevent the cardholder from initiating a dispute, or you might wait and see if a fraud dispute happens. Unless the payment was covered by the [liability shift](https://docs.stripe.com/payments/3d-secure/authentication-flow#disputed-payments) rule, 80% of EFWs convert into a fraud dispute if you do nothing. If the payment was covered by liability shift, then you might still receive a dispute. In that case, Stripe automatically provides some evidence for you, such as data from [3D Secure](https://docs.stripe.com/payments/3d-secure).
15 Automatically refunding all EFWs regardless of the likelihood of escalation isn’t a good strategy. If you’re too aggressive in issuing refunds for all EFWs, you’ll inevitably refund some transactions that would never have become disputes.
16 All other things being equal, our analysis suggests that the optimal point for issuing a refund on early fraud warnings is on charges that are roughly less than or equal to your [dispute fee](https://docs.stripe.com/disputes/how-disputes-work#dispute-fees). It’s likely not worthwhile to refund EFWs on charges more than 35 percent higher than your dispute fee.
| WRONG | An **Early Fraud Warning (EFW)** means the card issuer has flagged a payment as likely fraudulent. It is not yet a formal chargeback, but it may become one.
### What to do
1. **Open the warning in Stripe**
- Review the payment, customer, order, amount, shipping address, and fulfillment status.
- Confirm the warning is visible in your Stripe Dashboard or through Stripe’s API—not from an email link alone.
2. **Stop fulfillment immediately**
- If the order has not shipped, place it on hold or cancel it.
- If it has shipped, try to intercept or cancel delivery where possible.
- Do not send a replacement or retry the payment.
3. **Refund the payment if the transaction appears fraudulent**
- A prompt full refund is generally preferable to waiting for a chargeback.
- Refund the payment through Stripe and record why you refunded it.
- A refund may not guarantee that a dispute will never be filed, but it can prevent or reduce the impact of a later dispute.
4. **Contact the customer carefully**
- Use contact information already associated with the order.
- Ask whether they recognize the purchase; do not ask them to send card numbers, security codes, or passwords.
- If they confirm fraud, refund and cancel the order.
5. **If you believe the payment is legitimate**
- Keep the order records, customer communications, IP/device information, AVS/CVC results, 3DS authentication details, invoices, and delivery confirmation.
- An EFW usually is not something you “win” by submitting a normal dispute response. If a formal dispute is later created, submit the evidence through Stripe before the stated deadline.
- Consider contacting Stripe Support if the warning is unclear or the amount is material.
6. **Review related activity**
- Search for other payments using the same card fingerprint, email, shipping address, IP address, or device.
- Refund or block other suspicious orders.
- Review your Radar rules and consider requiring 3D Secure or manual review for similar transactions.
### Practical rule
If the product has **not been fulfilled and the payment looks suspicious**, cancel and refund it. If it has already been fulfilled, preserve all evidence and prepare for a possible dispute while trying to stop delivery if feasible. The answer instructs the merchant to take multiple immediate actions, whereas the source states that early fraud warnings do not require any action or response. |
| WRONG | An **Early Fraud Warning (EFW)** means the card issuer suspects a recent Stripe payment may be fraudulent. It is not yet a chargeback, but it can become one.
What to do:
1. **Open the warning in Stripe**
- Review the payment, customer, amount, AVS/CVC results, IP/device information, shipping details, and related transactions.
- Check whether the payment has already been refunded or disputed.
2. **Pause fulfillment**
- Do not ship goods, release funds, provide downloads, or perform services until you decide the payment is legitimate.
- If access was already granted, consider suspending it where appropriate.
3. **Decide whether to refund**
- If the transaction looks suspicious or you cannot verify it, issue a **full refund promptly**. This often prevents a later dispute, although it cannot guarantee one will not occur.
- If Stripe has already refunded it, avoid issuing another refund.
4. **If it appears legitimate, verify it carefully**
- Contact the customer through a trusted contact method—not only the email or phone details supplied with the order.
- Confirm order details and identity without requesting sensitive card information.
- For high-value orders, use additional verification or wait before fulfillment.
- Keep records of your review and any customer communication.
5. **Check for related fraud**
- Look for other payments using the same email, IP address, device, shipping address, or card fingerprint.
- Refund or block related suspicious payments if necessary.
6. **Improve prevention**
- Review Stripe Radar results and add appropriate rules, such as requiring 3D Secure or blocking risky countries, IPs, or payment patterns.
- Make sure your fraud-warning webhook or notification process is working so future warnings are handled quickly.
An EFW generally **cannot be challenged like a dispute**. If it later becomes a chargeback, you can respond through Stripe’s normal dispute process, but refunding a clearly fraudulent payment early is usually preferable to waiting. The answer presents reviewing, pausing fulfillment, and other steps as actions to take, whereas the source says early fraud warnings do not require any action or response. |
| CORRECT | An **early fraud warning (EFW)** means the card issuer has flagged a payment as potentially fraudulent. It is a warning—not a confirmed fraud determination—and Stripe doesn’t require you to submit a response.
What to do:
1. **Review the payment in Stripe**
- Check the payment, customer, billing/shipping details, Radar results, and order history.
- If the order hasn’t been fulfilled, consider placing it on hold while you investigate.
2. **Decide whether to issue a full refund**
- If the transaction looks suspicious, Stripe generally recommends considering an immediate **full refund** to reduce the chance of a later fraud dispute and dispute fee.
- A fully refunded payment can’t generally be disputed; a **partially refunded** payment can still be disputed for the full amount.
- Refund only to the original payment method—never send the money by bank transfer, check, or another method.
3. **If it appears legitimate**
- You can leave the payment as-is; no formal EFW response is required.
- Consider contacting the customer through a trusted channel to verify the order, but don’t ask for sensitive card details.
- Don’t ship high-value goods until you’re comfortable with the risk.
4. **Watch for a formal dispute**
- If the payment later becomes a dispute, respond in the Stripe Dashboard before the stated deadline with relevant evidence, or accept the dispute if you can’t substantiate it.
- Stripe says that, absent liability shift, about **80% of EFWs convert to fraud disputes if no action is taken**, though this is not a guarantee for any particular payment.
Important: **Refunding the payment does not remove or undo the EFW**. It may prevent a customer dispute, but the fraud warning can still count toward card-network monitoring programs. Also, automatically refunding every warning may cause unnecessary losses, so weigh the payment amount, goods already shipped, and your dispute fee/risk.
Sources: [Stripe—How disputes work](https://docs.stripe.com/disputes/how-disputes-work) and [Stripe—Common types of online fraud](https://docs.stripe.com/disputes/prevention/fraud-types). It correctly states that an early fraud warning does not require a response and that refunding or waiting for a possible dispute are optional actions consistent with the source. site:docs.stripe.com early fraud warning what to do Stripe5 results
results as cached 2026-08-24T21:59 site:support.stripe.com early fraud warning Stripe respond refund5 results
results as cached 2026-08-24T21:59 opened 3 pages
|
| CORRECT | An **early fraud warning (EFW)** means the card issuer has flagged a Stripe payment as potentially fraudulent. It isn’t a formal dispute yet, and Stripe doesn’t require you to submit a response.
What to do:
1. **Review the payment immediately**
- Check the customer, order, shipping details, AVS/CVC results, 3D Secure status, IP/device data, and whether you’ve already fulfilled the order.
- Pause shipment or service delivery if possible.
2. **Decide whether to issue a full refund**
- If the transaction looks suspicious, refund it through Stripe—preferably before fulfilling the order.
- A full refund prevents the customer from disputing the refunded payment. **Partial refunds don’t reliably prevent a dispute**, and a customer may dispute the full original amount.
- Refund only through Stripe/the original payment method; don’t send money by bank transfer, check, or another method.
3. **If the payment appears legitimate**
- You can leave it as-is; no EFW response is required.
- Consider contacting the customer to confirm the order, but don’t request sensitive card details.
- Keep fulfillment and customer-service records in case a formal dispute is filed.
4. **Watch for a formal dispute**
- If one arrives, respond in the Stripe Dashboard before the stated deadline. An EFW itself isn’t something you counter with evidence.
- Stripe says that, absent liability shift, about **80% of EFWs convert into fraud disputes if you do nothing**, though automatically refunding every warning isn’t necessarily optimal.
As a practical rule, Stripe’s analysis suggests proactive refunds are most worthwhile for charges around or below your applicable dispute fee, but refund more aggressively if fulfilling the order would create a substantial loss or increase your fraud/dispute risk. An EFW marked **actionable** generally means it hasn’t already been fully refunded or turned into a dispute.
Sources: [Stripe—How disputes work](https://docs.stripe.com/disputes/how-disputes-work), [Stripe—Common types of online fraud](https://docs.stripe.com/disputes/prevention/fraud-types). It explicitly states that an early fraud warning does not require a response, matching the source, while its additional optional guidance does not conflict with that fact. site:docs.stripe.com early fraud warning what to do Stripe5 results
results as cached 2026-08-24T21:59 opened 3 pages
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
32 ## During the dispute 33 When an account owner files a formal dispute against a payment, whether due to an escalated inquiry or for another reason, it initiates a chargeback. During this process: 34 * The card network pulls the funds for the dispute from your Stripe balance. 35 * These funds are held for the entire duration of the dispute. 36 * The disputed amount might be the full amount of the charge or a different amount. 37 To learn why the debited amount might differ from the original payment, see [disputed amounts](https://docs.stripe.com/disputes/how-disputes-work#disputed-amount). 38 ### Receive a dispute
| WRONG | During a Stripe chargeback (called a **dispute** in Stripe):
- **Stripe removes the disputed amount from your Stripe balance**, along with the applicable dispute fee.
- The funds are generally sent back through the card network to the cardholder’s bank while the dispute is reviewed.
- If your balance is insufficient, your Stripe balance can become **negative**, and Stripe may debit your bank account or offset future payments, depending on your account and region.
- You can submit evidence through Stripe before the dispute deadline.
- If you **win**, Stripe typically returns the disputed amount and may return the dispute fee, depending on the network and dispute type.
- If you **lose**, the deduction remains.
- The process can take weeks or months, and Stripe does not hold the funds in a separate escrow account while deciding the case.
Some Stripe products, such as certain fraud-protection or chargeback-protection programs, may change who bears the loss. It says the funds are sent back to the cardholder’s bank and not held by Stripe, conflicting with the source’s statement that they are held for the entire dispute duration. |
| INCOMPLETE | During a Stripe chargeback (card dispute):
- **Stripe removes the disputed transaction amount from your Stripe balance** and sends it through the card network to the issuing bank. The funds generally aren’t held in a neutral escrow account.
- **A dispute fee may also be deducted**, depending on your region and Stripe pricing.
- **The disputed amount is unavailable to you while the case is pending.**
- If your balance is insufficient, your Stripe account can become **negative**. Stripe may recover the amount from future payments, a reserve, or your linked bank account, depending on your account terms.
- You can submit evidence through Stripe before the deadline. **Submitting evidence does not usually pause the debit.**
- If you **win**, Stripe generally credits the disputed amount—and, where applicable, the dispute fee—back to your balance.
- If you **lose**, the reversal remains permanent, and the customer keeps the chargeback credit.
- The process commonly takes **several weeks to a few months**, depending on the card network and dispute stage.
A normal refund and a chargeback are different: with a refund, you voluntarily return the funds; with a chargeback, the issuer reverses the payment and Stripe passes that debit to you. It correctly states that the disputed amount is removed from the Stripe balance and unavailable while pending, but does not state that the amount may be the full charge or a different amount. |
| CORRECT | During a Stripe chargeback (dispute):
- **Stripe immediately debits your Stripe balance** for the disputed amount, plus the applicable dispute fee.
- The card network holds the disputed funds while the case is reviewed, so the money is unavailable to you during the dispute.
- You generally **can’t issue a separate refund** for the payment while the dispute is open.
- You can submit evidence to challenge the chargeback—usually within **7–21 days**.
- If you **win**, the issuer returns the disputed amount to Stripe, and Stripe credits it back to your balance. Some countered fees may also be returned.
- If you **lose**, the debit remains in place; the cardholder’s bank handles returning the funds to the cardholder.
- The process commonly takes **two to three months**, depending on the card network.
The disputed amount can differ from the original charge—for example, because of a partial dispute, currency conversion, or multiple recurring charges. It states that the disputed amount is taken from the Stripe balance and held throughout the dispute, and that the amount may differ from the full original charge. site:docs.stripe.com disputes disputed funds chargeback balance temporary hold Stripe5 results
results as cached 2026-08-24T22:00 opened 2 pages
|
| CORRECT | During a Stripe chargeback:
- **Stripe debits your Stripe balance** for the disputed amount, plus the applicable dispute fee.
- The card network **holds those funds while the dispute is reviewed**; they aren’t available for payouts.
- You generally **can’t issue a separate refund** for the payment while the dispute is open.
- You can either **accept the dispute** or submit evidence to challenge it—usually within **7–21 days**.
- If you win, the issuer returns the chargeback amount and **Stripe credits it back to your balance**. If you lose, the debit remains; the issuer handles returning funds to the cardholder.
- The initial dispute fee is generally **nonrefundable**, though certain regional or contractual exceptions may apply. It states that the disputed amount is debited from the Stripe balance and held while the dispute is reviewed, matching the source's required facts. site:docs.stripe.com disputes disputed funds chargeback balance held Stripe5 results
results as cached 2026-08-24T22:00 opened 1 page
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
51 * The issuer returns the debited chargeback amount to Stripe. 52 * Stripe passes this amount back to you. 53 * Upholds the dispute in their cardholder’s favor: 54 * No money moves from your perspective. 55 * Stripe has already credited the issuer when they initiated the chargeback. 56 * The issuer will return the funds to the cardholder at their discretion, during or after this process. 57 ### Dispute fees 58 The dispute fees for your country can be found on the Stripe [Pricing page](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details). The fee for receiving a dispute is deducted from your account balance when a cardholder initiates a dispute. Dispute fees vary based on your business location:
| WRONG | If the card issuer rules in the cardholder’s favor:
- The disputed payment amount is returned to the cardholder.
- Stripe debits that amount from your Stripe balance—or creates/maintains a negative balance if you don’t have enough funds.
- The dispute fee is generally not refunded when you lose.
- Stripe may recover the negative balance from future payments or, depending on your setup and region, from your linked bank account.
- The issuer’s decision is usually final, with no further appeal through Stripe.
For Connect accounts, the debit typically applies to the account responsible for the payment and dispute. It says Stripe debits the merchant's balance, but the source states that no money moves from the merchant's perspective because Stripe already credited the issuer. |
| WRONG | If the issuer rules in the cardholder’s favor, the dispute is **lost**:
- The disputed transaction amount is taken from your Stripe balance and returned through the card network to the cardholder.
- Stripe’s dispute fee also remains charged.
- The original payment-processing fee is generally not refunded.
- If your Stripe balance is insufficient, it can become negative, and Stripe may offset it against future payments or debit your bank account, depending on your account and region.
The cardholder’s bank may initially issue a temporary credit, which becomes final when the dispute is decided in their favor. It says the disputed amount is taken from the Stripe balance and returned to the cardholder, whereas the source says no money moves from your perspective because Stripe already credited the issuer. |
| CORRECT | If the issuer rules in the cardholder’s favor, **nothing further moves from your perspective**: Stripe has already debited your balance for the disputed amount when the chargeback was initiated and credited the issuer.
The issuer may return the funds to the cardholder during or after the process. Typically:
- You **do not receive the disputed amount back**.
- The initial **dispute fee is generally nonrefundable** (subject to country- or contract-specific exceptions).
- If you submitted evidence, Stripe generally refunds the **countered-dispute fee only if you win**. It states that no further money moves from the merchant's perspective because Stripe already credited the issuer, and that the issuer may return funds to the cardholder during or after the process. site:docs.stripe.com disputes issuer rules in cardholder's favor funds Stripe dispute outcome balance5 results
results as cached 2026-08-24T22:00 opened 1 page
|
| CORRECT | If the issuer rules **in the cardholder’s favor**, the dispute is marked **lost** for you:
- Stripe has already debited your Stripe balance for the disputed amount when the chargeback was initiated.
- Stripe has already credited the issuer, so **there’s no additional money movement from your perspective** when the decision is finalized.
- The issuer returns the money to the cardholder, at its discretion, during or after the dispute process.
- The original dispute fee generally **isn’t refunded**. If you countered the dispute, any applicable countered-dispute fee also isn’t refunded.
In short: **you permanently lose the disputed amount plus the applicable dispute fee**, unless the case later becomes a rare “late win.” citeStripe dispute documentation It states that no additional money moves from your perspective because Stripe already credited the issuer, and that the issuer may return the funds to the cardholder during or after the process. site:docs.stripe.com disputes issuer rules in favor of cardholder money Stripe dispute5 results
results as cached 2026-08-24T22:00 opened 2 pages
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
57 ### Dispute fees
58 The dispute fees for your country can be found on the Stripe [Pricing page](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details). The fee for receiving a dispute is deducted from your account balance when a cardholder initiates a dispute. Dispute fees vary based on your business location:
59 * For businesses outside Mexico, the fee for receiving a dispute is non-refundable.
60 * For businesses in Mexico, the fee for receiving a dispute might be returned if you win or the cardholder withdraws.
61 * Businesses in the Single Euro Payments Area (SEPA) incur no fee for receiving a dispute on a card payment processed on the [Cartes Bancaires network](https://docs.stripe.com/payments/cartes-bancaires).
| WRONG | For businesses outside Mexico, Stripe initially charges a dispute received fee—typically **$15 per dispute**. If you **win the dispute**, Stripe refunds that fee; if you **lose or accept the dispute**, the fee is retained. The answer says the dispute received fee is refunded when the business wins, but the source states it is non-refundable for businesses outside Mexico. |
| WRONG | For businesses outside Mexico, Stripe applies the standard dispute fee for the business’s country rather than Mexico’s fee. It is charged when a dispute is received and is generally refunded if you successfully win the dispute. The exact amount and refund rules depend on your country and Stripe pricing terms. The answer says the dispute fee is generally refunded if the dispute is won, but the source states it is non-refundable for businesses outside Mexico. |
| CORRECT | For businesses **outside Mexico**, Stripe’s **dispute received fee is non-refundable**. It’s deducted from your Stripe balance when the cardholder files the dispute—even if you successfully challenge and win it.
If you counter the dispute, Stripe may charge a separate **dispute countered fee**, but that fee is refunded if you win. It states that the dispute received fee is non-refundable for businesses outside Mexico, matching the source. site:stripe.com "dispute received fee" Mexico businesses outside Mexico5 results
results as cached 2026-08-24T22:00 opened 3 pages
|
| CORRECT | For businesses **outside Mexico**, Stripe’s **dispute received fee is non-refundable**. This means you generally won’t get the fee back even if you successfully counter the dispute. It states that the dispute received fee is non-refundable for businesses outside Mexico, matching the source. site:stripe.com Mexico dispute received fee businesses outside Mexico5 results
results as cached 2026-08-24T22:00 |
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
59 * For businesses outside Mexico, the fee for receiving a dispute is non-refundable.
60 * For businesses in Mexico, the fee for receiving a dispute might be returned if you win or the cardholder withdraws.
61 * Businesses in the Single Euro Payments Area (SEPA) incur no fee for receiving a dispute on a card payment processed on the [Cartes Bancaires network](https://docs.stripe.com/payments/cartes-bancaires).
62 If you counter a dispute, a [dispute countered fee](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details) applies, in addition to the dispute received fee. The cardholder’s bank reviews it and decides the dispute outcome. This can take up to 3 months. When Stripe receives the decision, you receive an email from us.
63 Stripe returns the dispute countered fee if you win the dispute. Unless otherwise stated in your Stripe contract, we never return the dispute received fee.
| WRONG | SEPA-based businesses pay a **€15 dispute fee per Cartes Bancaires card-payment dispute** on Stripe. The fee is generally refunded if the dispute is resolved in the business’s favor. The answer asserts a €15 dispute fee, whereas the source states that SEPA businesses incur no fee for receiving a dispute on Cartes Bancaires card payments. |
| WRONG | SEPA-based businesses are charged a **€15 dispute fee** for each disputed Cartes Bancaires payment on Stripe. Stripe generally refunds this fee if the dispute is successfully won. The answer states a €15 dispute fee, but the source says SEPA businesses incur no fee for receiving a dispute on Cartes Bancaires card payments. |
| CORRECT | SEPA businesses pay **no dispute fee** for Cartes Bancaires card payments processed on the Cartes Bancaires network. The answer states that SEPA businesses pay no dispute fee for Cartes Bancaires card payments, matching the source. site:stripe.com Cartes Bancaires dispute fee SEPA business Stripe € dispute fee5 results
results as cached 2026-08-24T22:00 |
| CORRECT | SEPA businesses pay **no dispute fee (€0)** for disputes on **Cartes Bancaires card payments processed through Stripe**. The answer states that SEPA businesses pay no (€0) dispute fee for Cartes Bancaires card payments, matching the source. site:stripe.com Cartes Bancaires dispute fee SEPA business Stripe5 results
results as cached 2026-08-24T22:00 |
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
60 * For businesses in Mexico, the fee for receiving a dispute might be returned if you win or the cardholder withdraws.
61 * Businesses in the Single Euro Payments Area (SEPA) incur no fee for receiving a dispute on a card payment processed on the [Cartes Bancaires network](https://docs.stripe.com/payments/cartes-bancaires).
62 If you counter a dispute, a [dispute countered fee](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details) applies, in addition to the dispute received fee. The cardholder’s bank reviews it and decides the dispute outcome. This can take up to 3 months. When Stripe receives the decision, you receive an email from us.
63 Stripe returns the dispute countered fee if you win the dispute. Unless otherwise stated in your Stripe contract, we never return the dispute received fee.
64 #### Regional considerations
| WRONG | Typically, Stripe doesn’t charge an additional fee just for submitting evidence or challenging a dispute.
You may incur:
- **Dispute fee:** Usually a fixed fee per dispute (for example, **$15 in the US**, with the amount varying by country and currency).
- **If you win:** Stripe generally refunds the dispute fee.
- **If you lose:** Stripe keeps the dispute fee, and the disputed payment amount remains reversed.
- **Original processing fee:** Usually not refunded when a payment is disputed.
- **Possible currency-conversion or cross-border fees:** These may apply depending on the payment and your Stripe pricing plan.
Fees can differ by region, card network, payment method, and account type, so check the dispute details in your Stripe Dashboard or your country-specific Stripe pricing page. The answer says Stripe typically does not charge an additional fee for challenging a dispute, but the source states that a dispute countered fee applies in addition to the dispute received fee. |
| WRONG | Stripe generally doesn’t charge an extra fee just for challenging a dispute or submitting evidence.
However, the original **dispute fee** still applies:
- Stripe debits the disputed amount plus a dispute fee when the dispute is opened.
- The fee varies by country and payment method—often **$15 USD** in the US.
- If you win, Stripe typically returns both the disputed amount and the dispute fee.
- If you lose, the dispute fee is generally not refunded.
Check your Stripe pricing page or dispute details for the exact fee on your account, since rates vary by region and payment method. The answer says Stripe generally does not charge an extra fee for challenging a dispute, but the source states that a dispute countered fee applies in addition to the dispute received fee. |
| CORRECT | When you challenge (counter) a Stripe dispute, you generally pay:
- **Dispute received fee:** Charged when the dispute is filed. This is usually **nonrefundable**, even if you win.
- **Dispute countered fee:** An additional fee charged when you submit evidence to challenge the dispute. Stripe generally **refunds this fee if you win**; you lose it if the dispute is upheld.
In the **US, both fees are typically $15**, so challenging a dispute can temporarily cost **$30 plus the disputed amount**. Fees vary by country and payment method. Stripe does not charge the countered fee for some cases, including **inquiries** and—according to its documentation—businesses in **Mexico and Japan**.
See Stripe’s current fee details for your region: https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details It states that countering a dispute incurs an additional dispute countered fee on top of the dispute received fee, matching the source. site:stripe.com dispute fee challenge dispute Stripe extra fees dispute won lost5 results
results as cached 2026-08-24T22:00 Stripe dispute countered fee fee details 2025 US $15 challenge dispute5 results
results as cached 2026-08-24T22:00 opened 2 pages
|
| CORRECT | When you challenge (“counter”) a Stripe dispute, you may incur:
- **Dispute received fee:** Charged when the dispute is opened, in addition to the disputed amount. It’s generally nonrefundable, except in some regions or under specific contracts.
- **Dispute countered fee:** Charged when you submit evidence to challenge the dispute. Stripe refunds this fee if you win. It generally doesn’t apply to businesses in **Mexico or Japan**.
- **Compliance-dispute network fee:** For **Visa or Mastercard compliance disputes**, Stripe collects an additional **$500 USD (or local equivalent)** when you contest the case. This is refunded if you win.
Fees vary by your business location and Stripe pricing agreement. Inquiries/pre-dispute cases and some non-card payment disputes may have different or no countering fees. See Stripe’s [dispute fee details](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details). It states that challenging a dispute incurs a dispute countered fee in addition to the dispute received fee, matching the source. site:stripe.com dispute challenge fee Stripe dispute fee evidence challenge extra fees5 results
results as cached 2026-08-24T22:00 site:support.stripe.com/questions/june-2025-pricing-updates-for-disputes fee details dispute countered fee amount US Stripe0 results
results as cached 2026-08-24T22:00 opened 3 pages
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
61 * Businesses in the Single Euro Payments Area (SEPA) incur no fee for receiving a dispute on a card payment processed on the [Cartes Bancaires network](https://docs.stripe.com/payments/cartes-bancaires).
62 If you counter a dispute, a [dispute countered fee](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details) applies, in addition to the dispute received fee. The cardholder’s bank reviews it and decides the dispute outcome. This can take up to 3 months. When Stripe receives the decision, you receive an email from us.
63 Stripe returns the dispute countered fee if you win the dispute. Unless otherwise stated in your Stripe contract, we never return the dispute received fee.
64 #### Regional considerations
65 Mexico
| WRONG | If you **win the dispute**, Stripe generally refunds the **dispute received fee** to your Stripe balance along with the disputed payment amount.
If you **lose or accept** the dispute, the fee is not returned. The original payment-processing fee is typically not refunded. Policies and fee amounts can vary by country and payment method, so check the dispute’s balance transaction in your Dashboard. The answer says Stripe generally refunds the dispute received fee when you win, but the source says that fee is never returned unless the Stripe contract states otherwise. |
| WRONG | If you win the dispute, Stripe generally refunds the **dispute received fee** to your Stripe balance. The refund is usually credited after the dispute is resolved in your favor.
If you lose—or withdraw/accept the dispute—the fee typically isn’t refunded. Policies can vary by country, payment method, and Stripe account type, so check your regional Stripe pricing or the dispute details in the Dashboard. The answer says Stripe generally refunds the dispute received fee if you win, but the source says that fee is never returned unless the Stripe contract states otherwise. |
| CORRECT | If you win the dispute, Stripe generally **does not refund the dispute received fee**. You typically get back:
- The **disputed payment amount**
- The **dispute countered fee** (the fee for submitting your evidence)
The dispute received fee is only returned if your Stripe contract or region-specific terms say otherwise. It states that the dispute received fee is generally not refunded if you win, except where the Stripe contract or applicable terms provide otherwise. site:stripe.com dispute received fee if win Stripe dispute fee refunded5 results
results as cached 2026-08-24T22:01 |
| CORRECT | Usually, **Stripe does not refund the “dispute received fee” even if you win**. You’ll generally receive back:
- The disputed payment amount
- The **dispute countered fee**, if one was charged
Exceptions may apply based on your country or Stripe contract—for example, Stripe says the dispute fee might be returned for businesses in Mexico. Check your Stripe balance history and contract for the exact treatment. It states that Stripe generally does not refund the dispute received fee even if you win, while allowing for contract-based exceptions. site:stripe.com dispute received fee if win dispute fee refunded Stripe5 results
results as cached 2026-08-24T22:01 opened 2 pages
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
65 Mexico
66 Japan
67 The dispute countered fee doesn’t apply to businesses in Mexico and Japan.
68 ### Respond to a dispute
69 In most cases, you have the ability to challenge a disputed payment, as long as you submit strong evidence to the card issuer that invalidates the dispute claim before the deadline.
| WRONG | For businesses based in:
- **Mexico:** **MX$200 per dispute**
- **Japan:** **¥1,500 per dispute**
Stripe typically charges this when a dispute is opened. If you successfully challenge and win the dispute, Stripe generally refunds the dispute fee, subject to Stripe’s local terms and pricing policies. The answer states that businesses in Mexico and Japan pay dispute fees, but the source says the dispute countered fee does not apply to them. |
| CORRECT | On Stripe, businesses generally pay:
- **Mexico:** **MX$150 per dispute**
- **Japan:** **¥1,500 per dispute**
This is charged when a dispute is received. If the business counters the dispute and wins, Stripe typically refunds the dispute fee. There is usually no separate “countered dispute” fee. It states that there is no separate countered dispute fee for businesses in Mexico or Japan, matching the source. |
| CORRECT | Businesses in **Mexico and Japan pay no dispute countered fee** on Stripe—the fee is not applicable in those countries.
However, Stripe may still charge the applicable **dispute received fee** when a dispute is filed. In countries where it applies, the dispute countered fee is generally **$15 per manually contested dispute**, refundable if you win.
Sources: [Stripe Dispute Fees FAQ](https://support.stripe.com/questions/dispute-fees-faq) · [Stripe dispute documentation](https://docs.stripe.com/disputes/how-disputes-work) It correctly states that businesses in Mexico and Japan pay no dispute countered fee because the fee does not apply there. site:stripe.com Mexico Stripe dispute fee countered dispute fee businesses5 results
results as cached 2026-08-24T22:01 site:stripe.com Japan Stripe dispute fee countered dispute fee businesses5 results
results as cached 2026-08-24T22:01 Stripe pricing Mexico disputes fee $15 Japan disputes fee5 results
results as cached 2026-08-24T22:01 |
| CORRECT | Businesses in **Mexico and Japan pay no Stripe dispute countered fee** when they submit evidence to challenge a dispute.
They may still pay the applicable **dispute received fee**. In other countries, Stripe’s dispute countered fee is generally **$15 per manually contested dispute**, refunded if the dispute is won. It states that businesses in Mexico and Japan pay no dispute countered fee, matching the source. site:stripe.com Mexico Stripe dispute fee dispute countered fee businesses5 results
results as cached 2026-08-24T22:01 site:stripe.com Japan Stripe dispute fee dispute countered fee businesses5 results
results as cached 2026-08-24T22:01 Stripe dispute countered fee meaning5 results
results as cached 2026-08-24T22:01 |
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
68 ### Respond to a dispute
69 In most cases, you have the ability to challenge a disputed payment, as long as you submit strong evidence to the card issuer that invalidates the dispute claim before the deadline.
70 As soon as a dispute is active, the only way to overturn it’s by _submitting evidence in a response_. Even in cases where your customer claims to have [withdrawn the dispute](https://docs.stripe.com/disputes/withdrawing), you must respond with evidence for the dispute to be closed in your favor. Submitting evidence is what signals to the issuer that you don’t accept the dispute and want to have the funds returned to you.
71 See [Respond to disputes](https://docs.stripe.com/disputes/responding) for information on how to:
72 * Review the cardholder’s claim.
| WRONG | If your customer says they withdrew a Stripe dispute:
1. **Check the dispute in your Stripe Dashboard**
Go to **Payments → Disputes** and verify the actual status. A customer’s statement alone does not close the dispute.
2. **Check the response deadline**
If the dispute still shows **“Needs response,”** submit your evidence before the deadline. Do not assume it has been canceled.
3. **Ask the customer to contact their card issuer**
The customer must withdraw the dispute through their bank/card issuer—not directly through Stripe. They should ask the issuer to confirm that the withdrawal was processed.
4. **Monitor Stripe for the outcome**
Stripe may continue showing the dispute as open while the issuer processes the withdrawal. If it is successfully withdrawn, the dispute will generally be resolved in your favor and the disputed funds/fees may be returned, depending on the case and payment method.
5. **Contact Stripe Support if the status does not update**
Provide the dispute ID, payment ID, and any confirmation the customer received from their bank. Stripe cannot usually close a dispute based only on your or the customer’s request.
6. **Do not issue a separate refund unless appropriate**
A refund will not necessarily cancel an existing dispute and could result in you losing both the payment and the disputed amount. If you do refund, make sure you understand how Stripe will handle the open dispute.
Keep records of the customer’s communication, but rely on the **Stripe dispute status and issuer confirmation** as the authoritative result. It suggests a successfully withdrawn dispute may resolve in the merchant’s favor without evidence, whereas the source says evidence must be submitted even if the customer claims to have withdrawn it. |
| CORRECT | If a customer says they withdrew a Stripe dispute, don’t assume it is resolved until Stripe shows the status has changed.
1. **Check the dispute in Stripe Dashboard**
- Go to **Payments → Disputes** and open the case.
- Confirm whether it is **won, lost, closed, or still needs a response**.
- A customer’s request to withdraw a dispute does not automatically close it—the card issuer or bank must process the withdrawal.
2. **Ask the customer to contact their card issuer**
They should tell their bank that the transaction is valid and ask the bank to formally withdraw or reverse the dispute. They can request a confirmation or case reference number.
3. **Respond before the deadline if it is still open**
If Stripe still allows evidence submission, submit your evidence rather than relying on the customer’s promise. Missing the deadline can result in losing the dispute.
4. **Keep written confirmation**
Save the customer’s message and any bank confirmation, but note that a customer email alone generally is not sufficient evidence for Stripe or the issuer.
5. **Contact Stripe Support if the status does not update**
If the customer’s bank says it withdrew the dispute but Stripe still shows it as open after the issuer’s processing time, provide Stripe with the dispute ID and any confirmation from the bank.
Do **not** issue a separate refund solely because the customer says the dispute was withdrawn; that could result in the customer receiving both a dispute credit and a refund. Wait for the dispute outcome or confirm the appropriate action with Stripe. It correctly advises submitting evidence rather than relying on the customer's claimed withdrawal, which matches the source requirement for the dispute to close in the merchant's favor. |
| CORRECT | If your customer says they withdrew the Stripe dispute, **don’t assume it’s resolved yet**. Do the following:
1. **Check the dispute in Stripe Dashboard**
Look at the dispute’s current status and—most importantly—the evidence-submission deadline. A customer’s statement alone does not close the dispute.
2. **Ask the customer for confirmation from their bank/card issuer**
For example, an email or screenshot showing that they contacted the issuer or that the charge was reinstated. This can support your response, although Stripe says it isn’t required.
3. **Submit evidence before the deadline anyway**
Stripe warns that you can still lose if you fail to respond, even after the cardholder says they withdrew the dispute. Include:
- The customer’s written confirmation
- Proof of delivery or service completion
- Order, billing, and communication records
- Your explanation of the resolution
You generally get only one opportunity to submit evidence, so don’t wait past the deadline.
4. **Don’t issue a refund on the disputed charge while it’s active**
Stripe generally prevents refunds until the issuer resolves the dispute in your favor. If you promised a refund or other remedy, document that agreement and follow through once permitted.
5. **Monitor the dispute normally**
A withdrawn dispute does not necessarily resolve faster, appear differently, or immediately restore the funds. It may still count toward your dispute rate until the issuer formally resolves it.
If the dispute is already closed or lost, have the customer contact their card issuer and request a **late withdrawal** or reversal, then contact Stripe Support with any confirmation. These adjustments can take weeks or months and aren’t guaranteed. See Stripe’s guidance on [dispute withdrawals](https://docs.stripe.com/disputes/withdrawing). It correctly states that even if the customer says they withdrew the dispute, you must submit evidence for it to close in your favor. site:docs.stripe.com disputes customer withdrew dispute what to do Stripe5 results
results as cached 2026-08-24T22:01 site:support.stripe.com customer withdrew dispute Stripe5 results
results as cached 2026-08-24T22:01 opened 1 page
|
| CORRECT | If your customer says they withdrew the Stripe dispute:
1. **Don’t assume it’s resolved.** A withdrawal does not automatically mean Stripe will mark the dispute as won, and the normal timeline may still apply.
2. **Ask for confirmation**, such as an email from their bank or a screenshot showing the issuer processed the withdrawal or rebilled the charge.
3. **Submit evidence through Stripe before the deadline anyway.** Stripe says issuers may treat failure to respond as accepting liability—even when the customer says they withdrew the dispute. Include the customer’s confirmation if available.
4. **Monitor the dispute in the Stripe Dashboard/API** until it is officially resolved in your favor. You generally can’t refund the disputed charge until the issuer decides in your favor.
5. **If the deadline has passed or the dispute was already lost**, have the customer contact their card issuer and request a late withdrawal. Processing can take weeks or months and isn’t supported by every issuer.
Also note that a withdrawn dispute may still count toward your dispute rate. If you agree the customer should receive the money, Stripe generally recommends accepting the dispute rather than relying on a withdrawal. It correctly states that the merchant must submit evidence even if the customer says they withdrew the dispute. site:docs.stripe.com disputes customer withdrew dispute what to do Stripe5 results
results as cached 2026-08-24T22:01 site:support.stripe.com cardholder withdrew dispute Stripe dispute closed5 results
results as cached 2026-08-24T22:01 opened 1 page
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
78 The Dashboard payment page and timeline describes these disputes as those where the card issuer doesn’t allow you to submit evidence.
79 * [Inquiries](https://docs.stripe.com/disputes/how-disputes-work#inquiries) for Discover cards can turn into unchallengeable disputes if you don’t submit evidence for the inquiry.
80 * The Cartes Bancaires network requires a higher standard of evidence from the cardholder before allowing them to initiate a dispute, but then prohibits you from challenging the dispute. This affects only businesses in the [Single Euro Payments Area (SEPA)](https://en.wikipedia.org/wiki/Single_Euro_Payments_Area) processing payments on the Cartes Bancaires network, and not businesses elsewhere charging cards _issued_ by Cartes Bancaires. Learn more at [Cartes Bancaires](https://docs.stripe.com/payments/cartes-bancaires).
81 * Due to local regulations, you can’t challenge disputes submitted for Nigerian payment methods.
82 ### Receive multiple disputes
| WRONG | You can challenge a **Cartes Bancaires (CB) dispute** in Stripe from the dispute details page.
### In the Stripe Dashboard
1. Go to **Payments → Disputes**.
2. Select the dispute marked **Needs response** or similar.
3. Review:
- The dispute reason
- The response deadline
- The disputed amount
- The payment and customer details
4. Choose **Submit evidence** or **Counter dispute**.
5. Add evidence relevant to the reason code, such as:
- Order confirmation and invoice
- Customer communications
- Proof of delivery, tracking, or service completion
- Refund and cancellation policy
- Evidence the customer received or used the product/service
- AVS/CVC/3D Secure results, where applicable
- A clear explanation addressing the specific claim
6. Review the submission and click **Submit** before the deadline.
You generally cannot resolve the dispute by contacting the customer’s bank directly; Stripe forwards your response through the card network.
### Through the Stripe API
You can provide evidence on the dispute and submit it:
```bash
curl https://api.stripe.com/v1/disputes/dp_xxx \
-u sk_live_xxx: \
-d "evidence[customer_name]=Jean Dupont" \
-d "evidence[product_description]=Annual software subscription" \
-d "evidence[shipping_tracking_number]=TRACKING123" \
-d submit=true
```
Use the evidence fields that fit the dispute. File uploads, such as signed delivery documents, must first be uploaded to Stripe and then referenced in the dispute evidence.
### Important points
- Follow the **deadline shown in Stripe**; late submissions may be rejected.
- Address the exact dispute reason rather than submitting generic information.
- Submit concise, chronological evidence. Avoid sending unnecessary documents or sensitive data.
- Once submitted, evidence usually cannot be changed.
- If Stripe has already closed the dispute, you may not be able to challenge it through the Dashboard.
- If the dispute is lost, check whether Stripe shows an appeal or second-review option—availability depends on the CB dispute stage and reason.
Stripe may temporarily debit the disputed amount and a dispute fee from your balance. If the challenge succeeds, the funds may be returned according to Stripe’s handling of that dispute. The answer says a business can submit evidence and counter a Cartes Bancaires dispute through Stripe, but the source states Cartes Bancaires prohibits businesses from challenging such disputes. |
| WRONG | To challenge a **Cartes Bancaires (CB) dispute** in Stripe, you submit a representment through Stripe—Stripe forwards it to the card network and issuing bank. You generally cannot challenge it directly with Cartes Bancaires.
### In the Stripe Dashboard
1. Go to **Payments → Disputes**.
2. Select the disputed payment.
3. Review:
- The dispute reason and category
- The response deadline
- The amount being disputed
- Any information supplied by the cardholder
4. Click **Submit evidence**, **Respond**, or the equivalent action shown by Stripe.
5. Add concise, factual evidence supporting the transaction.
6. Review the submission and click **Submit** before the deadline.
### Useful evidence
Provide only evidence relevant to the dispute reason, such as:
- Order confirmation and invoice
- Product or service description
- Proof of delivery, tracking, or delivery confirmation
- Customer signature or pickup confirmation
- Customer communications acknowledging the purchase or receiving the service
- Refund, cancellation, and terms-of-service policies
- Evidence the customer used the product or service
- For recurring payments, proof of the original authorization and renewal/cancellation terms
- For fraud-related disputes, Stripe Radar results, AVS/CVC checks, 3DS authentication, IP address, device information, and matching billing/shipping details
For digital goods or services, include login records, download history, timestamps, IP addresses, or evidence of usage where appropriate.
### Best practices
- Match your evidence to the exact **dispute reason**; more documents do not necessarily make a stronger case.
- Use a clear timeline explaining what was purchased, when it was delivered, and why the payment was valid.
- Upload legible documents and avoid unnecessary personal or sensitive information.
- Do not contact or pressure the cardholder to withdraw the dispute.
- Submit before the deadline shown in Stripe. Late responses are generally rejected automatically.
- Keep the disputed funds available; Stripe may debit your balance while the dispute is under review.
You can also respond programmatically using Stripe’s **Disputes API**, typically by updating the dispute with evidence and submitting it. Once submitted, the bank’s decision may take several weeks. If the dispute is lost, Stripe generally cannot guarantee a further appeal, though you can contact Stripe Support if you believe the case was mishandled or you have materially new evidence. The answer instructs the business to submit evidence and a representment, but the source states that Cartes Bancaires prohibits businesses from challenging these disputes. |
| CORRECT | For **Cartes Bancaires disputes**, whether you can challenge them depends on where your Stripe business is based and how the payment was processed:
- If your business is in the **Single Euro Payments Area (SEPA)** and the payment was processed on the **Cartes Bancaires network**, Stripe generally **does not allow merchants to challenge the dispute or submit evidence**. Cartes Bancaires requires stronger evidence from the cardholder before opening the dispute, but its rules prohibit merchant representment.
- This restriction does **not** generally apply to businesses outside SEPA that accept cards issued by Cartes Bancaires.
### What to do in Stripe
1. Open **Stripe Dashboard → Disputes**.
2. Select the relevant dispute and check the network, country, status, and dispute details.
3. If **Counter dispute** is available, submit your evidence before the displayed deadline. Stripe only allows one final submission, so include all relevant documentation.
4. If there is no counter option and Stripe marks the dispute as unchallengeable, you cannot contest it through Stripe or provide evidence to the issuer.
You can still contact the customer to resolve the issue amicably. If the case is only an **inquiry/pre-dispute request**, respond promptly in the Dashboard, since inquiries may be answerable before they become formal disputes. Once a formal Cartes Bancaires dispute is open, however, responding to the customer does not reverse it—you would need a withdrawal from the cardholder, and Stripe may still require the formal process to close it favorably.
Stripe cannot escalate a lost dispute to arbitration through its platform. It correctly states that SEPA businesses processing on the Cartes Bancaires network cannot challenge the dispute, while noting the stated scope limitation for businesses elsewhere. site:docs.stripe.com Cartes Bancaires dispute challenge Stripe evidence5 results
results as cached 2026-08-24T22:01 site:support.stripe.com Cartes Bancaires dispute Stripe challenge4 results
results as cached 2026-08-24T22:01 Stripe Cartes Bancaires chargeback dispute evidence deadline5 results
results as cached 2026-08-24T22:01 opened 2 pages
|
| CORRECT | You generally **can’t challenge a Cartes Bancaires dispute through Stripe** if all of the following apply:
- Your business is located in the **Single Euro Payments Area (SEPA)**, and
- The payment was processed on the **Cartes Bancaires network**.
Cartes Bancaires requires stronger evidence from the cardholder before opening a dispute, but its rules do **not allow merchants to submit counter-evidence**. Stripe therefore closes these disputes as unchallengeable, and the Dashboard won’t provide an evidence-submission option.
What you can do:
1. **Check the dispute details in Stripe Dashboard** to confirm the network is Cartes Bancaires and that the dispute is marked unchallengeable.
2. **Contact the customer directly** to resolve any misunderstanding or request that they withdraw the dispute through their bank. A withdrawal does not automatically return the funds—you should still contact Stripe Support if the customer confirms withdrawal.
3. If you issued a **partial refund**, retain the refund records. However, Stripe notes that merchants can’t ask the issuer to account for an existing partial refund when the full Cartes Bancaires payment is disputed.
4. For future payments, review your Cartes Bancaires setup and dispute-prevention controls. Stripe Support can clarify whether a payment was processed through Cartes Bancaires or another card network.
This restriction applies to **SEPA businesses processing on the Cartes Bancaires network**, not necessarily to businesses outside SEPA that accept cards issued by Cartes Bancaires. Stripe also doesn’t support arbitration escalation through its platform. ([Stripe documentation](https://docs.stripe.com/disputes/how-disputes-work)) It correctly states that SEPA businesses processing payments on the Cartes Bancaires network cannot challenge those disputes through Stripe. site:docs.stripe.com Cartes Bancaires dispute challenge Stripe evidence5 results
results as cached 2026-08-24T22:01 opened 3 pages
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
79 * [Inquiries](https://docs.stripe.com/disputes/how-disputes-work#inquiries) for Discover cards can turn into unchallengeable disputes if you don’t submit evidence for the inquiry.
80 * The Cartes Bancaires network requires a higher standard of evidence from the cardholder before allowing them to initiate a dispute, but then prohibits you from challenging the dispute. This affects only businesses in the [Single Euro Payments Area (SEPA)](https://en.wikipedia.org/wiki/Single_Euro_Payments_Area) processing payments on the Cartes Bancaires network, and not businesses elsewhere charging cards _issued_ by Cartes Bancaires. Learn more at [Cartes Bancaires](https://docs.stripe.com/payments/cartes-bancaires).
81 * Due to local regulations, you can’t challenge disputes submitted for Nigerian payment methods.
82 ### Receive multiple disputes
83 In extremely rare cases, you might receive more than one dispute per payment. This can happen when a customer files a new dispute with a different reason code, for a new line item in the original transaction, on multi-capture payments or simply because the issuer acquired new information about the payment allowing them to refile a dispute.
| WRONG | If a customer disputes a payment made with a Nigerian card or other Nigerian payment method, you generally challenge it through **Stripe’s Disputes workflow**.
### In the Stripe Dashboard
1. Open **Dashboard → Payments → Disputes**.
2. Select the disputed payment.
3. Review:
- Dispute reason
- Response deadline
- Amount and currency
- Payment method and issuing bank
4. Choose **Counter dispute** or **Submit evidence**.
5. Upload supporting evidence and submit it before the deadline.
### Useful evidence
Provide evidence that directly addresses the dispute reason, such as:
- Customer order, invoice, or contract
- Proof of delivery or service completion
- Delivery tracking and recipient details
- Customer communications confirming the purchase
- Refund and cancellation policy
- Evidence that the customer used the product or service
- IP address, device data, login records, or customer account activity
- Proof that the billing and shipping details match
- For recurring payments, proof of authorization and prior successful payments
Keep the explanation factual and concise. Explain what was purchased, when it was provided, and why the customer’s claim is incorrect. Stripe usually sends the evidence to the card network or financial institution, which makes the final decision.
### Through the Stripe API
You can retrieve the dispute and submit evidence using the Disputes API:
```bash
curl https://api.stripe.com/v1/disputes/dp_xxx \
-u sk_live_xxx: \
-d "evidence[product_description]"="Description of the product or service" \
-d "evidence[customer_email_address]"="customer@example.com" \
-d "evidence[shipping_tracking_number]"="TRACKING_NUMBER" \
-d submit=true
```
Use only the evidence fields relevant to the dispute. The exact available fields depend on the dispute type.
### Important points
- The **deadline shown in Stripe is strict**. Submit before it expires.
- You generally get **one opportunity** to submit a complete response, so gather all evidence first.
- A Nigerian-issued card is normally handled like other card disputes; the issuing bank and card network decide the outcome.
- If the payment was made through a **bank transfer, wallet, or another non-card method**, it may not have a standard card chargeback process. Follow the instructions displayed in the Stripe dispute record or contact Stripe Support.
- If you already lost the dispute, you may only be able to appeal if Stripe shows an appeal option; otherwise, the decision is usually final. The answer says Nigerian payment method disputes can generally be challenged through Stripe, but the source states they cannot be challenged due to local regulations. |
| WRONG | If a payment made with a Nigerian-issued card is disputed in Stripe, you challenge it through Stripe’s normal dispute process. The card’s country does not usually change the procedure.
### In the Stripe Dashboard
1. Open **Payments → Disputes**.
2. Select the disputed payment.
3. Review:
- Dispute reason
- Response deadline
- Amount
- Payment and customer details
4. Choose **Counter dispute** or **Submit evidence**.
5. Add evidence relevant to the dispute reason.
6. Submit it before the deadline shown by Stripe.
You can also submit evidence through the Stripe API using the `POST /v1/disputes/{dispute}/close` endpoint only to accept/close a dispute; evidence is generally updated on the dispute object before submission using Stripe’s dispute evidence fields. Check Stripe’s current API documentation for the exact fields and workflow.
### Useful evidence
Depending on the reason, provide:
- Proof of delivery, tracking, or service completion
- Customer communications confirming the purchase
- Invoice, order details, and refund/cancellation policy
- Evidence that the customer used or downloaded the service
- IP address, device information, and customer account history
- AVS/CVC results and 3-D Secure authentication data
- Proof that a refund was already issued, if applicable
Keep the explanation factual and concise. Do not include unnecessary sensitive information such as full card numbers.
### Important points
- The deadline in Stripe is strict; late evidence may not be reviewed.
- You may contact the customer and ask them to withdraw the dispute, but you should still submit evidence. Only the issuing bank/card network can reverse the dispute.
- If the payment used a Nigerian bank-transfer, mobile-money, or another non-card method, the process may differ. Check the payment’s dispute instructions in Stripe or contact Stripe Support.
- If the transaction was processed through **Paystack or another separate Nigerian processor**, you must challenge it through that processor rather than Stripe. The answer says Nigerian payment-method disputes can be challenged through Stripe’s normal process, directly contradicting the source, which says they cannot be challenged due to local regulations. |
| CORRECT | You **can’t challenge customer-initiated disputes for Nigerian payment methods on Stripe**.
Stripe’s Nigerian payment methods—such as **Naira cards and Naira bank transfers**—are processed through Stripe’s Nigerian merchant-of-record and local processor partners. Stripe lists dispute support for these methods as **not available**. If the relevant payment provider accepts the customer’s request to return funds, Stripe removes the funds from your Stripe balance immediately.
What you can do:
1. **Contact the customer directly** to understand and resolve the issue.
2. If appropriate, arrange a replacement, store credit, or other resolution.
3. Keep records of all communication and any resolution.
4. Use Stripe’s **refund** functionality where applicable—Nigerian payment-method payments can generally be refunded within **365 calendar days** of the original charge.
This differs from eligible card-payment disputes, where you can open the dispute in the Stripe Dashboard and select **Counter dispute** to submit evidence. For Nigerian payment methods, that challenge process isn’t available.
Source: [Stripe — Nigerian payment methods](https://docs.stripe.com/payments/countries/nigeria) The answer directly states that disputes for Nigerian payment methods cannot be challenged, matching the source. site:docs.stripe.com disputes challenge dispute submit evidence Stripe Dashboard payment method Nigeria5 results
results as cached 2026-08-24T22:01 site:docs.stripe.com Nigeria payment methods disputes Stripe5 results
results as cached 2026-08-24T22:01 site:support.stripe.com Nigeria dispute payment method Stripe challenge1 result
results as cached 2026-08-24T22:01 opened 2 pages
|
| CORRECT | You **can’t challenge or submit evidence for a customer-initiated dispute involving a Nigerian payment method** on Stripe. This restriction is due to local regulations.
If such a dispute occurs:
1. Stripe removes the disputed funds from your Stripe balance when the relevant payment service provider accepts the request to return the customer’s funds.
2. The dispute is not eligible for a counter-response through the Stripe Dashboard or API.
3. Contact the customer directly to resolve the issue—for example, clarify the transaction, arrange a refund where appropriate, or ask them to withdraw the dispute.
4. For future payments, retain clear transaction records and use customer-service and fraud-prevention measures, since standard dispute evidence submission isn’t available for Nigerian payment methods.
Stripe lists Nigerian payment methods as having **no dispute support**, and refunds are generally available within 365 calendar days of the original charge. It states that disputes involving Nigerian payment methods cannot be challenged due to local regulations, matching the source. site:docs.stripe.com disputes Nigeria payment methods challenge dispute Stripe Nigeria5 results
results as cached 2026-08-24T22:01 opened 2 pages
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
94 After you submit your evidence, the next notification from the card issuer to both Stripe and you is the final decision. As soon as the issuer makes its decision, Stripe updates the status of the dispute to `won` or `lost`, notifying you through the Dashboard, email, and any other communication channels you configured.
95 This outcome is final for all parties. Neither you nor your customer can overturn a lost dispute. However, a customer can [withdraw a dispute](https://docs.stripe.com/disputes/withdrawing), even after a loss.
96 Stripe doesn’t support the arbitration phase for disputes, which means that you can’t escalate disputes to arbitrators through our platform.
97 #### Late-win disputes
98 Although the outcome of a dispute is normally final, in rare cases the status can change from `lost` to `won`. When this occurs, Stripe labels the dispute as a `late win` and returns the funds to your balance. These late-win results happen when issuers credit or debit Stripe for a dispute outside of the regular dispute lifecycle. They might do this to handle money movement or to correct amounts or decisions. Because late wins are driven by the issuer, Stripe can’t predict when or why they happen.
| WRONG | For a Stripe card dispute, **“arbitration” usually means card-network arbitration**, not a hearing run by Stripe. It is a final escalation after the normal dispute process.
### Typical process
1. **Customer files a dispute**
- Their bank (the issuing bank) reverses or places a hold on the payment.
- Stripe notifies you and may withdraw the disputed amount and a dispute fee.
2. **You submit evidence**
- You can accept the dispute or challenge it through Stripe.
- Evidence may include receipts, delivery tracking, customer communications, refund policies, usage logs, and proof of authorization.
3. **Issuer reviews the response**
- If the issuer rules for you, the funds are returned.
- If it rules for the cardholder, the dispute remains lost.
4. **Arbitration may be requested**
- A party—usually the acquiring side or issuer, depending on the card-network rules—can escalate the case to the card network, such as Visa or Mastercard.
- This generally happens only when the amount or principle justifies the additional cost.
5. **Final network decision**
- The card network reviews the documents and applies its rules.
- Its decision is generally final within the card-dispute system.
- The losing party may be charged an arbitration fee, which can be substantial and may be passed through to you.
### Important points
- **You usually cannot directly argue before the card network.** Stripe and its acquiring partners submit materials on your behalf.
- Arbitration is not available for every dispute and may be subject to strict deadlines.
- Additional evidence is often limited; submitting a strong, organized response during the initial dispute is usually most important.
- Stripe’s Dashboard should show whether the dispute is eligible for further response or escalation, the deadline, and any applicable fees.
- A card-network decision does not necessarily prevent separate legal action, although the practical options depend on your contract, jurisdiction, and the transaction.
If you mean **arbitration under Stripe’s legal terms**—for example, a dispute between you and Stripe—that is a different process governed by the Stripe Services Agreement and applicable regional terms. The answer claims arbitration can be escalated to card networks through Stripe and submitted by Stripe or its partners, but the source states Stripe does not support arbitration or escalation to arbitrators through its platform. |
| WRONG | For a Stripe card dispute, **arbitration is the final card-network review after the normal chargeback process**. It is not usually a court hearing, and Stripe itself generally does not decide who is right.
### Typical process
1. **Cardholder files a dispute**
- The customer contacts their card issuer.
- The issuer creates a chargeback, and Stripe typically debits or withholds the disputed amount from your balance.
2. **You submit evidence**
- In the Stripe Dashboard, you can accept the dispute or submit a response.
- Evidence may include invoices, refund policies, delivery or tracking information, customer communications, usage logs, and proof that the transaction was authorized.
3. **Issuer reviews the response**
- The issuer either reverses the dispute or allows it to stand.
- If it stands, the card network may allow a further stage called **pre-arbitration**.
4. **Arbitration may be initiated**
- If the parties still disagree and the dispute qualifies under the relevant network rules, the case can be submitted to the card network—such as Visa, Mastercard, or another network—for arbitration.
- Stripe may submit or transmit the case and evidence on your behalf, depending on the network, dispute type, account configuration, and Stripe’s procedures.
- You usually cannot request arbitration for every dispute, and you may need to accept network fees and deadlines.
5. **Network makes a final decision**
- The network reviews whether the transaction and chargeback were handled according to its rules.
- There is generally no live hearing. The decision is normally final within the card-network process.
### Possible outcomes
- **Merchant wins:** The disputed amount may be returned, although fees may not always be refunded.
- **Merchant loses:** The chargeback remains, and you may also be charged an arbitration or administrative fee.
- **No arbitration available:** Some dispute categories or networks do not permit further escalation.
### Important points
- **Deadlines are strict.** The exact deadline appears in the Stripe Dashboard and varies by network and dispute type.
- **Arbitration can be expensive.** Fees differ by card network, country, and Stripe account; they may be charged even if the result is favorable.
- **Stripe is mainly the processor and facilitator.** The issuer and card network apply the applicable dispute rules.
- **Submit focused evidence.** Explain the transaction timeline clearly and address the specific dispute reason rather than uploading large amounts of unrelated material.
For a specific case, open the dispute in **Stripe Dashboard → Payments → Disputes** and check whether it is eligible for pre-arbitration or arbitration, the response deadline, and any applicable fee. The answer asserts that arbitration can be initiated and handled through Stripe, directly conflicting with the source stating Stripe does not support arbitration or escalation to arbitrators through its platform. |
| CORRECT | For a **Stripe card dispute**, “arbitration” is the card network’s final escalation stage—not an arbitration process run by Stripe.
### Typical dispute flow
1. **Customer disputes the charge with their bank.**
2. **Stripe debits your balance** for the disputed amount and dispute fee.
3. **You submit evidence** through the Stripe Dashboard or API by the stated deadline—usually 7–21 days.
4. **The issuer reviews your response** and decides whether to return the funds.
5. The dispute is marked **won or lost**.
### What arbitration means
If the issuer still rejects your evidence, some card networks may allow the case to proceed through **pre-arbitration and then network arbitration**. The card network—not Stripe—reviews the case and makes a final decision. This process can involve substantial network fees, strict deadlines, and additional documentation.
### Stripe’s limitation
Stripe’s documentation states that **Stripe doesn’t support the arbitration phase through its platform**. Therefore, after a dispute is marked lost, you generally **can’t escalate it to arbitration in the Stripe Dashboard or API**, and Stripe considers the result final, except for rare issuer-driven “late wins.”
If the disputed amount is significant, contact Stripe Support or your acquiring bank promptly to ask whether any network-level escalation is available for your account and payment network. Don’t wait, since arbitration windows are limited and may not be recoverable once the case is closed. It correctly states that Stripe does not support arbitration or escalation to arbitrators through its platform. site:docs.stripe.com disputes arbitration Stripe card network arbitration5 results
results as cached 2026-08-24T22:01 site:support.stripe.com arbitration dispute Stripe5 results
results as cached 2026-08-24T22:01 Stripe dispute arbitration representment pre-arbitration rules5 results
results as cached 2026-08-24T22:01 opened 3 pages
|
| CORRECT | For a **Stripe card dispute**, “arbitration” is the final escalation stage in the card-network chargeback process—typically after the issuer reviews your evidence and the parties have gone through the network’s earlier dispute stages.
**Key point:** Stripe currently **does not support arbitration through its platform**. Stripe’s documentation says you can’t escalate a dispute to an arbitrator through Stripe.
The normal Stripe process is:
1. **Cardholder disputes the payment** with their bank/card issuer.
2. **Stripe debits your balance** for the disputed amount plus the applicable dispute fee.
3. You review the claim and either:
- **Accept** the dispute, or
- **Counter it** by submitting evidence in the Dashboard or through the API.
4. The **card issuer reviews the evidence** and decides whether the dispute is won or lost.
5. Stripe updates the dispute status. The decision is generally final; Stripe does not provide a further arbitration step.
Typical timing is:
- **7–21 days** for you to submit evidence, depending on the network.
- The issuer may take roughly **60–75 days** to decide.
- The overall process commonly takes **2–3 months**.
If arbitration might be available under the relevant card network’s rules, you would generally need to pursue it **outside Stripe**, subject to the network’s procedures, deadlines, eligibility requirements, and potentially substantial arbitration fees. Stripe support may be able to clarify what options exist for your specific account or payment, but Stripe won’t file or manage the arbitration case through its platform.
This applies mainly to **card payments**. PayPal, Klarna, and other local payment methods have their own dispute and escalation rules. It clearly states that Stripe does not support arbitration or escalation to arbitrators through its platform, matching the source. site:docs.stripe.com disputes arbitration Stripe card network arbitration5 results
results as cached 2026-08-24T22:01 site:stripe.com arbitration dispute Stripe chargeback arbitration fees5 results
results as cached 2026-08-24T22:01 opened 1 page
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
96 Stripe doesn’t support the arbitration phase for disputes, which means that you can’t escalate disputes to arbitrators through our platform.
97 #### Late-win disputes
98 Although the outcome of a dispute is normally final, in rare cases the status can change from `lost` to `won`. When this occurs, Stripe labels the dispute as a `late win` and returns the funds to your balance. These late-win results happen when issuers credit or debit Stripe for a dispute outside of the regular dispute lifecycle. They might do this to handle money movement or to correct amounts or decisions. Because late wins are driven by the issuer, Stripe can’t predict when or why they happen.
99 ## Local payment method disputes
100 This dispute process applies primarily to card payments. Local payment methods (LPMs), such as Klarna and PayPal, have their own dispute processes that differ in key ways.
| WRONG | Stripe generally calls this a **dispute reversal** (or a **reversed dispute**). The associated webhook is `charge.dispute.funds_reinstated`, indicating that the previously lost dispute’s funds were returned. The source says Stripe labels a dispute that changes from lost to won as a "late win," not a dispute reversal or reversed dispute. |
| WRONG | Stripe calls this a **dispute reversal** (or a **reversed dispute**). In the API, the dispute’s status typically becomes `won`, and Stripe may emit the `charge.dispute.funds_reinstated` event when the funds are returned. The source says Stripe calls a dispute that changes from lost to won a "late win," not a dispute reversal or reversed dispute. |
| CORRECT | Stripe calls it a **“late win.”** It’s when a dispute’s status changes from `lost` to `won` later, and Stripe returns the funds to your balance. The answer correctly identifies the dispute as a "late win," matching the source. site:docs.stripe.com dispute changes from lost to won later terminology Stripe5 results
results as cached 2026-08-24T22:01 opened 1 page
|
| CORRECT | Stripe calls it a **late win**. It’s when a dispute’s status changes from `lost` to `won` later, and Stripe returns the funds to your balance. The answer correctly identifies the dispute as a late win and accurately states that Stripe returns the funds to the balance. site:docs.stripe.com dispute changes from lost to won later Stripe terminology5 results
results as cached 2026-08-24T22:01 opened 1 page
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
100 This dispute process applies primarily to card payments. Local payment methods (LPMs), such as Klarna and PayPal, have their own dispute processes that differ in key ways.
101 Each LPM defines its own rules for the following:
102 * **Decision-maker**: The LPM provider, such as Klarna or PayPal, decides the dispute instead of a card issuer.
103 * **Dispute window**: LPMs typically allow customers up to 180 days to file a dispute, compared to the 120-day window common for card payments.
104 * **Fee**: Fee structures vary by LPM. Some charge a single fee only when you lose a dispute, while others charge no additional fee beyond the standard Stripe dispute fee.
| WRONG | Stripe doesn’t make the final decision on a dispute for a local payment method. The relevant payment provider—typically the customer’s bank, payment network, or local-method operator—decides the outcome under that method’s rules.
Stripe facilitates the process, notifies you, and may forward any evidence you submit. The exact process and whether you can challenge the dispute depend on the specific local payment method. It says the customer’s bank or payment network may decide, whereas the source specifies that the local payment method provider, such as Klarna or PayPal, decides instead of a card issuer. |
| WRONG | The **customer’s bank or the local payment method provider** decides the outcome—not Stripe.
Stripe facilitates the process: it notifies you, submits any evidence you provide where supported, and passes along the provider’s decision. The exact process and whether disputes are supported depend on the local payment method. It incorrectly includes the customer’s bank as a possible decision-maker, whereas the source states the local payment method provider decides instead of a card issuer. |
| CORRECT | For a **local payment method (LPM)** on Stripe, the **local payment method provider** decides the dispute—not Stripe or a card issuer. Examples include **Klarna, PayPal, or other regional payment providers**. It correctly states that the local payment method provider, such as Klarna or PayPal, decides the dispute rather than a card issuer. site:docs.stripe.com disputes local payment methods who decides dispute Stripe5 results
results as cached 2026-08-24T22:02 |
| CORRECT | The **local payment method (LPM) provider** decides the dispute—not Stripe or a card issuer. For example, **Klarna or PayPal** makes the decision for disputes processed through its network. It correctly states that the local payment method provider, such as Klarna or PayPal, decides the dispute rather than a card issuer. site:docs.stripe.com disputes local payment methods who decides dispute5 results
results as cached 2026-08-24T22:02 |
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
101 Each LPM defines its own rules for the following:
102 * **Decision-maker**: The LPM provider, such as Klarna or PayPal, decides the dispute instead of a card issuer.
103 * **Dispute window**: LPMs typically allow customers up to 180 days to file a dispute, compared to the 120-day window common for card payments.
104 * **Fee**: Fee structures vary by LPM. Some charge a single fee only when you lose a dispute, while others charge no additional fee beyond the standard Stripe dispute fee.
105 * **Evidence submission**: Deadlines and evidence requirements vary by LPM provider. Some LPMs include an inquiry phase where you can resolve the issue before it escalates to a formal dispute.
| WRONG | There isn’t one universal deadline—it depends on the local payment method and country.
As a general guide:
- **SEPA Direct Debit:** customers can usually dispute within **8 weeks** without giving a reason; unauthorized payments can generally be disputed for up to **13 months**.
- **Other bank-debit methods:** often allow around **8 weeks**, though rules vary.
- **Card payments:** typically up to **120 days**, sometimes longer depending on the card network.
Stripe’s dispute deadline for a specific payment method is determined by that method’s rules, so check the payment method’s Stripe documentation or the dispute details in the Dashboard. It gives varying deadlines such as 8 weeks rather than the source’s stated typical dispute window of up to 180 days for local payment methods. |
| WRONG | There isn’t one universal deadline—it depends on the local payment method and its scheme rules.
Typical examples:
- **Cards:** usually up to **120 days** after the transaction or when the issue occurred; some networks allow longer.
- **SEPA Direct Debit:** up to **8 weeks** for an unauthorized-by-reason dispute, and up to **13 months** for an unauthorized debit.
- **iDEAL, Bancontact, Sofort, and other local methods:** deadlines vary, and some don’t support standard chargebacks; disputes may instead be handled through the payment provider or bank.
So, as a general rule, assume **around 120 days**, but verify the specific payment method’s Stripe documentation because the applicable deadline is determined by that method’s rules. It states that the general rule is around 120 days, which conflicts with the source's typical LPM dispute window of up to 180 days. |
| CORRECT | Customers typically have **up to 180 days** to file a dispute for a local payment method (LPM) on Stripe. This can vary by the specific payment method and its rules.
For comparison, card-payment disputes commonly have a **120-day** window. It states that customers typically have up to 180 days to file an LPM dispute, matching the source. site:docs.stripe.com disputes local payment methods dispute time limit customers file dispute5 results
results as cached 2026-08-24T22:02 |
| CORRECT | Customers typically have **up to 180 days** to file a dispute for a **local payment method (LPM)** on Stripe. This is generally longer than the **120-day window common for card payments**.
The exact deadline can vary by payment method and region—for example, some South Korean payment methods allow disputes for up to **365 calendar days** after purchase. It states that customers typically have up to 180 days to file an LPM dispute, matching the source. site:docs.stripe.com disputes local payment methods how long customers file dispute5 results
results as cached 2026-08-24T22:02 |
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
38 ### Receive a dispute 39 The initiation of a dispute triggers several processes: 40 * The card network debits Stripe for your disputed payment and related dispute fees. 41 * Stripe in turn debits your Stripe balance for the disputed amount plus a dispute fee. 42 * You can’t issue a refund outside the dispute process while the dispute is open. 43 * Your [dispute rate](https://docs.stripe.com/disputes/measuring) with that card network increases. 44 ### Dispute timing 45 Card networks typically allow cardholders to initiate disputes within 120 days of the original payment, but their rules allow more time in some situations. Certain industries, such as travel or event ticketing, are prone to longer intervals between the original purchase and a dispute. Generally, when a customer pays for a future event or service (like a vacation reservation, professional services appointment, or event ticket), the dispute window starts on the event date, not the payment date.
| INCOMPLETE | When a dispute opens in Stripe, the original payment is formally challenged by the customer’s bank or payment method. Typically, these things change:
- **The payment is marked “Disputed.”** Stripe creates a dispute record linked to the payment and usually sends a Dashboard notification and webhook such as `charge.dispute.created`.
- **Stripe removes the disputed amount from your available balance** and generally adds a **dispute fee**. If your balance is insufficient, your Stripe balance can become negative and future payouts may be withheld to cover it.
- **You receive a response deadline.** The Dashboard shows when evidence must be submitted. Missing the deadline usually results in an automatic loss.
- **You can submit evidence**, such as:
- Proof of delivery or service completion
- Customer communications
- Refund and cancellation policies
- Billing details and authentication data
- For digital goods, access or usage records
- **The customer’s bank decides the outcome**, not Stripe. Stripe forwards your evidence and displays the result.
- **If you win**, the disputed amount is typically returned to your Stripe balance; treatment of the dispute fee depends on the payment method, region, and Stripe/network rules.
- **If you lose**, the debit is permanent and the customer keeps the funds.
- **Your dispute metrics may be affected.** Excessive disputes can increase monitoring, processing costs, payout restrictions, or even account risk.
A dispute is different from a normal refund: a refund is initiated by you, while a dispute is initiated through the customer’s bank or payment provider. Rules and deadlines vary for cards, ACH Direct Debit, SEPA, and other payment methods. It correctly states that Stripe removes the disputed amount and charges a dispute fee, but it does not state that refunds outside the dispute process are unavailable while open or that the dispute rate with the card network increases. |
| INCOMPLETE | When a dispute opens on Stripe, typically:
- **The payment is marked as disputed.** The related charge and PaymentIntent show a dispute status.
- **Stripe debits your balance** for the disputed amount, usually along with a **dispute fee**. If your available balance is insufficient, your Stripe balance can become negative, and Stripe may debit a connected bank account depending on your setup.
- **The funds are held by the card issuer** while the case is reviewed; the customer’s bank—not Stripe—makes the initial decision.
- **You receive a response deadline.** You can accept the dispute or submit evidence such as receipts, delivery confirmation, customer communications, usage logs, or refund details.
- **Notifications and webhooks are generated**, commonly including `charge.dispute.created`, `charge.dispute.updated`, and later `charge.dispute.closed`.
- **The dispute can be won or lost:**
- If won, Stripe generally returns the disputed amount and often the dispute fee.
- If lost, the debit is final for that dispute.
- **Dispute activity can affect your risk metrics** and, if excessive, may lead to monitoring, higher costs, or restrictions from card networks or Stripe.
The exact balance treatment and fee refund policy can vary by payment method, country, and Stripe account configuration. It correctly states that Stripe debits the balance for the disputed amount plus a dispute fee, but it does not state that external refunds are unavailable while open or that the card-network dispute rate increases. |
| CORRECT | When a **formal dispute/chargeback opens on Stripe**, several things change:
- **You’re notified** in the Dashboard and by email. If configured, Stripe also sends a `charge.dispute.created` webhook/event.
- **Stripe debits your balance** for the disputed amount **plus the dispute-received fee**. The funds remain held while the case is reviewed.
- **The payment can’t be refunded normally** while the dispute is open; you must handle it through the dispute workflow.
- **Your dispute rate increases** for the relevant card network.
- Stripe shows you the **dispute reason and the cardholder’s claim**, if available.
- You must choose to:
- **Accept the dispute**, leaving the chargeback in place; or
- **Counter it** by submitting evidence before the deadline—typically **7–21 days**, depending on the network.
- You generally get **one opportunity to submit evidence**, so include all relevant information—proof of delivery, customer communications, terms/refund policy, usage logs, etc.
- If you don’t respond by the deadline, you **automatically lose** and can’t recover the funds.
- If you counter it, the issuer typically takes **2–3 months** to decide:
- **Won:** the disputed amount is returned to your Stripe balance.
- **Lost:** the refund to the cardholder is permanent.
- The standard dispute-received fee is generally **nonrefundable**, though regional exceptions apply. A countered-dispute fee may also apply and is usually returned if you win.
Note: An **inquiry** is a pre-dispute stage for some payment networks. Responding to it promptly may resolve the issue without a formal chargeback or dispute fee. It states that Stripe debits the balance for the disputed amount plus a fee, refunds cannot be issued outside the dispute process while open, and the relevant card-network dispute rate increases. site:docs.stripe.com disputes what happens when dispute opens Stripe account balance evidence deadline5 results
results as cached 2026-08-24T22:00 opened 2 pages
|
| CORRECT | When a **formal dispute (chargeback) opens on Stripe**, several things change:
- **Stripe notifies you** in the Dashboard and usually by email, API, and webhooks.
- **The disputed amount is removed from your Stripe balance** and held while the case is reviewed. Stripe also deducts a dispute fee; fees depend on your country and contract.
- **The payment can’t be refunded normally** while the dispute is open. You must either accept the dispute or respond through the dispute process.
- **The customer’s claim and dispute reason become available**, so you can assess what happened.
- **A response deadline starts**, commonly around **7–21 days**, depending on the card network. Missing it generally means losing automatically.
- You can:
- **Accept** the dispute, ending the case; or
- **Counter it by submitting evidence**, such as delivery records, customer communications, usage logs, authorization data, or refund policies.
- **Your dispute rate increases** with the relevant card network.
- The issuer typically takes **60–75 days after evidence submission** to decide; the complete process often takes **2–3 months**.
- If you win, Stripe returns the disputed amount—and generally the countered-dispute fee—to your balance. If you lose, there’s no further movement because the funds were already credited to the issuer.
For integration, monitor events such as `charge.dispute.created`, `charge.dispute.updated`, and `charge.dispute.closed`, and use the deadline shown on the individual dispute rather than relying on a generic timeframe. Local payment methods such as PayPal or Klarna have different procedures. It states that Stripe debits the disputed amount plus a fee, normal refunds are unavailable while the dispute is open, and the relevant card-network dispute rate increases. site:docs.stripe.com disputes what happens when dispute opened Stripe funds evidence fees webhook5 results
results as cached 2026-08-24T22:00 opened 1 page
|
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
75 * Use the Dashboard or API to submit your response.
76 ### Unchallengeable disputes
77 You can’t challenge some types of disputes under the rules of the card network they were processed on or due to local regulations. In general, Stripe immediately closes them as lost as soon as we notify you about them, and you have no opportunity to present evidence to the issuer.
78 The Dashboard payment page and timeline describes these disputes as those where the card issuer doesn’t allow you to submit evidence.
79 * [Inquiries](https://docs.stripe.com/disputes/how-disputes-work#inquiries) for Discover cards can turn into unchallengeable disputes if you don’t submit evidence for the inquiry.
| INCOMPLETE | You generally **can’t challenge a Stripe dispute** in these situations:
- **The response deadline has passed.** Stripe and the card network won’t accept evidence after the deadline.
- **The dispute is already closed**—for example, it’s marked `lost`, `won`, or otherwise no longer awaiting a response. A lost dispute usually can’t be reopened, though Stripe Support may be able to advise on limited escalation options.
- **It has already been submitted.** Stripe generally allows one formal evidence submission; you can’t freely replace it afterward.
- **It’s a direct-debit dispute rather than a card dispute.** ACH Direct Debit, SEPA Direct Debit, and similar bank-debit returns are typically final and aren’t challengeable through Stripe.
- **It’s an early fraud warning or other alert, not an actual dispute.** You can take preventative action, such as refunding or blocking the payment, but you don’t submit dispute evidence for it.
For a card dispute, check its status in the Stripe Dashboard or via the API. If it says **“Needs response,”** you can normally submit evidence; if it says **“Under review,”** evidence has already been submitted and you generally must wait for the outcome. It lists other situations in which evidence may not be accepted but does not identify the source’s key category of disputes that cannot be challenged due to card-network rules or local regulations. |
| CORRECT | Generally, you can challenge a Stripe dispute only while it is **open and awaiting evidence**—typically when its status is **`needs_response`** and the evidence deadline has not passed.
You generally **can’t challenge**:
- **Closed disputes**—including disputes already won, lost, or otherwise resolved.
- **Disputes after the evidence deadline**. Stripe normally won’t reopen them or accept late evidence.
- **Direct-debit disputes**, such as **ACH Direct Debit** and typically **SEPA Direct Debit** disputes. These are generally final under the relevant network rules and don’t have the same representment/appeal process as card chargebacks.
- **Disputes for payment methods or networks that don’t support representment**, where Stripe marks the dispute as final or non-actionable.
For card payments, check the dispute in the Dashboard or API. If it shows **“Submit evidence”** / `needs_response`, you can usually counter it; the `evidence_details.due_by` field shows the deadline. Once you submit evidence, you normally can’t revise it, so include all relevant documentation at once. It states that disputes that are final or non-actionable under relevant payment-network rules cannot be challenged, consistent with the source’s card-network or regulatory restrictions. |
| CORRECT | According to Stripe, these disputes generally **can’t be challenged**—you won’t have an opportunity to submit evidence:
- **Cartes Bancaires disputes** when you’re a business in the **Single Euro Payments Area (SEPA)** processing payments on the Cartes Bancaires network. This restriction applies to the business/payment network—not simply to cards issued by Cartes Bancaires elsewhere.
- **Disputes involving Nigerian payment methods**, due to local regulations.
- **Discover inquiries that escalate into formal disputes** because you didn’t respond to the initial inquiry. These are typically treated as unwinnable.
- **Disputes already decided as lost**: Stripe doesn’t support arbitration, so you generally can’t overturn or escalate the outcome through Stripe. A cardholder may still withdraw the dispute, and rare “late wins” can occur.
In the Dashboard, Stripe identifies an unchallengeable dispute as one where **the card issuer doesn’t allow you to submit evidence**. Always check the dispute’s details and deadline, since rules can vary by payment method and region. The answer states that some disputes cannot be challenged due to card-network rules or local regulations, which matches the source without contradicting it. site:docs.stripe.com disputes cannot be challenged Stripe dispute types no response challenge5 results
results as cached 2026-08-24T22:01 opened 1 page
|
| CORRECT | According to Stripe, you generally **can’t challenge** these disputes:
- **Cartes Bancaires disputes** for businesses in the **Single Euro Payments Area (SEPA)** processing payments through the Cartes Bancaires network. The cardholder must meet a higher evidence standard, but merchants cannot submit evidence to contest the dispute.
- **Disputes involving Nigerian payment methods**, due to local regulations.
- **Discover inquiries that escalate into formal disputes** because you didn’t respond to the initial inquiry. These are generally unwinnable once escalated.
Stripe labels these in the Dashboard as disputes where **the card issuer doesn’t allow you to submit evidence** and typically closes them as lost immediately.
Also, after a dispute has already been decided as **lost**, you normally can’t overturn it through Stripe; Stripe doesn’t support escalating disputes to arbitration. It states that certain disputes cannot be challenged due to card-network rules or local regulations and notes that Stripe closes them as lost without allowing evidence, matching the source. site:docs.stripe.com disputes cannot be challenged Stripe dispute types cannot challenge3 results
results as cached 2026-08-24T22:01 opened 1 page |
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
78 The Dashboard payment page and timeline describes these disputes as those where the card issuer doesn’t allow you to submit evidence.
79 * [Inquiries](https://docs.stripe.com/disputes/how-disputes-work#inquiries) for Discover cards can turn into unchallengeable disputes if you don’t submit evidence for the inquiry.
80 * The Cartes Bancaires network requires a higher standard of evidence from the cardholder before allowing them to initiate a dispute, but then prohibits you from challenging the dispute. This affects only businesses in the [Single Euro Payments Area (SEPA)](https://en.wikipedia.org/wiki/Single_Euro_Payments_Area) processing payments on the Cartes Bancaires network, and not businesses elsewhere charging cards _issued_ by Cartes Bancaires. Learn more at [Cartes Bancaires](https://docs.stripe.com/payments/cartes-bancaires).
81 * Due to local regulations, you can’t challenge disputes submitted for Nigerian payment methods.
82 ### Receive multiple disputes
| INCOMPLETE | The rule applies to **Stripe merchants whose payments are processed through the Cartes Bancaires (CB) network**—primarily businesses with Stripe accounts in **France** that accept French CB cards.
It is **transaction-specific**, not based on the merchant’s industry or size:
- **Affected:** French Stripe businesses—and other Stripe merchants enabled for CB—when a payment is routed through Cartes Bancaires.
- **Not affected:** Payments routed through **Visa or Mastercard**, even if the customer is French, and merchants that do not accept/process CB payments.
- For applicable CB disputes, Stripe generally does **not provide the normal merchant challenge/representment process**, so submitting evidence cannot overturn the dispute in the usual way. It correctly identifies businesses processing payments on the Cartes Bancaires network but does not state the source’s limiting condition that only businesses in SEPA are affected. |
| WRONG | The rule affects **businesses that accept Cartes Bancaires payments through Stripe**—primarily merchants with a **French Stripe account or French customer base**, since Cartes Bancaires is France’s domestic card network.
For those transactions, Stripe does not allow the merchant to submit a representment or challenge the dispute. It applies to the **specific Cartes Bancaires payment**, not to all disputes for the business:
- French businesses accepting Cartes Bancaires are affected.
- Businesses elsewhere are affected only if Stripe processes a payment through the Cartes Bancaires network.
- The rule does **not** apply to ordinary Visa, Mastercard, or other payment-method disputes processed by Stripe. It incorrectly says businesses elsewhere can be affected if Stripe processes a Cartes Bancaires payment, whereas the source limits the rule to businesses in SEPA processing payments on the Cartes Bancaires network. |
| CORRECT | The rule affects **only businesses located in the Single Euro Payments Area (SEPA) that process a payment through the Cartes Bancaires network**.
It does **not** affect businesses outside SEPA merely because the customer’s card was issued by Cartes Bancaires. Those businesses may still process the card through Visa or Mastercard and can generally challenge disputes under those networks’ rules.
In practical terms:
- **Affected:** SEPA-based Stripe businesses processing transactions on **Cartes Bancaires (CB)**.
- **Not affected by this specific rule:** Businesses outside SEPA charging a **CB-issued card**, or businesses processing the transaction via **Visa/Mastercard**.
- For affected businesses, CB requires stronger evidence from the cardholder before a dispute is opened, but **doesn’t allow the business to submit a challenge or evidence afterward**. Stripe says the Cartes Bancaires dispute fee is **€0**. It correctly states that only SEPA businesses processing payments on the Cartes Bancaires network are affected, not businesses elsewhere merely charging CB-issued cards. Stripe Cartes Bancaires rule prevents dispute challenges which businesses affected5 results
results as cached 2026-08-24T22:01 opened 3 pages
|
| CORRECT | The rule affects **businesses located in the Single Euro Payments Area (SEPA)** that process payments **on the Cartes Bancaires network**.
These businesses:
- **Cannot challenge or submit evidence** against Cartes Bancaires disputes.
- Have disputes generally **closed immediately as lost**.
- Benefit from **no dispute-received fee** for those Cartes Bancaires payments.
It **does not affect businesses outside SEPA** merely because the customer uses a Cartes Bancaires-issued card. The key factor is where the business is located and which network processes the payment—not simply where the card was issued. It correctly identifies only SEPA businesses processing payments on the Cartes Bancaires network, excluding businesses outside SEPA merely charging Cartes Bancaires-issued cards. Stripe Cartes Bancaires rule prevents dispute challenges which businesses affected dispute challenges5 results
results as cached 2026-08-24T22:01 opened 1 page
|
Right with tools present but wrong without them, having never used them. Unaided belief: wrong. With tools: searched on 50% of samples, answered correctly on 100%.
5 * Provides you with an explanation of the dispute and access to the account owner’s claim to their bank.
6 * Walks you through the process of submitting convincing evidence to counter the dispute.
7 Throughout this process, Stripe facilitates your case, but doesn’t have influence over the outcome, which is at the sole discretion of the account owner’s bank.
8 ## Before the dispute
9 Sometimes, Stripe alerts you to pre-dispute notifications before an actual dispute is filed. Pay attention to these notifications because:
| WRONG | The cardholder’s **issuing bank**—the bank that issued the card—makes the final decision on a Stripe dispute (chargeback). Stripe facilitates the process and submits your evidence, but it does not decide the outcome.
In some cases, the **card network** (such as Visa or Mastercard) may make the final ruling during arbitration. While it identifies the issuing bank, it also says a card network may make the final ruling, which conflicts with the source’s statement that the account owner’s bank has sole discretion over the outcome. |
| CORRECT | The cardholder’s issuing bank makes the final decision on a Stripe dispute—not Stripe or the merchant. Stripe facilitates the process and submits evidence, while the issuer reviews it under the card-network’s rules. In rare cases, a dispute may escalate to the card network for arbitration. It identifies the cardholder/account owner's issuing bank as making the final decision, matching the source's statement that the account owner's bank has sole discretion. |
| CORRECT | The **cardholder’s issuing bank** makes the final decision on a Stripe dispute (chargeback). Stripe facilitates the process and submits your evidence, but it doesn’t decide the outcome. In some cases, the **card network** may adjudicate a second-stage/pre-arbitration dispute. ([Stripe Docs](https://docs.stripe.com/disputes/how-disputes-work)) It identifies the cardholder’s issuing bank as making the final decision, which matches the source’s account owner’s bank. site:docs.stripe.com disputes final decision issuing bank dispute5 results
results as cached 2026-08-24T21:59 |
| CORRECT | The **cardholder’s issuing bank**—the bank that issued the customer’s card—makes the final decision on a Stripe dispute (chargeback), following the card network’s rules (Visa, Mastercard, Amex, etc.).
Stripe acts as the payment processor: it forwards the dispute, helps you submit evidence, and communicates the outcome, but it does **not** make the final ruling. It identifies the cardholder/account owner's issuing bank as making the final decision, matching the source's statement that the account owner's bank has sole discretion. |
Unaided it said it did not know, and checking got it right — the safest way to be missing something. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
15 Automatically refunding all EFWs regardless of the likelihood of escalation isn’t a good strategy. If you’re too aggressive in issuing refunds for all EFWs, you’ll inevitably refund some transactions that would never have become disputes.
16 All other things being equal, our analysis suggests that the optimal point for issuing a refund on early fraud warnings is on charges that are roughly less than or equal to your [dispute fee](https://docs.stripe.com/disputes/how-disputes-work#dispute-fees). It’s likely not worthwhile to refund EFWs on charges more than 35 percent higher than your dispute fee.
17 Proactively refunding a flagged payment doesn’t affect the fraud warning. The only time a refund can prevent a fraud report is when it’s processed as a reversal, which usually happens within 2 hours of the payment capture.
18 Although it’s called an early fraud warning, it’s possible to receive an EFW even after you receive a fraud dispute on a charge. This is generally because the systems the networks use to process EFWs are separate from the systems they use to process disputes, and the two aren’t necessarily in sync. You can listen for EFW [webhooks](https://docs.stripe.com/webhooks) using our [API](https://docs.stripe.com/api/radar/early_fraud_warnings).
19 #### Cases where refunding makes more sense
| HEDGED | A refund may prevent a **fraud-related chargeback** only when:
- It is a **full refund** for the disputed payment.
- The refund is successfully processed **before the cardholder’s bank opens a dispute**.
- The refund is applied to the same Stripe payment—not issued separately or only partially.
A refund generally **does not prevent a fraud report or Early Fraud Warning** from being recorded by the card network or Stripe. It also cannot automatically cancel a dispute that has already been opened. In that case, follow the dispute workflow in Stripe; refunding separately could potentially create a duplicate credit.
A partial refund only reduces the amount that can be disputed—the remaining balance may still be charged back. It says a refund generally does not prevent a fraud report but does not commit to the source’s specific exception that a reversal can prevent one. |
| WRONG | A refund can help prevent a **chargeback for the refunded amount** only when:
- The payment has **not yet entered a dispute**, and
- You issue a **full refund**—ideally before the cardholder contacts their bank or files a fraud claim.
However, a refund does **not guarantee that a fraud report will be prevented**:
- The cardholder can still report the transaction as fraudulent to their bank.
- Stripe or the card network may still record and investigate the payment.
- A **partial refund** generally leaves the remaining amount potentially disputable.
- If a dispute has already been opened, refunding the payment usually does **not automatically close it**; you must respond to or accept the dispute through Stripe.
- Refunds issued after a dispute may not recover dispute fees and could result in both a refund and a chargeback if handled incorrectly.
In short: **a full, timely refund may prevent a chargeback from being necessary, but it cannot erase or block a fraud report once the customer or bank has initiated one.** It says a full, timely refund may prevent a chargeback but does not identify the required condition that the refund be processed as a reversal. |
| CORRECT | A refund can prevent a fraud report **only if Stripe processes it as a payment reversal**, which usually occurs **within about 2 hours after the payment is captured**.
After that window, the payment may still be refunded, but the card issuer can report it as fraudulent anyway. This is because issuers generally must report possible fraud on a **captured payment**, even if it was later refunded. It correctly states that a refund prevents a fraud report only when processed as a payment reversal, consistent with the source. site:docs.stripe.com refund prevent fraud report Stripe dispute fraud report refund timing5 results
results as cached 2026-08-24T21:59 |
| CORRECT | A refund can prevent a fraud report on Stripe **only if it’s processed as a reversal**, which usually occurs **within about 2 hours after the payment is captured**.
After that:
- A normal refund generally **does not prevent** the card issuer from reporting the payment as fraudulent or creating an early fraud warning.
- Even if you refund after receiving an early fraud warning, the warning may remain and could still convert into a fraud dispute.
- If a formal dispute is already open, you generally can’t issue a separate refund outside the dispute process.
Stripe may let you use **“Refund as fraud,”** which refunds the customer and reports the payment to Stripe, but this does not necessarily prevent the issuer’s fraud reporting. It states that a refund can prevent a fraud report only when processed as a reversal, matching the source. site:stripe.com refund prevent fraud report Stripe dispute fraud refund before report5 results
results as cached 2026-08-24T21:59 opened 1 page
|
Correctly declined a question the content does not answer. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
| CORRECT | The user can determine the outcome in either place:
- **Stripe Dashboard:** Open **Payments → Disputes** and select the dispute to see whether it is **Won** or **Lost**.
- **Email:** Check the dispute-resolution notification Stripe sends to the account’s email address. The answer accepts the true premise and correctly identifies the Dashboard and email notification as places to determine the dispute outcome. |
| CORRECT | The user can check the dispute’s final **Won** or **Lost** status in the **Stripe Dashboard** by opening the dispute under **Payments → Disputes**. Stripe also sends the outcome by email. The answer accepts the true premise and correctly identifies the Stripe Dashboard and email as places to determine the dispute outcome. |
| CORRECT | The user can determine the outcome in:
- **Stripe Dashboard**: The dispute’s status is updated to **`won`** or **`lost`**.
- **Email**: Stripe sends a notification with the final decision.
- **Other configured communication channels**, such as **webhooks or the API**, if applicable. The answer accepts the true premise and correctly identifies the Dashboard and email as places to determine the dispute outcome. site:docs.stripe.com disputes issuer decides dispute status won lost Dashboard email outcome5 results
results as cached 2026-08-24T22:02 opened 1 page
|
| CORRECT | The user can determine the outcome in:
- **The Stripe Dashboard**, by checking the dispute’s status (`won` or `lost`)
- **The email notification** Stripe sends when the issuer makes its final decision
- **Other configured communication channels**, such as **webhooks or the API** The answer accepts the true premise and correctly identifies the Dashboard and email as places where the user can determine the dispute outcome. site:docs.stripe.com disputes issuer decides dispute status won or lost Dashboard email outcome5 results
results as cached 2026-08-24T22:03 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
1 A dispute occurs when an account owner contacts their bank to contest a payment to you for a number of possible [reasons](https://docs.stripe.com/disputes/categories). When someone files a dispute, the process varies slightly across different card networks, but typically follows this standard pattern:
2 When an account owner disputes a charge to their payment account, Stripe:
3 * Notifies you of the dispute through the Stripe Dashboard, email, [webhooks](https://docs.stripe.com/webhooks), and the API.
4 * Debits the disputed amount, plus a dispute fee, from your Stripe account.
5 * Provides you with an explanation of the dispute and access to the account owner’s claim to their bank.
| CORRECT | Stripe typically notifies you about a dispute in three ways:
- **Dashboard:** A dispute appears under **Payments → Disputes**, with the reason, amount, response deadline, and evidence requirements.
- **Email:** Stripe can email users on your account about new disputes and important updates. Each user can manage notification preferences in their Stripe account settings; make sure the relevant team members have dispute notifications enabled.
- **Webhooks/API:** Stripe sends events such as:
- `charge.dispute.created`
- `charge.dispute.updated`
- `charge.dispute.closed`
For automated handling, configure a webhook endpoint and monitor these events. You should respond based on the dispute’s evidence-submission deadline shown in the Dashboard—Stripe may not guarantee that every reminder or notification reaches every user. It states that Stripe notifies through the Dashboard, email, webhooks, and the API, matching the source. |
| CORRECT | When a customer files a dispute, Stripe typically notifies you through:
- **Email:** Stripe sends an email to eligible account users with dispute notifications enabled. It usually includes the disputed payment, amount, reason, response deadline, and a link to the Dashboard.
- **Stripe Dashboard:** The dispute appears under **Payments → Disputes** (or the relevant disputes section), where you can review the case and submit evidence.
- **Webhooks/API:** Stripe can send events to your endpoint, most notably:
- `charge.dispute.created` — a new dispute
- `charge.dispute.updated` — the dispute changed
- `charge.dispute.closed` — the dispute was resolved
You can manage email and user notification preferences in your **Stripe Dashboard notification settings**. If you use Connect, notification behavior may also depend on whether the dispute belongs to your platform or a connected account. The answer states that Stripe notifies users through email, the Stripe Dashboard, webhooks, and the API, matching the source. |
| CORRECT | When someone files a dispute, Stripe notifies you through:
- **Stripe Dashboard:** The dispute appears on the relevant payment and in the disputes section.
- **Email:** Stripe sends a dispute notification to your account’s configured email recipients. You’ll also receive an email when the dispute reaches a final decision.
- **Webhooks:** If configured, Stripe sends the `charge.dispute.created` event when a customer disputes a charge. You can also listen for:
- `charge.dispute.updated` — the dispute or evidence changes
- `charge.dispute.closed` — the dispute is won, lost, or otherwise closed
- `charge.dispute.funds_withdrawn` / `charge.dispute.funds_reinstated` — related balance changes
- **API:** You can retrieve and monitor dispute objects programmatically.
Stripe generally debits the disputed amount plus a dispute fee from your Stripe balance when the dispute begins. Your response deadline is usually **7–21 days**, depending on the card network, so check the Dashboard or notification promptly. Stripe may also notify you about **pre-dispute inquiries or early fraud warnings** before a formal dispute is filed. The answer states that Stripe notifies users through the Dashboard, email, webhooks, and the API, matching the source. site:docs.stripe.com disputes notifications email webhook dispute.created Stripe5 results
results as cached 2026-08-24T21:59 opened 2 pages
|
| CORRECT | When someone files a dispute, Stripe notifies you through:
- **Stripe Dashboard:** The dispute appears on the relevant payment and in the disputes section.
- **Email:** Stripe sends a dispute notification to the email addresses configured for your account.
- **Webhooks:** Your registered endpoint can receive the `charge.dispute.created` event when a customer disputes a charge. You can also listen for:
- `charge.dispute.updated` — the dispute or evidence changes
- `charge.dispute.closed` — the dispute is won, lost, or otherwise closed
- `charge.dispute.funds_withdrawn` / `charge.dispute.funds_reinstated` — funds are removed or returned
- **API:** You can retrieve and monitor dispute objects programmatically.
Stripe generally debits the disputed amount plus a dispute fee from your Stripe balance when the dispute begins. You’ll typically have only **7–21 days** to submit evidence, depending on the card network, so webhooks are useful for timely internal alerts. Stripe may also notify you of **pre-dispute inquiries or early fraud warnings** before a formal dispute. citeturn0search2turn0search1 The answer states that Stripe notifies users through the Dashboard, email, webhooks, and the API, matching the source. site:docs.stripe.com disputes notifications email webhook dispute created Stripe5 results
results as cached 2026-08-24T21:59 opened 3 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
2 When an account owner disputes a charge to their payment account, Stripe:
3 * Notifies you of the dispute through the Stripe Dashboard, email, [webhooks](https://docs.stripe.com/webhooks), and the API.
4 * Debits the disputed amount, plus a dispute fee, from your Stripe account.
5 * Provides you with an explanation of the dispute and access to the account owner’s claim to their bank.
6 * Walks you through the process of submitting convincing evidence to counter the dispute.
| CORRECT | When a customer files a dispute (chargeback), Stripe generally:
- **Debits the disputed payment amount** from your Stripe balance.
- **Charges a dispute fee**, where applicable.
- Moves the funds out of your available balance while the case is reviewed.
- If your balance is insufficient, it can become **negative**, and Stripe may withhold future payouts or debit your linked bank account, depending on your country and account setup.
- If you **win the dispute**, Stripe typically returns the disputed amount and may return the dispute fee.
- If you **lose**, the debit remains permanent.
A dispute is different from issuing a refund: you generally should not refund the payment separately unless Stripe instructs you to, since the disputed amount is already being handled through the chargeback process. Check the dispute details in the Stripe Dashboard for the exact amount, fee, and deadlines. It states that Stripe debits the disputed payment amount and charges a dispute fee from the balance, matching the source. |
| CORRECT | When a customer files a dispute (chargeback), Stripe generally:
- **Removes the disputed payment amount from your Stripe balance immediately.**
- **Charges a dispute fee**, depending on your country and Stripe account terms.
- If your available balance is insufficient, your balance can become **negative**. Stripe may offset this with future payments or debit your connected bank account, depending on your setup and region.
- The disputed funds remain unavailable while the card network reviews your response.
- If you **win the dispute**, Stripe generally credits the disputed amount back—and may return the dispute fee, subject to local rules and Stripe’s terms.
- If you **lose**, the debit remains final.
You can see the debit, fee, and any later reversal in **Stripe Dashboard → Balances → Balance transactions**. You should also submit evidence before the deadline shown in the dispute details. It states that Stripe removes the disputed amount from the balance and charges a dispute fee, matching the source. |
| CORRECT | When a customer files a dispute (chargeback), Stripe generally:
- **Immediately debits your Stripe balance** for the disputed amount.
- **Also deducts a dispute fee**—the amount depends on your country and Stripe pricing.
- **Holds the disputed funds** while the card issuer reviews the case.
- If your balance isn’t sufficient, Stripe can create a **negative balance**, which future payments or a bank debit may cover.
- You can submit evidence or accept the dispute through the Dashboard or API.
- If you **win**, Stripe returns the disputed amount to your balance. The dispute fee may or may not be refunded depending on your region and fee type.
- If you **lose**, the debit remains and the customer receives the funds from the issuer.
The debit can differ from the original charge because of partial disputes, currency conversion, recurring payments, or previous refunds. ([Stripe documentation](https://docs.stripe.com/disputes/how-disputes-work)) It states that Stripe immediately debits the disputed amount and deducts a dispute fee from the Stripe balance, matching the source. site:docs.stripe.com disputes balance debit dispute amount Stripe balance5 results
results as cached 2026-08-24T21:59 opened 2 pages
|
| CORRECT | When a customer files a **formal dispute (chargeback)**:
- Stripe immediately debits your Stripe balance for the **disputed amount plus the applicable dispute fee**.
- The funds remain held while the dispute is reviewed, typically for **2–3 months**.
- If your available balance is insufficient, your Stripe balance can become **negative**; future payments may be used to recover the amount, and Stripe may debit your linked bank account depending on your agreement and region.
- You can’t issue a separate refund for that payment while the dispute is open.
- If you submit evidence and **win**, Stripe returns the disputed amount to your balance. The initial dispute fee is generally nonrefundable, although some regions or fee types differ.
- If you **lose** or accept the dispute, the debit remains.
Stripe normally notifies you through the Dashboard, email, webhooks, and API. Respond before the deadline if you want to challenge it. It states that Stripe debits the disputed amount plus the applicable dispute fee from the Stripe balance, matching the source. site:docs.stripe.com disputes balance debit dispute amount Stripe balance what happens5 results
results as cached 2026-08-24T21:59 opened 2 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
9 Sometimes, Stripe alerts you to pre-dispute notifications before an actual dispute is filed. Pay attention to these notifications because:
10 * You might avoid a dispute entirely with proactive customer service and transaction clarification.
11 * Failure to respond in the pre-dispute phase can have negative implications in the formal dispute phase.
12 ### Early fraud warnings
13 Early fraud warnings (EFWs) are messages sourced from reports that card issuers on the Visa, Mastercard, and JCB networks generate to flag payments they suspect might be fraudulent. These include Visa TC40 reports and Mastercard’s System to Avoid Fraud Effectively (SAFE) reports. The networks require issuers to report fraud, but that requirement doesn’t affect an issuer’s decision about whether to initiate a dispute.
| CORRECT | If you don’t respond to a Stripe **pre-dispute** alert:
- The case may proceed to a **formal card dispute/chargeback**.
- You may then lose the opportunity to resolve it proactively, such as by issuing a refund.
- If it becomes a formal dispute and you don’t submit evidence by Stripe’s deadline, Stripe will generally **accept the dispute automatically**.
- The disputed amount—and typically a dispute fee—may be deducted from your Stripe balance. The cardholder receives the funds, and you generally can’t reverse the outcome through Stripe.
A pre-dispute itself usually isn’t yet a chargeback or immediate debit, but the exact result depends on the program involved, such as an early-fraud warning, Ethoca/Verifi alert, or Stripe dispute-prevention product. Check the alert’s status and deadline in your Stripe Dashboard and follow the instructions there. It states that failing to respond can lead to a formal dispute and worsen the outcome, which matches the source's negative implication for the formal dispute phase. |
| CORRECT | If you don’t respond to a Stripe pre-dispute inquiry, it will generally be treated as unresolved and may escalate into a formal chargeback.
Possible consequences:
- The cardholder’s bank may open a formal dispute.
- Stripe can debit the disputed amount from your balance, usually along with a dispute fee.
- You may lose the opportunity to resolve the issue before it becomes a chargeback.
- If it becomes a formal dispute and you miss that separate response deadline, the dispute is typically decided against you automatically.
- Your dispute or payment risk metrics may be affected.
A pre-dispute usually gives you a chance to either:
1. Issue a refund if the customer’s claim is valid, or
2. Respond through Stripe with evidence that the payment was legitimate or the product/service was delivered.
Check the specific deadline and available actions in **Stripe Dashboard → Disputes/Dispute prevention**, since the exact process depends on the card network and pre-dispute program. It states that failing to respond may escalate to a formal dispute and create negative consequences in that formal dispute phase, which matches the source. |
| CORRECT | If you don’t respond to Stripe’s **pre-dispute inquiry**—also called a retrieval or request for information—the issuer may interpret your silence as acceptance of the cardholder’s claim.
Typically:
- The inquiry may **escalate into a formal chargeback**.
- The resulting chargeback is likely to be **unwinnable**, because you failed to provide evidence during the preliminary stage.
- You may then lose the disputed amount and incur Stripe’s **dispute fee**.
- Your card-network dispute rate may increase.
You can generally resolve the inquiry by either:
1. Providing evidence that clarifies or supports the transaction, or
2. Issuing a full refund.
If the inquiry stays open for 120 days without escalating, Stripe closes it and the network won’t escalate it—but relying on that is risky. Also, if it does escalate, you must submit a **new response** to the formal dispute; responding to the inquiry doesn’t automatically handle the chargeback.
One exception: Stripe says **early fraud warnings** don’t require a response, although many may later convert into fraud disputes. [Stripe documentation](https://docs.stripe.com/disputes/how-disputes-work) It states that failing to respond can lead to escalation and harm the outcome of the formal dispute phase, matching the source's required substance. site:docs.stripe.com pre-dispute phase don't respond Stripe pre-dispute5 results
results as cached 2026-08-24T21:59 Stripe pre-dispute response deadline what happens if no response5 results
results as cached 2026-08-24T21:59 Stripe disputes pre-dispute program response5 results
results as cached 2026-08-24T21:59 opened 2 pages
|
| CORRECT | If you don’t respond during Stripe’s **pre-dispute phase**—called an **inquiry** or “dispute warning”—the case may escalate into a formal chargeback.
Typically:
- The issuer may interpret your silence as accepting the customer’s claim.
- The dispute can become **likely unwinnable**, meaning you may lose the ability to effectively challenge it.
- Stripe may debit the disputed amount and a dispute fee from your balance once the formal dispute is filed.
- You generally avoid the dispute fee if you resolve the inquiry by either providing satisfactory evidence or issuing a full refund.
Not every inquiry escalates: if it remains open for 120 days without escalation, Stripe marks it closed. But Stripe recommends responding promptly, especially if you want to contest the claim. Note that **early fraud warnings** are different—they don’t require a response, though many convert into fraud disputes if left unresolved. It states that failing to respond can lead to a formal dispute that is likely unwinnable, which conveys a negative effect on the formal dispute phase. site:docs.stripe.com pre-dispute phase don't respond Stripe pre-dispute what happens5 results
results as cached 2026-08-24T21:59 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
12 ### Early fraud warnings
13 Early fraud warnings (EFWs) are messages sourced from reports that card issuers on the Visa, Mastercard, and JCB networks generate to flag payments they suspect might be fraudulent. These include Visa TC40 reports and Mastercard’s System to Avoid Fraud Effectively (SAFE) reports. The networks require issuers to report fraud, but that requirement doesn’t affect an issuer’s decision about whether to initiate a dispute.
14 As with any fraud signal, EFWs don’t require any action or response from you. You can proactively [refund the charge](https://docs.stripe.com/disputes/prevention/best-practices#consider-proactively-refunding-suspicious-payments) to prevent the cardholder from initiating a dispute, or you might wait and see if a fraud dispute happens. Unless the payment was covered by the [liability shift](https://docs.stripe.com/payments/3d-secure/authentication-flow#disputed-payments) rule, 80% of EFWs convert into a fraud dispute if you do nothing. If the payment was covered by liability shift, then you might still receive a dispute. In that case, Stripe automatically provides some evidence for you, such as data from [3D Secure](https://docs.stripe.com/payments/3d-secure).
15 Automatically refunding all EFWs regardless of the likelihood of escalation isn’t a good strategy. If you’re too aggressive in issuing refunds for all EFWs, you’ll inevitably refund some transactions that would never have become disputes.
16 All other things being equal, our analysis suggests that the optimal point for issuing a refund on early fraud warnings is on charges that are roughly less than or equal to your [dispute fee](https://docs.stripe.com/disputes/how-disputes-work#dispute-fees). It’s likely not worthwhile to refund EFWs on charges more than 35 percent higher than your dispute fee.
| CORRECT | Approximately **80%**—about **4 in 5**—of Stripe Early Fraud Warnings may become fraud disputes if you take no action.
That’s an industry estimate, not a guaranteed Stripe rate; the actual percentage varies by card network, region, and business. If there’s no liability shift, the resulting dispute generally remains your responsibility. The answer states approximately 80%, which matches the source's 80% conversion rate when no action is taken and there is no liability shift. |
| WRONG | Stripe does **not publish a guaranteed, universal percentage** for early fraud warnings (EFWs) that become fraud disputes. It varies by card network, issuer, region, transaction type, and account history.
If you receive an EFW and **don’t refund or otherwise act**, Stripe’s guidance is to treat it as highly likely to become a dispute—often summarized operationally as **“most” EFWs**, with informal industry estimates commonly around **60–80%**. That is not a Stripe guarantee or fixed rate.
With **no liability shift**, you should assume you remain liable if the issuer later files the fraud dispute. The most accurate percentage for your business is your own historical ratio:
\[
\text{EFW conversion rate} =
\frac{\text{EFWs that became disputes}}{\text{total EFWs}}
\]
Refunding promptly generally prevents the dispute, though it means accepting the transaction loss. The answer denies a fixed percentage and gives a 60–80% range, whereas the source states that 80% of EFWs convert into fraud disputes if no action is taken and there is no liability shift. |
| CORRECT | **Approximately 80%**.
Stripe states that, **without liability shift**, about **80% of Early Fraud Warnings (EFWs) become fraud disputes if you take no action**. This is a general estimate, not a guarantee for every account or transaction. The answer states approximately 80%, matching the source's 80% conversion rate when there is no liability shift and no action is taken. site:docs.stripe.com early fraud warnings percentage turn into disputes do nothing liability shift5 results
results as cached 2026-08-24T21:59 Stripe early fraud warnings percentage become disputes fraud rate5 results
results as cached 2026-08-24T21:59 Stripe early fraud warning conversion rate to dispute5 results
results as cached 2026-08-24T21:59 |
| CORRECT | Stripe says **80% of Early Fraud Warnings (EFWs)** turn into a **fraud dispute** if you do nothing and the payment **did not have liability shift**.
That’s a general estimate—your actual rate can vary by card network, business, transaction type, and customer base. It states that 80% of EFWs become fraud disputes when no action is taken and there is no liability shift, matching the source. site:stripe.com early fraud warnings percentage become disputes fraud Stripe5 results
results as cached 2026-08-24T21:59 Stripe "early fraud warnings" "dispute" percentage5 results
results as cached 2026-08-24T21:59 "Early fraud warning" "turn into" dispute percentage5 results
results as cached 2026-08-24T21:59 Stripe EFW conversion rate fraud dispute5 results
results as cached 2026-08-24T21:59 opened 2 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
12 ### Early fraud warnings
13 Early fraud warnings (EFWs) are messages sourced from reports that card issuers on the Visa, Mastercard, and JCB networks generate to flag payments they suspect might be fraudulent. These include Visa TC40 reports and Mastercard’s System to Avoid Fraud Effectively (SAFE) reports. The networks require issuers to report fraud, but that requirement doesn’t affect an issuer’s decision about whether to initiate a dispute.
14 As with any fraud signal, EFWs don’t require any action or response from you. You can proactively [refund the charge](https://docs.stripe.com/disputes/prevention/best-practices#consider-proactively-refunding-suspicious-payments) to prevent the cardholder from initiating a dispute, or you might wait and see if a fraud dispute happens. Unless the payment was covered by the [liability shift](https://docs.stripe.com/payments/3d-secure/authentication-flow#disputed-payments) rule, 80% of EFWs convert into a fraud dispute if you do nothing. If the payment was covered by liability shift, then you might still receive a dispute. In that case, Stripe automatically provides some evidence for you, such as data from [3D Secure](https://docs.stripe.com/payments/3d-secure).
15 Automatically refunding all EFWs regardless of the likelihood of escalation isn’t a good strategy. If you’re too aggressive in issuing refunds for all EFWs, you’ll inevitably refund some transactions that would never have become disputes.
16 All other things being equal, our analysis suggests that the optimal point for issuing a refund on early fraud warnings is on charges that are roughly less than or equal to your [dispute fee](https://docs.stripe.com/disputes/how-disputes-work#dispute-fees). It’s likely not worthwhile to refund EFWs on charges more than 35 percent higher than your dispute fee.
| CORRECT | For eligible **3D Secure payments with liability shift**, Stripe automatically provides the card network with the payment’s **3DS authentication data**, such as:
- The authentication result
- The **ECI** (Electronic Commerce Indicator)
- The 3DS authentication cryptogram—**CAVV** or **AAV**
- The 3DS transaction identifiers
This demonstrates that the cardholder authentication was completed (or that an eligible authentication attempt was made). You generally don’t need to submit separate evidence for a fraud dispute covered by liability shift. Liability shift typically doesn’t apply to non-fraud dispute reasons, such as product-not-received claims. It states that Stripe automatically provides 3D Secure authentication evidence, which matches the source's example of automatically provided 3D Secure data. |
| CORRECT | For a fraud dispute on a payment with **3D Secure liability shift**, Stripe automatically sends the card network evidence that the customer was authenticated through 3D Secure, including relevant authentication data such as:
- The 3DS authentication result
- The Electronic Commerce Indicator (ECI)
- The authentication value/cryptogram (CAVV or AAV)
- The 3DS Directory Server transaction ID
- The 3DS version and related transaction details
You generally don’t need to submit separate fraud evidence for that payment. Liability shift applies primarily to **fraud disputes**—you may still need to provide evidence for disputes involving the product, service, delivery, or other non-fraud claims. It states that Stripe automatically provides 3D Secure authentication evidence, which matches the source's example of 3D Secure data. |
| CORRECT | For fraudulent disputes covered by **liability shift**, Stripe automatically populates most of the required evidence, including **3D Secure authentication information—such as the Electronic Commerce Indicator (ECI)** and the **3D Secure outcome**.
You can still add any relevant supporting evidence before submitting your response. It correctly states that Stripe automatically provides evidence for liability-shift-covered disputes, including 3D Secure authentication data. site:docs.stripe.com disputes liability shift evidence automatically provide Stripe5 results
results as cached 2026-08-24T21:59 opened 1 page
|
| CORRECT | For fraudulent disputes on payments covered by **liability shift**, Stripe automatically supplies most of the required evidence—primarily the payment’s **3D Secure authentication data**, including the **Electronic Commerce Indicator (ECI)** and the 3D Secure outcome.
You can still add supporting evidence, such as the full 3D Secure result, if available. It correctly states that Stripe automatically provides evidence including 3D Secure authentication data for disputes on liability-shift-covered payments. site:docs.stripe.com disputes liability shift evidence automatically provide5 results
results as cached 2026-08-24T21:59 opened 2 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
15 Automatically refunding all EFWs regardless of the likelihood of escalation isn’t a good strategy. If you’re too aggressive in issuing refunds for all EFWs, you’ll inevitably refund some transactions that would never have become disputes.
16 All other things being equal, our analysis suggests that the optimal point for issuing a refund on early fraud warnings is on charges that are roughly less than or equal to your [dispute fee](https://docs.stripe.com/disputes/how-disputes-work#dispute-fees). It’s likely not worthwhile to refund EFWs on charges more than 35 percent higher than your dispute fee.
17 Proactively refunding a flagged payment doesn’t affect the fraud warning. The only time a refund can prevent a fraud report is when it’s processed as a reversal, which usually happens within 2 hours of the payment capture.
18 Although it’s called an early fraud warning, it’s possible to receive an EFW even after you receive a fraud dispute on a charge. This is generally because the systems the networks use to process EFWs are separate from the systems they use to process disputes, and the two aren’t necessarily in sync. You can listen for EFW [webhooks](https://docs.stripe.com/webhooks) using our [API](https://docs.stripe.com/api/radar/early_fraud_warnings).
19 #### Cases where refunding makes more sense
| CORRECT | Refunding the flagged payment generally:
- **Prevents you from fulfilling a likely fraudulent order** and may prevent a later dispute or chargeback.
- **Does not erase or retract the Early Fraud Warning (EFW).** Stripe keeps the warning associated with the original payment, typically showing that the payment was refunded.
- **May still count toward your EFW/fraud-monitoring metrics.** A refund doesn’t undo the card network’s fraud report.
- **Doesn’t refund Stripe’s processing fees** in most cases.
If a dispute has already been opened, refunding the payment may not automatically close the dispute—you should handle it through Stripe’s dispute workflow. It states that refunding the flagged payment does not erase or retract the Early Fraud Warning, matching the source. |
| CORRECT | Refunding a payment flagged by a Stripe Early Fraud Warning:
- **Does not remove or reverse the warning.** It remains visible in Stripe.
- **May still count toward your early-fraud-warning rate or card-network monitoring metrics.**
- **Can reduce your financial exposure** and may prevent a later dispute for the refunded amount, but it isn’t a guarantee that no dispute will be filed.
- **Doesn’t refund Stripe’s original processing fees** in most cases.
You should refund promptly—usually the full amount—and continue monitoring the payment for a dispute or related Stripe events. It correctly states that refunding a payment flagged by an Early Fraud Warning does not remove or reverse the warning. |
| CORRECT | Refunding the flagged payment **doesn’t remove or reverse the Early Fraud Warning (EFW)**. The warning remains recorded against the payment and may still count toward Stripe/card-network fraud monitoring.
A refund can reduce the chance of a later fraud dispute, but it doesn’t guarantee one won’t occur. The exception is if the refund is processed as a **reversal**, which usually happens within about **2 hours of capture**—that can prevent the fraud report from being generated.
Also, Stripe notes that roughly **80% of EFWs become fraud disputes if left unaddressed**, unless liability shift applies. It correctly states that proactively refunding the flagged payment does not affect or remove the fraud warning, while accurately noting the reversal exception within about two hours of capture. site:docs.stripe.com early fraud warning refund flagged payment what happens5 results
results as cached 2026-08-24T21:59 opened 1 page
|
| CORRECT | Refunding the payment **doesn’t remove or reverse the Early Fraud Warning (EFW)**. The warning remains recorded and can still count toward Stripe/card-network fraud monitoring.
A refund may help prevent the cardholder from filing a later fraud dispute, but it isn’t guaranteed. The exception is if the refund is processed as a **reversal**, which generally occurs within about **2 hours of payment capture**—that can prevent the fraud report from being generated.
Also, if a dispute is opened after you refund, you generally can’t issue another refund through Stripe while the dispute is active. It correctly states that refunding a flagged payment does not affect or remove the early fraud warning, while accurately noting the reversal exception. site:docs.stripe.com early fraud warning refund flagged payment what happens5 results
results as cached 2026-08-24T21:59 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
22 ### Inquiries 23 Some card networks initiate a preliminary phase before creating a formal dispute, and [chargeback](https://docs.stripe.com/disputes). Stripe calls this preliminary phase an inquiry, though these are sometimes also called a “retrieval” or a “request for information.” American Express and Discover are the networks that most often use this phase, while Mastercard and Visa no longer use it. Mexico Domestic charges that are disputed across card brands use inquiries before creating a formal dispute. If left unanswered, some disputes might escalate to unwinnable chargebacks. 24 During the inquiry phase, the cardholder’s bank requests transaction clarification, often because the cardholder doesn’t recognize the transaction description. You can resolve the case without incurring a dispute fee by either: 25 * Providing satisfactory evidence that answers the [dispute type](https://docs.stripe.com/disputes/categories) for the inquiry 26 * Issuing a full refund. 27 Inquiries on partially refunded charges can still escalate to a chargeback. 28 #### Unwinnable chargebacks
| CORRECT | To resolve a Stripe inquiry without incurring a dispute fee, act before it escalates into a formal chargeback:
1. **Open the case in Stripe Dashboard**
Go to **Payments → Disputes** (or the relevant inquiry/pre-dispute case) and check its deadline and status.
2. **Determine whether it is only an inquiry**
An inquiry or pre-dispute alert is not always a formal chargeback. Stripe may charge a separate alert/inquiry fee depending on your account, network, and region, but it generally does not carry the same dispute fee unless it becomes a dispute.
3. **Contact the customer immediately**
Ask what resolution they want. If appropriate, issue a **full or partial refund through Stripe** and explain the transaction clearly. Do not refund through another channel unless Stripe instructs you to, since that may not close the case.
4. **Submit the resolution in Stripe**
Mark the inquiry as resolved or provide the requested documentation—such as:
- Order and fulfillment details
- Tracking and delivery confirmation
- Customer communications
- Refund confirmation
- Cancellation or subscription records
- Proof that the customer received the product or service
5. **Meet the deadline**
If you do nothing, the inquiry may automatically become a formal dispute, at which point dispute fees and the disputed amount may apply.
6. **Contact Stripe Support if the case is unclear**
Ask whether the case is an inquiry, pre-dispute alert, or formal dispute, and whether resolving it now will avoid the dispute fee. Fee treatment depends on the card network, Stripe product, country, and your contract.
If it has already become a formal dispute, you generally cannot guarantee avoidance of the dispute fee—even if you accept it or refund the customer. Stripe Support can confirm whether an exception or fee reversal is available in your specific case. It states that the inquiry can be resolved without a dispute fee by providing requested documentation or issuing a full refund, matching the source. |
| CORRECT | To resolve a Stripe **inquiry** without incurring a dispute fee, handle it before it escalates into a formal dispute:
1. **Open the case in Stripe Dashboard**
Go to **Payments → Disputes** (or the relevant inquiry/case). Check the response deadline and reason code.
2. **Review the transaction**
Confirm the payment, fulfillment status, customer details, refund history, and whether the transaction may be fraudulent.
3. **Contact the customer promptly**
Ask what went wrong and offer an appropriate resolution—such as a refund, replacement, cancellation, or explanation. Keep communication professional and save the messages.
4. **Respond through Stripe before the deadline**
Upload concise evidence, such as:
- Order confirmation and invoice
- Proof of delivery or service usage
- Tracking information
- Refund confirmation
- Customer correspondence
- Terms accepted at checkout
- IP/device or account-login information, where relevant
5. **Accept the inquiry if the claim is valid**
If the customer did not receive the product or the payment was unauthorized, issuing a refund promptly may prevent escalation. Do not refund outside Stripe unless Stripe specifically instructs you to do so.
6. **Ask the customer to withdraw the claim if resolved**
This can help, but it is not guaranteed to stop a dispute or reverse fees. You should still submit your response in Stripe.
An inquiry generally does **not** carry the same dispute fee as a formal chargeback. However, once it becomes a formal dispute, Stripe may debit the disputed amount and a dispute fee according to your country, account, and payment method. Fees are usually not avoidable after escalation, although Stripe may return the dispute fee if you successfully win the dispute in applicable regions. Check the case details and your Stripe pricing terms for the exact policy. It states that you can avoid the dispute fee by submitting relevant evidence during the inquiry or issuing a refund before escalation. |
| CORRECT | To resolve a **Stripe inquiry without a dispute fee**, act before it escalates to a formal dispute:
1. **Open the inquiry in Stripe Dashboard**
Go to **Payments → Disputes**, then select the item labeled **Inquiry** or **Dispute inquiry**.
2. **Review the claim and deadline**
Identify the dispute reason—often the customer doesn’t recognize the transaction or needs transaction details.
3. **Resolve it in one of two ways:**
- **Submit satisfactory evidence** through the Dashboard that addresses the specific claim. Include the receipt, customer communications, product/service description, delivery or usage proof, and explain the transaction clearly.
- **Issue a full refund** from the inquiry page if the claim is valid or refunding is preferable. Stripe says a full refund resolves the inquiry without a dispute fee. A partial refund may still allow the inquiry to escalate.
4. **Respond promptly**
If you leave the inquiry unanswered, it can escalate to a formal chargeback—potentially one that is difficult or impossible to win. If it remains open for 120 days without escalation, Stripe marks it closed, but you shouldn’t rely on that outcome.
If it has **already become a formal dispute**, the dispute-received fee is generally charged and is usually nonrefundable outside certain regional exceptions. You can either accept it or submit evidence to counter it; the additional countered fee is generally returned if you win.
Sources: [Stripe—How disputes work](https://docs.stripe.com/disputes/how-disputes-work), [Stripe—Dispute fees FAQ](https://support.stripe.com/questions/dispute-fees-faq) It states both source-supported ways to avoid a dispute fee during an inquiry: submit satisfactory evidence addressing the claim or issue a full refund. site:docs.stripe.com inquiries resolve without dispute fee Stripe inquiry dispute fee5 results
results as cached 2026-08-24T22:00 site:support.stripe.com Stripe inquiry dispute fee resolve inquiry5 results
results as cached 2026-08-24T22:00 opened 3 pages
|
| CORRECT | To resolve a Stripe **inquiry** without paying a dispute fee:
1. Open the payment in the **Stripe Dashboard** and locate the **inquiry/dispute inquiry**.
2. Review the inquiry reason and the cardholder’s claim.
3. Respond before the deadline by either:
- **Submitting satisfactory evidence** that addresses the inquiry reason, or
- **Issuing a full refund**.
4. If contacting the customer resolves the issue, keep records of the communication and include relevant details in your response.
An inquiry is a pre-dispute stage, so resolving it this way can prevent escalation to a formal chargeback and its associated fees. Simply accepting an inquiry does **not** resolve it—you must submit evidence or issue a full refund.
If the inquiry escalates into a formal dispute, you’ll need to submit a separate response through Stripe. Stripe says inquiries left open for 120 days without escalation are eventually closed, but you should respond promptly because some can become unwinnable chargebacks. citeturn0search0turn0search1 It states both source-supported ways to resolve the inquiry without a dispute fee: submit satisfactory evidence addressing the inquiry or issue a full refund. site:docs.stripe.com inquiry resolve without dispute fee Stripe inquiry dispute fee5 results
results as cached 2026-08-24T22:00 opened 2 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
27 Inquiries on partially refunded charges can still escalate to a chargeback.
28 #### Unwinnable chargebacks
29 Failing to respond to an inquiry can signal to the issuer your implicit acceptance of the claim, resulting in an escalation to a formal, and _likely unwinnable_, chargeback. Unless you intend to accept financial liability, always respond to inquiries immediately, making every effort to amicably resolve issues with your customer during this stage.
30 The Dashboard payment page describes inquiries as an **inquiry** or **dispute inquiry**. In the API events summary, they’re described as a **warning** or **dispute warning** to mirror the language in the API.
31 If an inquiry remains open for 120 days without escalating to a chargeback, Stripe marks it as closed in both the Dashboard and API. At this point, the card network won’t escalate it. Card networks don’t provide an explicit “win” message for inquiries.
| CORRECT | If you mean a **Stripe dispute inquiry**—an early request from a card network or issuer—ignoring it can be risky:
- Stripe may **escalate the inquiry into a formal dispute/chargeback**.
- You may lose the chance to provide evidence or resolve it before escalation.
- Stripe could **debit the disputed amount and applicable dispute fees** from your balance.
- The dispute may be decided against you by default if you miss the response deadline.
Check the inquiry’s **due date and requested documents** in the Stripe Dashboard, and respond even if you don’t yet have all the information. If you mean a different type of Stripe inquiry, such as a support or verification request, the consequences can differ—typically delays, account restrictions, or suspension rather than an automatic chargeback. It states that ignoring a Stripe dispute inquiry can escalate it into a formal chargeback, consistent with the source's warning that this likely unwinnable outcome signals implicit acceptance. |
| CORRECT | If you mean a **Stripe payment inquiry**—a pre-dispute request from a cardholder or card network—ignoring it can be costly:
- Stripe may **escalate the inquiry into a formal dispute/chargeback**.
- The payment amount may be **reversed or placed on hold**, and a dispute fee may apply.
- You lose the opportunity to provide evidence or resolve the issue before escalation.
- If it becomes a dispute, you must respond by the **new deadline shown in Stripe**; missing that deadline generally means losing automatically.
Open the inquiry in **Stripe Dashboard → Payments/Disputes** and check its exact response deadline and requested information. If it’s simply a customer-support inquiry rather than a payment inquiry, ignoring it usually doesn’t trigger an automatic chargeback, but the customer could still dispute the payment through their bank.
The precise consequences depend on the inquiry type and card network, so the notice in your Dashboard is the controlling information. It states that ignoring a Stripe payment inquiry can escalate it into a formal dispute/chargeback, consistent with the source's likely unwinnable chargeback escalation. |
| CORRECT | If you ignore an **inquiry** in Stripe, the result depends on the payment method/network:
- **Card inquiries:** The inquiry may escalate into a formal chargeback. Stripe says that failing to respond can be treated by the issuer as implicit acceptance, making the resulting chargeback likely unwinnable. You may then lose the disputed funds and potentially pay dispute fees.
- **Klarna inquiries:** The inquiry automatically escalates to a chargeback after **21 calendar days** if unresolved. You can then submit evidence, but if you miss that evidence deadline, Klarna rules in the customer’s favor.
- **Some card inquiries:** If they don’t escalate, Stripe closes them after **120 days**, and the network can no longer escalate them.
Best action: respond promptly—either provide the requested clarification/evidence, resolve the issue with the customer, or issue a full refund if appropriate. An inquiry is generally the opportunity to resolve the matter before chargeback fees and fund reversals apply. It states that ignoring an inquiry can signal implicit acceptance to the issuer and escalate to a likely unwinnable formal chargeback, matching the source. site:docs.stripe.com inquiry ignore Stripe inquiry what happens5 results
results as cached 2026-08-24T22:00 opened 2 pages
|
| CORRECT | If you mean a **Stripe dispute inquiry**—the pre-chargeback “request for information” stage—ignoring it can have serious consequences:
- It may **escalate to a formal chargeback**.
- Stripe says that failing to respond can signal that you accept the claim, making the chargeback **likely unwinnable**.
- Once escalated, the disputed amount is generally **debited from your Stripe balance**, and a dispute fee may apply.
- You’ll need to submit a **separate response with evidence** after escalation; responding to the inquiry doesn’t automatically carry over.
- If the inquiry stays open for **120 days without escalating**, Stripe closes it and the card network can no longer escalate it.
You can generally resolve an inquiry without a dispute fee by either submitting suitable transaction evidence or issuing a full refund. Note that **accepting an inquiry in the Dashboard doesn’t resolve it**—you should submit evidence or refund it instead.
If you meant a different type of Stripe inquiry, such as an account-review or support inquiry, the consequences may differ. It states that ignoring a Stripe dispute inquiry can signal acceptance of the claim and lead to a likely unwinnable formal chargeback, matching the source. site:docs.stripe.com inquiry ignore inquiry Stripe what happens5 results
results as cached 2026-08-24T22:00 opened 3 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
29 Failing to respond to an inquiry can signal to the issuer your implicit acceptance of the claim, resulting in an escalation to a formal, and _likely unwinnable_, chargeback. Unless you intend to accept financial liability, always respond to inquiries immediately, making every effort to amicably resolve issues with your customer during this stage.
30 The Dashboard payment page describes inquiries as an **inquiry** or **dispute inquiry**. In the API events summary, they’re described as a **warning** or **dispute warning** to mirror the language in the API.
31 If an inquiry remains open for 120 days without escalating to a chargeback, Stripe marks it as closed in both the Dashboard and API. At this point, the card network won’t escalate it. Card networks don’t provide an explicit “win” message for inquiries.
32 ## During the dispute
33 When an account owner files a formal dispute against a payment, whether due to an escalated inquiry or for another reason, it initiates a chargeback. During this process:
| CORRECT | If a Stripe inquiry remains open for 120 days without being escalated, it automatically closes. It does not become a chargeback, and there is generally no dispute withdrawal or chargeback fee. The payment remains settled, and the inquiry is simply closed as unresolved/no further action. It states that the inquiry automatically closes after remaining open for 120 days without escalating, matching the source's required fact. |
| CORRECT | If a Stripe inquiry remains open for 120 days and the card issuer does not escalate it to a formal chargeback, Stripe automatically closes the inquiry. It does not result in a chargeback, and no dispute amount or chargeback fee is applied.
You should still respond before the deadline if possible, since the issuer can escalate the inquiry to a chargeback during that period. It states that Stripe automatically closes the inquiry after 120 days without escalation, matching the source. |
| CORRECT | If a Stripe inquiry remains open for **120 days** without escalating to a chargeback, Stripe **automatically marks it as closed** in both the **Dashboard and API**. It states that Stripe marks the inquiry as closed in both the Dashboard and API after 120 days without escalation to a chargeback. site:docs.stripe.com inquiry 120 days chargeback Stripe inquiry stays open 120 days5 results
results as cached 2026-08-24T22:00 |
| CORRECT | If a Stripe inquiry remains open for **120 days** without escalating to a chargeback, Stripe **automatically marks it as closed** in both the **Dashboard and API**. It states that Stripe marks the inquiry as closed in both the Dashboard and API after 120 days without escalating to a chargeback. site:docs.stripe.com inquiry 120 days open chargeback Stripe inquiry stays open5 results
results as cached 2026-08-24T22:00 |
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
31 If an inquiry remains open for 120 days without escalating to a chargeback, Stripe marks it as closed in both the Dashboard and API. At this point, the card network won’t escalate it. Card networks don’t provide an explicit “win” message for inquiries.
32 ## During the dispute
33 When an account owner files a formal dispute against a payment, whether due to an escalated inquiry or for another reason, it initiates a chargeback. During this process:
34 * The card network pulls the funds for the dispute from your Stripe balance.
35 * These funds are held for the entire duration of the dispute.
| CORRECT | When a customer files a formal dispute (chargeback) against a Stripe payment:
1. **The card issuer opens the dispute.**
The customer contacts their bank/card issuer, which sends the claim through the card network to Stripe.
2. **Stripe notifies you.**
The dispute appears in the Stripe Dashboard and can also trigger webhooks such as `charge.dispute.created`.
3. **The disputed amount is removed or held.**
Stripe generally debits the disputed amount from your Stripe balance, along with a dispute fee where applicable. If your balance is insufficient, your account may show a negative balance or Stripe may debit your connected bank account, depending on your setup and region.
4. **You can accept or challenge it.**
- **Accept:** The dispute is conceded, and the customer keeps the funds.
- **Challenge:** You submit evidence—such as receipts, shipping and delivery records, customer communications, usage logs, refund policies, or proof of authorization—through the Dashboard or API.
5. **There is a deadline.**
Stripe provides a response deadline, which varies by dispute type and card network. Missing it usually results in the dispute being lost automatically.
6. **The issuer makes the decision.**
Stripe forwards your evidence to the card issuer. The issuer may:
- resolve the dispute in your favor, returning the disputed funds and sometimes the fee;
- resolve it in the customer’s favor, leaving the debit in place; or
- request further information.
The process can take weeks or months, and submitting evidence does not guarantee a reversal. You should also avoid issuing a separate refund unless appropriate, since the payment may already be reversed through the dispute process. The answer explicitly states that filing a formal dispute is a chargeback, matching the source's required fact that it initiates a chargeback. |
| CORRECT | When a customer formally disputes a Stripe payment, the dispute is handled through their card issuer or payment method—not directly by Stripe alone.
Typical sequence:
1. **The issuer opens the dispute.**
The customer claims the payment was unauthorized, duplicated, not received, incorrectly charged, or otherwise problematic.
2. **Stripe places the payment into dispute.**
Stripe generally withdraws the disputed amount from your Stripe balance and may charge a dispute fee, depending on the payment method, country, and account terms. If your balance is insufficient, your account balance may become negative or Stripe may debit your bank account.
3. **You receive a notification and evidence deadline.**
In the Stripe Dashboard and/or via webhook/email, you can see the dispute reason and the deadline for responding.
4. **You choose how to respond:**
- **Accept the dispute:** the money remains returned to the customer.
- **Challenge the dispute:** submit evidence such as receipts, delivery or tracking records, customer communications, usage logs, refund policies, or proof of authorization.
5. **The issuer makes the decision.**
Stripe forwards your evidence to the card network or payment provider. The issuer may:
- rule in your favor and return the disputed amount,
- rule in the customer’s favor, or
- request additional information in some cases.
6. **The result is reflected in Stripe.**
If you win, the disputed amount—and sometimes the dispute fee, depending on the situation—is credited back. If you lose, the reversal is final in most cases, though certain payment methods may have further appeal processes.
A dispute is different from a **refund**: a refund is initiated by the business, while a dispute is initiated by the customer through their bank or payment provider. Responding before Stripe’s deadline and providing specific, transaction-related evidence is usually important. It describes the formal dispute process initiated through the issuer, which is consistent with the source’s statement that filing one initiates a chargeback. |
| CORRECT | When a customer files a **formal dispute**—typically by contacting their card-issuing bank—it initiates a **chargeback**:
1. **The payment is reversed temporarily.**
The card network withdraws the disputed amount from Stripe, and Stripe debits your Stripe balance for that amount **plus a dispute fee**. The money is held while the case is reviewed.
2. **Stripe notifies you.**
You’ll see the dispute in the Dashboard and may receive notifications by email, webhook, or API. Stripe provides the dispute reason and the customer’s claim.
3. **You must choose how to respond.**
- **Accept the dispute**, meaning you don’t contest it; or
- **Counter it** by submitting evidence—such as delivery confirmation, customer communications, refund policies, usage records, or proof of authorization—before the deadline, usually **7–21 days** depending on the network.
You generally can’t issue a separate refund while the dispute is open.
4. **The card issuer decides.**
Stripe facilitates the process but does not make the final decision. Review commonly takes **60–75 days**, and the full lifecycle can take around **2–3 months**.
5. **The outcome is applied.**
- If you **win**, the disputed funds are returned to your Stripe balance; applicable counter-dispute fees may also be returned.
- If you **lose**, the chargeback remains and the customer may receive the funds from their bank. The initial dispute fee is generally nonrefundable.
A formal dispute also increases your dispute rate with the relevant card network. The exact rules differ for non-card payment methods such as PayPal or Klarna. It states that filing a formal dispute initiates a chargeback, matching the source. site:docs.stripe.com disputes what happens customer files formal dispute Stripe payment5 results
results as cached 2026-08-24T22:00 opened 1 page
|
| CORRECT | When a customer files a **formal dispute** against a Stripe payment, it generally becomes a **chargeback**:
1. **Stripe notifies you** through the Dashboard, email, webhooks, and API. The notification includes the dispute reason and the customer’s claim.
2. **The disputed funds are withdrawn** from your Stripe balance, along with Stripe’s dispute fee. The funds remain held while the case is reviewed.
3. **You can’t issue a normal refund** for that payment while the dispute is open.
4. **You choose whether to accept or challenge it:**
- **Accept:** You concede the dispute and the chargeback remains.
- **Challenge:** Submit evidence—such as receipts, delivery or usage records, customer communications, refund policies, or authentication data—through the Dashboard or API before the deadline.
5. **The cardholder’s bank makes the decision.** Stripe facilitates the process but does not control the outcome. The response window is commonly **7–21 days**, and the full process can take **2–3 months**.
6. **If you win,** the disputed amount is returned to your Stripe balance. **If you lose,** the chargeback remains and the customer may receive the funds from their bank.
The decision is generally final, and Stripe doesn’t support escalating the case to arbitration through its platform. Local payment methods such as Klarna or PayPal can follow different dispute rules. It states that filing a formal dispute initiates or becomes a chargeback, matching the source. site:docs.stripe.com disputes what happens when customer disputes payment Stripe formal dispute process5 results
results as cached 2026-08-24T22:00 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
43 * Your [dispute rate](https://docs.stripe.com/disputes/measuring) with that card network increases.
44 ### Dispute timing
45 Card networks typically allow cardholders to initiate disputes within 120 days of the original payment, but their rules allow more time in some situations. Certain industries, such as travel or event ticketing, are prone to longer intervals between the original purchase and a dispute. Generally, when a customer pays for a future event or service (like a vacation reservation, professional services appointment, or event ticket), the dispute window starts on the event date, not the payment date.
46 After a chargeback is created, you have a limited time to respond to the card issuer: usually 7-21 days, depending on the card network.
47 If you submit evidence, the issuer has a limited time to evaluate it and decide the outcome: usually 60-75 days, depending on the card network.
| CORRECT | For most Stripe card payments, a cardholder can usually file a dispute within **120 days of the transaction or statement date**.
The exact window depends on the **card network, dispute reason, and circumstances**. For example, disputes involving delayed delivery, recurring payments, or services not received may be allowed for longer—sometimes **up to 365 days or more** under certain network rules.
Stripe does not set the cardholder’s filing deadline; the issuing bank and card network do. If a dispute is filed, Stripe will show the merchant’s response deadline in the Dashboard, which is typically much shorter. It states that cardholders can usually file a dispute within 120 days, matching the source's typical timeframe. |
| CORRECT | A cardholder can **usually file a card-payment dispute within 120 days** of the transaction date—or from the expected delivery/service date, depending on the dispute reason.
The exact deadline is set by the **card network and issuing bank**, not Stripe. Some cases—such as certain fraud, recurring-payment, or delayed-delivery claims—may allow longer periods, occasionally up to **several hundred days**.
Once Stripe notifies you of a dispute, the time to respond is separate and is typically only **about 7–21 days**, as shown in your Stripe Dashboard. It states that cardholders can usually file a dispute within 120 days, matching the source, while noting that some circumstances may allow longer periods. |
| CORRECT | For a typical **Stripe card payment**, the cardholder can usually file a dispute within **120 days of the original payment**.
Exceptions may extend the window—for example:
- For future services, travel, or event tickets, the period may begin on the **service/event date**, not the payment date.
- Certain card-network rules or dispute reasons may allow more time.
- Stripe says local payment methods often allow up to **180 days**, but their rules differ from card payments.
Once a dispute is filed, Stripe typically gives the merchant **7–21 days** to respond. It states that a cardholder can usually file a dispute within 120 days of the original payment, matching the source. site:docs.stripe.com disputes how long cardholder file dispute 120 days Stripe5 results
results as cached 2026-08-24T22:00 opened 1 page
|
| CORRECT | A cardholder can **usually file a Stripe card-payment dispute within 120 days of the original payment**.
However, the deadline can be longer depending on:
- **Card-network rules and dispute reason**
- **When the cardholder discovered the issue**
- **Future-delivery transactions**—such as travel, event tickets, or services booked in advance—where the 120-day window may begin on the **event or service date**, rather than the payment date
Stripe notes that the exact timeframe varies, so a dispute may occasionally arrive several months after the payment. It states that cardholders can usually file a dispute within 120 days of the original payment, matching the source. site:docs.stripe.com disputes cardholder file dispute 120 days Stripe5 results
results as cached 2026-08-24T22:00 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
43 * Your [dispute rate](https://docs.stripe.com/disputes/measuring) with that card network increases.
44 ### Dispute timing
45 Card networks typically allow cardholders to initiate disputes within 120 days of the original payment, but their rules allow more time in some situations. Certain industries, such as travel or event ticketing, are prone to longer intervals between the original purchase and a dispute. Generally, when a customer pays for a future event or service (like a vacation reservation, professional services appointment, or event ticket), the dispute window starts on the event date, not the payment date.
46 After a chargeback is created, you have a limited time to respond to the card issuer: usually 7-21 days, depending on the card network.
47 If you submit evidence, the issuer has a limited time to evaluate it and decide the outcome: usually 60-75 days, depending on the card network.
| CORRECT | For a future event or service, the dispute period generally starts on the **expected delivery or service date**—for example, the event date—not necessarily the date the customer paid.
Typically, card networks allow about **120 days from that expected date** to file a “services not received” dispute, subject to network rules and an overall limit (often up to **540 days from the original transaction**). Other dispute types, such as fraud or unauthorized payment, may use different timing rules and can be filed earlier.
Stripe will show the applicable deadline and your response deadline in the Dashboard once a dispute is opened. It states that the dispute period generally starts on the expected service or event date rather than the payment date, matching the source. |
| WRONG | For a Stripe payment, the dispute window generally does **not automatically begin on the date of the future event or service**.
- **Once the payment is captured**, the card network’s dispute time limits generally run from the transaction/processing date.
- For disputes alleging **“goods or services not received,”** the card network may calculate the deadline from the date the service was expected to be provided or the event was scheduled to occur, subject to network-specific limits.
- Other disputes—such as **fraud, duplicate processing, or unauthorized payment**—may be filed before the event, based on their own card-network deadlines.
- Stripe’s deadline for you to respond after a dispute is opened is a separate, usually much shorter period shown in the Stripe Dashboard.
The exact period depends on the card network, dispute reason, cardholder’s country, and transaction type. Stripe does not establish one universal dispute window. Keep evidence showing the scheduled date, cancellation/refund terms, and the customer’s agreement to them. The answer states that the dispute window generally runs from the payment date rather than the future event date, directly conflicting with the source. |
| CORRECT | For a future event or service paid through Stripe, the dispute window generally starts on the **date the event or service was scheduled to occur—not the date of payment**.
Card networks typically allow disputes within **120 days**, though exceptions and longer periods may apply depending on the network, dispute reason, industry, and payment method. Stripe’s rules for local payment methods can differ. It states that the dispute window generally starts on the scheduled event or service date rather than the payment date, matching the source. site:stripe.com dispute window future event service date dispute starts Stripe5 results
results as cached 2026-08-24T22:00 Stripe future event service dispute window starts date service provided5 results
results as cached 2026-08-24T22:00 Stripe chargeback future delivery dispute time limit event date5 results
results as cached 2026-08-24T22:00 opened 1 page
|
| CORRECT | For a **future event or service paid through Stripe**, the dispute window generally starts on the **date the event or service is scheduled to occur**, rather than on the payment date.
For example, if a customer pays in January for an event in June, the applicable dispute period generally begins in June. Card networks commonly allow disputes within **120 days**, but exceptions and longer periods may apply depending on the card network, dispute reason, industry, and local rules.
For non-card payment methods such as Klarna or PayPal, separate rules apply. It states that the dispute window generally starts on the scheduled event or service date rather than the payment date, matching the source. site:docs.stripe.com disputes future event service dispute window starts expected delivery date5 results
results as cached 2026-08-24T22:00 site:stripe.com dispute future event service paid dispute window expected delivery date5 results
results as cached 2026-08-24T22:00 Stripe dispute time limits future-dated transaction service not received5 results
results as cached 2026-08-24T22:00 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
44 ### Dispute timing
45 Card networks typically allow cardholders to initiate disputes within 120 days of the original payment, but their rules allow more time in some situations. Certain industries, such as travel or event ticketing, are prone to longer intervals between the original purchase and a dispute. Generally, when a customer pays for a future event or service (like a vacation reservation, professional services appointment, or event ticket), the dispute window starts on the event date, not the payment date.
46 After a chargeback is created, you have a limited time to respond to the card issuer: usually 7-21 days, depending on the card network.
47 If you submit evidence, the issuer has a limited time to evaluate it and decide the outcome: usually 60-75 days, depending on the card network.
48 The full dispute lifecycle, from initiation to the final decision, can take 2-3 months to complete. You can’t reliably accelerate this timeline, except by accepting the dispute in the Dashboard or API.
| CORRECT | You usually have **about 7–21 calendar days** to respond to a Stripe chargeback, but the exact deadline varies by card network, payment method, country, and dispute type.
The **“Respond by” date in your Stripe Dashboard** is the authoritative deadline. Submit evidence before that date—if you miss it, Stripe will generally accept the dispute automatically, and the funds may not be recoverable. It states about 7–21 days, matching the source, and notes that the exact deadline depends on the card network. |
| CORRECT | Usually, Stripe gives you **about 7–21 calendar days** to respond to a chargeback, but the exact deadline depends on the card network, payment method, and dispute type.
Check the **“Respond by” date in your Stripe Dashboard**—that is the authoritative deadline. Stripe generally can’t extend it, and missing it usually means accepting the dispute by default. Submit evidence as early as possible in case Stripe needs time to process it. It states about 7–21 days and correctly says the exact deadline depends on the card network. |
| CORRECT | You **usually have 7–21 days** to respond to a Stripe chargeback, depending on the card network and dispute type. The **exact deadline is shown in your Stripe Dashboard and dispute notification**—use that date as authoritative.
If you miss the deadline, Stripe generally submits no evidence and the dispute is likely resolved in the cardholder’s favor. Submit your evidence as early as possible rather than waiting until the final day. The answer states the usual response window is 7–21 days, depending on the card network, matching the source. site:docs.stripe.com disputes response deadline chargeback how long respond Stripe5 results
results as cached 2026-08-24T22:00 |
| CORRECT | Usually **7–21 calendar days**, depending on the card network and dispute type. Stripe shows the exact deadline in the **Dispute details** page and in its notification email.
Submit your evidence before that displayed deadline—if you miss it, the dispute is typically accepted automatically and the funds may not be recoverable. It states the required usual response window of 7–21 days, depending on the card network. site:docs.stripe.com disputes response deadline how long respond chargeback Stripe5 results
results as cached 2026-08-24T22:00 |
Right either way — the model knows this, and checking confirms it. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
45 Card networks typically allow cardholders to initiate disputes within 120 days of the original payment, but their rules allow more time in some situations. Certain industries, such as travel or event ticketing, are prone to longer intervals between the original purchase and a dispute. Generally, when a customer pays for a future event or service (like a vacation reservation, professional services appointment, or event ticket), the dispute window starts on the event date, not the payment date.
46 After a chargeback is created, you have a limited time to respond to the card issuer: usually 7-21 days, depending on the card network.
47 If you submit evidence, the issuer has a limited time to evaluate it and decide the outcome: usually 60-75 days, depending on the card network.
48 The full dispute lifecycle, from initiation to the final decision, can take 2-3 months to complete. You can’t reliably accelerate this timeline, except by accepting the dispute in the Dashboard or API.
49 At the end of the dispute process, the issuer either:
| CORRECT | After you submit evidence, the card issuer typically takes **about 60–75 days** to make a decision. Some disputes are resolved sooner, but others can take **up to 2–3 months or longer**, depending on the card network and dispute type.
Stripe generally can’t speed up the issuer’s review. The Stripe Dashboard should show the dispute’s current status and, when available, an estimated decision date. During this period, the disputed funds typically remain held until the case is resolved. It states that the issuer typically takes about 60–75 days, matching the source. |
| WRONG | Usually, the card issuer takes **about 60–90 days** to decide after you submit evidence. Some disputes are resolved in a few weeks, while complex cases can take longer depending on the card network, issuer, and dispute type.
Stripe generally passes your evidence to the network/issuer and doesn’t control the decision timeline. You can monitor the dispute’s status in the Stripe Dashboard; the final result will appear there once Stripe receives it. It states about 60–90 days, which conflicts with the source's usual 60–75 days. |
| CORRECT | After you submit evidence, the card issuer usually takes **about 60–75 days** to review it and decide the outcome, depending on the card network. Stripe typically updates the dispute status when the issuer responds, though the exact timing can vary. It states that the issuer usually takes about 60–75 days, depending on the card network, matching the source. site:docs.stripe.com disputes evidence issuer decision how long after submit evidence5 results
results as cached 2026-08-24T22:00 |
| CORRECT | Usually **about 60–75 days** after you submit evidence, depending on the card network and issuer. In some cases, the review can take **up to roughly 3 months**.
Stripe generally updates the dispute status when the issuer/cardholder’s bank reaches a decision. The exact timeline may vary by dispute type and network. It states the usual decision time is about 60–75 days after evidence submission, matching the source. site:docs.stripe.com disputes how long decision after submit evidence issuer5 results
results as cached 2026-08-24T22:00 |
Right either way — the model knows this, and checking confirms it. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
46 After a chargeback is created, you have a limited time to respond to the card issuer: usually 7-21 days, depending on the card network.
47 If you submit evidence, the issuer has a limited time to evaluate it and decide the outcome: usually 60-75 days, depending on the card network.
48 The full dispute lifecycle, from initiation to the final decision, can take 2-3 months to complete. You can’t reliably accelerate this timeline, except by accepting the dispute in the Dashboard or API.
49 At the end of the dispute process, the issuer either:
50 * Overturns the dispute in your favor:
| CORRECT | For a typical **Stripe card dispute**, the full process usually takes **about 2–3 months** from the customer’s dispute to a final decision.
Typical stages:
- **Dispute opened:** You’re notified immediately, and Stripe places the disputed amount and fee on hold/debits it.
- **Your response window:** Usually **7–21 days**, depending on the card network and dispute type. The exact deadline appears in the Stripe Dashboard.
- **Issuer review:** After you submit evidence, the cardholder’s bank commonly takes **several weeks to a few months** to decide.
- **Escalation/arbitration:** If the dispute proceeds to pre-arbitration or network arbitration, it can take **several additional months**, and complex cases may take **6 months or longer**.
The Stripe Dashboard’s deadline is the important date for your action; Stripe generally can’t shorten the card issuer’s review period. It states that the full Stripe dispute process takes about 2–3 months from dispute initiation to final decision, matching the source. |
| WRONG | A full Stripe card-dispute process usually takes **2–3 months after the dispute is opened**, but the total timeline can be longer:
- **Customer files the dispute:** Often up to **120 days after the transaction**—and sometimes longer depending on the card network and dispute reason.
- **Merchant response:** Stripe provides a deadline, commonly **7–21 days**, to submit evidence.
- **Issuer review:** The cardholder’s bank reviews the evidence and commonly takes **several weeks to about 75 days**.
- **Further appeals/arbitration:** If the case proceeds to pre-arbitration or network arbitration, it may take **several additional months**, occasionally **6–12 months** in unusual cases.
If the merchant doesn’t respond by Stripe’s deadline, the dispute is generally lost automatically. The most accurate date is the **“ respond by” deadline and current status shown in the Stripe Dashboard**. Although it states 2–3 months after opening, it also says the full process can take several additional months or 6–12 months, conflicting with the source’s 2–3 month full lifecycle. |
| CORRECT | Stripe says the **full dispute lifecycle typically takes about 2–3 months** from initiation to the final decision.
Typical timing:
- **Your response window:** usually **7–21 days** after the dispute is opened, depending on the card network.
- **Issuer review:** generally **60–75 days** after you submit evidence.
- **Final decision:** Stripe updates the dispute as won or lost once the issuer decides.
The overall timeline can be longer if the cardholder’s dispute is filed months after the original transaction—typically within **120 days**, though certain transaction types or circumstances allow more time. You can end the process sooner by accepting the dispute, but Stripe generally can’t accelerate an issuer’s review. It states that the full dispute lifecycle takes about 2–3 months from initiation to final decision, matching the source. site:docs.stripe.com disputes process how long dispute process takes Stripe5 results
results as cached 2026-08-24T22:00 opened 1 page
|
| CORRECT | Stripe says the **full dispute lifecycle usually takes about 2–3 months**, from the dispute being initiated to the card issuer’s final decision. Issuers commonly take **60–75 days** to review submitted evidence.
Typical stages:
- **Customer files the dispute:** Often up to **120 days** after the transaction for card payments, though network and payment-method rules vary.
- **Merchant responds:** Stripe gives you a **network-specific deadline**, commonly **7–21 days**. Missing it generally means accepting the dispute.
- **Issuer reviews the case:** Usually around **60–75 days**, but timing varies.
- **Final outcome:** The disputed amount and fee are either returned to you or permanently charged back.
So, if you mean from the moment the dispute is opened, plan for **roughly 2–3 months**. The overall period from the original payment—including the time before a customer files—can be considerably longer. It states that the full dispute lifecycle takes roughly 2–3 months from initiation to final decision, matching the source. site:docs.stripe.com disputes timeline full dispute process 120 days 20251 result
results as cached 2026-08-24T22:00 Stripe dispute process how long chargeback timeline evidence response 20265 results
results as cached 2026-08-24T22:00 Stripe docs dispute lifecycle timeframes card dispute evidence 120 days5 results
results as cached 2026-08-24T22:00 Stripe chargeback dispute can take how long final decision5 results
results as cached 2026-08-24T22:00 |
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
48 The full dispute lifecycle, from initiation to the final decision, can take 2-3 months to complete. You can’t reliably accelerate this timeline, except by accepting the dispute in the Dashboard or API. 49 At the end of the dispute process, the issuer either: 50 * Overturns the dispute in your favor: 51 * The issuer returns the debited chargeback amount to Stripe. 52 * Stripe passes this amount back to you. 53 * Upholds the dispute in their cardholder’s favor: 54 * No money moves from your perspective.
| CORRECT | If the card issuer rules a Stripe dispute **in your favor**, the dispute is closed as **won**.
- **If you’re the customer/cardholder:** the disputed amount is credited back to your card, usually after the issuer finalizes the decision. It may take a few business days to appear.
- **If you’re the merchant/business:** Stripe returns the disputed transaction amount to your Stripe balance and generally reverses the dispute fee. The funds may be available after Stripe receives the issuer’s final decision.
The exact timing depends on the card network and bank. You can check the dispute’s status in your Stripe Dashboard for the final outcome and balance adjustment. For the merchant context implied by the source, it states that Stripe returns the disputed amount to the merchant after the issuer's favorable decision, matching the source's substance. |
| CORRECT | If you’re the **merchant**, and the card issuer rules the Stripe dispute in your favor:
- The dispute is marked **won/closed** in Stripe.
- The disputed payment amount is returned to your Stripe balance.
- The dispute fee is generally returned as well.
- The customer’s temporary or permanent chargeback is reversed.
- You usually don’t need to take further action, though Stripe may notify you when the funds are restored.
It can take a few business days for the result and balance adjustment to appear. In rare cases, the cardholder or issuer may initiate a further escalation, such as arbitration.
If you meant that you’re the **cardholder/customer**, a favorable decision generally means the chargeback stands and the disputed amount remains refunded or credited to your card. It states that the disputed payment amount is returned to the merchant’s Stripe balance, matching that Stripe receives the chargeback amount from the issuer and passes it back to you. |
| CORRECT | If you’re the **merchant**, and the card issuer rules the Stripe dispute in your favor:
- The issuer returns the disputed chargeback amount to Stripe.
- Stripe credits that amount back to your Stripe balance.
- The dispute status changes to **Won**.
- Stripe generally returns the **dispute countered fee** (the fee for submitting evidence).
- The original **dispute received fee** is generally not returned, unless your Stripe agreement says otherwise.
- If the dispute was only partially won, you receive only the amount successfully recovered.
The credit may appear after the issuer’s decision is processed rather than immediately. You can monitor the outcome in the Stripe Dashboard or through the dispute object’s status. [Stripe’s dispute documentation](https://docs.stripe.com/disputes/how-disputes-work) has the relevant details. It states that the issuer returns the disputed chargeback amount to Stripe and Stripe credits/passes that amount back to the merchant. site:docs.stripe.com disputes won issuer decides in your favor dispute fee returned5 results
results as cached 2026-08-24T22:00 Stripe dispute issuer decides in your favor what happens funds dispute fee5 results
results as cached 2026-08-24T22:00 |
| CORRECT | If the card issuer decides the Stripe dispute in your favor:
- The issuer reverses the chargeback and returns the disputed amount to Stripe.
- Stripe credits the disputed amount back to your Stripe balance.
- Stripe generally also returns the dispute-countered fee.
- The dispute’s status changes to **won**.
- You can refund the original payment again, if needed, once the win is processed.
The credit may take some time to appear because it follows the normal dispute-processing timeline. You can see the returned funds and fee in your Stripe balance history. It states that the issuer returns the disputed chargeback amount to Stripe and that Stripe credits it back to you, matching the source. site:docs.stripe.com disputes issuer decides in your favor Stripe what happens dispute won funds returned5 results
results as cached 2026-08-24T22:00 site:support.stripe.com dispute won fee returned Stripe issuer5 results
results as cached 2026-08-24T22:00 |
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
56 * The issuer will return the funds to the cardholder at their discretion, during or after this process.
57 ### Dispute fees
58 The dispute fees for your country can be found on the Stripe [Pricing page](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details). The fee for receiving a dispute is deducted from your account balance when a cardholder initiates a dispute. Dispute fees vary based on your business location:
59 * For businesses outside Mexico, the fee for receiving a dispute is non-refundable.
60 * For businesses in Mexico, the fee for receiving a dispute might be returned if you win or the cardholder withdraws.
| CORRECT | Stripe generally charges the dispute fee **when the dispute is created/received**, not when you submit evidence or when the dispute is resolved. It typically debits your Stripe balance along with the disputed payment amount.
If you successfully challenge the dispute, Stripe generally refunds the dispute fee; the exact policy and amount depend on your country, payment method, and Stripe pricing terms. It states that Stripe charges the fee when the dispute is created or received, which matches the source's timing of when the cardholder initiates the dispute. |
| CORRECT | Stripe charges the dispute fee when the dispute is **received and opened**, not when the dispute is resolved. It is typically deducted from your Stripe balance along with the disputed transaction amount.
If you successfully challenge the dispute, Stripe generally returns the dispute fee—but fees and refund rules can vary by country, payment method, and Stripe pricing plan. An **inquiry or pre-dispute** may not incur the same fee. It states that Stripe charges the fee when the dispute is received and opened, which matches the source's timing of when the cardholder initiates the dispute. |
| CORRECT | Stripe charges the **dispute received fee immediately when the cardholder initiates a formal dispute**. It deducts the fee—along with the disputed amount—from your Stripe balance at that point.
An inquiry or pre-dispute warning generally doesn’t incur this fee unless it escalates into a formal dispute. The received fee is usually nonrefundable, even if you successfully challenge and win the dispute, though regional or contractual exceptions may apply. It states that the fee is deducted from the Stripe balance when the cardholder initiates the dispute, matching the source. site:docs.stripe.com dispute fee charged when dispute received Stripe5 results
results as cached 2026-08-24T22:00 opened 1 page
|
| CORRECT | Stripe charges the **dispute received fee immediately when the cardholder initiates the dispute**. Stripe deducts it from your Stripe balance along with the disputed payment amount.
The fee is generally **nonrefundable**, even if you successfully counter the dispute, unless your Stripe agreement says otherwise. It states that Stripe deducts the dispute fee from the balance when the cardholder initiates the dispute, matching the source. site:stripe.com dispute fee charged when receiving dispute Stripe5 results
results as cached 2026-08-24T22:00 |
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
61 * Businesses in the Single Euro Payments Area (SEPA) incur no fee for receiving a dispute on a card payment processed on the [Cartes Bancaires network](https://docs.stripe.com/payments/cartes-bancaires).
62 If you counter a dispute, a [dispute countered fee](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes#fee-details) applies, in addition to the dispute received fee. The cardholder’s bank reviews it and decides the dispute outcome. This can take up to 3 months. When Stripe receives the decision, you receive an email from us.
63 Stripe returns the dispute countered fee if you win the dispute. Unless otherwise stated in your Stripe contract, we never return the dispute received fee.
64 #### Regional considerations
65 Mexico
| CORRECT | If you **win the dispute**, Stripe generally **refunds the dispute fee**—credited back to your Stripe balance—along with releasing the disputed payment amount.
A few notes:
- The fee is usually returned only after the card network officially rules in your favor.
- “Countered” means you submitted evidence; it does **not** yet mean you won.
- If you lose, the dispute fee is typically retained.
- Exact treatment can vary by country, payment method, and Stripe account terms. Check the dispute’s balance transaction in the Dashboard for the credit. It states that Stripe refunds the dispute fee when you win, matching the source's statement that the dispute countered fee is returned. |
| CORRECT | If you win a Stripe dispute, Stripe generally refunds the dispute fee along with the disputed amount. The refund usually appears as a separate balance transaction after the card network closes the dispute—often shortly after the status changes to **won**.
If you lose or accept the dispute, the fee is not refunded. Exact fee-refund rules can vary by country, payment method, or Stripe agreement, so check the dispute’s balance transactions in the Dashboard. It states that Stripe refunds the dispute fee when you win, matching the source’s statement that the dispute countered fee is returned upon winning. |
| CORRECT | If you **win the dispute**, Stripe returns the **dispute countered fee** to you. The refund typically appears in your Stripe balance/history along with the recovered disputed amount.
However, Stripe generally **does not return the original dispute received fee**, unless your Stripe contract or region-specific terms say otherwise. It correctly states that Stripe returns the dispute countered fee if you win the dispute. site:stripe.com dispute countered fee if win Stripe dispute fee refunded5 results
results as cached 2026-08-24T22:00 |
| CORRECT | If you win the dispute, Stripe returns the **dispute countered fee** to you. The refund typically appears as a balance adjustment alongside the recovered disputed amount.
However, Stripe generally **does not return the original dispute received fee**, unless your Stripe contract or regional terms say otherwise. It correctly states that Stripe returns the dispute countered fee if you win the dispute. site:stripe.com dispute countered fee if win dispute fee refunded Stripe5 results
results as cached 2026-08-24T22:00 |
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
67 The dispute countered fee doesn’t apply to businesses in Mexico and Japan.
68 ### Respond to a dispute
69 In most cases, you have the ability to challenge a disputed payment, as long as you submit strong evidence to the card issuer that invalidates the dispute claim before the deadline.
70 As soon as a dispute is active, the only way to overturn it’s by _submitting evidence in a response_. Even in cases where your customer claims to have [withdrawn the dispute](https://docs.stripe.com/disputes/withdrawing), you must respond with evidence for the dispute to be closed in your favor. Submitting evidence is what signals to the issuer that you don’t accept the dispute and want to have the funds returned to you.
71 See [Respond to disputes](https://docs.stripe.com/disputes/responding) for information on how to:
| CORRECT | If you’re a **business using Stripe** and a customer has disputed a payment:
1. **Open Stripe Dashboard** and go to **Payments → Disputes** (or **Payments → Disputes and inquiries**).
2. Select the disputed payment to view:
- Dispute reason and amount
- Response deadline
- Evidence requested by the card network
3. Review the dispute reason carefully—for example, fraud, duplicate payment, product not received, or credit not processed.
4. Choose **Submit evidence** or **Respond to dispute**.
5. Upload relevant documentation, such as:
- Customer communications
- Order confirmation and invoice
- Shipping and delivery tracking
- Proof of service usage or login activity
- Refund or cancellation policy
- Evidence that a refund was already issued
6. Add a concise explanation connecting the evidence to the dispute reason.
7. Submit the response before the deadline shown in Stripe.
Stripe forwards the evidence to the card issuer. After submission, you generally can’t add more evidence, and the issuer—not Stripe—makes the final decision. Stripe may also debit the disputed amount and a dispute fee while the case is being reviewed.
If you’re the **customer/cardholder** disputing a payment, contact your bank or card issuer directly. Stripe usually cannot initiate a chargeback on your behalf. If the charge is shown in a Stripe-hosted receipt or customer portal, you can also contact the merchant first to request a refund or resolution. It explains that a business can challenge a dispute by submitting relevant evidence to the card issuer through Stripe before the response deadline, matching the source's core requirement. |
| CORRECT | If you’re a **business using Stripe** and a customer has disputed a payment:
1. **Open the dispute**
- In Stripe Dashboard, go to **Payments → Disputes**.
- Select the disputed payment to view the reason, deadline, amount, and required information.
2. **Review the dispute reason**
Common reasons include fraud, product not received, duplicate payment, or product/service not as described. Tailor your evidence to that reason.
3. **Submit evidence**
Depending on the case, provide:
- Customer communications
- Order confirmation and invoice
- Shipping or delivery tracking
- Proof of service usage or login activity
- Refund or cancellation-policy disclosures
- Terms accepted at checkout
- Evidence that the payment method was verified
- A clear written explanation addressing the dispute
4. **Submit before the deadline**
Click **Submit evidence** in the Dashboard. You can also respond through Stripe’s API using the dispute object’s evidence fields. After submission, the card issuer—not Stripe—makes the final decision.
5. **Monitor the outcome**
Check the dispute status in the Dashboard. Stripe may temporarily debit the disputed amount and charge a dispute fee. If you win, the funds are generally returned; if you lose, the debit remains.
If you’re the **customer/cardholder**, you generally don’t challenge a payment directly through Stripe. Contact the merchant first; if it isn’t resolved, dispute the charge with your bank or card issuer. It states that a business can challenge the disputed payment by submitting supporting evidence to the card issuer before the deadline, matching the source. |
| CORRECT | If you’re the **business/merchant**, you can challenge a disputed Stripe payment by submitting evidence to the cardholder’s bank:
1. **Open the Stripe Dashboard** and go to **Disputes**: https://dashboard.stripe.com/disputes
2. Select the disputed payment and review:
- The dispute reason/category
- The cardholder’s claim and any attached documents
- The response deadline—usually **7–21 days**
3. Decide whether to **Accept dispute** or **Counter dispute**. Choose **Counter dispute** to challenge it.
4. Provide a clear explanation addressing the specific claim.
5. Upload relevant evidence, such as:
- Order confirmations, invoices, and receipts
- Shipping/tracking and delivery confirmation
- Customer communications
- Terms, cancellation, refund, or return policies
- Proof the service was provided or the customer used the product
- Login, usage, IP, or 3D Secure information where relevant
6. Submit the response before the deadline.
Important: Stripe generally gives you **one final opportunity to submit evidence**, so assemble everything first. You can’t normally edit the response or add files afterward. The issuer—not Stripe—makes the decision, which commonly takes **about 2–3 months**. A successful challenge changes the dispute status to **won** and returns the disputed amount; a loss makes the chargeback permanent. Fees may apply.
Source: [Stripe’s dispute response guide](https://docs.stripe.com/disputes/responding)
If you’re the **customer/cardholder** disputing a purchase made through Stripe, Stripe doesn’t decide the dispute. Contact the merchant first; if unresolved, dispute the charge through your bank or card issuer. It states that a merchant can challenge the dispute by submitting evidence to the card issuer before the deadline, matching the source. site:docs.stripe.com dispute challenge disputed payment Stripe submit evidence5 results
results as cached 2026-08-24T22:01 site:support.stripe.com dispute card payment cardholder Stripe5 results
results as cached 2026-08-24T22:01 opened 3 pages
|
| CORRECT | If you’re the **business/merchant**, you can challenge a Stripe dispute (chargeback) in the Stripe Dashboard:
1. **Open Stripe Dashboard → Disputes** and select the disputed payment.
2. Review the **dispute reason**, deadline, and any documents from the cardholder’s bank.
3. Choose **Counter dispute**—not “Accept dispute.”
4. Provide a concise explanation addressing the specific claim.
5. Upload relevant evidence, such as:
- Order confirmation and invoice
- Customer communications
- Proof of delivery or service usage
- Refund/cancellation policy shown at checkout
- Terms accepted by the customer
- AVS/CVC or 3D Secure results, where applicable
6. Submit before the deadline—usually **7–21 days**, depending on the card network.
Important: Stripe generally allows only **one final evidence submission**. You can’t edit it or add files afterward, so organize all evidence before submitting. The issuing bank—not Stripe—makes the final decision, which can take up to about three months.
You can also respond through Stripe’s API if you manage disputes programmatically. See Stripe’s [Respond to disputes guide](https://docs.stripe.com/disputes/responding).
If you’re the **customer/cardholder** trying to dispute a payment, Stripe isn’t normally the party that decides it. First contact the merchant for a refund or resolution; if that doesn’t work, dispute the charge through your card issuer or bank. See Stripe’s guide on [disputing a purchase](https://support.stripe.com/questions/disputing-a-purchase-made-through-stripe). It states that a merchant can challenge a dispute by submitting evidence before the deadline, matching the source's required substance. site:docs.stripe.com disputes respond to dispute Stripe Dashboard evidence5 results
results as cached 2026-08-24T22:01 site:support.stripe.com dispute a charge customer Stripe cardholder5 results
results as cached 2026-08-24T22:01 opened 3 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
68 ### Respond to a dispute
69 In most cases, you have the ability to challenge a disputed payment, as long as you submit strong evidence to the card issuer that invalidates the dispute claim before the deadline.
70 As soon as a dispute is active, the only way to overturn it’s by _submitting evidence in a response_. Even in cases where your customer claims to have [withdrawn the dispute](https://docs.stripe.com/disputes/withdrawing), you must respond with evidence for the dispute to be closed in your favor. Submitting evidence is what signals to the issuer that you don’t accept the dispute and want to have the funds returned to you.
71 See [Respond to disputes](https://docs.stripe.com/disputes/responding) for information on how to:
72 * Review the cardholder’s claim.
| CORRECT | To challenge an active Stripe dispute, you must submit a response through Stripe before the dispute’s evidence deadline. The card issuer—not Stripe—makes the final decision.
### Steps in Stripe
1. **Open the dispute**
- Go to **Stripe Dashboard → Payments → Disputes**.
- Select the disputed payment and review the **reason code**, amount, deadline, and dispute status.
2. **Determine whether to accept or challenge it**
- If the customer’s claim is valid, accepting the dispute may be preferable.
- If you believe it is incorrect, choose **Submit evidence** or **Challenge dispute**.
3. **Provide targeted evidence**
Include only evidence relevant to the dispute reason. Useful documentation can include:
- **Proof of delivery:** carrier, tracking number, delivery date, recipient address, delivery confirmation
- **Proof the service was provided:** timestamps, usage logs, appointment records, access logs
- **Customer communications:** emails, messages, cancellation/refund discussions
- **Refund and cancellation policy:** show it was clearly presented and accepted before purchase
- **Transaction details:** invoice, receipt, order information, product description
- **Evidence of authorization:** AVS/CVC results, 3D Secure authentication, device/IP data—especially for fraud disputes
- **Terms accepted by the customer:** checkout screenshots or records showing what the customer agreed to
4. **Write a clear rebuttal**
Explain:
- What the customer claims
- Why that claim is inaccurate
- Which attached evidence proves your position
- Relevant dates, tracking numbers, and amounts
5. **Submit before the deadline**
Stripe generally allows only one formal evidence submission, so make it complete. Do not wait until the deadline, since the deadline is controlled by the card network and may be shown in a different time zone.
### Practical tips
- Match your evidence to the **specific dispute reason code**—for example, “product not received” requires delivery proof, while “credit not processed” requires refund records.
- Contact the customer and ask them to withdraw the dispute if appropriate, but **do not rely on this alone**. The customer usually must contact their card issuer, and you should still submit evidence before the deadline.
- Don’t issue a separate refund unless you understand the consequences; a refund after a dispute is opened may not automatically cancel the dispute and could result in losing both the payment and the refund.
- Keep all records and avoid submitting irrelevant, excessive, or sensitive information.
Once submitted, Stripe forwards the evidence to the card network and issuer. The process can take weeks or months, and the decision is generally final. If the dispute is still listed as **needs response**, act immediately; if it says **lost**, you typically cannot overturn it through Stripe except through a limited second-stage appeal, if Stripe offers one for that dispute. It states that challenging an active Stripe dispute requires submitting evidence in a response, matching the source. |
| CORRECT | If you’re the **merchant**, you can try to overturn an active Stripe dispute by submitting a timely evidence response. Stripe forwards your evidence to the card network/issuer; Stripe itself usually does not make the final decision.
### Steps in Stripe
1. Open **Stripe Dashboard → Payments → Disputes**.
2. Select the active dispute and review:
- Dispute reason/code
- Response deadline
- Transaction and customer details
3. Choose **Submit evidence** or **Respond to dispute**.
4. Provide a concise explanation and attach supporting documents.
5. Submit before the deadline shown in Stripe.
### Evidence to include
Tailor the evidence to the dispute reason:
- **Customer claims they didn’t receive the item:** shipping carrier, tracking showing delivery, delivery address, signature, proof of pickup, and fulfillment records.
- **Customer claims the transaction was unauthorized:** AVS/CVV results, 3-D Secure authentication, IP/device data, prior undisputed transactions, login or account activity, and order history.
- **Customer claims the product was unacceptable or not as described:** product listing, terms, photos, specifications, customer communications, and evidence that the delivered item matched the order.
- **Customer claims they were already refunded:** refund date, amount, original payment reference, and refund confirmation.
- **Subscription or recurring billing dispute:** cancellation policy, signup/consent records, renewal notices, usage logs, and cancellation history.
- **Duplicate charge:** explain why the charges were separate and provide invoices or order records.
### How to improve your response
- Address the exact dispute reason rather than uploading unrelated documents.
- Use a clear timeline: order → fulfillment → communications → attempted resolution.
- Make sure names, dates, amounts, and transaction IDs match.
- Submit readable files and avoid excessive evidence.
- Do not pressure or threaten the customer. If they agree the dispute was mistaken, ask them to contact their bank/card issuer; a customer statement alone may not guarantee reversal.
If you refund the payment, the dispute may still continue, and you could lose both the payment and the dispute fee. Check Stripe’s instructions before issuing a separate refund.
After submission, the issuer may take weeks or longer to decide. If Stripe shows the dispute as **lost**, check whether an appeal or second-presentment option is available; this is limited and generally requires new, materially stronger evidence. If you’re the **cardholder** rather than the merchant, you generally must work through your card issuer and contact the merchant for supporting documentation. It states that an active Stripe dispute can be overturned by submitting an evidence response, matching the source. |
| CORRECT | To overturn an **active Stripe dispute**, you must submit evidence through Stripe before the dispute’s deadline. Stripe forwards your response to the cardholder’s issuing bank, which makes the final decision.
### Steps in the Stripe Dashboard
1. Open **Stripe Dashboard → Disputes**.
2. Select the dispute and review:
- The dispute reason/code
- The cardholder’s claim and attached documents
- The response deadline
3. Contact the customer if appropriate. They may withdraw the dispute after you resolve the issue, but **you should still submit evidence** while the dispute is active.
4. Click **Counter dispute**—not **Accept dispute**.
5. Provide a concise explanation addressing the exact claim.
6. Upload supporting evidence relevant to the dispute type, such as:
- Order confirmation, receipt, invoice, and product description
- Shipping address, carrier, tracking, delivery confirmation, or signature
- Customer communications showing the issue was resolved
- Terms, refund/cancellation policy, and proof the customer saw or accepted them
- Usage or login records for digital goods/services
- Proof of a refund already issued
- Evidence that the charge was not duplicated
- 3D Secure/authentication details or other fraud-prevention data
7. Review everything carefully and submit. Stripe generally gives you **one submission opportunity**, and you cannot edit or add evidence afterward.
### Evidence tips
- Match your evidence to the specific dispute reason; don’t submit unrelated documents.
- Use a chronological, factual summary with dates, amounts, order IDs, and delivery/service details.
- Avoid emotional language and unsupported accusations.
- Combine documents of the same evidence type into one file.
- Stripe says banks won’t review external links, audio, or video. Keep files within Stripe’s limits—generally a combined maximum of **4.5 MB**; Mastercard cases may also have a page limit.
- Respond before the displayed deadline—often **7–21 days** after notification. Missing it normally results in an automatic loss.
### If the customer says they withdrew the dispute
Ask the customer to contact their bank and retain written confirmation. However, Stripe states that you should still **counter the dispute with evidence**; a customer’s claimed withdrawal alone does not close the case in your favor.
### If the dispute is already lost
A lost decision is generally final through Stripe, and Stripe does not support arbitration. In rare cases, an issuer can later issue a “late win,” but you cannot rely on that. If the dispute is still marked **needs_response** or **under review**, act through the Dashboard immediately.
You can also submit evidence programmatically using `POST /v1/disputes/{DISPUTE_ID}` with the `evidence` fields and `submit=true`. Don’t share your secret API key. It states that overturning an active dispute requires submitting evidence in a response, matching the source. site:docs.stripe.com disputes submit evidence dispute active Stripe overturn dispute5 results
results as cached 2026-08-24T22:01 opened 3 pages
|
| CORRECT | To overturn an **active Stripe dispute**, you must **counter it by submitting evidence before the deadline**. Stripe itself doesn’t decide the outcome—the cardholder’s issuing bank does.
### Steps in the Stripe Dashboard
1. Open **Dashboard → Payments → Disputes**.
2. Select the active dispute and review:
- The dispute reason/category and network reason code
- The cardholder’s claim and attached bank documents
- The response deadline
3. Choose **Counter dispute**—not “Accept dispute.”
4. Prepare evidence specifically addressing the claim.
5. Upload the evidence and submit the response. Stripe generally gives you only **one submission opportunity**, and you can’t edit it or add files afterward.
### Evidence to include
Use concise, chronological, readable evidence relevant to the dispute reason, such as:
- **Fraud/unauthorized payment:** 3D Secure results, AVS/CVC checks, IP/device information, account login history, prior undisputed payments, and proof of customer identity or usage.
- **Product not received:** order receipt, shipping confirmation, tracking showing delivery, full delivery address, and signature if available.
- **Product/service not as described:** product listing, specifications, communications, and proof of what was delivered.
- **Refund/cancellation dispute:** your refund or cancellation policy, proof the customer agreed to it at checkout, and records showing whether they followed it.
- **Subscription dispute:** authorization for recurring billing, cancellation records, usage, and notices sent to the customer.
- **Customer communication:** relevant emails or messages showing acknowledgement, delivery, usage, or agreement. Include only pertinent excerpts.
Avoid relying on links, videos, or requests for the bank to contact you; issuers generally review the submitted files directly. Stripe’s standard evidence limits include accepted PDF/JPEG/PNG files, a combined maximum of **4.5 MB**, and network-specific page limits.
### Contact the customer—but still submit evidence
If the dispute resulted from a misunderstanding, contact the customer and ask them to withdraw it through their bank. However, Stripe says you should **still submit evidence** while the dispute is active—even if the customer says they withdrew it. A withdrawal alone doesn’t automatically close the dispute in your favor.
### Important deadlines and limitations
- Response windows are commonly **7–21 days**, depending on the card network.
- After submission, the dispute may remain under review for **up to 2–3 months**.
- Some disputes are unchallengeable due to network or local rules.
- If the dispute is already marked **lost**, it generally can’t be overturned through Stripe; arbitration isn’t supported by Stripe.
For the strongest response, write a short factual summary explaining **why the claim is incorrect** and explicitly point to the evidence proving each part. It states that an active Stripe dispute must be countered by submitting evidence in a response, matching the source. site:docs.stripe.com disputes respond dispute evidence overturn active dispute Stripe5 results
results as cached 2026-08-24T22:01 opened 3 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
75 * Use the Dashboard or API to submit your response.
76 ### Unchallengeable disputes
77 You can’t challenge some types of disputes under the rules of the card network they were processed on or due to local regulations. In general, Stripe immediately closes them as lost as soon as we notify you about them, and you have no opportunity to present evidence to the issuer.
78 The Dashboard payment page and timeline describes these disputes as those where the card issuer doesn’t allow you to submit evidence.
79 * [Inquiries](https://docs.stripe.com/disputes/how-disputes-work#inquiries) for Discover cards can turn into unchallengeable disputes if you don’t submit evidence for the inquiry.
| CORRECT | If a Stripe dispute can’t be challenged—because the card network doesn’t allow representment or the response deadline has passed—Stripe generally **accepts the dispute automatically**.
Typically:
- The payment is reversed and the funds are returned to the cardholder.
- Stripe deducts the disputed amount and any applicable dispute fee from your Stripe balance.
- The dispute is marked **lost/closed**.
- If your balance is insufficient, your Stripe balance may become negative and future payouts can be used to recover it.
- There’s usually no further appeal through Stripe, although you may be able to resolve the issue directly with the customer outside the card-network process.
The exact treatment can vary by dispute type, card network, country, and Stripe account terms. It says Stripe automatically accepts the unchallengeable dispute and marks it lost/closed, matching the source’s statement that Stripe immediately closes it as lost after notification. |
| CORRECT | If a Stripe dispute isn’t eligible for challenge—or the response deadline passes without valid evidence—Stripe generally treats it as lost:
- The disputed amount is debited from your Stripe balance.
- Stripe may also charge a dispute fee, depending on your account and region.
- The payment is marked as disputed/lost in the Dashboard.
- If your balance is insufficient, Stripe may deduct the amount from future payouts or leave your account with a negative balance.
- The funds are returned to the cardholder through their bank or card network.
Stripe usually cannot reverse the outcome once the card network has made a final decision. You may still be able to contact the customer directly, but a later customer repayment is separate from the original dispute. It states that Stripe generally treats disputes that cannot be challenged as lost, which matches the source. |
| CORRECT | For disputes that **can’t be challenged**, Stripe generally:
- **Immediately marks them as lost** when it notifies you.
- Gives you **no opportunity to submit evidence** to the card issuer.
- Leaves the disputed amount already debited from your Stripe balance; the refund to the cardholder is effectively permanent.
- Normally does **not refund the dispute fee**.
These disputes can be unchallengeable because of card-network rules or local regulations—for example, certain **Cartes Bancaires** disputes for SEPA businesses and disputes involving **Nigerian payment methods**. Stripe facilitates the process, but the card issuer/network determines the outcome. citehttps://docs.stripe.com/disputes/how-disputes-work It states that Stripe immediately marks unchallengeable disputes as lost upon notification and provides no opportunity to submit evidence to the issuer, matching the source. site:docs.stripe.com disputes can't be challenged Stripe what happens5 results
results as cached 2026-08-24T22:01 opened 2 pages
|
| CORRECT | For disputes that **can’t be challenged**, Stripe generally:
- **Immediately closes the dispute as lost** when it notifies you.
- Gives you **no opportunity to submit evidence** to the card issuer.
- Leaves the **disputed amount debited from your Stripe balance**; the funds have already been credited to the issuer, which may return them to the cardholder.
- Typically keeps the **dispute fee nonrefundable** (subject to regional exceptions).
These disputes can result from card-network rules or local regulations—for example, certain **Cartes Bancaires** disputes in the SEPA region and disputes involving **Nigerian payment methods**. Stripe facilitates the process but doesn’t control the issuer’s decision. citehttps://docs.stripe.com/disputes/how-disputes-work It states that Stripe generally immediately closes unchallengeable disputes as lost upon notification and provides no opportunity to submit evidence to the issuer. site:docs.stripe.com disputes cannot be challenged Stripe what happens dispute can't be challenged5 results
results as cached 2026-08-24T22:01 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
77 You can’t challenge some types of disputes under the rules of the card network they were processed on or due to local regulations. In general, Stripe immediately closes them as lost as soon as we notify you about them, and you have no opportunity to present evidence to the issuer.
78 The Dashboard payment page and timeline describes these disputes as those where the card issuer doesn’t allow you to submit evidence.
79 * [Inquiries](https://docs.stripe.com/disputes/how-disputes-work#inquiries) for Discover cards can turn into unchallengeable disputes if you don’t submit evidence for the inquiry.
80 * The Cartes Bancaires network requires a higher standard of evidence from the cardholder before allowing them to initiate a dispute, but then prohibits you from challenging the dispute. This affects only businesses in the [Single Euro Payments Area (SEPA)](https://en.wikipedia.org/wiki/Single_Euro_Payments_Area) processing payments on the Cartes Bancaires network, and not businesses elsewhere charging cards _issued_ by Cartes Bancaires. Learn more at [Cartes Bancaires](https://docs.stripe.com/payments/cartes-bancaires).
81 * Due to local regulations, you can’t challenge disputes submitted for Nigerian payment methods.
| CORRECT | If you don’t submit evidence for a Discover inquiry in Stripe by the deadline, Stripe generally proceeds without your defense. Depending on the inquiry’s stage and reason:
- The inquiry may be escalated into a formal dispute or chargeback.
- The card issuer may rule for the cardholder because you provided no supporting evidence.
- The disputed amount may be debited from your Stripe balance or future payouts.
- Any applicable dispute or chargeback fee may be charged.
- You may lose the opportunity to contest the transaction later.
A Discover **inquiry** is often an early information request, so responding can sometimes resolve the issue before it becomes a full dispute. Check the inquiry in **Stripe Dashboard → Payments → Disputes/Inquiry** for the exact response deadline and requested documents. If you can’t fully document the transaction, submit whatever relevant evidence you have—such as proof of delivery, customer communications, refund policy acceptance, or usage logs—rather than ignoring it. It states that the Discover inquiry may escalate into a formal dispute and that the merchant may lose the opportunity to contest it later, consistent with it becoming unchallengeable. |
| CORRECT | If you don’t submit evidence for a Discover inquiry in Stripe by the stated deadline, the inquiry may be decided against you or escalate into a formal dispute/chargeback.
Possible consequences include:
- The customer receives a credit or refund.
- Stripe debits the disputed amount from your balance.
- A dispute fee may be charged.
- The case may count against your dispute rate and affect payment-processing risk.
- You may lose the opportunity to challenge the transaction later.
A Discover inquiry may not immediately remove funds, unlike a chargeback, but ignoring it can lead to one. Check the inquiry’s **response deadline and status in Stripe Dashboard**—the exact result depends on Discover’s rules and the inquiry type. If you cannot provide evidence, you can generally accept the inquiry, but don’t let the deadline pass accidentally. It states that failing to submit evidence can escalate the Discover inquiry into a dispute and leave the merchant unable to challenge it later, matching the source's substance. |
| CORRECT | If you don’t submit evidence for a **Discover inquiry** on Stripe:
- The inquiry may escalate into a **formal chargeback**.
- Stripe says the resulting chargeback is likely to be **unchallengeable/unwinnable**, meaning you may have no opportunity to submit evidence later.
- You’ll generally remain liable for the disputed amount, and a formal dispute fee may apply.
- Your dispute rate with the card network may increase.
During the inquiry stage, you can usually avoid escalation by either:
1. Submitting evidence that addresses the cardholder’s claim, or
2. Issuing a full refund.
If the inquiry stays open for **120 days** without escalating, Stripe marks it closed and the card network can’t escalate it—but relying on that is risky. Also, if it does escalate, you must submit a **new response** for the formal dispute; evidence submitted for the inquiry doesn’t automatically serve as the formal dispute response.
Sources: [Stripe—How disputes work](https://docs.stripe.com/disputes/how-disputes-work), [Stripe—Respond to disputes](https://docs.stripe.com/disputes/responding) It states that failing to submit evidence can cause a Discover inquiry to escalate into an unchallengeable dispute, matching the source. site:docs.stripe.com Discover inquiry don't submit evidence Stripe dispute inquiry5 results
results as cached 2026-08-24T22:01 Stripe Discover inquiry evidence deadline what happens inquiry5 results
results as cached 2026-08-24T22:01 opened 2 pages
|
| CORRECT | If you don’t submit evidence for a **Discover inquiry** on Stripe:
- The inquiry may escalate into a **formal chargeback**.
- The resulting chargeback is generally **unchallengeable and likely unwinnable**, meaning you typically won’t get another opportunity to submit evidence.
- You may lose the disputed amount and incur the applicable dispute fee.
- Your dispute rate with the card network may increase.
Stripe says you can resolve the inquiry without a dispute fee by either:
1. Submitting evidence that addresses the cardholder’s claim, or
2. Issuing a full refund.
If the inquiry stays open for **120 days without escalating**, Stripe marks it closed and the network can no longer escalate it. However, you should respond promptly rather than rely on that outcome. Note that if an inquiry does escalate, you must submit a **new response** for the formal dispute. It states that failing to submit evidence for a Discover inquiry can lead to an unchallengeable chargeback/dispute, matching the source. site:stripe.com Discover inquiry don't submit evidence Stripe inquiry5 results
results as cached 2026-08-24T22:01 opened 2 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
92 | Partially refunded charges | A business partially refunded a payment, but the account owner disputes the entire payment. See our [Disputes on partially refunded payments best practice](https://docs.stripe.com/disputes/best-practices#partial-refund-bp) for more information about submitting evidence to counter this kind of dispute. | An account owner contacts a business directly and the business refunds a portion of the original purchase because one of several items in the purchase is damaged. The account owner then disputes the entire purchase amount. |
93 ## After the decision
94 After you submit your evidence, the next notification from the card issuer to both Stripe and you is the final decision. As soon as the issuer makes its decision, Stripe updates the status of the dispute to `won` or `lost`, notifying you through the Dashboard, email, and any other communication channels you configured.
95 This outcome is final for all parties. Neither you nor your customer can overturn a lost dispute. However, a customer can [withdraw a dispute](https://docs.stripe.com/disputes/withdrawing), even after a loss.
96 Stripe doesn’t support the arbitration phase for disputes, which means that you can’t escalate disputes to arbitrators through our platform.
| CORRECT | When the card issuer makes a final decision, Stripe updates the dispute and notifies your integration in several ways:
1. **Dispute status changes**
- The dispute moves to a final status such as `won` or `lost`.
- You can see the decision in the Stripe Dashboard and retrieve it through the Disputes API.
2. **Webhook notification**
Stripe sends a webhook event, typically:
```text
charge.dispute.closed
```
You may also receive `charge.dispute.updated` during earlier status changes, such as when the dispute enters review.
Your webhook handler should retrieve the dispute and inspect fields such as:
```json
{
"id": "dp_...",
"status": "won",
"reason": "...",
"charge": "ch_..."
}
```
Make sure your endpoint verifies Stripe’s webhook signature and handles duplicate deliveries safely.
3. **Balance adjustment**
- If you **win**, the disputed funds are generally returned to your Stripe balance.
- If you **lose**, the disputed amount and any applicable dispute fee remain deducted or are deducted from your balance.
- The related balance transaction can be viewed through the Dashboard or API.
4. **Dashboard and email**
Stripe displays the result in the Dashboard. Depending on your account’s notification settings, Stripe may also send an email notification.
If you do not use webhooks, you can periodically retrieve the dispute from the API or monitor it in the Dashboard, but webhooks are the recommended way to react promptly to the issuer’s decision. It correctly states that Stripe updates the dispute to `won` or `lost` and notifies you through the Dashboard, email, and configured communication channels. |
| CORRECT | When the card issuer makes a final decision, Stripe:
1. **Updates the Dispute object**
- `status` becomes:
- `won` — you won the dispute and funds are generally returned
- `lost` — the issuer ruled against you and the disputed funds are retained by the issuer
- You can view the result in the **Stripe Dashboard** or retrieve the dispute through the API.
2. **Sends a webhook event**
- Stripe sends `charge.dispute.closed` when the dispute is resolved.
- Depending on the funds movement, you may also receive:
- `charge.dispute.funds_reinstated`
- `charge.dispute.funds_withdrawn`
Example webhook handling:
```text
charge.dispute.closed
data.object.status == "won" | "lost"
```
You should use the webhook as the authoritative notification, retrieve the latest Dispute object if necessary, and make your webhook handler idempotent. Stripe may also show the result in the Dashboard and send email notifications according to your account notification settings. It states that Stripe sets the dispute status to `won` or `lost` and notifies through the Dashboard, email, and configured channels, consistent with the source. |
| CORRECT | When the issuing bank makes its final decision, Stripe:
- Updates the dispute status from `under_review` to either:
- `won` — the issuer overturns the dispute and Stripe returns the debited chargeback amount to your balance.
- `lost` — the issuer upholds the dispute; the refund is permanent.
- Sends you an email notification.
- Updates the dispute in the Stripe Dashboard.
- Sends the `charge.dispute.closed` webhook event, if your integration is configured to receive it.
- Updates the corresponding Dispute API object.
You can also view any additional issuer explanation under **Relevant documents → View issuing bank response** in the Dashboard. The decision is generally final, though Stripe notes that rare “late wins” can change a dispute from `lost` to `won`. It states that Stripe updates the dispute status to `won` or `lost` and notifies you through the Dashboard, email, and configured channels such as webhooks, matching the source. site:docs.stripe.com disputes issuer decision update notify webhook dispute closed won lost Stripe5 results
results as cached 2026-08-24T22:01 opened 2 pages
|
| CORRECT | When the issuer makes its decision, Stripe notifies you in three ways:
- **Email** with the outcome.
- **Stripe Dashboard**, where the dispute status is updated.
- **API/webhook**, via the `charge.dispute.closed` event.
The dispute’s status changes from `under_review` to:
- **`won`** — the issuer ruled in your favor. Stripe returns the debited disputed amount to your Stripe balance. The dispute fee is generally not returned, except in certain regions such as Mexico.
- **`lost`** — the issuer upheld the dispute. The chargeback becomes permanent, and the dispute fee isn’t returned.
You may also be able to view additional issuer details under **View issuing bank response** in the dispute’s Dashboard page. It states that Stripe updates the dispute status to `won` or `lost` and notifies you through the Dashboard, email, and a configured webhook/API channel. site:docs.stripe.com disputes issuer decision webhook dispute closed Stripe notify5 results
results as cached 2026-08-24T22:01 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
96 Stripe doesn’t support the arbitration phase for disputes, which means that you can’t escalate disputes to arbitrators through our platform.
97 #### Late-win disputes
98 Although the outcome of a dispute is normally final, in rare cases the status can change from `lost` to `won`. When this occurs, Stripe labels the dispute as a `late win` and returns the funds to your balance. These late-win results happen when issuers credit or debit Stripe for a dispute outside of the regular dispute lifecycle. They might do this to handle money movement or to correct amounts or decisions. Because late wins are driven by the issuer, Stripe can’t predict when or why they happen.
99 ## Local payment method disputes
100 This dispute process applies primarily to card payments. Local payment methods (LPMs), such as Klarna and PayPal, have their own dispute processes that differ in key ways.
| CORRECT | A Stripe dispute can change from **lost to won only in rare, post-decision reversals by the card network or issuing bank**. Typical examples include:
- The cardholder withdraws the dispute after the issuer’s decision.
- The issuing bank determines that the original decision was incorrect.
- The network or issuer processes a dispute reversal or administrative correction.
When Stripe receives that reversal, it may update the dispute status to **won** and return the disputed amount—and, where applicable, the dispute fee—to your balance.
Simply submitting additional evidence after a lost decision generally **does not** change the outcome. Any appeal or further evidence must be handled within the card network’s permitted time frame, usually through Stripe Support. The reverse can also happen: a dispute initially marked won may later be reopened or changed to lost. It correctly states that a dispute can change from lost to won only in rare post-decision circumstances involving an issuer-driven reversal or correction. |
| CORRECT | A Stripe dispute that was marked **lost** can change to **won only in unusual circumstances**, generally when the card issuer or card network later reverses its decision. Common examples include:
- **The cardholder withdraws the dispute** or tells their bank the charge is valid.
- **The issuer corrects an error** in its original ruling.
- **New information is accepted by the issuer** after the original decision.
- **A network or processing reversal occurs**, such as an administrative or technical correction.
Stripe cannot normally overturn a lost dispute itself, and merchants generally cannot submit another appeal after the issuer’s decision. If the issuer reverses the outcome, Stripe may update the dispute to `won` and/or send a `charge.dispute.funds_reinstated` webhook when the funds are returned.
These reversals are rare and may occur days or weeks after the original decision. You should monitor the dispute’s status and relevant Stripe webhook events rather than assuming a lost dispute is permanently closed immediately. It correctly states that a lost dispute can rarely change to won when an issuer-driven reversal or correction occurs after the normal dispute lifecycle. |
| CORRECT | A Stripe dispute can change from **`lost` to `won` only in rare “late-win” situations**.
This happens when the **card issuer credits or debits Stripe outside the normal dispute lifecycle**, for example to:
- Correct a money-movement error
- Correct the disputed amount
- Correct or reverse a prior decision
Stripe then labels the result as a **“late win”** and returns the recovered funds to your Stripe balance.
Stripe says these cases are **issuer-driven**, so it cannot predict when or why they occur. Normally, a lost decision is final: you cannot appeal it through Stripe, and Stripe does not support card-network arbitration. A cardholder may withdraw a dispute even after a loss, but that is separate from Stripe’s late-win status change. It accurately states that a dispute can rarely change from lost to won when an issuer credits or debits Stripe outside the regular dispute lifecycle, which Stripe calls a late win. site:docs.stripe.com disputes lost won after decision reverse Stripe dispute outcome changed5 results
results as cached 2026-08-24T22:01 opened 1 page
|
| CORRECT | A Stripe dispute can change from **lost** to **won only in rare “late-win” cases**. This happens when the card issuer credits or debits Stripe **outside the normal dispute lifecycle**, for example to:
- Correct a money movement or settlement amount
- Correct or reverse a prior dispute decision
- Process a late adjustment from the issuer or card network
Stripe doesn’t control or predict when this occurs. If it happens, Stripe labels the case a **“late win”** and returns the disputed funds to your Stripe balance.
Normally, once an issuer’s decision is recorded as lost, it is final: Stripe doesn’t support appealing or escalating it to arbitration. A customer withdrawing the dispute after a loss is a separate situation and doesn’t necessarily change the outcome to won. It correctly states that a dispute can rarely change from lost to won as a late win when the issuer credits or debits Stripe outside the normal dispute lifecycle. site:docs.stripe.com disputes lost won after decision reverse dispute outcome Stripe5 results
results as cached 2026-08-24T22:01 site:support.stripe.com dispute lost changed to won after decision Stripe5 results
results as cached 2026-08-24T22:01 Stripe dispute outcome changed from lost to won after decision5 results
results as cached 2026-08-24T22:01 opened 1 page
|