Executive roundtable · New York · By invitation
An invitation-only executive roundtable on agents at your front door
AI agents already log in, open accounts, and shop for your customers. Attackers send agents too, and theirs look the same. That changes who you're selling to, where fraud gets in, and what your front door has to prove. An afternoon in New York with bank leaders who own the same decision: ten minutes from us, four discussions led by the table, then dinner.
- Monday, December 7, 2026
- 3:00 to 5:30 pm ET, then dinner nearby
- JPMorgan Chase offices, New York · exact location to follow
Hosted by
Jose BaltazarChief Business Operations Officer, Incode
Roman KarachinskyChief Product Officer, Incode
Why now
Your login checks what an agent has. It needs to know who sent it.
Gartner expects 70% of customer journeys to begin and end with a third-party assistant by 2028. Block agents, and customers take their business elsewhere. Let them in blind, and fraud gets in with them.
A password, a device, and a one-time code can all be stolen or handed to an agent. The one proof an attacker can't steal is a live person. Incode verifies that person and ties each agent to them.
That isn't a fraud team's problem alone. It decides whether you win the customers who shop through agents, how much loss you absorb while the controls catch up, and how much friction your real customers put up with in the meantime. Every leader in this room is working out the same trade-off.
Source: Gartner, cited in Incode agentic platform briefing, October 2026
How the roundtable works
A conversation among peers, with two ground rules
Nothing is recorded or published. What's said can be used; who said it can't. Within a week, attendees receive shared notes without names attached. You're the leaders in this field; we're here to host the conversation about the parts of agentic security no one company can dictate alone.
A small table, one or two seats per company, for senior leaders at banks in digital, fraud and risk, payments, and customer identity. The banks in the room compete, so every question asks how you think, never for your secret sauce. We don't admit vendors or press.
Agenda · All times ET
Ten minutes from us, then four discussions led by the table
The pre-read covers the problem, so we won't retell it. Incode speaks for about ten minutes. The rest is four discussion blocks, each opening with one sentence on how we're thinking about it and then a question to the room, with a break in the middle and dinner nearby to close.
-
3:00 pm01 · 15 minutes
Welcome and ground rules
Jose sets the tone and the ground rules, then round the table: name, role, and the agent question keeping you up at night.
-
3:15 pm02 · 10 minutes
How we're thinking about it
Roman, one slide: how we see the problem and the approach. A short demonstration only if the room hasn't seen it.
-
3:25 pm03 · 30 minutes
Detection strategy: from blocking to allowing
Where the industry is on blocking agents versus allowing them, what would move it, and the biggest bottlenecks today.
-
3:55 pm04 · 30 minutes
Legacy platforms and integration
Where an agent decision would live in a legacy stack, what makes new controls hard to add, and what a workable integration path looks like.
-
4:25 pm10 minutes
Break
-
4:35 pm05 · 25 minutes
Consumer and individual accounts
Which retail journeys agents reach first, consent and limits for the customer behind the agent, and customer experience versus control.
-
5:00 pm06 · 25 minutes
Business and commercial banking
Whether agentic is different on the business side, treasury and payables automation acting as agents, and who is accountable when a company's agent acts.
-
5:25 pm07 · 5 minutes
Close
What we heard: the three or four themes in common, and what, if anything, the group wants to do together next.
-
5:30 pmonward
Dinner nearby
The conversation continues over dinner for everyone at the table. Final details to be confirmed.
What we want to hear from you
One question opens each block
The banks in the room compete, so every question asks how you think about the problem, never for your secret sauce. These go out with the pre-read.
-
01
You can't set a policy for agents you can't see, so detection comes first. Is that the right order for the industry?
Detection strategy. Is the industry moving from “block all agents” to “allow some,” and what would need to be true first?
-
02
Agent controls have to sit alongside existing authentication and fraud systems, not replace them. Where does that decision belong in a typical bank stack?
Legacy platforms. Build, buy or extend what exists, and what typically slows a bank down when adding a new control.
-
03
Every agent acting for a customer should trace back to a verified person and the limits they set. Is that the right anchor?
Consumer accounts. How much friction customers will accept to keep their agents working, and how accountability works when a delegated agent makes a mistake.
-
04
Business banking may need the same anchor, with roles and approvals layered on. Is the business side a different problem or the same one?
Commercial banking. How entitlements and approvals extend to agents acting for a company, and what the industry should agree on before each bank builds its own answer.
Who is in the room
The people who decide whether an agent gets in, and what it costs if they are wrong.
Senior leaders from large US banks in digital, payments, fraud and risk, and customer identity, across consumer and commercial banking. Everyone at the table is deciding what an agent has to prove before it can log in, move money, or change an account, and everyone faces the same adversary: agentic fraud.
If a colleague should be at the table with you, say so when you confirm. We'd rather have the right two people from your company than one from somewhere else.
What you take with you
A clearer decision, and the people to call about it.
The pre-read: an executive briefing on agents at the front door, sent before the session
Shared notes within a week, without naming who said what
An early look at the draft specification for agent credentials and mandates
A direct line to Incode's leadership, and to the peers around the table
By invitation only · agentic@incode.com
If you were invited, the seat is yours. Tell us who's coming.
We confirm within a business day with the venue details, the final agenda, and the dinner plan. Not sure it's right for you? Email agentic@incode.com or reply to whoever invited you.