The dispute notice landed Friday with a deadline on it. The records are in eight different places.

We assemble the evidence packet. You submit it.

Send us one chargeback. Within two business days you get a printable evidence packet, the field-by-field text for your evidence form, and a one-page note naming every record that was missing. We never contact your customer, and we do not contact the issuing bank.

$185 per dispute, after a free record checkThe record check is free and comes first. If your records cannot support a response, we say so and there is no invoice.

Written for US direct-to-consumer brands of 5 to 150 people, for the person who assembles dispute evidence today.

Start a free record check

A person reads your request in the order it arrives. Nothing activates, no account is created, no card is charged.

Case SAMPLE-01 / merchant copy Illustrative

Index of exhibitsStatus

01Order recordLine items, discounts, timestampsp. 1–2Attached
02Gateway transaction detailAVS full match, CVV matchp. 3Attached
033D Secure resultNot requested at checkoutnoneMissing
04Carrier history and delivery photoDelivered, no signature on filep. 4–6Partial
05Customer message threadFour messages, uneditedp. 7–9Attached
06Refund and store credit historyOne partial refund, $60.00p. 10Attached
07Policy as posted on the order dateWith the checkout acceptance recordp. 11–14Attached

Printed black and white. No color-coded information. 14 pages. Record check not run Checked: 5 attached, 1 partial, 1 missing

Invented case, built from public platform documentation. No real customer, order or brand appears here. Running the sample sends nothing.

What arrives

Three files, one deadline, no login.

Everything below is what you receive by email. There is nothing to install and nothing to log into.

The packet

One printable document with a numbered index, the exhibits in the order a reviewer reads them, and every page legible in black and white. That last part is a formatting standard the platform recommends, because many banks still receive evidence by fax.

The form text

Field-by-field text for the evidence form in your own admin, written to be pasted rather than composed. You read it, change anything you want, and submit it yourself.

The gap note

One page naming each record that did not exist and where in your stack it should have been captured. This is the part that is worth something after the case closes, whichever way it goes.

The second file, shown

Evidence form, field by field

Three of the nine fields from the same invented case. This is the text as it would be delivered, ready to paste into your own admin.

The other six cover the billing address, the shipping address, the carrier and tracking number, the refund policy disclosure, the cancellation policy, and the customer signature where one exists. Each is written from a record in the packet, and each names the exhibit it came from.

Field 02 Product description

Order 10482 was placed on Aug 24, 2026 at 9:12 PM ET. Two items: Coastal Shell Jacket, size M, $280.00, and Ridge Beanie, $60.00. Subtotal $340.00 with free shipping. The billing address matched the card on file, returning an AVS full match, and the security code matched.
Field 05 Shipping documentation

The label was purchased Aug 25, 2026 at 10:04 AM ET to the shipping address on the order. Carrier scans show pickup Aug 25, an in-transit scan Aug 27, and delivery Aug 28 at 2:41 PM ET with a delivery photo, attached as Exhibit 04. Signature on delivery was not purchased with the label, so no signature exists.
Field 08 Additional evidence

The cardholder emailed support on Aug 29 at 8:07 AM ET confirming the package arrived and asking about sizing. The full four-message thread is Exhibit 05, pages 7 to 9, unedited. A partial refund of $60.00 was issued Sep 2 and appears as Exhibit 06. The returns policy in force on the order date is Exhibit 07, with the checkout record showing acceptance at 9:12 PM ET on Aug 24.

When it arrives: Within two business days of a complete intake, US business hours. Cases are scheduled in the order intakes arrive. No overnight, weekend or holiday work.
How many we take: Six cases a week during this test, in arrival order. If a case cannot be scheduled before its deadline, we say so at intake and do not invoice.
If we miss the two days: You do not pay for that case. We do not promise the dispute is recovered, and no outcome is refundable, because no outcome was sold.

How a case runs

You send records. We assemble. A person signs off before anything leaves.

What you send

The dispute notice with reason code, amount and response deadline
The order record export, with line items, discounts and timestamps
Gateway transaction detail: AVS, CVV, 3D Secure if present, device and IP if your platform records it
Carrier tracking history and proof of delivery, with the photo or signature where one exists
The complete customer message thread across email, chat and SMS, unedited
Refund, exchange and store credit history for that customer
The returns, shipping and terms pages as they read on the order date
The checkout record showing the customer accepted them

Exports are fine. If you would rather grant access, make it a scoped staff account limited to orders and disputes. We do not ask for owner credentials and will refuse them.

What we do

