A lower tolerance for disputes
Dispute vendors report that Visa lowered the dispute ratio at which a merchant is treated as excessive in April 2026. We have not checked that against Visa's own rules.
Dispute Pack
Show what the customer agreed to.
Dispute Pack assembles what a customer was shown and agreed to at checkout into the evidence a card dispute asks for: the terms, the disclosure, the acceptance and the usage that followed.
What goes wrong
The charge was agreed to, and the proof is in five places.
A subscription seller answering a dispute needs the sign-up screen, the renewal terms, the reminders and the usage. These usually sit in different systems, and the response window is short.
Evidence the network can match
As dispute vendors describe Visa's rules, some fraud disputes can be answered with earlier undisputed transactions that share device, address or login details. A merchant needs to have kept those details.
First-cycle disputes
A dispute in the first billing cycle arrives before any transaction history exists. What is left is the record of the sign-up itself.
A record nobody kept
Many sellers can show that a box was ticked. Fewer can show the wording that was next to it on that day.
How it works
One packet per disputed charge.
Dispute Pack links the sign-up record to the transactions that followed and assembles the packet. It runs on the same consent record, rule library and append-only log as the other eight modules.
- It starts at checkout
- The wording shown, the renewal terms and the action the customer took are captured when they sign up, in the same consent record Sender Check writes.
- It ties the record to the charge
- Each acceptance is bound to the account, the order and the transactions that followed, so a dispute can be traced back to what was agreed.
- It adds what happened afterwards
- Reminders sent, price-change notices, logins, usage and any cancellation request are attached with their dates.
- It produces the packet
- For one disputed charge, Dispute Pack exports a single document. You hand it to the dispute tool or processor you already use.
Features
What Dispute Pack is made of
Acceptance record tied to the transaction
Links what the customer was shown and accepted at checkout to the order and the charge that followed.
Recurring-billing disclosure history
Keeps the renewal terms shown at sign-up and each reminder or price-change notice sent afterwards.
Device and login details
Stores the device, address and login details recorded at sign-up and at later sessions, the kind of details card networks ask merchants to match.
Usage after purchase
Attaches the activity you send us that shows the product or service was used after the charge.
Cancellation history
Shows whether the customer asked to cancel, when, and what happened to the request.
One packet per dispute
Assembles these records into a single document for one disputed charge.
Works beside your dispute tool
The packet is handed to the dispute tool or processor you already use. Dispute Pack does not file the response for you.
On the platform
The steps of the consent record this module runs
All nine steps run in every module, from capturing what a person was shown to producing the record when someone asks for it.
- 1. Capture
- Record the page, form or script a person was shown, the exact wording, the time, the device and the action they took. A screenshot alone is not a record; the wording and the event are.
- 2. Bind
- Tie the event to one person, one phone number or account, and one named seller. A consent that cannot be linked to the person who gave it is the kind courts have refused to accept.
- 6. Record
- Write the decision, the inputs and their dates to a log that is appended to and never edited, so it can be produced later exactly as it was.
- 9. Produce
- Export the record for one person as a single packet: for a carrier reviewer, a card network, an auditor or your own counsel.
What this does not do
Where Dispute Pack stops
It does not win a dispute
The card issuer decides the outcome under the network's rules. Dispute Pack supplies the record and makes no claim about results.
It does not file the response
It sits beside a dispute tool or your processor. It does not submit evidence to a card network.
It does not create evidence that was never captured
Sign-ups made before Dispute Pack was connected have only the records you already hold.
It does not replace counsel or your processor's guidance
Card network rules change and differ by network. The packet format follows published guidance and is no substitute for it.
Read next
The guide, the article and the quiz
Reviewed 12 November 2026
Consentra is software. Nothing on this site is legal advice, and using Consentra does not by itself make a business compliant with any law or carrier rule. Whether a rule applies to your business is a question for your counsel.
See the consent record for yourself
Book a call and we show you the record on your own flow: what each person saw, what they agreed to, and what you can hand over when someone asks.