AI Agents Will Pay Online Soon. Korea's Door Is Locked.

Opening

In May 2025, Coinbase quietly unveiled a protocol. Its name: x402. It revived HTTP status code 402 — the “Payment Required” code that had existed since the internet’s earliest days but sat unused for nearly 30 years.

The concept is simple. An AI agent sends a request to an API; the server responds, “This information costs $0.001”; the agent pays instantly, with no human involved, and receives the data. No credit card, no subscription, no account needed. Payment functionality gets attached with a single line of code.

7 months after launch, x402 had processed over 100 million transactions worldwide. Cloudflare co-founded the protocol’s foundation, and Google Cloud’s agent payment system adopted x402 as a payment rail.

And here, one question occurred to me.

Can Korean AI agents actually access this payment infrastructure?

Network Usage Fees: Where the Structure Began

To answer this question, we first need to understand a peculiar feature of Korea’s internet ecosystem.

Korea is the only country in the world where network usage fees have gone up. In 2015, the Ministry of Science, ICT and Future Planning (MSIP, now the Ministry of Science and ICT) revised the Interconnection Notification — the regulation governing interconnection fees between telecom carriers — introducing a traffic-based fee system. Under this structure, overseas services sending traffic into domestic networks effectively had to pay Korean telecom carriers.

In 2016, one company became the first to publicly criticize this change: Cloudflare, an internet infrastructure company operating servers in more than 120 countries.

Cloudflare revealed on its official blog that Korea’s network usage fees were more than 15 times higher than Europe’s. Then it quietly changed strategy — rerouting free-plan users’ traffic away from Korean servers to servers in Japan, Hong Kong, and the US instead.

Domestic developers still feel the result today. Unless you’re on the $200/month Business plan, running a Korean service through Cloudflare actually increases latency. You spin up a service in Seoul, and requests end up crossing the Pacific twice. That’s why “using Cloudflare routes you through Japan” is common knowledge in Korean developer communities.

There was an even more direct incident. In 2023, Korea’s 3 major telecom carriers blocked the domain of Cloudflare’s storage service, R2¹​, at the DNS level. When one user asked a carrier why, the reply was:

“Cloudflare was blocked because it doesn’t pay network usage fees for its non-enterprise customers, and the block won’t be lifted unless Cloudflare takes action.”

This is no longer a “performance issue.” It’s a structure that controls access itself.

The Day Twitch Left, the Carriers Smiled

If Cloudflare’s rerouting and the R2 block were signals from the infrastructure layer, the most dramatic incident broke in February 2024.

Twitch, the world’s No. 1 game-streaming platform, ended its service in Korea. CEO Dan Clancy wrote on the company’s official blog: “Due to regulation, network costs in Korea are 10 times higher than in other countries. The core reason for ending operations is clearly network usage fees.”

Of course, this claim has its critics. AfreecaTV, a domestic competitor, argued that “they’re blaming network fees for a withdrawal that was really about losses.” In fact, Twitch’s exit likely resulted from a combination of a global strategy shift and profitability concerns, so it’s hard to say network fees were the sole cause.

One thing, however, is clear: the burden of network usage fees has become a key variable in calculating service sustainability. Netflix, after a 3-year legal battle with SK Broadband, reached a strategic partnership under which it effectively pays an undisclosed sum, and Facebook already agreed to pay network usage fees back in 2017. Players who couldn’t hold out left; players who could, eventually paid up.

So what did consumers get out of this process? Fewer choices. And most people don’t even know it!

The Country Stripe Still Can’t Enter After 10 Years

If network usage fees are a barrier for content and infrastructure services, payment infrastructure faces a wall of its own.

Stripe²​ is the online payment platform developers around the world treat as the default. You can add credit-card payments with a few lines of API code, and global SaaS companies like OpenAI, Shopify, Slack, and Notion have adopted it as their payment backbone. It currently operates officially in 46 countries. Korea is not one of them.

Stripe did once consider entering Korea and even tried to hire local developers. But it ultimately withdrew. The reasons are complex, but the core issue is one: the registration requirement for Payment Gateway (PG)³​ operators under Article 28 of the Electronic Financial Transactions Act.

For a foreign company to run a payment service in Korea, it must register with the Financial Services Commission, hold at least ₩1,000,000,000 in capital, employ at least 5 IT staff, and build an information-security system that meets Korean regulatory requirements. The network separation regulation⁴​ is a particular sticking point — it structurally conflicts with the cloud-based, globally unified architecture Stripe runs on.

PayPal can only handle “receiving” money in Korea — “sending” requires a separate license, so it operates only in a de facto half-functional mode.

As a result, if a Korean startup wants to sell to global customers, it has to set up a separate legal entity in Singapore or the US and open a Stripe account there. That alone typically costs several million won and takes several weeks or more. While founders everywhere else attach payments with a few lines of API, Korean founders have to start by incorporating a company.

In Korean-language communities, this line circulates: “It’s been over 10 years since the Cheon Song-yi coat incident, and you still need an overseas business entity to sell to overseas users.” (This might be too old a reference to place — it refers to the coat actress Jun Ji-hyun wore in the drama My Love from the Star.)

Oz’s Lens

In go-to-market strategy, friction cost matters most. When deciding whether a service should enter a given market, you weigh expected returns against the cost of entry. Network usage fees, licensing requirements, network separation regulations — these are all friction costs.

