KOHEN AVOCATS FIRM · PARIS 16
Revolut Down: What Happened to Your Money and How to Get It Back in France

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 Down: What Happened to Your Money and How to Get It Back in France

Speak to a lawyer 06 89 11 34 45

On Tuesday 20 October 2026, the Revolut app went dark for millions of users: logins failed, card payments were declined and transfers froze for most of the day. The cause, identified the same day, was a power incident in a Google Cloud data-centre region near London on which Revolut relies. Complaints poured in from the United Kingdom, Ireland, France, Spain and Japan, and the incident made headlines in the Irish and French press in the same week it topped Google searches in Ireland. Revolut stated in the evening that services were restored and that customer funds and data remained safe. For the more than eight million French customers of the bank, the practical questions remain: a transfer that never arrived, a direct debit rejected during the outage, a card declined at a shop till — who bears the loss, and what must be done before the file goes stale? This article explains the European and French rules that answer those questions: the liability of the payment service provider for transactions that are not properly executed, the thirteen-month deadline for reporting a problem, the next-business-day refund rule, the burden of proof that rests on the bank, the duty of banks to inform their clients after a major IT incident, and the path from written complaint to the banking mediator and the courts.

I. Is Revolut still down? What happened to your money on 20 October 2026

A. What happened to Revolut on 20 October 2026?

Early signals appeared in the morning: users could no longer reach their money or pay with their cards, payments were refused at tills while others received an error message when trying to log in to check their accounts, as Euronews reported on 20 October 2026. After numerous accounts on social networks, the company published a statement to reassure its clients, confirming that it was working on a solution and that their funds remained intact. In a statement issued during the day, Revolut said it was experiencing a service interruption affecting several services and confirmed that all clients’ money and data were safe. In the evening, the company announced that the problem was resolved and services restored.

The incident was traced to a power cut in a Google Cloud data centre near London, which caused severe service failures on Tuesday. Google stated in a service update that its Cloud platform had suffered an outage further to an electrical incident, and several other British banks also reported disruptions. Google later announced that the problem had been largely mitigated for most clients. The incident began at 6:08 GMT on Tuesday in Google’s europe-west2 region, its London data-centre zone, where increased errors and intermittent network outages were reported, as Euronews reported on 20 October 2026. Revolut’s online banking services were disrupted, including cash withdrawals, transfers and card top-ups, with a source close to the matter attributing the failures to the Google Cloud problems; the British banks Lloyds and HSBC also confirmed their clients were affected. For much of the day, some Revolut customers could not log in to the app, make card payments, transfer money or withdraw cash, and a Revolut spokesperson confirmed the bank had been working on the problem since it was identified, apologising for the inconvenience caused.

The scale explains why the topic surged on Google Trends in Ireland on 21 October 2026, with searches such as “revolut service outage digital bank”, “is revolut still down”, “what happened to revolut?” and “is revolut working again”. Complaints came from around the world, with clients in the United Kingdom, Ireland, France, Spain and Japan all reporting disruptions. Revolut is Europe’s most valuable start-up, currently valued at around 121.1 billion dollars, ahead of traditional European banking giants such as Barclays, Lloyds and Santander, and it reports more than eighty million retail clients, growing by about one million new users every seventeen days. In France alone, the bank counts more than eight million customers and over fifty-five thousand businesses, figures consistent with the licensing announcement of 10 August 2026.

That licence matters for the legal analysis. Revolut Bank S.A. was granted a full banking licence in France following a joint assessment by the European Central Bank and the French prudential supervisor, the Autorité de contrôle prudentiel et de résolution (ACPR), as Euronews reported on 10 August 2026. The bank counts eight million French users, and the licence strengthens deposit protection to 100,000 euros through the Fonds de garantie des dépôts et de résolution (the French deposit guarantee fund, FGDR), while opening access to mortgages and regulated savings products. The rules set out below are the French provisions that transpose the European Payment Services Directive, and they are the rules French courts apply to payment incidents suffered by users in France, as the court decisions cited in this article show.

