KOHEN AVOCATS FIRM · PARIS 16
Revolut Outage in France After Google Cloud Failure: How to Claim When Your Money Was Blocked

Hassan KOHEN acts in urgent matters, from the police station to the assize court. Initial strategic analysis: €80 incl. VAT, personal reply within 24 hours.

100% confidential · Legal professional privilege · No obligation

Article generated by artificial intelligence, through a process designed and supervised by the firm

Source: French Court of Cassation – Judilibre and Légifrance open data

Paris Bar Police custody, investigation, assize court CNB listing avocat.fr
Maître Hassan KOHEN, avocat au Barreau de Paris
Hassan KOHEN
Attorney at the Paris Bar

Revolut Outage in France After Google Cloud Failure: How to Claim When Your Money Was Blocked

Speak to a lawyer 06 89 11 34 45

On Tuesday 20 October 2026, millions of Revolut customers across Europe opened their banking app and found nothing working: cards declined at shop tills, transfers stuck, cash withdrawals impossible and logins returning error messages. Clients in the United Kingdom, Ireland, France, Spain and Japan reported the same disruption, according to Euronews, which described the incident as a worldwide outage of the online bank. By the evening the company stated that the problem was resolved and services restored. The cause, according to both the bank and Google, was a power incident in a Google Cloud data centre near London, in the europe-west2 region, and not an attack on the bank itself. Revolut said in a statement that its customers’ money and data remained safe, apologised for the inconvenience, and confirmed it had been working on the fix since the morning.

Two reservations matter before any legal analysis, and they frame everything that follows. At the time of writing, no official source has established any intrusion, any data theft or any lasting loss of funds connected with this outage: the only established facts are a temporary inaccessibility of services and the explanations given by the two companies themselves. And this article is general legal information about French and European payment law, not advice on any individual file: account contracts prevail over any general analysis, and only a court seized of a concrete dispute can decide whether a bank owes compensation to a particular customer.

The question is nevertheless real and cross-border, which is why it belongs on this desk. When a bank that serves customers in France becomes unreachable for a full business day because its American cloud provider suffers an electrical failure, who bears the legal risk? French law gives a precise answer, built on the European payment services directives, on a liability regime that the Cour de cassation has declared exclusive, and on recent rulings that show exactly what judges demand before awarding a single euro. This article explains that framework in two steps: first, what French payment law requires of a bank even when its screens go dark; second, what a French judge will actually check before compensating a customer whose money was temporarily blocked.

I. French law does not let a bank disappear behind a cloud error message

The first reflex of a customer locked out of his account is to assume that a technical failure suspends everybody’s obligations. French payment law takes the opposite starting point: the bank remains responsible for executing payment operations, and a failure to execute triggers defined remedies. The cloud is the bank’s chosen infrastructure, not the customer’s problem.

A. Your payment orders must be executed, and a botched execution must be put right

The cornerstone is article L. 133-22 of the Code monétaire et financier. When the payment order is given by the payer, the text provides that his payment service provider is, subject to a few stated exceptions, “responsable de la bonne exécution de l’opération de paiement à l’égard du payeur” until the beneficiary’s provider receives the funds. Where the payer’s provider is responsible for a badly executed operation, the same article provides that “il restitue sans tarder son montant au payeur” and, where needed, “il rétablit le compte débité dans la situation qui aurait prévalu si l’opération de paiement mal exécutée n’avait pas eu lieu”. In plain terms: an order that never arrives because the app was down is, for the customer, a non-executed operation, and the statute orders the account to be put back as if the failed operation had never happened.

The companion provision is article L. 133-18 of the same code, which deals with unauthorised operations and is worth knowing because outages breed fraud, as this article explains below. It provides that the payer’s provider “rembourse au payeur le montant de l’opération non autorisée immédiatement après avoir pris connaissance de l’opération ou après en avoir été informé, et en tout état de cause au plus tard à la fin du premier jour ouvrable suivant”, unless it has good reason to suspect fraud by the user and has reported those reasons in writing to the Banque de France. The mechanism is deliberately strict: refund first, argue later.