Record check, free. We mark each of the eight inputs present, partial or missing, and say go or decline before any invoice exists.
Assemble. Pull the order and gateway detail, carrier history, the unedited thread, the refund history, and the policy version that was live on the order date.
Map to the reason code. Place each artifact against the evidence that reason code asks for, and write down the gaps rather than papering over them.
Format. Build one printable document with a numbered index, set for black-and-white legibility, nothing carried by color, nothing that needs zoom.
Draft the form text. Write each evidence field so you paste rather than compose.

Where a person signs off

Before the invoice. A person decides go or decline on the record check. A case we cannot answer is declined, not sold.
Before delivery. A second read against the reason-code checklist and the exclusions list. Nothing leaves on an agent's say-so.
Before submission. You approve the packet text in writing. Then you submit it in your own admin, or a scoped staff account does, and we log the time.

Written into the engagement: we do not contact your cardholder, the issuing bank or the card network. Customer data in a packet is used to build and submit that packet, is never used for marketing or research, and our working copy is deleted after the case closes.

Fit

Both lists are set in the same type.

Send us a case if

You run a US direct-to-consumer brand between 5 and 150 people and you are the person who assembles this today
At least 24 hours remain on the response deadline
You can export, or grant scoped read access to, the order, gateway, carrier and inbox records
One named person on your side can approve the text and submit it
What you want back is the hours, not a prediction
The dispute is a card chargeback inside your payment platform, not a marketplace or buyer-protection claim

Do not send us a case if

The response window has closed, or fewer than 24 hours remain at intake
You want a win rate, a recovery estimate or a success-share price. We decline to give one
You want us to submit on your behalf using owner credentials
The case turns on alleged criminal conduct or a counterfeit claim, or is already in litigation
You need arbitration or pre-arbitration filings, legal advice, or representation before a bank, network or regulator
You want fraud scoring, order screening or prevention work. This is assembly after the fact
You run hundreds of disputes a month. That is a volume operation and an incumbent fits it better

The questions we get

Answered with scope, not with superiority.

Our platform already does this.: Partly true, and worth saying plainly. The evidence form is free, it fills itself from platform data, and a redesign published on 2025-12-17 adds an optional AI-assisted defense and shows you the exact PDF sent to your payment provider. What it cannot pull is the carrier's delivery photo, the SMS thread, the warehouse exception note, or the version of your returns policy that was live on the order date. Those are the fields that come back blank. That blank part is the work.
Why should we trust you?: Nothing here rests on trusting us. The record check is free and happens before any invoice. You see the packet before anything is submitted. You submit it yourself, inside your own admin. One named person handles your case and answers when something is wrong. What we exclude is published in the same type size as what we include.
Why $185?: We budget two to four hours for a case, a person going through your gateway, carrier, inbox and policy history and formatting the result to the black-and-white legibility standard the platform recommends. That estimate is ours and we have not yet measured it against a live case. The nearest priced comparison in public is a $29 alert deflection, which is a different job, and a 25 percent share of recovered amounts, which is a different bet. We charge flat because we will not price on an outcome we do not control.
What do you need from us?: The dispute notice with its deadline, and read access or exports for eight things: the order record, gateway transaction detail with AVS, CVV and 3D Secure results, tracking and proof of delivery, the full message thread, refund and credit history, the posted policies as they read on the order date, and the checkout acceptance record. If fewer than 24 hours remain, we decline at intake.
Who talks to our customers?: You do. We do not contact your customer. The platform states merchants cannot contact the customer's bank directly about a chargeback, and we do not contact it either. We work only from records you supply.
What if it goes wrong?: Two failure modes, one answer each. If the records cannot support a response, we tell you at the free record check and there is no invoice. If we miss the two business day delivery, you do not pay for that case. We do not promise recovery of the dispute itself, and no outcome is refundable, because no outcome was sold.
Why not an assistant, or an incumbent?: A capable assistant can do this, and some brands should hire one. The difference is that a per-case packet needs someone who already knows what each reason code asks for and how the formatting has to read, on the first case rather than the tenth. An incumbent like Chargebacks911 is quote-gated and built for volume. If you have hundreds of disputes a month, they are the right call, and we will tell you so on the record check.

Free reference, no email required

Where each record lives, by reason code.

The evidence form asks for different things depending on why the cardholder disputed. Below is what each type asks for and where it usually sits in a direct-to-consumer stack. Useful whether or not you ever send us a case.

The cardholder says: I did not authorize this purchase.