B. Is Revolut working again, and is your money still safe?

The short answer, on the basis of the sources available at the time of writing, is that access was restored on the evening of 20 October 2026 and that no loss of funds or data has been established by any official source. Revolut confirmed that its clients’ money and data were safe, and Google indicated that the underlying Cloud incident was largely mitigated. An account that is temporarily inaccessible is not an account that has been emptied: a service interruption freezes the use of the app, the cards and the transfers, but it does not in itself move money. If, when access returned, your balance was intact and no transaction you did not authorise appears on your statements (relevés), the incident caused you delay and inconvenience, not a debit. If, on the contrary, a transaction you never ordered appears, a different and stricter regime applies, explained below: the refund of unauthorised transactions by the end of the next business day.

European law gives you a first concrete right here: the right to be informed. EU digital-resilience rules for finance require financial entities to report major technology incidents to their supervisor and to inform affected clients of the incident and of the mitigation measures without undue delay. Revolut published such communications during the day. Keep them: screenshots of the app’s error messages, the company’s statements, the times at which each payment failed and the amounts concerned are the evidence on which any later claim will rest. The outage therefore leaves two traces: a public one toward clients, and a supervisory one toward the authorities.

A final preliminary point concerns deposits. The press coverage of the outage reported no concern about the safety of deposits, and Revolut’s statements confirmed funds were safe. Eligible deposits are covered up to 100,000 euros per person through the FGDR, subject to the exclusions published by the fund. A deposit guarantee protects you if the bank fails; it is not the tool for recovering a payment blocked by a one-day outage. For that, the payment services rules below are the correct instrument, and they start with a simple distinction: was your transaction unauthorised, or was it authorised but badly executed or never executed?

II. Revolut not working today: how to recover blocked payments in France

A. Failed transfers, rejected direct debits and declined cards: who bears the loss?

French law allocates the risk of a failed payment to the payment service provider, not to the client. When the payment order is initiated directly by the payer, the payer’s provider is liable for the proper execution of the transaction toward the payer. This is the rule of article L. 133-22 of the Code monétaire et financier (the French Monetary and Financial Code): “responsable de la bonne exécution de l’opération de paiement à l’égard du payeur” (liable for the correct execution of the payment transaction with regard to the payer). Where the payment order is given by the payer, the provider bears that liability toward the payer. Where the payer’s provider is liable, the same article requires it to return the funds without delay and to restore the account: “il restitue sans tarder son montant au payeur” (it shall refund the amount to the payer without delay), with a value date no later than the debit date: “La date de valeur à laquelle le compte de paiement du payeur est crédité n’est pas postérieure à la date à laquelle il a été débité” (The credit value date for the payer’s payment account shall be no later than the date on which it was debited). This French rule transposes the European Payment Services Directive (Directive (EU) 2015/2366), whose liability regime French courts apply to payment incidents suffered by users in France. A transfer (virement) ordered from your Revolut app before or during the outage that never reached its recipient, and that Revolut cannot show was received by the beneficiary’s provider, therefore falls in principle on Revolut to refund and re-credit, not on you to absorb.

The same logic governs timing. Article L. 133-13 of the same code requires the amount to be credited to the beneficiary provider’s account no later than the end of the first business day following receipt of the order: “Le montant de l’opération de paiement est crédité sur le compte du prestataire de services de paiement du bénéficiaire au plus tard à la fin du premier jour ouvrable suivant le moment de réception de l’ordre de paiement” (The amount of the payment transaction shall be credited to the payee’s payment service provider’s account at the latest by the end of the first business day following the time of receipt of the payment order). A payment that arrived days late because the systems were down is a late execution, and the value-date protection above applies to late payments as well.

