A soft decline cluster on one rail can look like “customers hate this method” when the real story is issuer friction or a misconfigured 3-D Secure challenge. That is why our flagship packs include a companion sheet for the top decline reasons by method.
What we ask for in the export
Method identifier, authorised vs completed flags, and a decline reason field your PSP already labels. We do not need raw gateway payloads.
How we present it
Large bars for conversion; a smaller table for declines. Colour stays consistent across both so a director can glance from chart to table without relearning a legend.
What we refuse to claim
Decline codes rarely prove fraud intent on their own. Our commentary stays inside operational language: retry patterns, challenge rates, and whether a method deserves a quieter placement while issuer issues settle.
If your exports lack decline detail, we still run conversion comparison — and we say clearly what the pack cannot explain.