Chapter 87: Chapter 87: The Unerasable Footprints – Bank Statements and Call Logs

In the previous chapters of our journey through the depths of digital fraud, we addressed the art of visual documentation. We discussed screenshots as first aid, and saving WhatsApp messages as living evidence of the solicitation process. However, as we step into the legal arena – whether against a bank, or in the context of a police complaint or civil lawsuit – screenshots are merely the outer shell. To build a steel skeleton for a case, one must descend into the deeper layers, those not dependent on the phone’s selective memory or the ability to click "Capture." Institutional evidence is required: bank statements and call logs.

If a screenshot is the "testimony" of what occurred, then bank statements and call logs are the DNA found at the scene. These are documents generated by third parties – banks and telecommunications companies. They carry a stamp of reliability that can be presented in court. In this chapter, we will learn how to turn these paper documents into legal weapons, and how they tell the story that the scammers tried to conceal.

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

Amir (a pseudonym) is a software engineer, a person who lives and breathes technology. One Tuesday at 4:30 PM, while he was immersed in his work, his phone rang. The screen displayed a number purporting to be his bank's customer service center.

"Hello Amir, this is Guy from the bank's security department," said the voice on the other end. The voice was calm and authoritative. "We have detected an unusual withdrawal attempt from your account. Did you just perform a transfer of 12,000 NIS to someone named 'Murad'?"

Amir became anxious and replied in the negative. "Okay, don't worry," Guy continued, "we are blocking the transaction. I have just sent a verification code to your mobile device to confirm it is you so that we can freeze the account. Just read it out to me."

Amir saw the message from the bank. The logo and the sender appeared legitimate, and he read out the code. And then another. Following that, the call was disconnected. When Amir tried to call the number back, he reached the bank's actual call center, where he was informed that no call had been made to him from the security department. Within a few short minutes, Amir discovered that a significant sum had vanished from his account in several installments. The bank, in an initial response, claimed that the transactions were authorized using a code sent to him and that the liability rests with the customer.

During the years of professional practice for an attorney working in this field, it appears that the first stage in such cases is not merely a telephonic dispute with the bank, but the summoning of "hard evidence": complete account statements and itemized lists of incoming and outgoing calls from the cellular provider.

Chronicle of the Embezzlement: Analysis of the Bank Statement as a Timeline

A bank statement is much more than a list of numbers. In the forensic analysis of fraud, it is a roadmap. In Amir's scenario, a standard statement is insufficient; a "detailed transaction statement" is required, including the exact hour and minute of the transaction, the reference number, and the full details of the beneficiary.

When analyzing such a statement, the data begins to provide a clear picture. If it is observed that transfers were executed at a specific time, this information can be cross-referenced with call logs. If the bank transaction was performed exactly while the client was on the line with the "bank representative," this serves as an indication that the client was under influence or real-time manipulation.

Furthermore, the bank statement may reveal the identity of the beneficiaries. In cases of fraud, money sometimes passes through "mule accounts" in the country, which serve as a transit point. The detailed statement provides their names and account numbers, information that is essential for the police to attempt to locate and freeze the funds.

It is important to understand: regulatory provisions require banks to monitor suspicious activity. When a bank statement shows a sequence of high-value transfers within a few minutes to new accounts, a legal question may arise regarding the effectiveness of the bank's monitoring systems. The statement is the tool for proving a pattern of suspicious activity.

Types of Bank Documents That May Be Requested

Beyond the screenshot, the following documents may be examined:

• Historical transaction statement: Including precise execution timestamps.
• Full beneficiary details: Name, bank number, branch, and account number of the recipient.
• Documentation of account setting changes: Verification of whether the daily transfer limit was increased or a new device was added to the SMS service near the time of the incident.
• Account access log: A list of IP addresses from which the account was accessed. If the IP does not match the client's location, this may indicate a security breach.

Call Details: The Silent Witness That Does Not Lie

In this study scenario, the significant evidence is the call detail record. Scammers sometimes use "Spoofing" technology, which causes the bank's number to appear on the display. However, an official call log from the cellular service provider may present different data.

