Home/Letters/RC/FP/2026/T.31

Letter from the table · RC/FP/2026/T.31

Letter from the table: The transfer I could not take back

Valentina Pérez explains the safeguards she built after a deceptive payment request cost her CLP 1,480,000, and why she supports a common fraud standard.

Valentina PérezContributor · Fair Play Council · ChileSantiago, Chile
Fair Play13 September 2026Supports
3 pages · US Letter

Use Readable text for larger type, or zoom in on the pages.

Fair Play Council

RC/FP/2026/T.31published

Letter from the table: The transfer I could not take back

To the Fair Play Council

I support FP-001 because I learned how much of the work of preventing payment fraud can be pushed onto the person who has already been deceived. I am writing from Santiago, where my business is small enough that one missing payment can change the whole month. I will not name it here. What matters is the set of habits I built after a transfer I approved turned out not to be a payment to the person I intended.

On 18 November 2025, I received an email in an existing conversation about an invoice. It said that the recipient’s bank details had changed. The message looked ordinary: the thread was familiar, the amount matched what I expected, and the new account details were included in the same way as the earlier invoice. At 10:14 in the morning, I made a bank transfer of CLP 1,480,000.

Not long after, I contacted the supplier through a phone number I already had, rather than replying to the email. They told me they had not changed their account and had not received the money. That was when I understood that the email conversation had been interfered with. I called my bank, reported the transfer as suspected fraud and asked for the payment to be recalled. I also sent the information the bank requested and made a report to the police. The bank could ask for the money to be returned; it could not make the receiving account give it back immediately. The money was not recovered.

I do not want to pretend that every institution I contacted was indifferent. I was given instructions and a case reference. But the urgent question for me was simple: could the money be stopped before it disappeared? I had no clear way to see whether the recall request had reached the receiving institution, whether it had been acted on, or what would happen next. A case reference is useful for keeping records. It does not pay the invoice a second time.

RC/FP/2026/T.31Page 1 of 3
Fair Play CouncilRC/FP/2026/T.31 · Continued

I looked at Chile’s Law No. 20.009, as amended, because I wanted to understand what protections might apply. I did not treat it as a promise that I would automatically be reimbursed. The transaction had been authorised by me, even though I had been misled about the recipient. The rules for unauthorised use of payment instruments and electronic transactions did not give me a simple answer to the immediate problem of recovering a transfer I had personally sent to the wrong account. I also understood that the Comisión para el Mercado Financiero has a supervisory role, but that raising a complaint with the regulator is not the same as an instant payment recall.

While waiting for any answer, I changed how I worked. I stopped accepting new bank details by email, even when a message appeared inside a familiar thread. If a supplier says its account has changed, I now call a number already saved in my contacts or printed on an earlier document. I do not use a phone number or link supplied in the change request. I ask a second person to check the account details before a transfer above CLP 300,000. If I cannot do that, I wait. I also keep a short written log of the time I sent a payment, the time I reported it and the case number. Those steps slow me down. They are the safeguards I could create for myself.

They are not a complete fix. A business owner can check, call and keep records, but cannot see what is happening between the sending and receiving payment providers. Nor can a small team maintain a perfect verification process every time an urgent invoice arrives. The people running small businesses are already doing several jobs at once. A fraud standard should not assume that a warning message or a customer’s carefulness can replace action by the institutions that move and receive the money.

That is why I support FP-001. I want payment providers to make a meaningful check that the payee name matches the account details before a payment is made, and to give customers a clear warning when it does not. If a customer reports a suspected fraud, the providers should act quickly to request a recall, share the information needed to trace the payment, and explain the status in language a small business can use. Where a business has been deceived into authorising a payment, there should be a fair route to reimbursement rather than an assumption that authorisation means the loss must stay with the victim. Cross-border payments should not be left outside the conversation simply because recovery is harder.

RC/FP/2026/T.31Page 2 of 3
Fair Play CouncilRC/FP/2026/T.31 · Continued

I know a standard cannot promise that every transfer will be recovered. But speed matters. A recall request made promptly should not disappear into an invisible process, and a small business should not have to invent its own rules for a crisis that payment providers see repeatedly. My new checks have reduced the chance that I will repeat the same mistake. They have not restored the money I lost, or given me the power to reach the receiving provider myself. I support a common standard because those protections should not depend on how much time, technical knowledge or bargaining power one business happens to have.

Respectfully,

Valentina PérezContributor · Fair Play CouncilSantiago, Chile

RC/FP/2026/T.31Page 3 of 3

Replies 4

Luciana Carvalho Curitiba, Brazil · 15 September 2026

I recognise the pressure you describe, Valentina. In Brazil, small firms often handle invoices and supplier conversations through email or messaging, and a familiar thread can make a changed account seem routine. I now treat any request to alter payment details as a new instruction, even when it arrives in an old conversation. I call a number saved before the request, and I do not rely on contact details included in the message. That takes time, but so does trying to recover a transfer.

Miguel Nogueira Faro, Portugal · 18 September 2026

I agree that the person who has been deceived should not be left to carry the whole burden. In Portugal, I have seen how quickly a normal invoice can become a stressful decision when a supplier is waiting and the payment deadline is close. The transfer may be properly authenticated while the intended recipient is not the person who receives it. I would like a common standard to require prompt, coordinated recall efforts, with clear updates to the customer rather than silence after a report is made.

Rana Abu Rumman Amman, Jordan · 22 September 2026

Your account of checking with the supplier through a number you already had is an important practical detail. In Jordan, I have learned to keep trusted contact information separately from invoice emails, because a reply within a genuine-looking thread may not be trustworthy. I also wonder whether banks could make reporting simpler at the moment a customer suspects a transfer is fraudulent. What information should a person have ready, and who should explain the next steps? A standard should make that process understandable, not another burden.

More from the Fair Play Council

Spotted a factual error on this page? Tell the Secretariat.