Proof the card details were verified: Gateway transaction detail: AVS result, CVV result, and the 3D Secure result if your checkout requested one
Proof the buyer is the cardholder: Order record: account age, prior orders on the same card, email or shipping address
Device and network evidence: Order risk detail in the platform or gateway: IP address, device fingerprint where it is recorded
Proof the goods reached the cardholder: Carrier tracking history, delivery photo, and the signature if signature on delivery was purchased
Contact after delivery: Helpdesk inbox and SMS platform, exported unedited, including anything the cardholder wrote after the package arrived

The cardholder says: The order never arrived.

Delivery to the address on the order: Carrier tracking portal, or the third-party logistics export when the warehouse buys the label
The timeline from order to delivery: Order record timestamps alongside the carrier scan history, in one sequence
Any delivery exception and how it was handled: Warehouse exception notes and the carrier exception scan, plus what your team did next
What you told the customer about shipping: The shipping policy page as it read on the order date, and the order confirmation email that was actually sent
Anything already given back: Refund, exchange and store credit history for that customer

The cardholder says: It is not what was advertised.

What was advertised: The product page as it read on the order date, including the images and the size or material copy live that day
What the customer says they received: Photos and messages in the helpdesk thread, exported unedited
Your policy and its acceptance: The returns policy version in force on the order date, plus the checkout record showing the customer accepted it
Whether a return was offered or attempted: Returns app or helpdesk record, and the carrier record of any return label that was created
Anything already given back: Refund, exchange and store credit history for that customer

Reason code names differ between card networks and platforms. The three above are the ones you will recognize in your admin. Where a record usually lives is not where it always lives: half the work on a case is finding out which of these your stack actually kept.

Take the sample apart

The packet and the checklist, both open.

Both files are invented and safe to inspect. The packet is the exact shape of what a case produces. The checklist is the working document behind it, written to be useful on a case you do yourself.

HTML The sample packet, printable

The full invented case SAMPLE-01 as one black-and-white document: index of exhibits, the order and gateway detail, carrier scans, the unedited message thread, the policy record, the three form fields and the gap note. Print it to see the legibility standard.

Download Markdown The record checklist

The eight records with where each usually lives in a direct-to-consumer stack, what each reason code type asks for, the black-and-white formatting rules, deadline arithmetic, and a capture-gap table. Useful whether or not you send us a case.

Download

What we checked before writing this page

The alternatives, stated as they state themselves.

Chargeflow publishes automation at 25 percent of the recovered amount and alerts at $29 per deflected chargeback. Vendor claim on its pricing page, observed 2026-09-07, not audited by us.
chargeflow.io/pricing
Shopify's disputes evidence form is included at no additional charge, and a changelog entry dated 2025-12-17 describes a redesign that adds an optional AI-powered defense and shows the merchant the exact PDF sent to the payment provider.
Shopify changelog, 2025-12-17
Shopify states the evidence window is usually 7 to 21 days after a chargeback is filed, that the bank's decision is final, and that Shopify is not involved in the decision.
Responding to chargebacks and inquiries
Shopify recommends high-contrast evidence that prints clearly in black and white, because many banks receive chargeback evidence by fax. That is the formatting standard the packet is built to meet.
Resolving a chargeback or inquiry
Chargebacks911 publishes no price. Its public path is a demo or an ROI analysis request, observed 2026-09-07.
chargebacks911.com

Here is the strongest argument against paying us anything. The issuing bank decides these cases, not the packet. A success share costs you nothing when the case is lost, while our flat price is the same either way. And merchants in public forums describe submitting signatures, delivery photos and full threads and still losing. If the free form plus its AI defense already produces for your cases what our packet produces, we would rather you learn that during the free record check than after an invoice. That is part of why the check is free.

The workspace behind this

Praxis is where the case is worked.

Praxis is the workspace the case is worked in. The dispute notice, the exports, the message thread and the draft packet sit in one place instead of five browser tabs and a folder of screenshots. Where an agent helps, it helps with fetching and formatting. It never decides what the evidence means.

The judgment stays with a person. Someone reads every exhibit against the reason-code checklist before the packet leaves, and nothing is submitted until you have approved the text in writing.

Kevin Pantasdo answers when something is wrong with your case. A name and an inbox, not a ticket queue.

You do not get a login as part of this, and there is nothing here to evaluate as software. You get a document, the form text and a gap note. Praxis is how we make them, not what we are selling you.

Send us the dispute you are looking at right now.

Start with the free record check. Tell us the reason code, the amount and the deadline, and which of the eight records you can put your hands on. We either say go, or we say the records will not support a response. If it is the second, there is no invoice and you have your afternoon back.