Rejected direct debits (prélèvements) deserve separate attention, because the harm often comes from the creditor, not the bank: a landlord, an insurer or a tax office that could not collect on the due date may charge late fees or suspend a service. The bank’s failure to execute does not make the underlying debt disappear, and you should pay the creditor by another means as soon as possible to stop the loss from growing. But the additional cost caused by the bank’s failure — late-payment penalties, reconnection fees, documented loss — can be claimed from the provider. French contract law preserves this: article 1231-3 of the Code civil (Civil Code) states that “Le débiteur n’est tenu que des dommages et intérêts qui ont été prévus ou qui pouvaient être prévus lors de la conclusion du contrat, sauf lorsque l’inexécution est due à une faute lourde ou dolosive” (The debtor is liable only for damages that were foreseen or that could have been foreseen at the time of the contract, except where non-performance is due to gross negligence or wilful misconduct). In practice, this means the refund of the payment itself follows the automatic statutory regime, while consequential losses follow your contract and the general law of contractual liability, with proof of each euro claimed.

A related but distinct situation is the debit you did authorise but whose amount surprised you — for example a creditor who collected twice once systems recovered, or a direct debit for an amount you had never agreed. Article L. 133-25 of the Code monétaire et financier gives the payer a right to a refund of an authorised transaction ordered by the beneficiary where the authorisation did not specify the exact amount and the amount exceeded what could reasonably have been expected. The request must be made within a strict period: “Le payeur présente sa demande de remboursement avant l’expiration d’une période de huit semaines à compter de la date à laquelle les fonds ont été débités” (The payer shall present the request for refund before the expiry of a period of eight weeks from the date on which the funds were debited). Within ten business days of receiving the request, the provider must either refund the full amount or justify its refusal: “Dans un délai de dix jours ouvrables suivant la réception de la demande de remboursement, le prestataire de services de paiement soit rembourse le montant total de l’opération de paiement, soit justifie son refus de rembourser” (Within ten business days of receiving the request for refund, the payment service provider shall either refund the full amount of the payment transaction or justify its refusal to refund). Check your statements carefully in the weeks after the outage: duplicates and catch-up debits are the classic aftershock of a day-long failure.

Finally, the strongest protection applies if a transaction appears that you never authorised at all — the confusion of a crash being fertile ground for fraud. Article L. 133-18 of the Code monétaire et financier requires the payer’s provider, once informed, to refund the payer immediately and in any event by the end of the first business day following, and to restore the account as if the transaction had never occurred: “le prestataire de services de paiement du payeur 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” (the payer’s payment service provider shall refund the payer the amount of that transaction immediately after becoming aware of the transaction or after having been informed of it, and in any event no later than by the end of the first business day following), and “rétablit le compte débité dans l’état où il se serait trouvé si l’opération de paiement non autorisée n’avait pas eu lieu” (shall restore the debited account to the state in which it would have been had the unauthorised payment transaction not taken place). The European directive uses the same terms: refund immediately and in any event by the end of the first business day following, with the account restored to the state it would have been in had the transaction not taken place. Do not let an outage narrative blur this line: money that left your account on an order you never gave is not a late payment, it is an unauthorised payment, and the next-business-day rule applies.

B. How to claim: report within thirteen months, complain in writing, then turn to the mediator and the courts

