Transparency in Banking & SBI concerns with the core issue of security of Banking transactions. There is a manifold increase in the number of cyber criminals in society due to rampant corruption and insecure transactions. As technology evolves, so do the tactics of these criminals, leading to a heightened sense of urgency around robust security measures. Financial institutions, including SBI, are compelled to adopt advanced cybersecurity technologies and practices to safeguard their customers’ sensitive information. This includes implementing multi-factor authentication, encryption protocols, and real-time monitoring systems to detect suspicious activities. Furthermore, educating customers about secure banking practices is essential in combating potential threats. By prioritizing transparency and security, banks can foster trust and reduce the risks associated with digital transactions, ultimately contributing to a more secure banking environment for all.
Key Takeaways
- The rise in cyber crime demands improved security in banking transactions, particularly for SBI customers.
- A recent case highlights the issue of a payment that appears successful on SBI’s side but fails on Meta’s end, raising questions about transaction reliability.
- Two main questions emerge: why did a secure transaction not reflect on the merchant’s side, and what is the source of the unexplained fee increase?
- The complaint’s status is currently ‘Under Process’ with the Prime Minister’s Office, indicating ongoing consumer frustration regarding dispute resolution.
- Continued failures in digital transactions highlight a systemic issue, necessitating regulatory action to ensure accountability and transparency in banking.
Transparency in Banking & SBI: The Case of the Vanishing Meta Transaction
In short: Money left a customer’s SBI account for a payment to Meta, and the bank confirmed the debit. However, Meta’s system marked the transaction “failed” and gave no explanation. Consequently, the case is now with the RBI and PMO, and it points to a bigger problem: what happens when a payment succeeds on the bank’s side but disappears on the merchant’s side.
What happened (Transparency in Banking & SBI)
On 15 March 2025, Yogi M. P. Singh tried to pay ₹2,282.44 to Meta (Facebook India) for an ad, using SBI Net Banking.
On SBI’s side, the payment went through smoothly: SBI processed it (reference: IGASORXOF7) and then sent a confirmation SMS. In other words, every signal on the bank’s end confirmed that the money had left the account and reached its destination.
On Meta’s side, though, the transaction shows as “Failed — No reason available,” even though the money had already left the customer’s account. As a result, the customer was left holding a debited account and a merchant record that flatly contradicted it, with no obvious way to reconcile the two.
This is precisely the kind of gap that erodes trust in digital payments. After all, when a system works, nobody notices; but when it breaks silently, and neither side takes responsibility, the customer is the one left absorbing the cost and the confusion.
Two unanswered questions
First, why did a “secure” transaction disappear? SBI Net Banking is marketed as one of the safest platforms available. So, if that’s true, how does a validated payment fail to show up in the merchant’s records at all? Either the bank’s confirmation was wrong, or the merchant’s failure notice was wrong — and right now, nobody has said which. (Transparency in Banking & SBI)
Second, where did the extra money come from? The order total was ₹2,164.12, including GST. But after logging into the payment portal, it jumped to ₹2,282.44 — a difference of over ₹118 with no visible breakdown of fees or charges. Because neither SBI nor Meta itemized this difference, the customer couldn’t tell whether it was a legitimate gateway charge, a currency conversion cost, or simply an error.
Where the complaint stands
The grievance is registered as PMOPG/E/2025/0036236 and is currently marked “Under Process.” So far, it has been escalated to: (Transparency in Banking & SBI)
- Ministry: Prime Minister’s Office
- Action officer: Nodal Officer, Consumer Education and Protection Department (CEPD), Reserve Bank of India
- Status as of: 16 March 2025
Even though the case has reached the country’s highest grievance-redress channel, that alone doesn’t guarantee a fast resolution. Therefore, the complainant has continued to document new evidence, since a paper trail matters more than a single filed complaint when a case involves recurring technical failures.
How cases like this are supposed to be resolved
When a payment succeeds at the bank but fails at the merchant, a standard process exists for closing that gap. Understanding it helps explain exactly where SBI and Meta are falling short.
First, there’s an automatic refund window. RBI rules generally require banks to reverse a failed transaction within T+5 working days. If they miss that window, the bank typically owes the customer compensation for each day of delay. So far, though, no refund and no compensation has been credited, which itself may constitute a violation of RBI’s Turnaround Time framework.
Next comes reconciliation between bank and merchant. Often, the money simply sits in a “suspense account” between the two systems, neither returned to the customer nor delivered to the merchant. Therefore, the RBI Nodal Officer needs to pull a technical reconciliation report to see whether the failure was a timeout, a dropped connection between SBI and Meta’s servers, or something else entirely. Without that report, both sides can keep pointing at each other indefinitely. (Transparency in Banking & SBI)
Finally, there should be a clear fee breakdown. Banks and merchants must itemize charges under RBI’s disclosure norms. So the jump from ₹2,164.12 to ₹2,282.44 needs a specific explanation — for example, a convenience fee, a gateway charge, or a tax miscalculation. Until that breakdown is provided, the additional ₹118 remains, in effect, an unexplained charge.
Why it matters
A “Digital India” needs more than fast internet connections; it also needs a dispute process that actually resolves disputes. Otherwise, pushing individual cases up to the PMO becomes the only way to get a straight answer out of a bank — and that isn’t a sustainable model when millions of transactions happen every day. If even a fraction of them hit this same wall, silent failure with no accountable party, the burden of chasing down ₹100 or ₹1,000 falls entirely on the individual customer, who usually has far less leverage than a national regulator. (Transparency in Banking & SBI)
A related, more recent problem
On 8 January 2026, around 9:58 AM, the same person hit another SBI error — this time on the merchant payment portal (merchant.onlinesbi.sbi): “Due to technical problem unable to generate the QR.” (Transparency in Banking & SBI)
As a result, this adds a second data point to the original complaint, showing that the reliability issue wasn’t a one-off. Nearly ten months separate the two incidents, yet the underlying pattern, a transaction breaking down with no clear explanation, looks strikingly similar.
What it suggests:
- The instability is ongoing. Nearly a year after the first incident, SBI’s systems still fail at a basic function: generating a payment QR code.
- The “no reason given” pattern repeats. In other words, March 2025’s “No reason available” and January 2026’s generic “technical problem” both leave the customer with no way to know what went wrong or where the money is. (Transparency in Banking & SBI)
- Regulatory oversight hasn’t closed the gap. So, recurring failures like this raise the question of whether RBI is actually enforcing its service standards for digital banking, or whether such standards exist mainly on paper.
Suggested next steps for the complainant
- First, add it to the existing case. Upload the January 2026 screenshot to CPGRAMS as supplementary evidence under the existing complaint, since a second, dated incident strengthens the argument that this is systemic rather than incidental. (Transparency in Banking & SBI)
- Then, contact the Nodal Officer directly. Email it to pgrs.cepd@rbi.org.in, cite the registration number, and request a technical audit of why merchant-payment QR generation keeps failing.
- Finally, keep a running log. Because isolated incidents are easy to dismiss, a dated record of every failure gives the case more weight the next time it’s reviewed.
Contacts for similar complaints (Transparency in Banking & SBI)
If you’ve run into a similar issue, these are the channels most likely to help.
Prime Minister’s Office / CPGRAMS (Transparency in Banking & SBI)
This office handles systemic grievances and routes them to the right ministry.
- Grievance ID: PMOPG/E/2025/0036236
- Website: pgportal.gov.in
- “Write to the PM”: pmindia.gov.in
- Phone: 011-23386447
Reserve Bank of India (banking regulator) (Transparency in Banking & SBI)
- Website: rbi.org.in
- Complaint Management System: cms.rbi.org.in
- Consumer Education & Protection (CEPD) email:
pgrs.cepd@rbi.org.in - Central complaints email:
crpc@rbi.org.in - Toll-free: 14448 (9:30 AM–5:15 PM)
- CEPD Mumbai: 022-22604106
- Banking Ombudsman, UP/Kanpur region: 0512-2305174, 2303004 · email
cms.bokanpur@rbi.org.in
State Bank of India (the bank in this case) (Transparency in Banking & SBI)
- Website: bank.sbi
- Internet banking support: retail.sbi.bank.in
- Mirzapur City branch: Dankinganj, Chaubey Tola, Mirzapur, UP – 231001 · 05442-252337 · email
complaint@sbi.co.in - Nodal Officer, Lucknow Circle: 0522-2295395 / 2295392 · email
agmcustomer.lholuc@sbi.co.in - Customer care: 1800-1234 / 1800-2100 · email
customercare@sbi.co.in
Cyber fraud reporting (Transparency in Banking & SBI)
National helpline: 1930explaining why the QR code failed to generate on January 8th?
Website: cybercrime.gov.in
Facing a similar challenge? Share the details in the box below, and our team of experts will do their best to help.