Chapter 18: The First Contact with the Bank: What to Say and When

The first few seconds after discovering a scam are moments of chilling, profound silence. This is the moment the smokescreen dissipates and reality hits you with the force of a freight train: the money is gone. That phone call from the "bank," that SMS from the "credit card company," that polite representative who only wanted to "verify details"—they were all part of a well-orchestrated play where you were the lead actor, and the audience was empty. All at once, your self-confidence is replaced by profound shame, and common sense is pushed aside in favor of raw panic.

But precisely at this moment, when your heart rate is racing and your hands are shaking, you need the composure of a heart surgeon. The first contact with the bank is not just an attempt to save what remains; it is the cornerstone of future case management. Every word you utter in this recorded conversation, every phrasing you choose, and every minute that passes from the moment of discovery until the report, may be scrutinized under a magnifying glass by the bank's legal department, and sometimes by legal tribunals. In this chapter, we will learn how to manage this dialogue, what words might complicate your position, and how to turn the initial report into a powerful, professional tool.

The following scenario is an educational example based on common fraud patterns. The characters and events are for illustration purposes only.

The Silent Phone: An Educational Scenario

Itzhak (a pseudonym), a retiree, was sitting on his porch when he received the call. The phone screen displayed the name "Bank Security Center." The voice on the other end was authoritative yet reassuring. "Mr. Cohen, we have detected an unusual withdrawal attempt from your account abroad. We need you to provide the code you received via SMS so we can block the transaction immediately." Itzhak, fearing for his life savings, did exactly what was asked. He read out the six digits, and the representative thanked him politely and said, "Everything has been handled, your account is now secure. Do not access the application for the next 24 hours so as not to disrupt the security process."

Three hours later, a nagging gut feeling wouldn't let him be. He ignored the "representative's" instruction and logged into the application. The account was empty. A significant sum had vanished in four separate transfers to beneficiaries he had never heard of. Itzhak immediately called the real bank's call center. "They stole my money!" he told the agent, "You called me earlier and I gave you a code, why didn't you stop it?"

The bank agent asked one critical question: "Sir, did you provide the code of your own free will?" Itzhak, in a state of emotional distress, replied: "Yes, because I thought it was you!" This word "yes" was recorded in the system. In a possible scenario, the bank might use this answer to claim later that the customer acted with "gross negligence" and attempt to shift the responsibility for the damages onto him. The conversation might end with the agent's promise to "look into the matter," but without the correct action, the chance of recovering the funds could be significantly compromised at the preliminary stage.

A Race Against the Clock: The Importance of Immediate Reporting

Israeli law, and specifically the Payment Services Law, 2019, imposes an active duty on the customer: to report any incident of "misuse" or unauthorized transaction as soon as they become aware of it. Time is a critical component. Delay is one of the greatest challenges facing anyone who has fallen victim to fraud.

Why is speed so critical? First, from a technical perspective, bank transfers—especially transfers within the banking system or Real-Time Gross Settlement (RTGS)—are executed quickly. If you act within minutes, there is a chance the bank can attempt to stop the money in the recipient's account before it is withdrawn or transferred further. Second, from a legal perspective, a late report may allow the bank to argue that had the report been made on time, the damage could have been prevented or mitigated. An unjustified delay may affect the allocation of liability.

But speed is not the only factor. The manner in which you report is just as important as the timing. Many customers tend to blame the bank in the first conversation, or alternatively, express regret for their actions. These approaches can be complex to manage later on. The first conversation must be factual, relevant, and goal-oriented.

What to Say and What Not to Say: Highlights for the First Call

When dialing the bank's call center, it is important to remember that the agent is documenting the details. Here are several rules recommended for adoption:

• Avoid the word "voluntarily": Even if a code was provided, it was usually done under false pretenses, deception, and fraud. The more accurate phrasing is: "I was defrauded," "I was misled into believing it was a bank representative," or "A transaction was performed on my account without my actual authorization."
• Demand an immediate freeze: It is important to demand: "I request an immediate freeze on any outgoing activity from the account and to attempt to cancel the recent transfers made without my consent."
• Document the conversation: Whenever possible, try to document the details of the conversation, note the agent's name, the exact time, and the reference number. This documentation may be significant down the road.
• Focus on the unauthorized transaction: The law defines an "unauthorized transaction" as a transaction performed without the customer's consent. You can emphasize: "I did not authorize the transfer of money to this beneficiary. This transaction is unauthorized."

The Legal Framework: Payment Services Law and Financial Institution Liability

