• Unpacking what 'reasonable steps' means in practice under the SPF's core obligations
A scam survivor, a victim advocate and an academic researcher come together to ask a question this framework hasn't answered yet, who is actually guiding the person who's lost the money through it. This session moves from one person's story to the structural gaps still sitting outside the room and closes by asking what "reasonable steps" would look like if the people who lived through unreasonable ones had a seat at the table.
• Hear directly from a scam survivor on what navigating the system after the fact actually looks like, and why reimbursing the loss isn't the same as repairing the harm
• Understand the patterns behind the story: how common these experiences are, and where banks, telcos and platforms consistently fall short
• Explore the blind spots the SPF doesn't cover, from CALD communities to scams that sit entirely outside the framework, like dating apps
• Discuss what a trauma-informed, victim co-designed response could look like, and whether "reasonable steps" should be defined with lived experience at the table
• 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.
• Deployment architecture options for institutions without in-house build capacity
• Sequencing confirmation-of-payee rollout against the 31 March 2027 deadline
• Where real-time detection sits in the evidence chain alongside payee verification
• What 'live' actually requires versus what the major banks have already built
Scammers thrive when industries operate in isolation, exploiting the blind spots between digital platforms, telcos, banks and other industries. This session reveals how a silo-free ecosystem shares real-time intelligence to catch manipulative chats early and stop fraudulent payments at the gate.
• Defining who owns a scam that touches a platform ad, a telco message and a bank payment
• What mandatory AFCA membership changed for complaints spanning multiple entities
• Negotiating an apportionment model when no precedent exists yet
• Building the multi-party IDR (internal dispute resolution) system the cooperation obligation assumes exists
• The SMS Sender ID Register and network-level disruption obligations in practice
• Advertiser verification and pre-publication ad review at platform scale
• Detecting and disabling scam content without decrypting encrypted messages
• Where platform and telco obligations on verification actually overlap
• Building the evidence layer that converts 'compliant' from an assertion into a defensible claim
• Evaluating an AI model's decisions when no regulator has tested it yet
• Building audit trail requirements before deployment, not after an incident
• Who owns the outcome when the model gets it wrong, the team that built it or the business that deployed it
• What organisations across banking, telco and platforms should ask before an AI system goes live
• 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.