KOHEN AVOCATS FIRM · PARIS 16
Google Cloud Outage Blocked Card Payments: Paying in Cash and Getting Reimbursed 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

Google Cloud Outage Blocked Card Payments: Paying in Cash and Getting Reimbursed in France

Speak to a lawyer 06 89 11 34 45

On Tuesday 20 October 2026, a power incident in a Google Cloud datacenter near London disrupted online services on a massive scale. According to Euronews, which covered the incident the same day, the Revolut application and its services were unavailable for millions of users, with cards refused at the point of sale, and the company announced in the evening that the problem was resolved and the services restored The same report explains that users could no longer access their money or use their bank cards, with cards refused at the point of sale, and that complaints poured in from around the world, including customers in the United Kingdom, Ireland, France, Spain and Japan.

The same Euronews coverage notes that several other British banks also reported disruptions linked to the same failure, and that Google described the incident as a power issue affecting its Cloud platform. The company statements relayed by the press were reassuring: Revolut said that its customers’ funds and data were safe, and Google said the problem had been largely mitigated for most customers. The developments that follow are general in scope: they describe the checks and remedies that are useful in any comparable situation where card payments collapse across France, and they do not describe the situation of Google or Revolut, on which this article makes no finding. No data loss has been established by any official source at the time of writing, liability for any loss remains a matter for the judge, and the contracts signed by each customer take precedence over any general analysis.

This guide answers two practical questions for anyone in France who could not pay by card during the outage: how to pay when terminals are down, and how to obtain reimbursement or compensation afterwards. The first part covers cash payment and proof; the second covers refunds and the courts that can hear a claim in France. All the legal rules below are French rules verified in their official texts.

I. Google cloud outage: how to pay when your card is refused

A. Can a shop in France refuse your cash?

When every terminal displays an error message, cash becomes the fallback. In France, refusing cash is not a matter of shop policy: it is a criminal matter. Article R. 642-3 of the Code pénal provides: “Le fait de refuser de recevoir des pièces de monnaie ou des billets de banque ayant cours légal en France selon la valeur pour laquelle ils ont cours est puni de l’amende prévue pour les contraventions de la 2e classe.” (Refusing to accept coins or banknotes that are legal tender in France, for the value at which they are legal tender, is punished by the fine for 2nd-class petty offences.) A merchant who systematically turns away customers paying in cash therefore exposes himself to a criminal fine, even on a day when his card terminal works perfectly, and all the more on a day when cash is the only means of payment left.

The Cour de cassation has already upheld a conviction on exactly this ground. In a judgment of 3 October 2007 (Crim., no. 07-80.045, rejet), the court approved a lower court which, to find the manager of a company guilty of the petty offence under article R. 642-3 for refusing cash from a customer, noted that the company accepted no cash payment at all, so that the debtor was unable to comply with his own duty regarding change. That duty is stated in article L. 112-5 of the Code monétaire et financier: “En cas de paiement en billets et pièces, il appartient au débiteur de faire l’appoint.” (For payment in notes and coins, it is for the debtor to tender the exact amount.) In practical terms, the customer should prepare the exact amount, because the merchant is entitled to refuse to empty his till for change, but he is not entitled to refuse cash as such.

Cash is not unlimited either. Article L. 112-6 of the Code monétaire et financier prohibits cash payment of a debt above an amount set by decree, depending on the debtor’s tax domicile and on whether the transaction is professional. Article D. 112-3 of the same code sets that amount: “1° Lorsque le débiteur a son domicile fiscal sur le territoire de la République française ou agit pour les besoins d’une activité professionnelle, à 1 000 euros pour les paiements effectués en espèces et à 3 000 euros pour les paiements effectués au moyen de monnaie électronique” (1. Where the debtor is tax-resident in France or acts for professional purposes, 1,000 euros for cash payments and 3,000 euros for electronic-money payments). A higher ceiling of 10,000 euros applies where the debtor proves he is not tax-resident in France, acts for non-professional purposes and pays a person outside the anti-money-laundering perimeter. For everyday purchases during an outage, these ceilings are rarely an obstacle, but for a large purchase they matter: above the ceiling, the buyer must use another instrument, and the seller who accepts cash above the ceiling breaks the prohibition himself.

Three practical consequences follow for an outage day in France. First, withdraw or keep cash early: once the outage is public, cash machines themselves can run dry. Second, tender the exact amount whenever possible, since the duty to make change lies with you. Third, if a merchant refuses your notes or coins while accepting no other working means of payment, note the refusal precisely (time, place, amount, witnesses), because that refusal is exactly the conduct punished by article R. 642-3 as interpreted by the Cour de cassation in 2007.

B. How do you prove you paid when the terminal is down?

