How does an authorization reversal work?
An authorization reserves funds on the customer’s card. Until the payment is captured and settled, the merchant can cancel it, and the issuer releases the hold. Stripe explains that refunds issued shortly after the original charge are often processed as reversals: the original charge drops off the customer’s statement and no separate credit appears. Adyen’s documentation describes a reversal request that cancels the payment if it has not been captured and refunds it if it has, with the final outcome reported later by webhook.
Why do reversals matter?
They are the cheapest and clearest way to undo a payment. As an illustrative example: an online store’s checkout times out on 200 payments a day and the customer retries, producing 30 duplicate approvals. If the duplicates are reversed within minutes, the customers see one charge and never contact support. If they are refunded days later, each shows as a charge plus a credit, some customers dispute them before the credit arrives, and the merchant pays fees on both sides.
What are the risks?
A reversal is only possible within a window, and the window depends on the network, provider and capture timing. A reversal or refund request can itself fail or be rejected, so its outcome needs to be confirmed. And a reversal sent for the wrong payment, for example after a timeout where the first attempt actually failed, creates its own reconciliation problem. Unique references and idempotency keys keep each reversal tied to exactly one payment.
Where does Omno use it?
Omno’s webhooks report transaction status changes, Get Transaction Info confirms the final status of a transaction, and the routing-decision log shows which provider processed the original payment, which is where a reversal has to be sent.