Pat Kinsel on Proof's X401 protocol for AI agent identity and payment authorization
Summary
Pat Kinsel, Founder & CEO of Proof, discusses the cybersecurity challenges of AI agents in commerce, particularly deepfakes and unauthorized transactions. He argues that current KYA (bot detection) is insufficient for legal authorization in regulated industries like finance. Kinsel introduces X401, an open protocol for identity layering, and compares Proof's verifiable credentials to EMV chips for cryptographic signing. He highlights the gap between consumer authentication (Google Auth) and financial legal authorization, advocating for step-up authentication and intent mandates. Finally, he notes that stablecoins may become the payment rail for agentic commerce due to micropayment needs.
Episode sections
- 0:00 – 4:00
Introduction and Guest Background
Pat Kinsel discusses the cybersecurity threat of AI agents bypassing website blocks via phone calls and the need for real identity authorization. Simon Taylor introduces the episode, guest Pat Kinsel (Founder & CEO of Proof), and co-host Bam Azizi.
- 4:00 – 4:59
Deepfakes, Cybersecurity, and Identity Challenges
Kinsel explains that remote interactions post-COVID and deepfakes create trust issues in agentic commerce. He mentions Project Glasswing and the difficulty financial institutions face in verifying who is authorizing transactions.
- 4:59 – 6:23
KYA, KYC, and Legal Authorization
Kinsel defines KYA as bot detection and model performance verification, while arguing it is insufficient for legal authorization. He emphasizes that intent mandates and legal authorization are required for regulated transactions like mortgages or wealth management.
- 6:23 – 10:44
Comparing Agentic Commerce Protocols
Kinsel compares protocols from Google (AP2 for payment instructions), Shopify (UPC for catalog indexing), Visa (Tap for agent registration), and Mastercard (Verifiable Intent for signing mandates). He notes all require trusted key issuance, which is Proof's role.
- 10:44 – 15:07
X401 and Verifiable Credentials
Kinsel describes Proof's verifiable credentials as equivalent to EMV chips, enabling cryptographic signing of transaction payloads. He introduces X401 as an open protocol for websites to gate resources and specify required credentials, submitted to FIDO.
- 15:07 – 17:06
Financial Institutions and AI Agents
Kinsel explains that banks are blocking agents due to cybersecurity risks but recognize agents can bypass websites via call centers. He advocates for creating 'happy paths' with granular identity authorization policies instead of blanket blocks.
- 17:06 – 19:39
Intent Mandates and Step-Up Authentication
The discussion covers the need for step-up authentication (SMS, MFA, notarization) for high-value transactions. Kinsel highlights that verifiable credentials provide legally enforceable evidence of intent, satisfying compliance obligations.
- 19:39 – 31:37
Stablecoin Micropayments and Identity
Kinsel notes that stablecoins enable machine-to-machine micropayments without enterprise agreements. He describes Proof's integration with X402 and MPP to allow just-in-time enrollment and payment, combining identity and payment authorization.
- 31:37 – 32:59
Intent Mandates and Agent Handshakes
Pat Kinsel discusses the necessity of signed intent mandates, KYA/KYC integration, and step-up policies for agent authorization. He notes that publishing agent or skills files allows agents to respect site-specific traffic rules, comparing this to establishing customs or handshakes between humans.
- 32:59 – 33:13
x401 Implementation and Resources
Kinsel directs listeners to proof.com/x401 for implementation details, stating the solution is in production and can be stood up for a proof of concept within a day or two.
- 33:13 – 34:16
Podcast Outro and Guest Links
Simon Taylor closes the episode, directing listeners to meshpay.com and Bam Azizi's socials, while promoting his own ventures at brainfood.xyz and tempo.xyz.
Claims worth verifying
Pat Kinsel claims that AI agents can bypass website blocks by calling call centers and pretending to be clients.
Pat Kinsel ·0:00
How to verify: Primary source: Transcript at [00:00]. Verification: Industry reports on AI voice phishing (vishing) and call center security breaches. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
Pat Kinsel states that 70-90% of customer interactions are now remote and digital.
Unidentified speaker (UNKNOWN) ·4:01
How to verify: Primary source: Transcript at [04:01]. Verification: Industry reports on remote banking and digital customer service adoption post-COVID. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
Pat Kinsel mentions Project Glasswing as a cybersecurity initiative by financial institutions.
Pat Kinsel ·4:21
How to verify: Primary source: Transcript at [04:21]. Verification: Search for 'Project Glasswing financial institutions cybersecurity' in news archives. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
Pat Kinsel defines KYA as bot detection and model performance verification.
Unidentified speaker (UNKNOWN) ·5:00
How to verify: Primary source: Transcript at [05:00]. Verification: Industry literature on Know Your Agent (KYA) frameworks. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
Pat Kinsel states Google uses AP2 for signing payment instructions.
Pat Kinsel ·6:44
How to verify: Primary source: Transcript at [06:44]. Verification: Search for 'Google AP2 protocol agentic commerce' or 'Google Agent Payment Protocol'. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
Pat Kinsel states Shopify uses UPC for catalog indexing.
Unidentified speaker (UNKNOWN) ·7:03
How to verify: Primary source: Transcript at [07:03]. Verification: Search for 'Shopify UPC protocol' or 'Universal Product Catalog'. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
Primary sourcePat Kinsel states X401 was submitted to FIDO as an open protocol.
Pat Kinsel ·13:26
How to verify: Primary source: Transcript at [13:26]. Verification: FIDO Alliance website or Proof's public documentation regarding X401 submission. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
Pat Kinsel cites Brian Armstrong saying crypto and stablecoins will be the payment rail for agentic commerce.
Pat Kinsel ·19:40
How to verify: Primary source: Transcript at [19:40]. Verification: Search for Brian Armstrong interviews or tweets regarding 'crypto stablecoins payment rail agentic commerce'. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
AI models like Claude and ChatGPT identify x401 as a leading agentic protocol when asked.
Pat Kinsel ·31:58
How to verify: Query LLMs such as Claude or ChatGPT with the prompt 'what is a leading agentic protocol' and record the output. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
x401 is in production and can be stood up for a proof of concept within a day or two.
Unidentified speaker (UNKNOWN) ·32:59
How to verify: Visit proof.com/x401 and review documentation or contact the company to confirm production status and implementation timeline. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
Agents can respect site-specific traffic rules if the site publishes agent or skills files.
Pat Kinsel ·32:34
How to verify: Test by deploying an agent skills file on a test domain and observing if an AI agent respects the defined constraints. For recent events, verify 2026-08-19 through 2026-11-19. Use another period only when the speaker explicitly names it.
Do your own research
- Verify the technical specifications of the X401 protocol submitted to FIDO by checking the FIDO Alliance documentation.
- Review Proof's production status and proof-of-concept capabilities as claimed on proof.com/x401.
- Compare the capabilities of Google AP2, Shopify UPC, Visa Tap, and Mastercard Verifiable Intent against Proof's verifiable credentials.
- Assess the legal enforceability of 'intent mandates' in regulated financial transactions by consulting relevant banking compliance guidelines.
- Investigate the integration between Proof's identity layer and X402/MPP for stablecoin micropayments.
- Check for any conflicts of interest or sponsorships involving Proof, Meshpay, or the hosts.
- Evaluate the security risks of AI agents bypassing website blocks via call centers as described by Kinsel.
- Research Brian Armstrong's public statements on stablecoins as payment rails for agentic commerce.
Full transcriptexpand
0:00Pat Kinsel: I think what people should understand is these agents, like you may block them on your website, but they know how to make phone calls. So they're calling the call center and they're pretending to be your client, which is an even worse problem. And so most people recognize that they have to create happy paths. Uh those happy paths have to enforce real identity authorization policy. Uh, and that's the right end state.
0:31Simon Taylor: Welcome to Tokenized, the show focused on stablecoins and the institutional adoption of tokenized real world assets. My name's Simon Taylor, head of market dev at tempo, author at Brain Food, and of course back once again with my agentic commerce As co-host, Bamazizi, founder of Mesh. How are you doing, sir?
0:49Unidentified speaker (speaker_2): Good, good, excited for this episode. Thank you, Simon.
0:52Simon Taylor: I'm excited too, because joining us today is Pat Kinsell, who is founder and CEO of Proof. How are you doing, Pat?
0:58Pat Kinsel: Good. Psyched to be here.
0:59Simon Taylor: I'm psyched to have you on because we are talking about not X402, no, no, no, X401, which does sound like some crazy X-Men reference, but it's even more interesting than that, quite possibly.
1:12Pat Kinsel: I was gonna make an eight-minute abs joke versus five-minute abs. So
1:17Simon Taylor: yeah, now you got me thinking about something about Mary, uh, which is a great reference all the way along. But before we get into all of that, I've got to remind viewers and listeners that views and opinions of our contributors today are their own and might not reflect those of company they represent. And please don't take anything we say as tax, legal, or financial advice. And of course, this series is brought to you by Visa and our friends at Mesh. This episode is brought to you by Mesh, the Global Crypto Payments Network. Mesh makes it possible for anyone or any agent to get paid or pay instantly from any wallet on any chain, anywhere in the world. You can learn more at meshpay.com.
2:02Unidentified speaker (UNKNOWN): Hi
2:02Simon Taylor: Pat, since you're here, um you co-founded a company called Spindle, which Twitter bought back when they were called Twitter. Do we call them the ASIS formerly known as these days? And then you founded Notarize in 2015, and Notarize became proof in 2023. So tell me about that journey from where you were to where you are.
2:22Pat Kinsel: Yeah, I actually even before starting Spindle was at Microsoft and at Microsoft. really did two projects that are noteworthy. One, Docs.com, which was a collaboration with Facebook. And we were actually their launch partner for Facebook Connect and what they called granular data permissions. And so this identity thing going all the way back to docs.com. And then I built a search engine internally for Microsoft on top of Twitter and Facebook data. So Spindle was an extension of that, built a search engine. sold it to Twitter. You missed that I was the lead investor in Drizzly.
2:56Unidentified speaker (UNKNOWN): So
2:56Pat Kinsel: Drizzly was an alcohol commerce company sold to Uber. And that's relevant because a lot of identity issues, a lot of regulatory issues associated with Drizzly. So I got that exposure. And then ultimately, when Twitter went public, I had to get a document notarized. And I uh went into a notary. Notary screwed it up. It was a huge pain in the butt for me. And that really set me off on someone's gotta solve this problem. So it's been about 10 years now. And really what we've done is we've gone out and digitized transactions, changed regulation, and figured out how to uh authorize things with full legal effect. And that is very relevant in the age of agentic. That's the problem everyone's trying to work on.
3:36Simon Taylor: So talk to me about where we are now, right? Everything's agents. Everybody's worried about it. Uh everything I'm seeing, there's a new report by Visa saying 50% of the time it works every time with Agentic Commerce. They're they're struggling to even buy the right thing. What do you see as the core problems that that agents are having? And where are we at in this evolution of the whole space?
4:01Unidentified speaker (UNKNOWN): Yeah,
4:01Pat Kinsel: I think even to broaden the conversation. context more than that, I mean, you got to go back to COVID, and COVID forced the world to go remote. And so all these institutions, now 70, 80, 90% of all of their customer interactions are remote and digital. After COVID comes deepfakes, and this idea that you can't trust who you're you're doing business with on the other side of any transaction. And so agentic is really just the the full expression. of that challenge. You you now don't know if it's a deep fake. You don't know if it's a human on the other side of a transaction that's explicitly authorized something. And also let's talk about Project Glasswing. You have these major, you know, financial institutions that are under tremendous threat from cybersecurity. And so I think they're struggling across the board to have confidence and certainty in who they're doing business with. and exactly what their customers are authorizing them to do.
4:54Unidentified speaker (speaker_2): What's the role of KYC and KYA on on the agent e-commerce side?
5:00Unidentified speaker (UNKNOWN): Yeah,
5:00Pat Kinsel: it's so funny. KYA to me is just about bot detection effectively, right? Uh and a lot of people are really focused right now on KYA to filter traffic. They want to know that it's an agent that's actually hitting their services. But then what?
5:16Unidentified speaker (UNKNOWN): You
5:16Pat Kinsel: know, how do you actually create a channel where the agent can do something? And to me, that is where not just KYC, but intent mandates and legal authorization come into play. And I think, again, so much of the world is focused on a gentic commerce. You know, the event that with Simon we co-hosted in Las Vegas was about, it's bigger than the buy button, right? Every industry is having these challenges. now, whether it be mortgage, retirement, auto, wealth. These aren't simple purchases of $500 shoes, right? These are highly regulated transactions with real legal obligations and compliance requirements. And that's where we're very focused is on full legal effect, right? How do you actually, you know, meet all of the industry obligations and still provide a tremendous customer experience out of these platforms?
6:02Unidentified speaker (UNKNOWN): So
6:03Simon Taylor: talk to me about that a little bit more because there's an alphabet soup of protocols coming out of the woodwork. Um I think Decagon has one for something. And then the guys at Sierra worked with Mesra and a bunch of other companies. Just talk to me about that alphabet soup of protocols and where you think what you guys are doing fits into all of that.
6:24Pat Kinsel: There's always been an alphabet soup super of protocols, right? And you know, a lot of this stuff we've been working with Google and Visa on for two and three years. And that was just the tail end of five and ten year processes through FIDO and other institutions around identity, right? And so again, this is just this sort of sudden dramatic expression of challenges on the internet, which is how do you know it's your customer? How do you create an authenticated session? You know, how do you assign intent? mandates? And so the way that I see sort of this all playing out is, you know, Google has been very focused on, you know, AP2, which is how do you sign, you know, a payment instruction.
7:03Unidentified speaker (UNKNOWN): Uh
7:03Pat Kinsel: Shopify with UPC has been focused on how do you express your catalog, right? So if you're a merchant, how do you actually express and have your catalog indexed? Visa with tap is basically uh, you know, how do you register the agent? MasterCard with very viable intent is how do you, you know, sign a mandate. When you look at all of those protocols, they all asked a key question, which is that someone has to issue the trusted keys to the consumer.
7:29Unidentified speaker (UNKNOWN): And
7:29Pat Kinsel: so that's where proof comes into play is that irrespective of what is being authorized, how do we make clear that Simon actually authorized this transaction and otherwise? we're carrying the rest of these protocols forward. So, you know, what uh CR came out with with PAP or PAPI is really a form of authentication. So for read write access, right? In financial services, I would make the point or highlight the fact that you can't sign into the bank with you can't create an account with Google Auth.
7:56Unidentified speaker (UNKNOWN): I
7:56Pat Kinsel: can't go to a new bank and just sign in with Google and get an account.
8:00Unidentified speaker (UNKNOWN): And
8:00Pat Kinsel: when I need to do a wire, the
8:02Unidentified speaker (UNKNOWN): fact
8:02Pat Kinsel: that I'm signed in isn't enough already, right? They have additional step ups. It could be SMS OTP, it could be an MFA experience coming back through their apps, could be something you sign, could be something you notarize. And that's really where proof comes into play is going past off into the full legal effect of these transactions.
8:20Unidentified speaker (UNKNOWN): So
8:20Unidentified speaker (speaker_2): you said like about bot detection. Do you think after we decided, okay, this is an A agent? Now I want to know there that agent. Do you think there is a link between is going to be a link between KYA and KYC? So I know it's an agent, but next step is like who is the user behind the agent and what are the roles and responsibilities that the agent has? So if something goes wrong, then the user is basically is not going to be on the hook from like legal a standards. standpoint.
8:51Unidentified speaker (UNKNOWN): I
8:51Pat Kinsel: think that's exactly right. I mean, again, look, KYA has a lot behind it. I mean, one is like a nationalistic cybersecurity thing, right? And knowing these aren't Chinese models or
9:00Unidentified speaker (UNKNOWN): so
9:01Pat Kinsel: how does a merchant or relying party know this, for example, is an OpenAI, Chat GPT versus Claud versus you know, whatever. Two is model performance. I mean, some models are going to be better at carrying out users' instructions versus not. right? And so that's as Visa just came out with their benchmark, it's going to know that this Muse model is actually good at following customers' instructions versus others not. And so KYA is important for a lot of those reasons around model performance and accuracy. You alluded to this fact, but ultimately taking on some responsibility for that. If you have a signed intent mandate from a consumer, so I, hey, this is BAM. He told me to buy five green shoes. I have this explicit payload authorizing that transaction, but the instruction that Muse sent was for green shoes. Well, that's Muse not you know operating successfully. You can figure out who's screwed up in that chain, right? Um, so yes, you know, KYA plus our version of KYC, which which by the way is
10:01can be privacy preserving. It's not all. always the point to actually share someone's personal information. It's creating this strong cryptographic link between what they've authorized and the fact that you can chain to a person, right? They come together, they compose.
10:14Unidentified speaker (UNKNOWN): And
10:15Simon Taylor: then on that, it's probably worth explaining X401 and your vision for how you link a human to its agent age and to those intents, because that whole space is like this new language, everybody's trying. to figure it out. So really help me get what X401 is and explain it in the context of I've asked my agent to do a thing on my behalf. And how is that legal consent followed from me and proof of who I am to the agent and proof of who it is and the intent all the way through?
10:45Pat Kinsel: Yeah. So maybe before 401, I'll explain what we do for credentials. It's lock and key. right? And sometimes it's easier to understand the key than the lock. And so at proof, what we do is we verify identity to a high legal standard IO2, and we issue verifiable credentials backed by our own certificate authority. And so these are credentials that can chain all the way, right? So you understand the cryptography and the policy all the way from the credential back to the issuance, storage, access, management. revocation, all sorts of things like that. It is equivalent to the EMV chip in someone's credit card, right? So if you think about the transformational benefit of a of card present transactions versus card not present transactions, that's attributable to the chip. So we're giving the same equivalent chip to transactions. And it supports transaction signing. That's that's a critical distinction, right? So the ability to take a payload it could be buy this for me, wire this for me, add a beneficiary to my account. Yes, I agree to borrow this money. You can actually cryptographically sign that payload with someone's unique key. And so I know it's tamper evident, it's chained to you. You you sign this thing, right? Um, and so that's what's what proof credentials solve. X X401 four oh one is a way for a website to very easily gate
12:04any resource. And so it could be access to a system. It could be to trade something. You know, it could be what we announced we're collaborating with Circle on, which is actually sign, you know, stablecoin transactions, agentic transactions, whatever, and to actually say what's required. And so you can say for this transaction, I need a verified ID, I need an email address, address, whatever it is. You can specify what you need.
12:27Unidentified speaker (UNKNOWN): And
12:27Pat Kinsel: then you can say what credentials you're going to trust. So you could trust proof, but it's an open protocol. So you could say that you want to trust someone else
12:35Unidentified speaker (UNKNOWN): that
12:36Pat Kinsel: meets the specification. That agent hits the site, it gets blocked, it reads X401 and understands what's required. And then it can, you know, query the consumer, access the credentials, sign the transaction, and it then agent to agent can move. forward. So we're a huge believer in this future that agent to agent, there's gonna be many, you know, much larger share of global commerce. And this really allows for machine identity.
13:00Unidentified speaker (speaker_2): Makes sense. The X four oh one existed before or it is your invention?
13:06Unidentified speaker (UNKNOWN): I
13:06Pat Kinsel: guess you could say it's our invention. I mean it's uh it's inspired by other great work. I mean, so X X402, four oh two, uh, you know, Coinbase and others that have carried for it. So it's 402 because HTTP protocol, you know, status codes already had 402 for payment required. 401 was already authorized, unauthorized. And what we would say is that the internet was always intended to have an identity protocol and an identity layer. It's just no one ever did it. Right. And so modeled after what they did. So we've created this and designed it. We had some great design partners that gave us feedback and we've now submitted it. to FIDO as an open protocol.
13:41Simon Taylor: And round out the vision for X401 for me. What problem is that going to be able to solve in this new world in which we're trying to make agents be able to do things with some link back to the human?
13:55Unidentified speaker (UNKNOWN): Yeah.
13:55Pat Kinsel: I mean, right now, again, we're spending a lot of energy in stablecoin space. One of the benefits of market clarity there is that real financial. institutions are engaging. And so they need identity that actually satisfies their compliance obligations. We're spending a lot of energy there. We're spending a lot of energy with large banks, financial institutions, insurance companies, wealth management firms. They want to open up agents as a channel. You know, if you go read any of these sites, they say they'll meet their strategy strategies is to meet customers where they are,
14:25Unidentified speaker (UNKNOWN): right? So
14:26Pat Kinsel: their customers
14:26Unidentified speaker (UNKNOWN): are
14:27Pat Kinsel: in news and they're in Chat GPT and they want to enable these experiences. And so we're we're walking down the path of enabling those scenarios. A lot of exchanges. And so we've having folks taking a dependency. You can put an API behind X401, not just a website. So thinking about how You know, it can uh require signed identity, you know, presentation inside of an exchange. So it's really it's flexible. There's there's tons of stuff that's going on.
14:54Simon Taylor: I'm excited to learn more. I'm kind of interested in how it fits into this whole narrative at the moment about the whole some companies are blocking agents, some are trying to like build them an MCP. Like what's your perspective on all that?
15:08Unidentified speaker (UNKNOWN): The
15:08Pat Kinsel: whole blocking agents thing, what do people expect? Right? Like if you're a regulated financial. institution, again, I mentioned Project Glasswing earlier, you're getting hammered right now by cybersecurity issues.
15:21Unidentified speaker (UNKNOWN): You
15:21Pat Kinsel: know, a lot of large banks are dedicating huge percentages of their engineering resources to just like battening the hatches down, right? And all of a sudden this thing comes along that is breaking all of your security, you know, policies.
15:34Unidentified speaker (UNKNOWN): So
15:34Pat Kinsel: look, I I've sat in some rooms lately with some of the largest banks where if you think about their model risk governance and their their various policies and control surface area, like they're actually extremely sophisticated with how they're thinking about this, right? End to end who's responsible for what. So a lot of work on sort of the legal frameworks around this sort of stuff. And most of the people are are actively working to create happy paths. I think what people should understand is these agents, like you may block them on your website, but they know how to make phone calls. So they're calling the call center and they're pretending to be your client, which is an even worse problem. And so most people recognize that they have to create happy paths. Uh those happy paths have to enforce real identity authorization policy. Uh, and that's the right end state. And so we're working with many of the people that have said that they're not allowing this. They're trying to figure out how to.
16:25Unidentified speaker (UNKNOWN): I
16:25Simon Taylor: wonder who some of those might be.
16:28Unidentified speaker (UNKNOWN): So
16:28Unidentified speaker (speaker_2): you're saying that instead of like blocking or giving full access, there should be something in the middle that's more granular, right? So, and when I was working identity, there was a concept called AAA, like authentication, authorization, and accounting. So authentication is obvious. Like you authenticate the username, password, your phone number, then authorization shows like what level of author. access your agent can have. And then the accounting is the session time, right? So how long you have that access uh in that level. Do you guys have similar like type of mechanism built for X401 for the agent e-commerce?
17:07Pat Kinsel: Yeah. I mean, and it's again, it gets into our our verifiable credentials. I mean, the thing about being a CA, so a certificate authority is you have to publish your policies. So we have a published, you know, certificate practice statement and things like that. And it goes into how identity verification is done, how access is granted and reauthentication occurs. And it's very transparent. And so in the PKI world, you have things called OIDS, right? So it has to do with, you know, at time of transaction, was it cashed, you know, did it require a biometric. Did it require a full step up?
17:40Unidentified speaker (UNKNOWN): Um,
17:41Pat Kinsel: and so a lot of regulated industries may have a specific policy that's required, right? Like if you're gonna do a mortgage, right, or anything that touches those types of transactions, you have to collect identity at time of transaction. It doesn't matter,
17:55Unidentified speaker (UNKNOWN): you know,
17:55Pat Kinsel: what level of efficiency people want to provide. I think from your, you know, triple A, what's missing and what's required in this agentic world. is the intent mandate.
18:04Unidentified speaker (UNKNOWN): And
18:05Pat Kinsel: so we talk a lot about verifiable evidence. If you think about for you know payment geeks out there, um, compelling evidence, right? Uh dispute frameworks, what can you go and request, what data you get, does this stand up in court?
18:19Unidentified speaker (UNKNOWN): Right.
18:20Pat Kinsel: And that's so much of what our tenure history is, you know, producing a digital transaction that stands up in court.
18:27Unidentified speaker (UNKNOWN): you
18:27Pat Kinsel: know, that doesn't create some new liability bomb for industries and allows them to transact with full legal effect.
18:34Simon Taylor: Let's avoid those liability bombs as much as we can. Um, I'm gonna do my best as well to avoid angering our sponsors. So we'll take a quick pause here while we hear from
18:44Unidentified speaker (UNKNOWN): them.
18:47Simon Taylor: Stablecoin operations usually mean a wallet from one vendor and on. on-ramp from another, and then controls stitch together across all of them. Visas, stablecoin platform fixes this fundamentally. You can mint, move, and manage stable coins across OpenUSD, and you remain your own custodian, all in one single environment. Then stablecoin linked link cards let you spend balances anywhere visa is accepted. That's Visa, the global leader in payments and of course sponsor of this show.
19:21Unidentified speaker (UNKNOWN): You
19:21Simon Taylor: can find out more at Visa.com forward slash crypto.
19:28Unidentified speaker (UNKNOWN): All right,
19:28Unidentified speaker (speaker_3): thank you to our sponsors. Pat, um, you've been doing some stuff with X401 and X402 as well. So talk to me about the stablecoin land. We are on tokenized after all. What was What's your your exposure to that be?
19:40Pat Kinsel: I'm thrilled with the state of, you know, where things are with stable coins, the industry at large. You know, Brian Armstrong came out and he says that he thinks that crypto and stable coins will be the payment rail for a Gentec. And I agree completely. It's funny in our history, I was never asked to put anything on a blockchain in in 10 years, despite, you
19:59Unidentified speaker (UNKNOWN): know,
19:59Pat Kinsel: digitizing real estate and retirement and all these industries. And we've seen a total change in interest in how we can interface with the crypto industry because of stable coins.
20:09Unidentified speaker (UNKNOWN): And
20:10Pat Kinsel: so really it's two-sided. So one is we now accept payment ourselves, you know, over 402 with MPP coming. And really, if you think about this, if you want to allow machine transactions, they're not going to go negotiate an enterprise license agreement. They're not going to make volume commitments. They want to have micropayments and they want to basically enroll and pay at just in time. And so it's not just that we're accepting 402 MPP. It's that we're allowing someone to register at the edge for our service. And so there's a really easy way for someone to put basically code on their site, which makes them a relying party for our credentials at time of transaction and so that they can do this without signing an agreement. and pay as they go. That's critical. And the second thing is thinking about how they can run side by side, right? And so how you actually have one authorization that includes identity and payment. And so industries can really unlock agenda commerce and commerce broadly, not just you know paying for things with a credit the card, but know who someone is, know that they uh can pay through those rails and those things coming together, we think is the great unlock.
21:17Unidentified speaker (speaker_2): Do you see in your vision, do you think blockchain, besides payment, is a good ledger for identity in a decentralized way? So I can have my identity and I have my private key. So I can sign requests. So proof that basically I am BAM is As easy. Do you think those type of project projects will come to fruition at some point because of the payment use case?
21:39Pat Kinsel: Such a loaded question. I uh look, I think it's an evolution. I mean, verifiable credentials live on device at the edge, right? And so it's already in our implementation, you already are storing, you know, a portion of your identity at the edge. The reality though is that regulated industries still require the collection of data. And so our vision and plan is that you first have to convince people to rely on a verifiable credential. You then can talk about zero-knowledge proofs and what's what's required. If you have someone that is basically attesting to the process having been performed, taking on liability and risk associated with that, you can start to talk about there not being an exchange of PII, but we see it as a phased approach to get to that point. And then also in our design format. for 401 and our scheme, we do account for there being other issuers, right? And so it's not unlike the payment networks where you have open standards, open protocols, you have governing associations that, you know, manage a lot of these things. Then you have people that operate networks on top and those networks win based on the their efficacy and scale. Uh we see the same playing out for identity.
22:47Unidentified speaker (UNKNOWN): Yeah,
22:48Unidentified speaker (speaker_3): identity networks are a really interesting idea. For the simple fact that I think a lot of the decentralized identity stuff is probably built in a vacuum unaware of how decentralized verifiable credentials are. And the legal definition of identity is when a government identifies you and says they they sort of point the finger at you and say, That's Pat. That. And so you're looking for that non non-reputable repudiable true truat at source token. that PKI verifiable credential that came from a government source and also another issuer of identity. If you can triangulate these things, then what do I need to put them on a blockchain for? I think is is a fair question. Well, maybe I want to build a marketplace of that. And their blockchains might be might be helpful and and suitable for things of that nature.
23:36Unidentified speaker (UNKNOWN): I
23:37Pat Kinsel: think you just hit on a couple of really important points. that people should understand. So one, verifiable credentials can be copied, right? And it's literally it's just a format for the expression of data. Like I on my computer right now can generate a verifiable credential that says I'm you Simon. Like I can take your name and your address and I can create a verifiable credential. So the question is who issued it and do you trust the person that issued it?
24:02Unidentified speaker (UNKNOWN): And
24:02Pat Kinsel: can you prove that it was, that it's been unaltered since it was issued? And and and that is why we also built a certificate authority and why we sign our verifiable credentials with our CA. Because then you know, okay, here's this credential that I have. It meets the standard in terms of presentation of data, and it was issued by a company called Proof. And I can see all of the policy and cryptography from the moment of issuance to the moment of presentation. We think that is critical and not all verifiable credentials are the same. Then you get into transaction binding and signing. I think it's also important for people to know this is why the FinCEN guidance that came out of such a big deal. FinCEN came out and said for the first time ever that a private issuer of verifiable credentials can be used in KYC SIP and not just a government. government-issued identity. You know, people talk a lot about MDLs and we really see two core issues. One is enrollment. There's just not a lot of people that have MDLs. And so how can you do just in time enrollment? It's been a big focus of ours. You're in Muse and you're trying to get a
25:07prescription from Amazon Pharmacy, hypothetical. You got gotta to be able to meet it right here, right now. And then the second thing is liability. Like you cannot go back to the state and say you're liable for this transaction, right? And so that's where we think a private network that sits and manages these standards is critical to advance all this forward.
25:28Unidentified speaker (speaker_3): I think mobile drivers licenses, MDLs, yeah, I had dunno how many states they're available in. Is it four now, maybe six, something like that?
25:36Unidentified speaker (UNKNOWN): No,
25:36Pat Kinsel: it's it's I'm gonna forget the number, but it's more than that.
25:39Unidentified speaker (speaker_3): Okay. But the amount of people that actually use those as well versus having the physical driver's license is is is kind of few and far between. The amount of people that have a bank account have been through some form of KYC, though, is is kind of enormous. And so if I've taken you through that identification process, why shouldn't I monetize that? People want to be able to verify identity and they want to identify it from a brand they've heard of and they trust. So being able to do that. is really, really hard. But to your point, liability. Do I want to be uh exposing myself to that liability? I think that's always been a bit of a hard question. But the FinTech guidance said, look, this is something that we expect the the market will develop. So I'm so interested in how that continues to evolve over time and uh you know what you're seeing from your early customers. Like who's adopting this now and what are the going to be the use cases?
26:26Pat Kinsel: Yeah. So we have, you know, nearly 10,000 businesses on our platform. Uh that was one of our advantages, is we have all sorts of industries doing these highly regulated transactions on our platform. We've done more than a trillion dollars of volume in our history. And so our initial challenge was how do we issue a credential that can just be used by our own customers? So these are wealth management customers, retirement, typically associated with large flows of funds. And so someone is withdrawing, you know, $160,000 out of their retirement account. And so it has to be valuable, right? So it's not, hey, here's this cool fancy tech. It's hey, better customer experience, better security, higher conversion rates, right? Uh, those are the ways that you can deploy credentials into these, into these workflows. And then the fact that it ultimately creates a network is, you know, an artifact that comes, you know, at a later date. And that's really been our strategy.
27:22Unidentified speaker (speaker_2): One question about the you said you were excited about a gentic to agentic type of transaction. So agent to agent is going to be bigger than agent to humans or human to agents from like volume perspective at some point. And the reason is very simple. Like we have five billion users connected to internet. You will have hundreds of billions of agents connected to internet. Human, they do two to three transactions per day. Agents are doing thousands of transactions per second. So it's really not hard to kinda calculate the math that agent to agent would be bigger. But what I'm hearing from you is identity could be here the bottleneck. So if every time that there is a transaction, I need to kind of ping my human to like approve my transaction, would that slow down the agent-to-agent transactions?
28:10Unidentified speaker (UNKNOWN): Yeah,
28:10Pat Kinsel: but you don't need to. I think that's what's so critically important. I mean, like a couple things. Like one of the ways I've sold our product at points in time is to basically say to someone on IT, hey, imagine if you know a third-party third party service doing an API integration didn't use TLS and you allowed unsigned instructions and into your organization.
28:28Unidentified speaker (UNKNOWN): And
28:28Pat Kinsel: they're like, I would never do that. And I say, Well, that's what you do with every person that you are interacting with, right? They're signing things, they're submitting things. You have no idea who it is. What if you could bring people into the same security paradigm of the web as machines are? And that's really what we've done with PKI and verifiable credentials. And then everything else is policy, right? So if you're going to allow someone to delegate access or authority, is that how long should that be lived? Right. And from an intent mandate perspective, you know, hey, when the Taylor Swift concerts, you know, drop under $500, buy them for me. A lot of commerce is not does not point in time, right? It's just no different to how a merchant, you know, stores a payment credential, right? It's tokenized, it has a caching policy and a replay policy. There's it's just policy, right? I think what's critical though is let's just say you hit a gate and that business has a real compliance obligation or a fraud concern.
29:28Unidentified speaker (UNKNOWN): You
29:28Pat Kinsel: know, how do you then mitigate that, right? How do you step up so much of credit cards? Now just think about this. Like, you know, my Amex, for example, I get an alert that it was used, right? Uh I have a centralized policy. place to go and see the transactions that I've authorized. I can revoke access to credentials, right? Uh, and it's all the same concepts for identity are are required and are we're moving toward.
29:49Unidentified speaker (speaker_3): Pat, if people are trying to get their head around, hey, I'm expecting some agent traffic. I'm already seeing some of it. You've talked about the the CISO angle, you've talked about, you know, kind of people on that side and building happy paths. How would they get started if they wanted to talk to you? How would they implement like an X401? How would they work with your certificate authorities? Like, how would you advise them to just get control of this agent traffic that's coming at them right now?
30:17Pat Kinsel: What's happening right now is everyone's focused on detection and then they're using that to just try to get a handle on the situation and and effectively shut it off. Now they're dealing with call center. That's where the traffic has shifted. And so we have a bunch of tools. Almost all of our customers start in call center. And so we have a lot of tools to think about how to get someone into a secure identity posture out of the call center. But when it comes time to start to actually open up to agentic traffic in real and supported ways, you know, we deployed Cloudflare workers. And so more than half of our customers, for example, on Cloudflare. they can one click deploy this thing in Cloudflare. And I think something that is relevant to what you brought up earlier, Simon, around liability is we have transaction templates. And so in payments, think about MCC codes, right? Um, they treat going to a gaming site differently than buying a sandwich, right? And so we have these transaction templates that allow someone to start to authorize individual use cases, start to define the identity policy and interaction model around those individual use cases. And so a lot of what we're doing right now is trying to create industry alignment, not just around this broad concept of agentic authorization, but talking about specific use cases, what data should be exchanged changed with a focus on data minimization. So we're not sharing too much information,
31:37what specific intent may
31:38Unidentified speaker (UNKNOWN): be.
31:38Pat Kinsel: mandate needs to be signed? How does it carry KYA, KYC, the intent mandate? What's the step up policy associated with this? All of it, right? And that's where we're working with our customers to walk down this path. And so to me, it's pick a use case, right? You know, robots.txt, right? Like ultimately people putting skills files and agents files on their site. They're publishing what they will and won't do. One of the things I've found this is an aside is it's so interesting. Like we publish, you know, 401. I asked Claude and Chat TPT questions like, what's a leading uh gentic protocol? It'll pick 401.
32:14Unidentified speaker (UNKNOWN): But
32:14Pat Kinsel: then when you ask it about use cases, it doesn't always land. And the reason is because people have to actually express their intent. Like it's amazing how these agentic systems understand intent. And for a site to simply in an agent's file or skills file say, hey, we are working to enable, right? And here's a place where we're willing to start. It's amazing how these agents will figure it out and start to respect where you want your traffic to go.
32:38Unidentified speaker (speaker_3): Hey, agent, I would like you to do this thing is a surprisingly powerful way to greet them. I often describe a lot of what we need to do is just build really good handshakes. There's so many customs for humans to greet each other in various parts of the world and we learn each other's customs. We should probably learn the uh customs of agents. So, Pat, if people do want to get started, where do they go to learn more?
32:59Unidentified speaker (UNKNOWN): Just
32:59Pat Kinsel: go to proof.com slash X401. We're all over the internet. So, you know, we're working with a ton of customers or not. You'd be surprised. Like, we can get this stood up in a matter of a day or two if people want to POC it. And it's in production. So like people can do this right now.
33:13Unidentified speaker (UNKNOWN): All
33:13Simon Taylor: right. That's awesome. Thank you very much. Pat. And and uh that brings us to a close for today. So, Bam, why don't you tell me where people can find out more about you and everything you're doing at Mesh and all of your really spooky ghost cards?
33:24Unidentified speaker (UNKNOWN): Yeah,
33:24Unidentified speaker (speaker_2): you can go to meshpay.com or find me Bam as Z Mesh on X or LinkedIn.
33:29Unidentified speaker (UNKNOWN): Yeah,
33:29Simon Taylor: you'll find me at SYTALO on all of the socials at brainfood.xyz screaming into the void, and of course at the tempo.xyz as well,
33:37Unidentified speaker (UNKNOWN): just
33:37Unidentified speaker (speaker_3): making
33:37Simon Taylor: top-level domain names. that are hard for corporates
33:40Unidentified speaker (speaker_3): to get access
33:41Simon Taylor: to, as always. And uh you'll find a lot more of this show if you hit the subscribe button. And I think for conversations like this, it was well worth your time. Gentlemen, thank you very much, and we'll catch you next
33:51Unidentified speaker (UNKNOWN): time.