Outage days create disputes: the customer says he paid, the merchant says the payment never arrived, or the account shows a debit long after the purchase. French law places the burden of proof on the person who claims performance. Article 1353 of the Code civil states: “Celui qui réclame l’exécution d’une obligation doit la prouver. Réciproquement, celui qui se prétend libéré doit justifier le paiement ou le fait qui a produit l’extinction de son obligation.” (Whoever claims performance of an obligation must prove it. Conversely, whoever claims to be discharged must establish the payment or the fact that extinguished the obligation.) If you claim you paid a shop, a supplier or a creditor while the systems were down, it is for you to prove the payment.

Keep every trace from the moment the terminal fails. Ask the merchant for a handwritten receipt stating the date, time, amount and means of payment, and keep it with the till receipt if one is printed later. Photograph the error message on the terminal or on your banking application, with the time visible. Note the names of witnesses, for example other customers in the queue. Check your account the following days: a card payment that seemed refused can be debited late, and a double debit is possible when the customer tries twice. These documents decide later disputes, because a bare statement that you paid is rarely enough.

Where the dispute is with your own bank, the law reverses the burden in your favour. Article L. 133-23 of the Code monétaire et financier provides: “Lorsqu’un utilisateur de services de paiement nie avoir autorisé une opération de paiement qui a été exécutée, ou affirme que l’opération de paiement n’a pas été exécutée correctement, 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.” (Where a payment service user denies having authorised an executed payment transaction, or asserts that the transaction was not correctly executed, it is for his payment service provider to prove that the transaction was authenticated, accurately recorded and entered in the accounts, and was not affected by a technical or other deficiency.) The Cour de cassation applies this rule strictly. On 18 January 2017 (Com., no. 15-18.102, rejet), it held that although the user must take reasonable measures to preserve the security of his personalised security credentials and inform his provider promptly of any unauthorised use, it is for the provider to prove, under articles L. 133-19, IV and L. 133-23, that the user who denies authorising a transaction acted fraudulently or failed, intentionally or through gross negligence, in his obligations. During an outage, the provider cannot simply point to its own logs: it must show there was no technical deficiency, which is precisely what is hardest to show on a day its systems collapsed.

The same decision recalls your own duties, which condition your protection. Take reasonable measures to preserve your security credentials, never share them, and inform your provider promptly of any anomaly: a payment you do not recognise, a transfer you did not order, an alert that does not match your actions. After every large-scale outage, fraudsters send fake messages pretending to be the bank and inviting customers to “secure” their accounts. If you disclose your codes in response to such a message, the provider may argue gross negligence, and the 50-euro ceiling stated in article L. 133-19, I of the Code monétaire et financier (“les pertes liées à l’utilisation de cet instrument, dans la limite d’un plafond de 50 €” — losses linked to the use of the instrument are borne by the payer up to a 50-euro ceiling) may not protect you. Report first, click never.

II. Getting your money back after the Google cloud outage in France

A. When must the bank refund a failed payment?

Not every failed payment gives rise to a refund: the remedy depends on what actually happened to your money. Three situations must be distinguished. First, the payment was refused at the terminal and your account was never debited: there is nothing to refund, but there may be consequential loss, such as a direct debit rejected the next day for lack of funds, with bank fees, or a contractual penalty for late payment to a supplier. Second, your account was debited but the payee never received the funds: this is a badly executed transaction, and the law orders the bank to restore the money. Third, a transaction you never ordered appears on your account, possibly after phishing linked to the outage: this is an unauthorised transaction, and the law orders a refund by the end of the next business day.

The starting point is consent. Article L. 133-6 of the Code monétaire et financier provides: “I. – Une opération de paiement est autorisée si le payeur a donné son consentement à son exécution.” (I. – A payment transaction is authorised if the payer has given his consent to its execution.) The Cour de cassation added, on 30 November 2022 (Com., no. 21-17.614, cassation), that a transaction initiated by the payer is deemed authorised only if the payer also consented to its amount, and that for an unauthorised transaction reported under article L. 133-24, the payer’s provider must refund the payer. A card payment triggered twice by an unstable terminal, for an amount you never approved, falls squarely within this case law.

For badly executed transactions, article L. 133-22 of the Code monétaire et financier makes your own provider responsible for proper execution towards you until the payee’s provider receives the funds, and states: “Lorsque le prestataire de services de paiement du payeur est responsable, au titre du premier alinéa, de l’opération de paiement mal exécutée, il restitue sans tarder son montant” (Where the payer’s payment service provider is responsible, under the first paragraph, for the badly executed transaction, it refunds its amount promptly). Your bank therefore cannot send you to its own technology provider: as between you and your bank, the bank answers for proper execution under article L. 133-22, and any recourse by the bank against its cloud supplier is a separate matter between them.

