Author: Yuki (Liu Yuqing), Stablehunter / Money in Motion
Over the past six months, I transitioned from being an observer of Web3 to working deep inside the payments industry. Now, I have chosen to stop and am no longer working on Web3 payments.
This is not a retreat after failure, but an adjustment of judgment made after truly diving in. During these six months, I visited Yiwu, Shuibei, Putian, and even Mexico, observing how payments are actually done in the most talked-about places in reports. I also got hands-on, built an MVP for Web3 payments, connected accounts, created Web3 payment collection tools, and tried to run imagined pathways from the first step to the last.
But the deeper I went, the more clearly I realized one thing: This is not an industry where "making a great product guarantees winning." Payments don't compete on features, but on banking relationships, licenses, capital efficiency, and long-term risk control capabilities.
Many seemingly "profitable" payment businesses essentially earn not a capability premium, but a risk premium—they just haven't faced issues yet. What truly determines how far a payment company can go is never how much money it makes, but whether it can withstand and survive before risks truly materialize.
This article is not meant to negate this industry, but to remove the filters, lay out the real structure, and leave behind some clearer judgments for those who come after. (A few weeks ago, I also recorded a podcast with Robert, former Kun Global VP, Alex, CEO of Nayuta Capital and former CEO of Didi Finance, discussing the same issues.)

