Payments · Trial
Payment Failure Decoder
See why card, ATM and instant transfers fail, whose side each failure is on, and how much money customers tried to move and could not.
Why nowAs reported on 9 October 2026, the central bank is tracing delayed eKash transfers with the sending and receiving institutions to find where each payment stalled; failed funds should be returned. KT Press, 9 Oct 2026 ↗
- Prepared for
- Prepared by
- Frutos Kamanzi · CEO & Founder, SAANO AI NETWORKS
Drop in a transaction log
A CSV of card, ATM or transfer attempts with their response or reason codes. It is read in your browser and never leaves this page.
Expected columns (any order, matched loosely): time, code (an ISO 8583 response code such as 00, 51 or 91, or an ISO 20022 status or reason such as ACSC, AB05 or AC01; a separate status column such as RJCT is also read), optional channel, counterparty (issuer, bank or wallet), amount, terminal and customer (a masked card or account reference, used to spot retries). Codes outside these two standards are ranked but not decoded.
Your own file needs a 3-day trial code
The illustrative sample is free. To read your own export, enter the code Frutos sent you. Your file still never leaves this page.
No code yet? Message Frutos on WhatsApp · or call +250 731 000 163
Your 3-day trial has ended
The full version reads every day's switch and core logs, alerts you when a counterparty or terminal starts failing, and gives you the evidence to settle whose side it was. Let's set it up for your institution.
Full version: RWF 300,000 a month for your organisation, USD 200 outside Rwanda. Every tool in the kit, unlimited runs on your own data, cancel any month.
Message Frutos on WhatsAppOr call +250 731 000 163