By Eric Kuvykin. Reviewed October 17, 2026. This practical guide replaces an earlier general commentary article at the same address.
A falling approval percentage can mean several different things: a new customer mix, repeated attempts by the same shopper, a checkout defect or a processor issue. Treat it as an investigation prompt. Start with a worksheet that distinguishes the customer’s purchase attempt from every message sent by the payment system. Otherwise a burst of retries can make a small problem look much larger.
Define the event you are counting
Choose a stable order reference and count unique orders alongside authorization requests. Record channel, time, payment method, amount band and the response category supplied by the provider. Keep personally identifying and payment credentials out of the analysis sheet. Ask the processor to explain unfamiliar response categories rather than translating every decline into suspected fraud.
Separate technical failures from responses returned by the issuer or processor. A checkout timeout does not by itself tell staff whether an authorization occurred. Mark uncertain outcomes for reconciliation instead of immediately inviting another payment. The important question is whether there is a verified transaction record for the original attempt, not whether the browser displayed a reassuring message.
Compare like with like
Review a consistent period before and after a change. Split online and in-person activity; then consider whether order values, device mix or customer traffic changed. Use both counts and percentages. Three declines out of ten attempts and thirty out of one hundred have the same ratio but imply different workloads. Small samples deserve an explicit uncertainty note.
Choose one hypothesis to investigate with the processor. For example, did a checkout update coincide with missing required fields? Did a configuration change affect one terminal? Keep a change log with the time, owner, expected effect and rollback route. Avoid changing several controls at once, because an improved headline rate would not reveal which change helped.
Give the counter team a safe response
Staff need a short script that explains the transaction was not completed and offers an approved next step without blaming the customer. Do not ask for card credentials in email or chat to diagnose the decline. The PCI Security Standards Council’s merchant resources provide a starting point for payment data handling questions to discuss with the acquirer.
Before enabling automatic retries, use the duplicate-charge reconciliation guide to establish how uncertain attempts are checked. Pair this worksheet with front-counter fraud and escalation scripts. A New York owner can place both in the operating review described in the New York business guide. The target is a clearer explanation of failed purchases and an auditable correction process; a higher approval rate alone is not proof of healthier payments.