A distinction must be made between an "outgoing call log" and an "incoming call log." While an outgoing log is easily accessible, obtaining an incoming call log may require specific procedures or a legal demand depending on the circumstances. In Amir's scenario, the call log showed a prolonged incoming call at the time the account transactions were executed.

Cross-referencing the times between the call log and the bank statement may create a picture where the banking transactions were carried out under the telephonic instruction of an impersonator. Such an analysis could form the basis for legal claims under the Payment Services Law, 5779-2019, regarding an "unauthorized transaction."

What can be learned from the call logs?

The call detail record provides important technical data:

1. Call Duration: A lengthy call may indicate a "social engineering" process and the pressure to which the victim was subjected.
2. Network Identification: It is sometimes possible to identify whether the call originated via an internet-based network (VoIP) or through an international gateway.
3. SMS Messages: The log indicates the exact time of receipt of verification codes, allowing for an examination of the temporal proximity to the execution of the transfers.

Legal Aspect: Payment Services Law and Burden of Proof

In the context of a legal analysis, banks may raise a claim of "gross negligence" on the part of the customer who provided the code. However, the Payment Services Law provides certain protections for the consumer.

Section 20 of the Law stipulates that if an "unauthorized transaction" was performed, liability may be imposed on the payment provider, unless it is proven that the customer acted with gross negligence or fraudulent intent. Bank statements and call logs are used to examine whether the customer was a victim of sophisticated manipulation that even the bank's systems did not timely identify.

In the context of legal representation, these documents can be used to construct a "timeline" that illustrates the connection between the phishing call and the sequence of irregular transfers, and to examine whether the bank fulfilled its monitoring obligation.

Case Study: When the Numbers Tell the Truth

In Amir's scenario, a table can be presented cross-referencing the call detail logs with the bank statement timestamps. It can be demonstrated that while the client was on the call, account access occurred from a new device or an unrecognized IP address.

The legal argument may focus on the fact that had the bank identified the correlation between the data in real-time, the damage could have been avoided or mitigated. The objective evidence transforms the case into a technical analysis of response times and professional liability.

How can evidence be obtained?

The manner in which evidence is collected is of great importance:

1. Official Transcript Requirement

It is recommended to request official and signed documents from the bank. This assists in preventing future claims regarding the authenticity of the document.

2. Itemized Incoming Calls

Since mobile operators do not always provide this data in the standard itemization, legal procedures such as a request for disclosure of information or a judicial order may be required. It is important to act quickly as the information is retained for a limited time.

3. Cross-Referencing

It is recommended to consolidate all data chronologically:
16:30 – Incoming call initiated.
16:32 – SMS message received with code.
16:34 – First transfer on bank statement.

This action assists in accurately reconstructing the timeline of events.

Warning Signs in Bank Statements (Post-Factum)

Even after the incident, one must continue to monitor statements due to the risk of future unauthorized use of account details:

• New Standing Orders: Check whether unauthorized direct debit mandates have been established.
• Change of Contact Details: Verify with the bank that the contact details for sending notifications have not been altered.
• Pending Transactions: Monitor future activities that have not yet been settled, which may allow for stopping funds at the last minute.

Practical Steps for Case Review

1. Formal request to the bank: A demand for complete transaction documentation including IP addresses and precise timestamps.
2. Request to the cellular provider: A request for itemized call and message logs (excluding content) for the purpose of documenting times.
3. Preservation of physical records: Records made in real-time may serve as part of the chain of custody.
4. Filing a police report: The police will require these printouts for the purpose of investigating the matter.

Legal Aspect: Liability of Banks in Israel

Israeli law and jurisprudence impose upon banks a duty of care toward their customers. When suspicious circumstances exist, the bank is expected to take measures to verify the transaction. The combination of the bank statement and the call log is the foundation for examining claims regarding bank negligence.

However, it is important to remember that each case is examined on its own merits and that there is no prior guarantee of recovering funds. Courts also examine the customer's "contributory negligence" under the circumstances of the matter. Accuracy in gathering evidence is intended to maximize the legal prospects of the case.

In the next chapter, we will continue to delve into the world of digital evidence and discuss call recordings – the legal rules and the ways to use them as evidence.