Payments 101 · lesson 06 · 5 min

Declines, reversals and disputes

The unhappy paths — and why each one exists to protect somebody.

Declines are not errors — they're the platform protecting someone. A decline means a rule said no: the card is blocked, the transaction type is restricted (e-commerce off, international off), a limit is exhausted, or something looked fraudulent. Everest returns structured reason codes so your channel can tell the customer *why* and, where appropriate, offer the fix ("enable international purchases?").

Reversals undo same-day mistakes. Posted the wrong amount? Duplicate booking? Within the same-day window, a reversal by utid unwinds the transaction cleanly. After the window closes, the books have moved on — which is where disputes begin.

Disputes (chargebacks) are the formal process when a cardholder challenges a transaction: goods never arrived, fraud on a stolen card, an unrecognized charge. The issuer opens a case with a scheme reason code, attaches evidence, and the scheme's timeline governs the exchange between issuer and acquirer until money is returned or the charge stands. Everest manages cases end to end against schemes' systems (Mastercom, VROL).

One more protection runs through everything: idempotency. Every write call carries your referenceNumber; retrying with the same reference returns the original result instead of booking twice. Networks fail — this is why a timeout never becomes a double charge.