Context: When a banking app crashes right at payday or a balance ‘evaporates’ overnight, customers often receive an apology instead of compensation; the line between the two outcomes is whether the fault sits in the bank’s system or in the customer’s own actions.
The Legal Framework That Decides the Issue
A bank’s responsibility when a system incident occurs is built from three overlapping duty sources. First, the account and payment service contract: the bank commits to system availability and accurate transaction recording, so money wrongly debited by a system error must be fully refunded — this is repayment of a baseless debit, not ‘goodwill compensation’. Second, State Bank rules on information-system safety and incident reporting: the bank must detect, report and remedy incidents by procedure, and concealing an incident to avoid liability is itself a violation. Third, civil liability to compensate damage under the Civil Code where the bank’s fault causes actual loss to the customer, such as late payment exposing the customer to contract penalties with a third party.
By contrast, a pure outage (app maintenance, peak-hour overload) that loses no money and causes no proven damage usually stops at the duty to notify and apologise under the service terms. The hardest dispute point is indirect loss: the customer says ‘the app crash cost me a contract’, the bank says ‘that is speculative loss’. To recover this layer, the customer must prove a concrete causal chain in writing — the bank’s incident notice, the lost contract, the penalty actually borne — not merely narrate felt damage. And the golden principle remains time: a complaint with blocking and trace requests must be filed as soon as an abnormality is spotted, because system logs are evidence with an expiry date.
Beyond the Text: How Authorities and the Market Actually Operate
When a balance looks wrong, the customer should screenshot the before-and-after balance, save the app’s error notice with its timestamp, and call the hotline for a complaint code the same day. These three small pieces of evidence are worth more than any later argument, because they fix the system’s state at the incident moment before the bank completes its reconciliation cycle.
What to Do: Action Checklist
The steps below turn the analysis above into concrete work:
- First, test your own situation against this ground: A bank’s responsibility when a system incident occurs is built from three overlapping duty sources.
- Record the application point specific to this case instead of copying conclusions from another case: Second, State Bank rules on information-system safety and incident reporting: the bank must detect, report and remedy incidents by procedure, and concealing an incident to avoid liability is itself a violation.
- Prepare the evidence and file relating to the following point before dealing with authorities or partners: When a balance looks wrong, the customer should screenshot the before-and-after balance, save the app’s error notice with its timestamp, and call the hotline for a complaint code the same day. These three small pieces of evidence are worth more than any later argument, because they fix the system’s state at the incident moment before the bank completes its reconciliation cycle.
- Answer the question clients ask most directly with this conclusion, and keep it on file: Usually not, if the outage lost no money and you cannot prove actual damage: the bank’s duty then is to notify, remedy and apologise under the service terms. Compensation arises only where a system fault causes specific, document-proven loss, under the Civil Code’s damage principles.
Frequently Asked Questions
If the banking app is down and I cannot transact, am I compensated?
Usually not, if the outage lost no money and you cannot prove actual damage: the bank’s duty then is to notify, remedy and apologise under the service terms. Compensation arises only where a system fault causes specific, document-proven loss, under the Civil Code’s damage principles.
If money ‘evaporates’ from my account due to a system error, who bears it?
The bank bears it. Money debited by a system error is a baseless debit and must be fully refunded after tracing; the customer should complain immediately and keep before-and-after balance evidence. If the bank claims the customer made the transaction, the burden of proving it by system logs rests on the bank.
Must the bank publicly disclose system incidents?
The bank must report system-safety incidents to the State Bank under incident-management procedure, and notify affected customers to protect their accounts. The degree of public disclosure depends on the incident’s nature, but concealing an incident from the regulator is a violation independent of customer damage.
This article has been quality-reviewed by the FLAW AI Legal Council