Cloudflare absorbed the friction cost by rerouting around it. Twitch left once the friction cost exceeded the returns. Stripe judged the friction cost too high and gave up on entry.

Now, a protocol called x402 has appeared. It lets AI agents pay simply by sending an HTTP request. This isn’t just payment technology — it’s the foundation of a new economic infrastructure. The fact that Cloudflare co-founded this protocol’s foundation is itself a declaration: they intend to be the player defining the payment layer of the next-generation internet.

Here’s what unsettles me.

Cloudflare already doesn’t function “normally” in Korea. Free-plan traffic gets rerouted; R2 has been blocked. Can Korean AI services really build on top of the agent-payment infrastructure that this same Cloudflare is designing?

In an ecosystem without Stripe, is “agent payments with one line of API” even possible? An AI agent can’t agree to a Korean PG company’s terms of service, obtain a certified digital certificate, and go through electronic-financial-business registration procedures. In fact, AI coding tools like Cursor, Trae, and Replit all offer Stripe payment integration — but none of it works in Korea. You could pay for it and still not be able to use it!

To compete in the AI agent economy, you have to build on top of the infrastructure that powers it. But right now, Korea has a structure that keeps that infrastructure from properly entering the country. It’s not that services are arriving late — the structure itself is pushing the infrastructure out.

Whether this is a short-term policy problem or a problem with a telecom-and-finance cartel isn’t for me to judge. But from a data standpoint, I can say one thing: losses that go unmeasured don’t get reflected in policy decisions. The productivity losses developers suffer from Cloudflare’s rerouting, the opportunity cost startups bear from being unable to build global services without Stripe — none of it shows up as a number in any report.

If it never shows up as a number in the first place, it looks like there’s no problem at all.

Closing

Let me sum up three points.

First, Cloudflare is at odds with Korea’s network usage fee structure, rerouting free users’ traffic around it, and its R2 service has been blocked outright. This is the same company that co-founded the x402 foundation.

Second, the limited entry of Stripe and PayPal structurally makes it hard for Korean startups to get onto the global agent-payment ecosystem.

Third, the AI agent economy needs its infrastructure layer laid down first, before services can be built on top of it. Right now, that infrastructure isn’t functioning properly in Korea.

This isn’t a story about a tech trend. It’s a story about where the structure of the next competition is being built. Personally, I’ve noticed more and more people in Korea getting into development through vibe coding these days, and interest in payment tools like Stripe is naturally growing alongside it. I hope an environment takes shape that lets Korea keep pace with the agent era. If things continue as they are, we’ll end up stranded on yet another Galápagos island.

References & Further Reading

• Coinbase, “Introducing x402: a new standard for internet-native payments”, Coinbase Developer Platform, May 2025.: The official launch announcement for the x402 protocol. It explains how it works and its partner ecosystem.
• The Block, “Coinbase-incubated x402 payments protocol built for AIs rolls out V2”, December 2025.: Covers the V2 upgrade and the milestone of 100 million transactions.
• GeekNews, “Did a domestic ISP block r2.cloudflarestorage.com?”, September 2023.: A developer-community record preserving the DNS-level R2 outage on Korean carriers and the ISP’s response at the time.
• Mashup Ventures, “Surviving Without Stripe: 4 Global Payment Strategies for Korean SaaS”.: Analyzes the real-world impact of Stripe’s absence on Korea’s SaaS ecosystem.
• bendh.kim, “Korea’s Galápagos (feat. Stripe)”, September 2024.: Breaks down, from a practitioner’s perspective, how Article 28 of the Electronic Financial Transactions Act and network separation regulations block Stripe’s entry.
• Opennet, “The Warning Behind Twitch’s Withdrawal from Korea”, December 2023.: A civic group’s commentary using Twitch’s withdrawal as a lens to review net neutrality issues.

The author, Kwangseob Ahn, is a professor of business administration at Sejong University and lead consultant at OBF (Oswarld Boutique Consulting Firm). He teaches statistics and data analysis — business data management and business analytics — while leading GTM and AI strategy consulting in the field, designing the seam between technology and business. He has published academic research on a memory architecture for AI dialogue systems (HEMA) and runs Daily Arxiv, a daily curation of global AI papers. He holds a master’s from Korea University’s Graduate School of Technology Management and a KMBA. He is the author of Homo Brainless: The People Who Outsource Their Thinking.

Footnotes

1. R2 (Cloudflare R2): Cloudflare’s cloud storage service. It plays a role similar to AWS S3, but its distinguishing feature is that it charges no data egress fees. Developers widely use it to store and serve images, videos, and files. ↩

2. Stripe: An online payment platform built by two Irish-born brothers. With just a few lines of API code, you can add credit-card payments, and it has become the de facto standard payment tool for developers worldwide. It currently operates officially in 46 countries. ↩

3. Payment Gateway (PG): A business that acts as an intermediary for payments, rather than having online shops or services contract directly with card companies and banks. In Korea, you must register as a PG operator with the Financial Services Commission to provide such services. ↩

4. Network separation regulation: A regulation requiring financial institutions and related service providers to physically or logically separate their internal business network from the internet. It often structurally conflicts with global fintech services that run on unified, cloud-based infrastructure. ↩