Dispute evidence already assembled
When a case opens anyway, the merchant's own record of the transaction is what decides it. Smartbills already holds that record, down to each line item, and packages it in the formats the card schemes expect.
Chargeback prevention that stops disputes before they open
Chargeback prevention that shows cardholders the merchant's real name, logo, location and receipt. When a dispute opens anyway, the evidence is ready.
Dispute Defence shows the merchant's real name and location on the transaction, plus the receipt when we have it.
Chargeback prevention with a real answer
Deflection only turns into a dark pattern when there's no real answer behind it. Here the transaction detail screen shows the merchant's trading name and logo, the specific store and the receipt behind the charge.
- Trading name, logo, address and map pin in place of a raw descriptor
- The itemized receipt when the merchant is on the network
- A "was this you?" step the cardholder resolves in the app
- For a purchase an AI agent made, the instruction it followed and who set it
Tell a forgotten charge from real fraud
The biggest categories of non-fraud disputes each leave a signature: a subscription bills on a cadence, a free trial has a conversion date, a family account has a second cardholder and an AI agent buys under an instruction someone gave it.
- Recurring charges shown with their cadence and start date
- Free-trial conversions flagged against the changed descriptor
- Secondary-cardholder purchases identified on shared accounts
- AI agent purchases shown with the limit and end date they stayed within
How dispute defence works
A cardholder taps a charge
They question it from the transaction screen in your app, before any case is opened.
The screen explains it
Merchant name, location and category, plus the itemized receipt when there is one. They see what they actually bought.
The rest is sorted at intake
Recurring charges, trial conversions, purchases by a secondary cardholder and purchases an AI agent made are labelled first, so the fraud team only sees fraud.
Real disputes come with evidence
The itemized receipt, merchant record and transaction history are packaged in the scheme's format and sent to the dispute platform you already use.
Keep exploring
See all products- ProductTransaction enrichmentResolve a card descriptor into a business your customer recognizes, with logo, location and category, plus the itemized receipt when the merchant sent us one.
- ProductAI agent receiptsAn itemized receipt for every purchase an AI agent makes for your business, with who authorized it, the card it paid with, and every tax and fee.
- ProductEmbedded receiptsItemized receipts from the merchant's point of sale, shown inside your own app under the transaction they belong to. For banks, fintechs, retailers and any app built on the API.
FAQ
Frequently asked questions
What people ask us before they sign up.
Chargeback prevention means stopping a card dispute before it is filed, often by helping the cardholder recognize a charge they did make. Smartbills shows the merchant's real name, logo, location and receipt on the transaction screen. A forgotten purchase is recognized instead of disputed.
Common, and growing. In the Merchant Risk Council's 2026 Payments and Fraud Report, 64% of merchants said first-party misuse was rising: charges the cardholder doesn't recognize or doesn't remember approving. Merchants put the cost of resolving one such dispute at over $80, and 83% fight them with compelling evidence. That evidence is the record Smartbills already holds.
Mostly issuers, though merchants and acquirers use it too. An issuer uses it to keep cases from entering the process, while an acquirer or merchant uses the same receipt to represent a case that did. Either way, the evidence is the merchant's own record of the sale, captured before anyone disputed anything.
Partly. Merchant identity, location and category come from Transaction Enrichment and cover every transaction, which on its own resolves a lot of recognition queries. The itemized receipt only exists when the merchant is on the network, and that receipt is what turns a deflected query into a complete evidence bundle.
When an AI agent buys for a cardholder, Smartbills keeps the instruction it bought under on the receipt: the limit, the category, the end date and the person who set them. The transaction screen shows it, so the cardholder sees their own agent made the purchase within the limits they gave it. If a case opens anyway, the instruction goes into the evidence bundle with the receipt.
Visa and Mastercard. The bundle follows the formats both schemes specify, including the prior-transaction pattern in Visa's Compelling Evidence 3.0 rules, and when scheme rules change the bundle is reconfigured rather than rebuilt.
In two places, and you can adopt either one on its own: in your app on the transaction detail screen before a case exists, and behind your dispute platform as an evidence lookup by transaction. It doesn't replace your dispute management system.
No. Showing cardholders what they bought gives them information and puts nothing in their way. The option to open a case stays on the same screen and is no harder to find or use.
A fraud model scores a transaction before it's authorized, whereas Dispute Defence works afterwards, on whether the cardholder understands a charge they really did make. No score can fix that, because the transaction was genuine.
Get started
Find out how much of your queue is really fraud.
Bring a month of reason codes and we'll show you which ones a readable transaction screen would have answered.