No. 07Week of September 23, 2026This week’s briefing
Tradecraft

This week’s issueNo. 07 · September 23, 2026

Cover storyField guide No. 01

Moving a bank off SMS OTP: the field guide

A step-by-step plan for retiring text-message codes: which flows go first, what replaces them, who owns each step, and what the markets that already did it can teach you.

Read the field guide This week’s briefing

Choose your desk

Tradecraft is organized by the job you do. Pick yours for a reading path, checklists and the rules that apply.

Field guides

Step-by-step playbooks with owners, decision tables and checklists.

Moving a bank off SMS OTP: the field guide

A step-by-step plan for retiring text-message codes: which flows go first, what replaces them, who owns each step, and what the markets that already did it can teach you.

7 steps · 6 min read

Rolling out passkeys to retail banking customers

Passkeys are the phishing-resistant option NIST now accepts at AAL2. Getting millions of customers to use them is a product problem as much as a security one. A rollout plan, from policy to recovery.

6 steps · 3 min read

Shutting down OTP bots: a fraud team’s field guide

OTP bots automate the call that talks a customer into reading out their code. The durable fix is removing the code; until then, context, timing and customer education narrow the window.

5 steps · 4 min read

All field guides Printable checklists

The Wednesday BriefingNo. 07 · Wednesday, September 23, 2026

The UAE’s SMS OTP phase-out is done. What US banks can take from it + 2 more

The UAE’s deadline for retiring SMS and email codes has passed, and NIST’s “restricted” label for SMS is a benchmark US examiners and auditors use. This week’s reading is about what each means for a US bank’s roadmap.

Read the issue Archive

8 exploited vulnerabilities added by CISA this week

Featured buyer’s guideCommercial-intent · Not sponsored · No rankings

SMS OTP alternatives: a buyer’s guide

The options for replacing text-message codes, how to evaluate them and what to ask vendors. We explain approaches; we don’t rank products.

Our owner has a financial interest in a vendor in this category. Ownership & funding · Methodology

  1. Passkeys (FIDO2) Phishing-resistant key pairs bound to the site’s domain; synced passkeys accepted at AAL2.
  2. In-app approval on a registered device The customer confirms a sign-in or payment in the organization’s own app.
  3. Carrier network checks Number verification and SIM-change signals from the mobile operator.
  4. SIM-based cryptographic authentication A key held in the SIM signs the request; newer and carrier-dependent.
  5. Authenticator app codes (TOTP) Allowed at AAL2, but the code can still be phished or read out.

Explainers and dispatches

One question answered well, and the news behind it.

Explainer

Carrier-native authentication, explained: how a SIM can sign a login

Carrier-based authentication verifies a user through their mobile operator instead of sending them a code. The simplest form checks that a request comes from the SIM tied to a phone number; stronger forms use cryptographic keys held in the SIM to sign the request.

Explainer

The FCC’s SIM-swap rules: what carriers now have to do

The FCC’s 2023 order (FCC 23-95) requires US wireless carriers to authenticate customers securely before moving their number to a new SIM or provider, to notify customers of SIM change and port-out requests, and to offer account locks. It does not regulate how banks or apps use SMS codes.

Dispatch

Inside BSP Circular 1213, the Philippines’ OTP rule

Bangko Sentral ng Pilipinas Circular No. 1213 bars banks and other supervised financial institutions from using SMS or email one-time passcodes to authenticate high-risk transactions, starting June 25, 2026.

Regulations

Singapore, Malaysia, the UAE and the Philippines have ordered banks off SMS or email codes for some or all transactions since 2022. India's 2025 RBI rules, in force April 2026, open the door to alternatives.

Open the tracker Download CSV