Skip to article
ecomservices.io
Chargebacks · How to run this
MatchingNot on this page yetPricingCalculatorIntakeCalculatorReason codesCalculatorRepresentmentCalculatorThresholdsCalculatorAllocationCalculatorOptimisationCalculatorPrevention stackCalculatorProviders

Library · Chargebacks · How to run this

Write RDR rules you can defend

How to run thisChargebacks4 steps
GuideRDR rule sheet for this MID · Calculator lives in the articleOpen

Automatic on RDR is not Mastercard deciding for you. It is the decision engine running rules you wrote — amount, dispute category, condition code, and the other attributes on this seat. Cases that match accept liability and credit the cardholder before a chargeback. Cases that match nothing continue as chargebacks.

Pair: RDR rule sheet for this MID on Chargebacks. What RDR is: RDR. What it hides in the ratio: RDR mix.

What “automatic” actually means

No human opens the case when a rule hits. You still chose the rule. You still lose the sale and pay the per-case fee. Get whether RDR sits in primary in writing from this acquirer.

Verifi’s public rule shape lets merchants combine attributes such as transaction amount, dispute category, dispute condition code, BIN, purchase identifier, date, and currency. Up to a small set of rules per enrollment in the hosted engine. That is enough to include cheap not-received cases and exclude clear fraud you would fight.

Scope by amount and reason

Amount. A low ceiling auto-refunds small tickets you will not represent. A catch-all “amount greater than daily volume” refunds nearly everything. Name the dollar you mean.

Dispute category / condition. Fraud with a clean auth packet is often worth excluding. Unshipped not-received is often worth including. Not-as-described and cancelled-recurring need a written posture — not a vibe.

Shipped vs not. If your CRM knows fulfillment, put that in the rule logic or the Decision API path. Blind auto-refund on delivered goods is how you pay twice.

Turning a rule off

You are not stuck with last quarter’s catch-all. Public Verifi guidance: request a suspend, remove, or update through support on the hosted engine, or own the Decision API if you host decisions. Name who can change rules on this MID. An orphan rule that refunds everything is a hole, not a program.

What this is not

This is not enrollment 101. This is not Ethoca or CDRN — those need a human in hours. After a rule fires and something still looks open: RDR fired — why a dispute still shows.

Related: prevention stack, price the path.

Procedure

  1. Name the MID and the RDR enrollment.
  2. Write amount, dispute category, and condition posture.
  3. Turn the catch-all off unless you mean it.
  4. Name who can change rules. Measure hidden points on the mix tool.

Failure modes

  • Leaving a catch-all amount rule that refunds nearly everything.
  • Treating automatic as ‘we cannot turn codes off.’
  • No named owner for suspend or edit.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

Automatic
Your pre-set RDR rules fire without a human. Not Mastercard refunding every dispute.

Work with us — We run this job on your accounts. Services

FAQ

Does automatic RDR mean every dispute refunds?
No. Automatic means your pre-set rules fire without a human. Cases that miss every rule go on as chargebacks.
Can I turn RDR off for some reason codes or amounts?
Yes. Rules can scope amount, dispute category, and condition code. Suspend or edit a rule in writing with the seat owner.
Is a catch-all amount rule a good start?
Only if you mean to refund almost everything. That is how RDR hides a pile of winnable cases behind a calm primary ratio.