%201.svg)
What Should I Do When a Bank Requests More Evidence?
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
600+ reviewsTL;DR:
- Identify the case stage before preparing a follow-up.
- Answer the exact request with relevant, linked records.
- Confirm whether additional evidence is permitted.
- Use the case deadline and retain submission confirmation.
When a bank or payment provider requests more evidence, first identify the case stage, requested records, submission route, and deadline. A request may concern an inquiry, an open dispute, or a later escalation; it does not always mean an earlier response was rejected.
Written by Jodi Lifschitz, Head of Content at Chargeflow. Updated 12 October 2026.
Identify the Request Before Sending Files
| Request | Check | Action |
|---|---|---|
| Inquiry before a formal dispute | Whether this is an information request or a chargeback. | Answer through the designated inquiry process. |
| Open evidence collection | Which fields or records are still needed. | Complete the requested response before final submission. |
| Later escalation | Whether another response or new evidence is permitted. | Ask the processor which next steps are supported. |
| Unclear notification | Case ID, sender, and matching dashboard notice. | Verify through your established processor contact. |
Stripe’s response documentation distinguishes inquiries from formal disputes and explains that an inquiry which escalates requires a response to the chargeback. It also states that a submitted dispute response cannot be supplemented. A general instruction to “send a second round” would therefore be misleading.
Answer Each Requested Point
Follow what the stage permits
Turn the request into a source-backed response
Request-to-record checklist
Copy the request into an internal checklist. For each point, identify the relevant record, where it comes from, and what it demonstrates. Refer to a document already submitted if it answers the question; add or replace files only as permitted.
Claim-specific event history
For delivery, connect the order to the destination and delivery record. For a cancellation, show the request and effective date against the billing timeline. For a refund, link the amount and status to the disputed payment.
Do not require every event to share the purchase date. Payment, shipment, delivery, and refund normally occur at different times. Explain their sequence and any inconsistency accurately.
Confirm What the Current Stage Allows
Read the case notice and ask the processor about uncertain instructions before the deadline. There is no universal 30-day second-response window. Pre-arbitration and representment are distinct processes, not interchangeable names for any evidence request.
Use the evidence-rejection diagnostic when interpreting a decision and the issuer-review overview when organizing records.
Close the Operational Loop
Through the supported case channel
Close the request with confirmed delivery
Assign an owner
Make responsibility for the requested response explicit.
Open the final files
Check the actual attachments before sending.
Submit and retain confirmation
Use the approved channel and track follow-up status separately from support.
If a requested record is unavailable, state that accurately and ask whether another form is acceptable.
Use the workflow audit checklist to fix recurring retrieval problems. You can explore Chargeflow’s chargeback recovery workflow for evidence preparation.
Two Requests With Different Response Routes
| Illustrative request | Check before acting | Owner and record |
|---|---|---|
| Inquiry asks whether goods were supplied | Is this an inquiry, what is its deadline, and how does the provider accept the response? | Fulfillment supplies order-linked delivery; payments retains response confirmation. |
| Message arrives after final evidence submission | Does this stage permit new material, or is it a notice of decision/escalation? | Payments verifies the supported route before promising an amended response. |
An inquiry that escalates to a Stripe chargeback requires a separate response, according to Stripe’s response instructions. Do not assume the inquiry packet was automatically sufficient for the filed dispute. Use the chargeback evidence source map to assign records by the specific point requested, and retain the notice alongside the response.
Frequently Asked Questions
Does a Request for More Evidence Mean I Lost?
A request for more evidence does not necessarily mean you lost. Check whether it concerns an inquiry, an open response, or a later dispute stage.
Should I Always Replace Earlier Documents?
Do not automatically replace earlier documents. Answer the requested point and follow the rules for the current stage; referring to an existing record may be appropriate.
How Long Do I Have to Respond?
Use the deadline in the case notice. Follow-up and escalation windows vary, and your processor may require action before a network-level cutoff.
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
.png)
More articles.
How Do I Track Dispute Performance Across Multiple Accounts?
Track disputes across accounts with consistent metrics, reconciled recovery, currency controls, and clear treatment of pending cases.
How Do I Standardize Evidence Across Dispute Types?
Standardize chargeback evidence with reusable source records, case-specific selection, quality controls, and verified submission.
How Do I Align Customer Support and Payments to Reduce Disputes?
Align support and payments with shared case records, refund controls, escalation ownership, and practical dispute-prevention workflows.
Questions?
we’ve got answers.
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.
need more help?
Have a question? We’re here to help. Just hit the chat button to initiate a conversation with support.