A third provision completes the picture and often surprises customers. Article L. 133-21 of the Code monétaire et financier provides that “Un ordre de paiement exécuté conformément à l’identifiant unique fourni par l’utilisateur du service de paiement est réputé dûment exécuté pour ce qui concerne le bénéficiaire désigné par l’identifiant unique.” The unique identifier, typically the IBAN, is therefore decisive: an order executed exactly as instructed, to the IBAN typed by the customer, counts as duly executed even if the customer typed the wrong IBAN. During an outage this rule cuts both ways. Orders that the system silently dropped were never executed and fall under the restoration duty of article L. 133-22; orders the customer re-typed in a panic on a shaky connection, with a wrong digit, may be deemed duly executed, leaving the customer to chase the unintended recipient with the bank’s assistance rather than with a refund.

These three articles transpose the European payment services directives, first 2007/64/CE then (UE) 2015/2366, which means the same skeleton applies across the Union, including to an institution operating in France under a European passport. That cross-border uniformity is precisely what makes a London cloud incident litigable in Paris under French statutes: the applicable French provisions are the domestic face of Union-wide duties.

B. A single exclusive liability regime, not a pick-and-mix of grievances

Customers often assume they can sue their bank on every available ground at once: contract law, tort, payment law, consumer law. The Cour de cassation has closed that door. In two recent rulings, both handed down by its commercial, financial and economic chamber, it held that the payment liability regime of articles L. 133-18 to L. 133-24 of the Code monétaire et financier is exclusive of any competing national regime for the same facts.

On 4 March 2026, in pourvoi no. 25-11.959 opposing BNP Paribas to customers who had wired their personal contribution to fraudsters impersonating their notary, the Court recalled that the Court recalled that article L. 133-21 of the Code monétaire et financier, which transposes the inaccurate-unique-identifiers rule of Directive (EU) 2015/2366, deems an order executed in line with the user-supplied unique identifier duly executed as regards the designated beneficiary, and releases the provider from liability for defective or non-execution where that identifier is inaccurate The interest of the ruling for an outage scenario lies in its reasoning on the boundary of that regime: the Court added that ordinary contract liability under article 1231-1 of the Civil Code is excluded where the provider merely executed the payment order in line with the user-supplied unique identifier, but remains available where the provider went further than mere execution Because the bank had itself drawn up the transfer order from a glaringly forged bank identity slip instead of merely executing the customers’ instruction, ordinary contract liability applied and the rejection of the bank’s appeal was confirmed. The lesson for 20 October is symmetrical: a bank that simply could not execute anything because its platform was down stays inside the special payment regime; a bank that actively mishandled the incident, for example by displaying false confirmations or inventing orders, could step outside it.

The exclusivity principle had already been stated even more bluntly on 15 January 2025, in pourvoi no. 23-13.579, where the Bred banque populaire challenged a Paris appeal ruling that had split losses from unauthorised transfers fifty-fifty between the bank and its corporate customers. Citing the Court of Justice’s Beobank judgment of 16 March 2023 (C-351/21) and its CRCAM judgment of 2 September 2021 (C-337/20), the Cour de cassation held that where a payment service provider is sued over an unauthorised or badly executed operation, only the liability regime of articles L. 133-18 to L. 133-24 of the Code monétaire et financier applies, to the exclusion of any alternative liability regime under national law It quashed the appeal decision for applying ordinary contract liability on top of the special regime. For customers of the October outage, the message is clear and double-edged: the special regime protects them with automatic restoration duties, but it also channels their claim and forbids creative detours around its conditions.

One of those conditions deserves immediate attention because time limits in payment law are forfeiture rules, not mere guidance. Article L. 133-24 of the Code monétaire et financier provides that “L’utilisateur de services de paiement signale, sans tarder, à son prestataire de services de paiement une opération de paiement non autorisée ou mal exécutée et au plus tard dans les treize mois suivant la date de débit sous peine de forclusion”, unless the provider failed to supply the required information. The decisions consulted for this article do not settle whether a day-long inability to log in, with no debit at all, counts as a badly executed operation triggering that thirteen-month clock, or as a mere temporary unavailability governed by the account contract. The prudent course is therefore to complain in writing immediately, as if the clock were running, rather than to test the classification later before a judge.

II. A blocked afternoon does not automatically mean compensation: what a French court will demand

Establishing that the bank bears a statutory execution duty is only half the battle. French courts award damages only for proven, quantified loss caused by the failure, and they listen carefully when the bank invokes an outside cause. The October 2026 facts, a power incident at a subcontractor’s data centre, sit exactly on that fault line.

A. Force majeure, the cloud subcontractor and the evidence you will really need

