The Future of Agentic Payments with Clink Founder Patrick Wu

In this episode, I spoke with Patrick Wu, Founder and CEO of Clink, about what payments need to look like in an agentic commerce world. Patrick previously worked on payments infrastructure at Amazon and AWS Payments, and later led global payments at Temu as the company expanded market by market. His view is that payments today are largely built for humans at checkout, but not yet for agents acting under delegated authority.

The conversation started with a basic but important question: if Stripe, PayPal, Airwallex, Visa and Mastercard already exist, why do we need another payments company? Patrick’s answer is that the problem is not just processing a payment. For agentic commerce to work, the system needs to understand who the agent represents, what permission it has, whether the purchase fits the user’s original intent, and whether that authorization can still be verified later. Clink is positioning itself less as a replacement for payment processors and more as a connector across agents, merchants, payment providers, and card networks.

We also spent a lot of time on why payments remain so fragmented globally. Payment habits are local: cards, wallets, bank transfers, convenience-store payments in Japan, and different payment methods across emerging markets. Patrick argues that no single provider is best in every market, which is why AI builders and global merchants may need orchestration across multiple PSPs, local payment methods, and eventually multiple agent platforms.

The most interesting part of the conversation was around trust and liability. If an agent buys the wrong thing, who is responsible? Patrick’s view is that fully autonomous shopping is possible eventually, but the trust layer is not there yet. In the near term, agentic payments will likely work through delegated mandates: user-defined instructions, spending limits, merchant controls, passkeys, audit trails, and chargeback mechanisms. His differentiated view is that the industry may be too focused on creating brand new crypto or blockchain rails, when the more immediate challenge is making existing fiat rails work safely for agents — and getting the ecosystem to align around clearer standards.

Get in touch with Patrick via LinkedIn.

And company website here.

Chapters

00:00 Introduction

00:13 What Clink does and why payments need to evolve for AI agents

01:18 Why today’s payment stack is not ready for agentic commerce

03:07 Why payments remain fragmented across geographies, regulations and user habits

05:48 Clink’s role as a connector across agents, merchants, processors and networks

07:06 Why AI builders may need more than Stripe, Airwallex or PayPal

09:34 Visa partnership and what it means to be an “agent enabler”

15:23 What happens when agents spend a user’s money

21:02 Trust, liability, chargebacks and why China’s wallet model is different

23:26 What agentic commerce actually means today

43:54 Patrick’s differentiated view on fiat rails, stablecoins and protocol fragmentation

Transcript (AI-generated, for reference only)

Grace Shao (00:00)

Hey Patrick, so good to have you on today on AI Proem. Thanks so much for joining.

Patrick (00:05)

Hey Grace, thank you for having me here.

Grace Shao (00:06)

Yeah. To start with, give us the high level. Who are you and what is Clink in a few sentences?

Patrick (00:13)

Sure. so at simplest level, I’ll introduce Clink first. Clink is building the the payment and the bill infrastructure for AI builders and for the agent that they will serve. So payments today we see at design around human being on a checkout page and but we’re building the layer that let authorized agents complete the same transaction safely while helping merchants accept the global payments through the system they already use.

And for myself, I started my payment career path at Amazon and AWS. I learned how to build a payment infrastructure that has to perform at a very high level of reliability and the security. And at Temu, I led a team to solve the problem with payments and the global market expansion. So we expand country by country, market by market, and solving the payment issue locally.

And Clink bring those lessons to a new problem that when we see agent becoming the new commercial actor, but we see the payment stack is not fully ready for that, so we won’t solve that problem.

Grace Shao (01:18)

So what do you mean by the payment stack is not ready for that?

what do you mean by the world’s not ready for agentic payments? And where do you see the gap from existing offerings? Because obviously, when we talked offline, I did challenge you on this. I said, you know, there’s a lot of major fintech players already and payment solutions, Stripe Airwallex PayPal,

right? But where does Clink come in and how does Clink solve this issue,

Patrick (01:44)

Yeah, I think payments are largely solved for human who is present at checkout. so the industry had made it much easier for developer to accept payments like except from card, from our wallet and from like so many payment that local customers prefer. and also the developer can easily launch a product to launch a subscription, send a payment link, right? Those those are like a real progress already made the word.

So but what is not solved on the payment side we see is agents acting under the delegated authority. Right. Processing the charges only one part of that transaction, but the system also needs to know who the agent represents and the what permission that it has and whether the purchase is within the policy, within the intent, like matches the original mandate that the user has given. And then the how the evidence being being persist, right? And if we come back in six months later.

is that transaction still like able to be verified at the point that the agent made the decision. So I think like global merchants still face another unsolved problems like a single provider isn’t no single provider that best at the every market and solve all that agent issue. And then we know worldwide that the agent can can buy product from anywhere. So we see that’s a big gap that the agent e commerce need to

have a both the authentication layer authorization layer and also a practical way to across with all the providers in the market today.

Grace Shao (03:07)

Yeah, actually on that, you did say, you know, payments are very fragmented, right? Like, and but is that fragmentation mostly based on geo geography, regulatory reasons? Is it about payment habits? Like how do we understand that? Why is it so fragmented and it’s not a one solution fits all?

Patrick (03:24)

Yeah, I think that’s a great question and a great observation, right? And to be honest, I think it’s all about like all about that because payment really reflects a local financial system, right? Like you spend twenty dollars in Singapore that you may use a card, you may use your wallet, your bank transfer. But if you know in Japan that many e-commerce orders actually being paid over konbini payment. Konbini is the Japanese word for convention store. If you would like to place an order online and

getting to a company store and the pay when they check out some some goodies. So it’s just a habits and also the regulation and also how the payments being developed in that particular marketplace. So we see that it’s like all different across the world. That that’s a lesson we learned from from building Tammu payment stack that we actually adopted 70 payment method when in the first year. So every country has their own top three payment method.

And every time you add a new pay method, you got some new customers. So it’s kind of very interesting. And then but then the fragmentation is not simply like I I guess you can solve that by building an API and building more like a convenient experience, but we see that as a reflection of local, right? Like habits and migration, all that just as we said. And the the things that we cannot force the users, right? Use got their own votes for what they want to pay.

And that will always exist because…

Get full access to AI Proem at aiproem.substack.com/subscribe