For unauthorised transactions, the remedy is even faster. Article L. 133-18 of the Code monétaire et financier provides: “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” (For an unauthorised transaction reported by the user under article L. 133-24, the payer’s provider refunds the amount immediately after learning of it and in any event no later than the end of the next business day, unless it has good reason to suspect fraud by the user and communicates those reasons in writing to the Banque de France.) The report itself is subject to a strict time limit: article L. 133-24 of the Code monétaire et financier requires the user to report an unauthorised or badly executed transaction to his provider promptly “et au plus tard dans les treize mois suivant la date de débit sous peine de forclusion” (and no later than thirteen months after the debit date, failing which the claim is foreclosed). Missing that thirteen-month limit extinguishes the claim, so the written complaint should be sent within days of the outage, not months.

Can the bank escape by invoking force majeure, arguing that the failure came from its cloud provider? French contract law allows the defence in principle: article 1218 of the Code civil defines force majeure as “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” (an event beyond the debtor’s control, which could not reasonably have been foreseen when the contract was concluded and whose effects cannot be avoided by appropriate measures), and article 1231-1 of the same code orders damages for non-performance or delay “s’il ne justifie pas que l’exécution a été empêchée par la force majeure” (unless he shows that performance was prevented by force majeure). But in payment services, the Cour de cassation keeps the special statutory regime separate from ordinary contract liability: on 4 March 2026 (Com., no. 25-11.959, F-B, rejet), it recalled that ordinary contractual liability under article 1231-1 does not apply to a provider’s execution of a payment order in accordance with the unique identifier supplied by the user, while it does apply where the provider goes beyond mere execution. Whether a continent-wide cloud failure meets the three cumulative conditions of article 1218 for a professional payment provider, which is expected to maintain backup systems, is assessed case by case by the judge. Do not accept a blanket refusal stamped “force majeure”: demand a written explanation identifying which condition of article 1218 the bank claims is met, and keep the thirteen-month reporting limit in mind regardless.

B. Which court can hear your claim in France?

Start with a written complaint to your provider, sent as soon as the outage ends. Describe each disputed transaction with its date, time, amount, channel and the error message received; attach screenshots, receipts and witness details; state precisely what you ask for: refund of the debited amount with the correct value date, reversal of fees charged because of the failure, and compensation for any demonstrated additional loss. Ask for a written answer and keep proof of sending. Most disputes end at this stage, because the provider can see from its own incident logs that its systems were down.

If the answer is negative or never comes, consumers have a free remedy before going to court. Article L. 316-1 of the Code monétaire et financier provides: “Tout consommateur a droit de recourir gratuitement à un médiateur […] en vue de la résolution d’un litige qui l’oppose à un établissement de crédit, une société de financement, un établissement de monnaie électronique, un établissement de paiement ou un prestataire de services d’information sur les comptes” (Every consumer is entitled to resort free of charge to a mediator […] for the resolution of a dispute with a credit institution, a finance company, an electronic-money institution, a payment institution or an account-information service provider). Identify the competent mediator from your account agreement or the provider’s website, and file the mediation request with the same file of evidence.

Before a court, the default rule sends the claimant to the defendant’s home court: article 42 of the Code de procédure civile states: “La juridiction territorialement compétente est, sauf disposition contraire, celle du lieu où demeure le défendeur.” (The court with territorial jurisdiction is, unless otherwise provided, the court of the place where the defendant resides.) But consumers benefit from an exception: article R. 631-3 of the Code de la consommation provides: “Le consommateur peut saisir, soit l’une des juridictions territorialement compétentes en vertu du code de procédure civile, soit la juridiction du lieu où il demeurait au moment de la conclusion du contrat ou de la survenance du fait dommageable.” (The consumer may seise either one of the courts with territorial jurisdiction under the Code of civil procedure, or the court of the place where he resided when the contract was concluded or when the harmful event occurred.) A consumer living in France can therefore bring his payment claim before the French court of his home. File the complaint, the provider’s written answer, the mediation outcome if any, and the full chronological file: judges decide on documents, and outage cases are won with timestamps.

Conclusion

Three reflexes decide the outcome of an outage day in France. Pay in cash without fear: a merchant cannot systematically refuse legal-tender notes and coins, prepare the exact amount since making change is your duty, and stay below the statutory ceilings for cash payments. Prove everything at once: written receipts, photographs of error screens, witness names and account statements, because the person who claims payment must prove it, while your bank must prove its systems worked. Claim fast and in writing: report any unauthorised or badly executed transaction to your provider within days, since the thirteen-month foreclosure limit of article L. 133-24 extinguishes late claims; demand refund with the correct value date and reversal of outage-related fees; use the free mediator if the provider resists; and bring the case before the French court of your home if needed, since European law allows it. No data loss was established by any official source for the October 2026 incident, no liability has been determined, and each customer’s contract remains the primary reference. Applied calmly, these steps turn a day without working cards into a documented file that French and European law knows how to resolve.

📄 Official circular