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

Library · Chargebacks · How to run this

Build the fight packet the family needs

How to run thisChargebacks4 steps
GuideEvidence pack by reason family · Calculator lives in the articleOpen

Issuers file a code, not “a chargeback.” The packet has to match the family. A 3DS log on not-as-described is labor you will not get back.

Pair: Evidence pack by reason family on Chargebacks. Packet floor before family docs: representment packet minimum. The default moves sit next to reason codes that matter. Visa 10.4 Compelling Evidence 3.0 is two prior sales, not this family table: Compelling Evidence 3.0: two prior transactions.

Families and what wins

Fraud (Visa 10.4, Mastercard 4837): they say they did not authorize. 3DS success, AVS/CVV, device, fulfillment. Fight if auth is clean. Refund if the order has not shipped.

Authorization (Visa 11.x, Mastercard 4808): capture without a valid auth. The receipt has to match the capture. Credit and close unless it does.

Processing (Visa 12.x, Mastercard 4834): wrong amount, duplicate, currency. Credit the delta. Do not write a novel.

Not received (Visa 13.1, Mastercard 4855): carrier scan, delivery photo, AVS match. Fight if delivered. Refund if it is still in the warehouse.

Not as described (Visa 13.3, Mastercard 4853): SKU, listing, CS transcript, return policy shown. Refund if the page lied. Fight if it did not. 3DS does not win these.

Cancelled recurring (Visa 13.2, Mastercard 4841): cancel log, last MIT, refund of unused cycles. Cancel the token first. Then credit. See subscriptions.

Credit not processed (Visa 13.6, Mastercard 4860): refund confirmation in the processor. Post the credit. Do not fight a missing refund.

Defaults are operational priors, not network law. A $12 CNP fraud on a one-shot is a write-off even if you “could” fight it.

Allocate the case to the MID that took the sale. A blended brand queue is how a good account dies for a bad code mix.

When this fails

Sending a 3DS packet on not-as-described. Fighting cancelled-recurring while MIT still bills. Using the reseller’s renamed reason.

Related: refunds, subscriptions.

Procedure

  1. Read the network code.
  2. Put it in a family.
  3. Pull only the docs that family needs.
  4. Refund if the default move says so.

Failure modes

  • Sending a 3DS packet on not-as-described.
  • Fighting cancelled-recurring while MIT still bills.
  • Using the reseller’s renamed reason.

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

Family
Fraud, authorization, processing, or consumer. Fight the network family, not a reseller nickname.

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

FAQ

Can I send the same packet for every code?
No. Fraud wants authentication and device. Not-received wants a carrier scan. Not-as-described wants the listing and the CS transcript. The wrong packet is a write-off with extra labor.
The reseller renamed the reason. Which label do I use?
The network code. If the portal says fraud and the code is 13.1, believe 13.1. Compelling Evidence is shaped around families, not nicknames.
Do I fight cancelled-recurring if I have a cancel log?
Cancel the token first, then credit unused cycles. Fighting while the CRM is still billing is how you lose twice.