Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
When a bank asks for more evidence, first find out what stage the case is in. It may be a retrieval request, an open chargeback, or a later escalation. Then match each record to the exact point asked, and send it before the due date. A request does not mean you lost.
Written by Chargeflow Experts. Updated 12 November 2026.
| Request | Check | Action |
|---|---|---|
| Inquiry before a formal dispute | Whether this is a request for information or a chargeback. | Answer through the inquiry process. |
| Open evidence collection | Which fields or records are still missing. | Finish the response before you submit. |
| Later escalation | Whether another response or new evidence is allowed. | Ask the processor which next steps it supports. |
| Unclear notification | Case ID, sender, and a matching dashboard notice. | Check it through your usual processor contact. |
Stripe’s response documentation separates inquiries from formal disputes. If an inquiry turns into a chargeback, you must respond again. A sent dispute response also cannot be added to. So a general tip to “send a second round” would mislead you.
Follow what the stage permits
Turn the request into a source-backed response
Request-to-record checklist
Copy the request into a checklist. For each point, name the record, where it comes from, and what it proves. Point to a document you already sent if it answers the question. Add or replace files only if the stage allows it.
Claim-specific event history
For delivery, tie the order to the address and delivery record. For a cancellation, show the request and cancel date against the billing dates. For a refund, link the amount and status to the disputed payment.
Stripe lists the data each record must show to count as chargeback evidence:
Events will not all share the purchase date. Payment, shipping, delivery, and refund happen at different times. Explain the order of events and any gap plainly.
Read the case notice and ask the processor about unclear steps before the due date. There is no universal 30-day window for a second response. Pre-arbitration and representment are different stages, not two names for any evidence request.
Use the evidence-rejection diagnostic when interpreting a decision and the issuer-review overview when you organize records.
A retrieval request asks for records before, or instead of, a full chargeback. Stripe calls it an inquiry. It says most retrieval requests now come from American Express and Discover, while Visa and Mastercard no longer use them. Unlike chargeback reason codes, the codes below ask for a document. Stripe’s code list includes these:
| Network and code | What the bank asks for | Record to send |
|---|---|---|
| Visa 28 | A copy bearing the signature | The signed receipt or contract |
| Visa 30 | Information because the cardholder raised a dispute | Records that answer the customer’s question |
| Visa 34 | Records for a legal process | The full transaction record |
| Mastercard 6305 | The cardholder disagrees with the amount billed | An itemized receipt and the agreed price |
| Mastercard 6321 | The cardholder does not recognize the charge | Receipt, billing descriptor, and what was bought |
| Mastercard 6323 | Information for the cardholder’s records | A copy of the receipt |
| Discover 6021 | Transaction documentation | The receipt and order details |
Source: Stripe’s reason code categories and guide to how disputes work. On Stripe, answering an inquiry with evidence or a full refund avoids the dispute fee. An unanswered inquiry can turn into a chargeback you are unlikely to win, and a Discover inquiry left unanswered can become one you cannot challenge.
Stripe marks an inquiry closed if it stays open for 120 days without escalating. For the difference in fees and timing, see retrieval request vs chargeback.
Through the supported case channel
Close the request with confirmed delivery
Assign an owner
Make one person clearly responsible for the reply. They request and review evidence from each team.
Open the final files
Check the actual attachments before you send.
Submit and retain confirmation
Use the approved channel. Track the follow-up apart from support tickets.
If a record is missing, say so plainly and ask whether another form will do.
Use the workflow audit checklist to fix repeat retrieval problems. Chargeflow’s chargeback recovery workflow helps with evidence prep.
| Illustrative request | Check before acting | Owner and record |
|---|---|---|
| Inquiry asks whether goods were supplied | Is it an inquiry, when is it due, and how does the processor take replies? | Fulfillment supplies delivery tied to the order; payments keeps the confirmation. |
| Message arrives after final evidence submission | Does this stage allow new material, or is it a decision or escalation notice? | Payments checks the allowed route before promising any new response. |
An inquiry that turns into a Stripe chargeback needs its own response, per Stripe’s response instructions. Do not assume the inquiry packet covers the new dispute. Use the chargeback evidence source map to assign records to each point asked, and keep the notice with the response.
No. A request for more evidence often comes before any decision. On Stripe, it may be an inquiry with a warning status, an open chargeback, or a new dispute on the same payment.
No. Answer the point the bank asked about, and refer to a record you already sent where the stage allows it. On Stripe, a submitted chargeback response cannot be changed, so a new request means a new stage.
Use the due date in the case notice. On Stripe, chargebacks usually allow 7 to 21 days. Network limits are longer, at 30 days for Visa and 45 days for Mastercard, but your processor’s earlier date is the one that counts. See chargeback time limits by network.
Successful representment needs evidence that answers the reason code: proof of delivery for non-receipt, proof of who paid for fraud, and cancel or refund records for billing claims. Each record must show the key data, such as the date, amount, and full delivery address.
Some processors flag missing dispute evidence for you. Stripe lists required actions for Visa CE 3.0 cases, such as a missing product description, and returns an error when a packet is over the page limit. Chargeflow Automation builds each response from your order and payment data.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
Track dispute performance across multiple accounts with clear rate definitions, a reconciled case register, weighted win rates, net recovery after fees, and a fixed report schedule.
Standardize chargeback evidence with one core record set, a module for each dispute category, a fixed file format, and a check that each response was sent.
Align customer support and payments with a shared case record, complaint-to-dispute playbook, refund and dispute overlap rules, and subscription habits that cut disputes.
Chargeflow collects data from dozens of third party signals, not just transaction data like Stripe Dispute does. This allows for much more coverage and much better win rates because the evidence submitted is much more comprehensive and compelling..
Chargeflow collects data like order info, customer messages, and payment details. It builds a full dispute case for you, so you don’t have to lift a finger.
Yes! Chargeflow works with many processors — not just Stripe. That means one tool for all your chargebacks, no matter how you process payments.
Chargeflow Automation uses success-based pricing on recovered chargebacks. Other Chargeflow products have separate pricing. Check the pricing page and your agreement for the applicable terms.
Chargeflow’s security documentation describes SOC 2 Type 2 compliance, GDPR compliance, encryption at rest and in transit, and access controls. Review the security page for details on its safeguards and data handling.
Have a question? We’re here to help. Just hit the chat button to initiate a conversation with support.