1. Why Did I Enter Web3 Payments?
As a serial entrepreneur, I concluded a multi-year startup project last year. During the company's closure, I also took a break for myself, returning to a more "cleared" position to seriously consider where to focus my energy next.
Six months ago, a friend invited me to Hong Kong to try entrepreneurship related to Web3 payments together. At the time, I wasn't familiar with Web3 itself and had limited knowledge of the payments industry. From a macro perspective, it was clearly an industry with a large enough scale and still in an upward cycle, while also having potential synergy between Web3 and AI.
In previous entrepreneurial ventures, we had worked on cross-border business and platforms/software for remote workforces. Through these practices, I repeatedly encountered the same fact: Business can go global quickly, but the flow of funds always lags behind. Slow settlement, fragmented paths, opaque costs, uncontrollable payment terms—these issues might be bypassed through experience and patience when the scale is small; but once business scales up, they are not solved by "management capability" but only magnified. Money cannot flow freely like information, which itself is an invisible ceiling for many global businesses.
It was in this context that when I began systematically understanding the actual usage of Web3 payments in clearing and settlement, it presented not as an abstract technical narrative, but as a solution that logically addresses these pain points directly: faster settlement speed, higher transparency, and near 24/7 clearing capabilities.
At the time, this seemed like a direction that was both solving real problems and Day 1 Global—I didn't enter because of Web3 itself, but because in the specific scenario of payments, it seemed to offer a superior structure—at least logically, it looked capable of leveraging those long-existing but often-ignored frictions.
Looking back now, I have also gradually realized that, like many others at the time, I assumed a premise that was later constantly challenged by reality: as long as clearing and settlement efficiency is high enough, payments will naturally migrate on-chain. It was even further simplified to an intuition—payments are just matching transactions; as long as the process runs, you can "hand-craft" cash flow.
Given my unfamiliarity with Web3 and the payments industry, I decided at the time to first spend three months truly entering this industry, understanding its structure, and then deciding what to do and where to position myself.
2. What Payments Truly Compete On Is Never the Product
When I arrived in Hong Kong, the initial idea wasn't complicated. The first thought was simple: leveraging some existing resources and relationships from friends, start with OTC or relatively simple payment/collection scenarios, get cash flow running first, and then judge what to do next based on real demand.
I wasn't here to do research or watch long-term; I wanted to see—was it possible to first build something that works and then calibrate direction based on real business.
But soon, the external environment accelerated noticeably. In May, the US passed the GENIUS Act, and almost overnight, the entire industry was ignited. Capital, projects, and entrepreneurs flooded in. Web3 payments transformed from a relatively niche infrastructure topic into a frequently discussed "new opportunity." From the outside, this was positive; but for a startup team just getting started, this sudden buzz wasn't necessarily a good thing.
The more chaotic, noisy, and rapidly consensus-forming the moment, the easier it is to mask the real problems. Internet giants, financial institutions, banks, traditional Web2 payment companies, and Web3 Native teams entered the scene one after another. Everyone talked about opportunities, but few talked about structure. I felt it was even more important to immerse myself on the front lines and truly understand this industry.
1. The "Buzz" in Reports and What You See on the Front Lines Are Not the Same Thing
When I truly started running on the front lines, the first thing I did wasn't optimizing product plans, but observing: Who is actually using Web3 payments? Why? Where? I first went to Yiwu, a place often mentioned in reports.
In many research reports and discussions, Yiwu is often cited as a representative sample of "Web3 payments already being applied at scale." But after truly visiting, I saw a different picture. Stablecoins do exist, but more as fragmented, relationship-driven, hidden usage.
They haven't become a standardized, productized, replicable settlement method as described in reports. Many transactions aren't because of "optimal efficiency." I later visited Shuibei, Putian, and Mexico, and also learned about penetration rates in places like Africa and Argentina. The situation wasn't fundamentally different.
Web3 payments do exist, but they are far from forming a stable, scalable main path. More often, they are just a "patch" embedded within the existing system. The real penetration rate doesn't match the heat we perceive in reports, communities, or discussions.
But it was during these exchanges that I gradually shifted my perspective from "can we build a product" to the industry structure itself. I began to realize that the incremental market for stablecoins likely isn't within the "crypto circle," but in those existing Web2 business scenarios that have long been slowed down by traditional clearing and settlement systems.
This isn't a narrative shift, but more like a slowly happening fintech upgrade. Simultaneously, questions emerged: If real usage is so fragmented, does the productization path hold up?
2. When We Actually Started Building Applications, All Problems Pointed to the Same Place: Channels
From July to September, I continued field research while systematically contacting potential clients. Human resource companies, insurance, travel, MCN agencies, service trade, cross-border businesses, gaming companies... Their needs varied, but the core problem pointed to was highly consistent: Money should flow faster, cheaper, and more stably.
Payroll, task settlements, B2B payments—these scenarios are logically very suitable for stablecoins. Initially, we also thought the application layer was a viable entry point. But soon, an unavoidable premise emerged: You must have stable, compliant, sustainable fiat ⇄ crypto channels.
We started integrating with several seemingly good service providers in the market, but the real experience showed that it was hard to say any channel was "long-term reliable." To meet business needs, we even tried to build our own channel. But once we started, we realized: This isn't a product problem at all; it's an infrastructure problem.
Banking relationships, license structures, KYB/KYC compliance, risk control capabilities, quota management, regulatory communication... The entire channel layer heavily relies on long-term accumulated trust, experience, and capital. These are not capabilities a small team with an internet background can quickly acquire.
It was here that I truly realized for the first time: Payments are not an industry where "making a great product guarantees winning."
3. You Think You're Making Money, But Actually You're Earning Risk Premium
During this process, one statement deeply resonated with me: In payments, it's not about how much money you make, but how much money you can spend. Many seemingly "functional" Web3 payment paths essentially earn not a capability premium, but a risk premium.
The more dangerous part is: Many people don't know what risks they are taking or where the risks specifically lie.
- Is it compliance issues with counterparties?
- Mismatched capital pool structures?
- Lagging risk control rules?
- Or gray areas of regulatory interpretation?
If a business's viability is built on "nothing has happened yet," then it's not a structure that can be scaled with peace of mind.
4. The Essence of Payments Is a "Water Flow" Business
Slowly, I began to understand payments from a simpler perspective. The essence of payments is a "water flow" business. Whoever controls the waterways makes money; the greater the flow from the tap, the greater the earning potential. Water passing by your doorstep means you can take a cut—it sounds like an almost "passive income" business.
But precisely because of this, payments are never a simple business. Not every company "by the water" can make money. The payment companies that make money long-term are often those with extremely strong control over water volume, pressure, backflow, pollution, and leakage.
How much water you can handle depends on how much risk you can bear; how long you can keep the water flowing depends on your endurance under compliance, risk control, and regulatory environments. Many paths that seem to have "great water flow" are essentially just places where the tap hasn't been turned off yet. It was during this process that I developed a more complex, yet more realistic, respect for the payments industry.
Its charm doesn't lie in who made another new product, but in—it will very honestly tell you which industries in the real world are actually making money, and which are just making a lot of noise. Standing on the waterways, you can see where real capital is flowing, not who is constantly doing PR outside.
5. Payments Are a Good Business, But Not One We Can Do Best
At this point, I also had to face a judgment that is not easy but very important for entrepreneurs. Payments are a good business, but not the type of business we can do best. This isn't a negation of the direction, but a respect for resource endowment.
What the payments industry truly needs is not the rapid trial-and-error, iterative product capabilities, but long-term stable banking relationships, sustainable compliance systems, mature risk control capabilities, and credit accumulated through repeated negotiations in regulatory environments. These capabilities aren't something you can "just push hard to get," nor can they be quickly acquired through intelligence or effort. They are more like industry-level assets, often formed only within specific types of teams and specific time windows.
After truly viewing payments as a "water flow business," I also realized more clearly: What determines whether a team can stand on the waterways long-term isn't whether you want to, but whether you have that pressure-bearing structure in hand.
Under this premise, continuing to push forward was no longer a rational investment for us, but more like using time and luck to fight an industry structure that isn't on our side. This question ultimately led me to the next choice.
3. I Still Believe in Payments, Just Saw Its True Battlefield
First, I need to clarify: My choice to stop working on Web3 payments isn't because I'm bearish on this industry. On the contrary, over the past six months, I have become increasingly certain: The structural opportunities in the payments industry are still enormous.
But when I truly dissected these opportunities, I gradually realized something more brutal but equally important—payments are a business with longer time cycles, heavier structures, and higher resource requirements. Its opportunities exist, but they aren't distributed evenly under every startup team's feet.
1. The Increment in Payments Isn't a Short-Term Bonus, But a Long-Term Restructuring
Taking a long-term view, cross-border payments aren't a question of "whether they can explode," but an ongoing infrastructure rebuilding process. The continued spillover of global supply chains, growth in cross-border service trade, and acceleration of distributed team collaboration are all magnifying the friction of traditional clearing and settlement systems.
In this process, the value of Web3 payments isn't reflected in being "cheaper," but in three things:
- Significant improvement in turnover efficiency
- Transparency in clearing paths
- Unified settlement capabilities across currency zones and regulatory zones
This is a structural improvement, not a tactical-level optimization. Precisely because of this, it naturally belongs to a cross-decade scale project, not a market that can be leveraged by a product sprint.
2. What's Truly Difficult Isn't "Collecting Money," But the Fund System Within a Marketplace
After encountering enough real scenarios on the front lines, I increasingly clearly realized: The difficulty in payments has long ceased to be in "collecting money" itself. Especially in Marketplace scenarios, payments are never an independent component, but an entire ecosystem-level fund system.
Buyers, sellers, platforms, logistics, hosts, delivery riders, taxes, frozen accounts, subsidy accounts—all roles are interconnected within the same fund chain. In such a system, what truly determines the barrier isn't the payment interface, but:
- Escrow and freezing mechanisms
- Settlement split and payment term design
- Risk control and anti-fraud capabilities
- Cross-regional compliance and regulatory obligations
Once such systems stabilize, they naturally have space to extend into financial capabilities; but similarly, they also place extremely high demands on the team's capital strength, risk control systems, and long-term patience.
3. Web3 Payments Are Not a Front-Office Revolution, But a Back-Office Upgrade
One thing I became increasingly certain of over these six months is: The true scaling of Web3 payments won't happen on the user side.
It won't explode because users start actively using wallets, but because corporate back offices start upgrading their Treasury, reconciliation systems, cross-border settlement paths, and capital pool management methods.
In other words, the mainstream path is likely: Front-end Web2 remains unchanged, back-end Web3 is reconstructed. This is a "hidden" upgrade. And precisely this upgrade means it relies more on system stability, compliance certainty, and long-term operational capability, not market education.
The true inflection point also isn't in the most mature markets. If viewed geographically, payment growth is also not balanced.
Asia-Pacific is already a relatively mature market. The true structural growth is more likely to appear in regions like Latin America, Africa, the Middle East, and South Asia:
- Payment systems are severely fragmented
- High costs, complex paths
- Stronger willingness for users and merchants to migrate
But the other side of these markets is: Highly localized, strong regulatory differences, strong operational requirements. What they need isn't "cleverness," but long-term deep cultivation.
When I truly looked at these opportunities together, I also had to face a clear conclusion: Payments are indeed a good business, but the resource endowments they require—
- Long-term stable banking relationships
- Mature, sustainable compliance systems
- Risk control capabilities that withstand stress tests
- Credit accumulated through repeated negotiations in regulatory environments
—are not within our team's current capability boundaries. This isn't a negation of the direction, but a respect for reality. The battlefield of payments still exists, it's just no longer under our feet. It was under this judgment that I ultimately chose to stop and reconsider: If I'm not standing on the waterways, where else can I stand to continue participating in this ongoing structural change?
4. After I Decided to Stop Doing Payments
When I truly made the decision to stop working on Web3 payments, I didn't feel a strong sense of "ending." It was more like an exploration had finally reached a point where it should stop. I haven't left this industry. I just moved from trying to stand on the waterways to collect water, to standing beside the waterways, reobserving how water flows and where it ultimately goes.
While repeatedly dissecting the payment structure, one judgment became increasingly clear: Payments solve the problem of flow—whether money can move and how fast. But what truly determines long-term value is never the flow itself, but—where the money stops after flowing, and how it is managed.
Looking back at the development path of China's fintech over the past twenty years, this logic is actually very clear. Payments are just the entry point, balances are the transit station, but what truly forms scale and barriers are the subsequent fund management and asset allocation systems. Yu'ebao, Tian Tian Fund, Tian Hong didn't succeed because they had "better payments," but because they stood after payments, receiving and reorganizing the already-scaled fund flows.
Payments are the doorway, but not the destination. Placing this structure back into the Web3 world, I see similar problems gradually emerging. On-chain, there are already many not-so-aggressive but sufficiently robust asset forms—lending, short-duration RWA, neutral strategies, portfolio products... They are more like on-chain money market funds, short-term bond funds, and stable allocation tools. The real problem isn't "whether there are assets," but: Most people don't know what kind of risks they face, and lack an entry point to understand, compare, and judge these assets.
As more and more capital starts flowing on-chain, this problem will only become more prominent. It was precisely at this point that I began to realize: If I'm not continuing with payments, I can still stay within this change in another way. Not by competing for waterways, but by explaining the structure of the water flow, laying out the boundaries and risks, letting people know which places are worth staying, and which require extra caution. This is also the direction my team and I will continue to explore next.
This article is not meant to draw conclusions on Web3 payments, nor to persuade anyone to enter or exit. It's just an attempt to clearly explain why I chose to stop working on payments. I hope it can provide some reference for those who come after, perhaps helping them avoid some detours.