The bank’s predictable defence is force majeure: the failure came from Google Cloud’s infrastructure, an external giant, after an electrical incident, so the bank could do nothing. French contract law defines the defence narrowly. Article 1218 of the Civil Code provides that “Il y a force majeure en matière contractuelle lorsqu’un événement échappant au contrôle du débiteur, qui ne pouvait être raisonnablement prévu lors de la conclusion du contrat et dont les effets ne peuvent être évités par des mesures appropriées, empêche l’exécution de son obligation par le débiteur.” Three cumulative conditions, then: outside the debtor’s control, unforeseeable at contracting, unavoidable in its effects despite appropriate measures. And where the obstacle is temporary, the same article adds that “Si l’empêchement est temporaire, l’exécution de l’obligation est suspendue à moins que le retard qui en résulterait ne justifie la résolution du contrat.” A one-day outage is the textbook case of temporary impediment: obligations are suspended, not extinguished, which is why services could lawfully resume in the evening.

Mirror provision: article 1231-1 of the Civil Code provides that “Le débiteur est condamné, s’il y a lieu, au paiement de dommages et intérêts soit à raison de l’inexécution de l’obligation, soit à raison du retard dans l’exécution, s’il ne justifie pas que l’exécution a été empêchée par la force majeure.” The burden structure matters: it is the bank that must justify the force majeure, with evidence, not the customer who must disprove it. A press article quoting the provider is not such proof; the bank would need to document the incident, its exteriority, its unforeseeability and the absence of available workaround, such as a failover to another region, which is precisely the kind of resilience planning that the European regulation on digital operational resilience now scrutinises for the financial sector.

Crucially, subcontracting the IT to a cloud giant does not, in itself, satisfy that test. The payment code itself treats outsourcing as part of the provider’s sphere: article L. 133-19 of the Code monétaire et financier expressly contemplates losses connected with “une entité vers laquelle ses activités ont été externalisées”, and the logic of the provision places the consequences of the provider’s organisational choices on the provider, not the payer. Whether the October power incident was truly unforeseeable and unavoidable for a bank of this size, which had concentrated millions of customers’ access on a single cloud region, is exactly the kind of question a court would examine file by file, and the decisions consulted for this article do not pre-judge it. What can be said is that the defence is neither automatic nor hopeless: it will turn on documents, redundancy architecture and the precise timeline of the restoration, all of which lie in the bank’s hands.

The customer’s side of the evidential equation is just as demanding, and a very recent appeal ruling illustrates it. On 25 June 2026, the Versailles Court of Appeal (chambre civile 1-6, RG 23/08142) confirmed the dismissal of a customer’s claim against the online bank Boursorama after a payment incident combining a card ceiling problem and a transfer sent to a wrong IBAN. The court noted that the bank’s mediator had already established that the customer had been warned by text message, that he knew his ceilings, and that as an informed trader he should have used an immediate transfer from the start instead of persisting with a doomed card payment. The ruling is a warning in three parts for outage victims: first, follow the bank’s real-time guidance during the incident rather than forcing doomed transactions; second, mitigate the loss as soon as an alternative channel exists, because judges notice when a creditor lets damage grow; third, expect the bank’s mediator to reconstruct the timeline message by message, so keep every screenshot, error notice and timestamp.

Causation will be the hardest hurdle. A customer who simply could not check his balance for a day has suffered annoyance, not compensable loss. A customer who can prove a concrete chain, a time-sensitive payment missed, a contractual penalty incurred, a cheaper fare or rate lost, a documented business opportunity destroyed, enters the zone where damages become conceivable. Vague assertions about stress or hypothetical gains will not survive the analysis that French courts apply to bank liability files, where the prejudice must be certain, personal and directly linked to the fault. Every claimed euro needs a receipt, a contract clause or a bank statement.

One specific trap deserves emphasis because outages reliably trigger it: phishing. When the genuine app is down, fake support messages, mirror login pages and fraudulent compensation forms multiply within hours. Any payment validated by the customer on a fraudulent page is a different legal animal from the outage itself, governed by the unauthorised-operation rules, under which the payer’s own negligence can leave part of the loss on him, within a fifty-euro threshold in the standard case set by “le payeur supporte, avant l’information prévue à l’article L. 133-17 , les pertes liées à l’utilisation de cet instrument, dans la limite d’un plafond de 50 €” of article L. 133-19 of the Code monétaire et financier. Never re-enter full credentials through a link received during an outage; use only the previously installed application or the known website address typed by hand.

B. The practical path from France: complain, mediate, escalate, and watch the supervisors