To understand how to conduct yourself toward the bank, it is worth knowing the provisions of the law. The Payment Services Law establishes a starting point whereby if an unauthorized transaction is performed, the payment service provider may be required to reimburse the customer for the transaction amount. At the same time, the law sets exceptions, such as situations where the customer acted with fraudulent intent or in circumstances amounting to "gross negligence."

This is the focus of the professional debate. Banks may attempt to claim gross negligence in cases of providing a one-time code. The professional counter-argument is that sophisticated means of deception (Social Engineering) are often used, intended to lead a reasonable person to believe they are participating in a legitimate action. Liability may also include a duty to identify unusual activity patterns and stop them in real-time.

The bank is sometimes perceived as the "gatekeeper" of funds. There are monitoring systems that are supposed to detect unusual activity, such as significant transfers at unusual hours to unknown accounts. If there is a claim that the bank did not do enough to identify the activity, its liability can be examined in the circumstances of the case. Therefore, the question regarding how the security systems operated in real-time may arise during the conversation.

The Dynamics of Reporting: Internal Processes

After the report, the bank usually begins an internal investigation that includes examining IP addresses, device types, and the money trail. Sometimes the initial response will be that the matter is under investigation, and later, a claim may arise that since a code was provided, the responsibility does not lie with the bank.

It is important to know that this answer is not necessarily the final word. It is often an initial position. Precision in the details during the first conversation is critical. Describing the case as "deception" rather than a "mistake" may influence the ability to examine the recovery of funds later on.

Case Analysis: The Difference in Phrasing

If Itzhak from the educational scenario had managed the conversation differently, it might have sounded like this:

Itzhak: "Hello, I am reporting an unauthorized transaction on my account. I discovered that funds were transferred to beneficiaries I do not know. I request to freeze the account immediately and attempt to cancel the transfers."

Agent: "How did it happen, sir? Did you give a code to anyone?"

Itzhak: "I was subjected to a sophisticated fraud involving impersonation. Someone who deceived me made me believe I was interacting with the bank. The actions performed were not with my approval. I request that all information be preserved."

In this phrasing, the event is defined as fraud and as an action without genuine consent, which may make it difficult to raise a "gross negligence" claim at an early stage.

Recommended Steps After Contacting the Bank

The call to the bank is only the first step. Afterwards, there are additional actions that can be considered:

1. Reporting to the police: Filing a complaint is a standard step in the process. In the description of the event, specify the nature of the fraud—the impersonation and deception.
2. Written inquiry: Beyond the telephone conversation, a detailed letter can be sent outlining the facts and examining the legal options for fund recovery.
3. Collection of documentation: Saving screenshots of SMS messages, a list of incoming calls, and the transfers that were performed.

Professional Advice

During years of professional work, the question often arises: "When is the right time to involve a lawyer?" Examining legal options at an early stage can help in formulating the correct strategy against the bank. Professional guidance can help ensure that the correct legal arguments are raised from the very first moment.

Possibilities for recovering funds can be examined, where the chances depend on the specific circumstances of each case. A lawyer can assist in managing the case professionally and ensure that the customer's rights are upheld against the bank's claims. Sometimes, a professional approach can lead to a re-examination of the case by the bank.

Points to Consider When Dealing with the Bank

During the process, it is worth noting the following situations:

• Statements that providing a code automatically cancels the bank's responsibility are not always legally accurate. Providing a code is one parameter among a range of circumstances.
• Refusing to provide details about the destination account may sometimes complicate the process, but there are professional ways to examine receiving this information.
• Significant delays in providing answers from the bank may require professional intervention to move the matter forward.

General Action Checklist

• Upon discovery: Contact the bank's call center to block the account and cards.
• Initial documentation: Record the details of the conversation with the bank and ensure factual phrasing.
• Reporting to authorities: File a complaint with the police and save the confirmation number.
• Professional review: Consult legal counsel to examine the circumstances of the case and the chances for fund recovery.
• Caution: Avoid further communication with suspicious parties.

Legal Aspect: General Analysis

According to the Payment Services Law, there is a certain framework of liability imposed on payment service providers in the event of unauthorized transactions. To examine an exemption from this liability, proof of intent to defraud or gross negligence on the part of the customer is sometimes required. In legal literature and jurisprudence, there are discussions on whether providing a code in circumstances of social engineering always constitutes gross negligence, and this is usually examined based on the circumstances of the case: the bank's ability to identify the fraud, the existence of warnings in the system, and the customer's characteristics. These are arguments that can be raised as part of managing the case.

The process of attempting to recover funds requires patience and precision. The first contact with the bank is a significant step on this path—and it is recommended to ensure it is done in the best possible way.