• Unpacking what 'reasonable steps' means in practice under the SPF's core obligations
• Defining the named senior accountability the governance obligation requires
• A named designated entity walks through their live SPF program from the inside — governance stand-up, control build and code-readiness roadmap
• Converting $50 million per-contravention penalty exposure into a board-approved funding case
Twenty minutes, back-to-back vendors, zero slides — a rapid lap of the technology shaping SPF compliance right now.
Morning Networking Break - thirty minutes to trade notes with
Small-group, facilitator-led roundtables — no slides, no stage. Each one opens with a live operational challenge and spends the session working out how designated entities are actually solving it, with the relevant vendor category in the room to react in real time.
How much customer friction a control can defensibly add before it undermines the obligation, and where transaction-level detection sits in the evidence chain
What changes operationally now the register is live, and where network-level blocking hits its limits
Calibrating onboarding and ongoing verification against the mule-account detection obligation without over-verifying low-risk customers
The build-versus-buy decision facing ADIs without major-bank infrastructure budgets, and what 'wait' actually costs
Why detection and takedown speed diverge in practice, and building an intelligence pipeline that meets the 'actionable' bar the SPF sets
Turning the cross-sector cooperation obligation into an actual operational contact model
Sixty minutes to debrief the IDGs, keep the morning's conversations going, and build the relationships that turn compliance obligations into shared solutions. VIP Lunch runs concurrently — a curated, guest-list-led room for the summit's most senior designated-entity leaders. By invitation only.
Confirmation of Payee at National Scale
• Calibrating warnings, holds and declines against real fraud-loss data
• What 'immediately' actually means operationally for a receiving bank
• Implementation sequencing for carriers, CSPs and messaging aggregators
• What 'additional rigour' means under the Digital Platforms Code in practice
• Detecting and disabling scam content without decrypting encrypted messages
• Building the evidence layer that converts 'compliant' from an assertion into a defensible claim
• Navigating a fragmented vendor landscape against an unsettled code
• Pulling the day's threads together across governance, funding, detection and evidence
A day of live intelligence, hard conversations and new connections — the room stays open to keep all three going.