BSP Circular 1213: when an SMS OTP is not enough
Larger banks and e-wallets had until late June to stop relying on SMS and email codes for high-risk transactions. Why an office's approvals should follow.
Published · 4 min read

In the week of 22 June, a deadline set by the Bangko Sentral ng Pilipinas (BSP) arrived for the banks and e-wallets that handle the most money online: one-time passwords sent by SMS or email were no longer enough for high-risk transactions, such as enrolling in online banking, sending money to someone else's account or changing a registered phone. The rule is BSP Circular No. 1213, and it gives its reason plainly: codes that can be shared with, or intercepted by, someone outside the transaction are what social engineering is after. If the central bank will not trust a text message to approve a high-risk transfer, an office should not trust one to approve a payment in its own systems.
What the circular requires, and from when
The Monetary Board approved the circular on 22 May 2025 and the governor signed it on 30 May, to carry out part of the Anti-Financial Account Scamming Act, Republic Act 12010. It tells every institution the BSP supervises to limit codes sent by SMS and email. Those offering complex electronic services, with online transactions averaging at least ₱75 million a month, must adopt strong authentication instead: biometrics such as a fingerprint or a face, behavioural signals such as typing patterns, passwordless methods such as FIDO security keys, or checks that adapt to the device and location. Lower-risk transactions, such as checking a balance or paying a recipient already registered, can still use an SMS code, the Daily Tribune reported.
The date needs a note, because the sources disagree. The circular sets no calendar deadline: it took effect fifteen days after it was published in a newspaper, and gives institutions a year from then. GMA News and the Daily Tribune, both carrying the BSP's statement, gave the deadline as 25 June 2026. The authentication vendor Authsignal had written in March that it was 30 June.
Why an office should borrow the rule
Most offices are not supervised by the BSP, but their finance staff meet the circular in corporate online banking, and their own systems have the same weak point. In an office, the high-risk steps are approving a payment, adding a supplier or an employee to be paid, changing the bank account money goes to, and making someone an administrator. If any of those rests on a code sent by text or email, a caller posing as IT or the bank only has to persuade one person to read it out.
The circular also asks institutions to pause transactions for 24 hours after a key account change, such as a new mobile number, email address or registered device, unless strong authentication lets them shorten it. That one is worth copying. When the bank account on file for a supplier or an employee changes, a system can tell the person at their old contact details and hold payments for a day, so that a change somebody else made has time to come to light.
I have built payment steps into systems, card and e-wallet payments on a valet storage platform among them, and I connect systems to PayMongo, Stripe and PayPal. I have not worked inside a bank or any BSP-supervised institution, and how a bank meets this circular is for the bank to say. What carries over is the office's own side of an approval workflow: who may approve a payment, how they prove it is them, and a record of each step.
Five checks for your own approvals
- List every step in your systems that moves money or changes where it goes: approvals, new payees, changed bank details, new administrators.
- Move those steps, and every administrator login, from SMS codes to a passkey or a security key, which cannot be read out to a caller, starting with the people who approve payments. An authenticator app is a step up where those are not yet possible.
- When bank details on file change, notify the person at their old contact and hold payments to the new account for a day.
- Check that whoever runs payroll has set up what your bank now asks for well before pay day, since a newly registered phone can mean a pause of up to a day.
- Tell staff in writing that nobody from IT, the bank or management will ever ask them for a code.
If an approval in your own system still rests on a text message, it is worth changing before somebody tests it, and the fit check is a good place to raise it.
Sources
- Bangko Sentral ng Pilipinas, Circular No. 1213, Series of 2025: Amendments to Regulations on Information Technology Risk Management to Implement Section 6 of the Anti-Financial Account Scamming Act (AFASA), 30 May 2025
- GMA News, No more SMS, email OTPs for high-risk financial transactions starting June 25, 24 June 2026
- Daily Tribune, BSP: No more SMS, email OTPs, 25 June 2026
- Authsignal, BSP Circular 1213: Philippine banks must replace SMS OTPs by June 2026, 17 March 2026
Enrique Lacambra III builds internal business systems from Cainta, Rizal.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