French courts apply these provisions strictly, and they place the burden of proof on the bank. Article L. 133-23 of the Code monétaire et financier provides that where a user denies having authorised an executed transaction, or claims a transaction was not correctly executed, it is for the provider to prove the transaction was authenticated, duly recorded and booked, and unaffected by any technical or other deficiency: “il incombe à son prestataire de services de paiement de prouver que l’opération en question a été authentifiée, dûment enregistrée et comptabilisée et qu’elle n’a pas été affectée par une déficience technique ou autre” (it is for its payment service provider to prove that the transaction in question was authenticated, accurately recorded and entered in the accounts and not affected by a technical breakdown or other deficiency). The provider’s own logs are not enough on their own: “L’utilisation de l’instrument de paiement telle qu’enregistrée par le prestataire de services de paiement ne suffit pas nécessairement en tant que telle à prouver que l’opération a été autorisée par le payeur” (The use of the payment instrument as recorded by the payment service provider is not in itself necessarily sufficient to prove that the transaction was authorised by the payer). The court of appeal of Aix-en-Provence applied exactly this reasoning on 9 October 2025 (chamber 3-3, RG no. 21/01687), holding a bank liable for 13,770.37 euros where it could not prove the disputed payments had been made under the customer’s identifiers, even though the bank had managed to recover part of the funds, and ordering a further 3,000 euros for irrecoverable costs. On 14 May 2025, the Paris judicial court (9th chamber, 2nd section, RG no. 24/02342) ordered La Banque Postale to pay 9,000 euros plus interest running from 19 October 2023, with 2,000 euros in costs, holding that without strong customer authentication the payer bears no financial consequence absent fraud. And the Cour de cassation, in a published judgment of 15 January 2025 (Commercial, Financial and Economic Chamber, appeal no. 23-15.437), recalled that where liability is sought for an unauthorised or badly executed transaction, only the regime of articles L. 133-18 to L. 133-24 of the Monetary and Financial Code applies, to the exclusion of any alternative liability regime under national law. The bank cannot therefore answer a failed-payment claim with general arguments about its vigilance; it must answer within the statutory regime, and it must prove its case.

The regime is protective, but it is conditional on one deadline you must not miss. Article L. 133-24 of the Code monétaire et financier requires the user to report an unauthorised or badly executed transaction to the provider without delay and no later than thirteen months from the debit date, on pain of foreclosure (forclusion, the loss of the right to complain): “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” (The payment service user shall report to its payment service provider any unauthorised or defectively executed payment transaction without delay and no later than thirteen months following the debit date, failing which the right to complain shall be foreclosed). For the 20 October 2026 outage, that period runs into late 2027, which seems comfortable — but the earlier you write, the easier the evidence, and related claims such as creditor late fees are best raised while the incident is fresh and documented. Send a written complaint through the app and keep a copy outside the app: describe each failed payment with date, time, amount, recipient and supporting screenshots, state the legal basis in one sentence, quantify the refund and each consequential loss, and set a response deadline. European payment services law requires providers to maintain complaint procedures and to answer users, so send the complaint in writing, keep proof of sending, and set a clear response deadline.

If the answer is a refusal or never comes, the next step provided by statute is the banking mediator (médiateur), with no need for a lawyer at that stage. Article L. 316-1 of the Code monétaire et financier provides that every consumer has the right to have recourse to a mediator for a dispute with a credit institution or payment institution: “Tout consommateur a droit de recourir gratuitement à un médiateur” (Every consumer is entitled to have recourse to a mediator free of charge). Identify the correct respondent before writing: address the Revolut entity that holds your account, as shown in the app, and attach the complaint history and the evidence file. If mediation fails, court proceedings remain available, and the decisions cited above show how French judges handle these files: refund of the payment, restoration of the account, interest, and costs. Bring the complete record — complaint, provider replies, statements showing the failure and any duplicate debits after restoration, creditor demands and proof of amounts paid to stop the loss — because under article L. 133-23 it is the bank that must prove proper execution, but it is you who must prove the loss that goes beyond the payment itself.

Conclusion

The 20 October 2026 failure was, on the established record, a one-day interruption of access caused by a power incident at a Google Cloud facility near London, restored the same evening, with funds and data confirmed safe by the bank and no unauthorised outflow established by any official source. That factual boundary defines the legal one: inaccessibility is not loss, and the claim is for proper execution, not for missing money. For users in France, the European and French payment services regime answers each practical question — the provider’s liability for non-executed or badly executed transactions, refund without delay with a protected value date, the next-business-day refund for anything never authorised, the burden of proof on the bank to the exclusion of any parallel regime, the thirteen-month complaint deadline, the fifteen-day complaint response, and the mediator before the judge. Use that sequence now: screenshot everything, report in writing, quantify each loss, complain, mediate, and only then litigate. An outage lasts a day; a forclosed claim lasts forever.

📄 Official circular