For a customer in France, the useful sequence starts on the day itself with evidence. Preserve everything contemporaneously: screenshots of error messages with visible times, declined-payment receipts, the reference of any time-sensitive order that failed, correspondence with the intended payee showing the deadline, and any penalty or surcharge actually incurred. The method is the same one recommended for any cross-border claim pursued from France, as explained in the guidance on complaining and claiming from France after a data incident: contemporaneous proof decides cases more often than legal theory. Note the exact amounts, keep the originals, and avoid recreating the timeline from memory weeks later.

Next, complain to the bank in writing without delay, describing each failed operation, its time, its amount and its consequences, and asking expressly for restoration of the account and compensation for the documented loss. Written form matters for two reasons: it starts an auditable file, and it protects against the thirteen-month forfeiture rule of article L. 133-24 discussed above, whose precise scope for pure unavailability is, as noted, unsettled in the decisions consulted. A complaint sent within days can never be criticised as late; a complaint sent after a year of silence invites a forfeiture debate the customer does not need.

If the bank’s answer is unsatisfactory, the consumer mediation route is a statutory right. Article L. 612-1 of the Code de la consommation provides that “Tout consommateur a le droit de recourir gratuitement à un médiateur de la consommation en vue de la résolution amiable du litige qui l’oppose à un professionnel.” Every bank serving consumers in France must guarantee effective access to such mediation, and the Versailles ruling discussed above shows that mediators in banking disputes examine files closely, message by message. Mediation is free, it suspends nothing by itself, and it produces a reasoned position that later judges read with attention. It is the natural second step before any court action, and it costs nothing to the consumer.

Beyond the individual file, the incident has a regulatory dimension that French customers should understand, because it improves their position structurally. Reuters, relayed by RTE, reported that the outage spotlighted United Kingdom and European Union regulators’ concern about finance’s dependence on a handful of external technology providers; that the United Kingdom brought Google Cloud, Microsoft, Amazon Web Services and Oracle under direct oversight as critical third-party suppliers to finance in July; and that European Union regulators had designated Google Cloud among nineteen critical technology providers to the bloc’s finance industry. That designation sits within the European regulation on digital operational resilience in the financial sector, Regulation (EU) 2022/2554, known as DORA, whose oversight framework for critical third-party providers is the Union’s answer to exactly this scenario: one provider’s incident freezing several banks at once. The framework does not create a direct compensation cheque for each customer, and this article makes no such claim, but it means the incident will be examined by supervisors with powers to demand resilience plans, backup arrangements and incident reports. A customer file that references the incident precisely, with dates, amounts and the provider’s own acknowledgements, therefore lands in an environment where the facts are already under official scrutiny.

For court action proper, the account contract governs the competent forum and the applicable detail, and it must be read before anything is filed. French consumers bringing a claim connected with services used in France will generally find a French court available, but jurisdiction and limitation questions turn on the contract, on the European instruments and on the precise nature of each loss, none of which this general article can settle for any individual. What the recent case law guarantees is the framework the judge will apply: the exclusive payment liability regime for badly executed operations, ordinary contract law only where the bank stepped outside mere execution, force majeure tested against its three statutory conditions with the burden on the bank, and damages only for proven, quantified, causally linked loss with mitigation by the customer. Measured against those four filters, most files from a one-day outage will end with restoration of the account and no more; a minority, with documented cascading loss, may genuinely deserve compensation.

Conclusion

The 20 October 2026 outage was spectacular in scale and modest in legal mystery: a power incident at a London cloud region, acknowledged by the provider, cascading into a digital bank’s application and freezing millions of customers, including customers in France, out of their money for most of a business day. The bank states that the problem is resolved, that services are restored and that funds and data stayed safe, and no official source has established any intrusion, theft or lasting loss at the time of writing. Within those boundaries, French payment law is well armed: the bank answers for proper execution up to receipt by the beneficiary’s provider, restores the account without delay when execution fails, and can only escape damages by proving a genuine force majeure, a test that outsourcing to a cloud giant does not automatically satisfy. But the same law is demanding towards claimants: exclusive regime, thirteen-month vigilance, proven and mitigated loss, and ordinary contract liability reserved for conduct beyond mere non-execution. Customers who document everything now preserve every option, from mediation to the courtroom; those who wait, or who confuse a day of annoyance with a quantified loss, will likely recover nothing beyond the restoration the statute already guarantees. Account contracts prevail over this general analysis, and only the judge seized of a concrete file will have the last word.

📄 Official circular