When an unknown transaction appears on a Crédit Agricole card statement, the priority is not just to block the card. The real difficulty begins afterward: obtaining a refund, especially when the bank believes that the customer has validated the transaction via their banking app. This article measures the discrepancies between what the Monetary and Financial Code imposes on the bank and what it actually opposes to the cardholder.
Dispute period and obligation to refund: what the Monetary and Financial Code provides
| Criterion | Unauthorized transaction (fraud) | Authorized but disputed transaction (commercial dispute) |
|---|---|---|
| Deadline to report | 13 months from the debit | 8 weeks from the debit |
| Obligation to refund by the bank | Yes, no later than the next business day after notification | Not automatic, examined on a case-by-case basis |
| Franchise remaining the responsibility of the customer | None if the payment was made without strong authentication | Not applicable |
| Frequent reason for refusal | Severe negligence by the cardholder | Dispute out of time |
The table above summarizes the fundamental distinction. When a fraudulent transaction is reported within the deadlines, the bank must refund, unless it proves that the customer acted with severe negligence or fraudulently. The procedure described on the Finance Guide website details the steps specific to the Crédit Agricole card.
In contrast, for a purely commercial dispute (product not received, subscription not canceled), the mechanism differs: it is a chargeback, a procedure managed by the card network (Visa or Mastercard), and not an automatic right to a refund.

Severe negligence of the customer: how the bank refuses a refund for card fraud
The notion of severe negligence is the main lever used by banks to refuse a refund after a fraudulent transaction. Crédit Agricole, like other institutions, can invoke this reason as soon as strong authentication (validation via the Ma Banque app, SMS code, SécuriPass) has been recorded on the disputed transaction.
The reasoning is as follows: if the system shows that a security code has been validated from the customer’s phone, the bank considers that the transaction was authorized. It deduces that the customer either communicated their credentials or validated the notification without reading it.
Involuntary validation in the banking app
Several scenarios lead to a validation that the customer did not consciously give. A phone call from a fake bank advisor asking to “confirm a block” on the app, a push notification validated reflexively during a phone manipulation, or even remote access to the device by malicious software.
A validation in the app does not prove that the customer consented to the payment. The burden of proof of severe negligence lies with the bank, not the customer. This point is explicitly provided for by the Monetary and Financial Code: it is up to the institution to demonstrate that the holder acted with characterized negligence.
Differentiating strong authentication and informed consent
Strong authentication (SécuriPass, biometric validation) proves that a device registered in the name of the customer was used. It does not prove that the customer read, understood, and accepted the details of the transaction. This distinction is crucial for disputing a refund refusal.
- Check in the history of the Ma Banque app if the validation notification clearly mentioned the amount and beneficiary of the disputed transaction
- Keep screenshots of the push notification history and timestamps of calls received on the day of the fraud
- Request in writing from the bank to provide technical proof that the validation was indeed performed voluntarily, and not just a record of authentication on the device
The bank must prove negligence, not simply assume it based on an authentication log.
Disputing a refund refusal from Crédit Agricole: concrete recourse
If the written complaint to the agency and then to the Crédit Agricole customer service does not succeed, several avenues for recourse exist before considering legal action.
The first step is to contact the banking mediator. For Crédit Agricole, this is the mediator with the French Banking Federation or the mediator specific to the regional branch. The referral is free and suspends the limitation period. The mediator issues an opinion within a generally shorter timeframe of three months.
At the same time, filing a report on the Perceval platform (accessible via Service-Public.fr) strengthens the case. This report does not directly trigger a refund, but it constitutes an official document attesting to the fraud declaration to the authorities.

Building a strong case against the negligence argument
- Write a registered letter with acknowledgment of receipt detailing the precise chronology: time of the disputed transaction, time of the possible fraudulent call, time of discovery
- Attach the Perceval receipt, annotated account statements, and any correspondence with the Crédit Agricole fraud service
- Cite articles L133-18 to L133-24 of the Monetary and Financial Code, which frame the obligation to refund and the burden of proof
- If the mediator issues an unfavorable opinion, referring the matter to the judicial court remains possible, with a dispute amount often below the threshold requiring a mandatory lawyer
Filing a complaint and the Perceval report do not replace the written dispute with the bank, but they document the fraud in a legally binding manner.
Blocking Crédit Agricole card and securing the account: act before disputing
Before any dispute process, blocking the card remains the priority. Crédit Agricole offers several channels: the Ma Banque app allows you to temporarily block the card in seconds, the interbank server is accessible at all times, and the agency can intervene during opening hours.
Blocking the card is not enough if the online banking credentials have been compromised. Changing the password for the client area, deactivating and then reactivating SécuriPass, and checking that no unknown transfer beneficiary has been added are complementary measures to take on the same day.
The time between discovering the fraud and formally notifying the bank matters. Any fraudulent transaction reported within 13 months must be refunded, but a quick report reduces the risk that the bank will invoke a lack of vigilance. A bank statement checked every week, combined with payment alerts activated in the app, remains the most effective preventive measure to spot a suspicious transaction before it multiplies.



