South Korea just put real weight behind tokenized money. The Bank of Korea is moving its CBDC deposit-token pilot into a live environment with nine commercial banks and a hard cap of half a million wallets. If you follow payments, banking tech, or crypto, this is one of those moments where the rails shift under our feet a little.
This piece breaks down what the tokenized won is, how transfers will work, what changed in Phase 2, and where the guardrails sit. I’ll also compare it with stablecoins and old-school bank transfers, plus call out risks that don’t fit into neat press releases.
Timing matters. Phase 2 goes live in September 2026 with bigger limits, more users, and real-world government payouts like EV charging subsidies. The details decide whether this sticks or stalls.
South Korea’s CBDC deposit-token pilot is expanding to nine banks and up to 500,000 live wallets in September 2026. Users will be able to send tokenized won between bank wallets, receive targeted subsidies, and try new features like biometric authentication and programmable payment rules. Regulators also raised wallet and remittance limits to make everyday usage viable. The pilot stays ring-fenced and KYC’d, but this is the closest Korea has come to mainstream tokenized money so far.
- Timeline: Phase 2 live transfers begin September 2026, expanding from seven to nine banks Decrypt.
- Scale: Wallet cap rises to 500,000 users, up from 100,000 initially authorized Financial Services Commission (Korea) press release.
- Limits: Per-wallet holding up to 10,000,000 KRW, with cumulative up to 100,000,000 KRW; remittances capped at 1,000,000 KRW per transfer and 5,000,000 KRW per day for individuals FSC.
- New utilities: P2P transfers, biometric login, auto top-ups, and programmable rules; first real subsidy disbursements begin with EV charging support Yonhap News Agency.
- Context: Phase 1 processed 114,880 transactions across roughly 81,000 wallets, setting the baseline for the jump to Phase 2 Yonhap.
How will the live tokenized won transfers actually work?
Think of a deposit-token wallet as a new balance displayed inside a familiar bank app. The won you hold is represented as a token on a permissioned ledger maintained by the pilot. When you pay a friend, your bank debits your token balance and credits theirs, and the interbank settlement happens on rails coordinated with the central bank in the test environment. To you, it looks like sending money in a chat. Under the hood, it is closer to atomic, ledger-native settlement than a delayed bank transfer.
Phase 2 adds person-to-person wallet transfers and basic programmability. That means the wallet can follow rules, such as only spending a subsidy at approved merchants or auto-topping up when you dip under a threshold. Yonhap reports these features are part of the Phase 2 scope, alongside biometric logins for fewer password resets and less friction during checkout Yonhap News Agency.
The stated goal is not to build a crypto free-for-all. It is a controlled environment with strict KYC, spending limits, and bank intermediation. The upside is speed and precision. The tradeoff is you play by the same compliance rules as your bank account, plus new pilot-specific constraints set by regulators.
Pro tip: Treat tokenized-won balances like a specialized account, not a new asset class. It is still Korean won under banking rules, just living on different rails.
What changed from Phase 1 to Phase 2?
Scale first. Phase 1, which ran April to June 2025, onboarded roughly 81,000 wallets and processed 114,880 deposit-token transactions. Those numbers set the benchmark for Phase 2’s expansion Yonhap News Agency.
Regulators just approved the Phase 2 framework and cranked up the dials. The Financial Services Commission greenlit a wider rollout on July 15, 2026, raising the pilot’s wallet cap from 100,000 to 500,000, and boosting per-wallet holding limits to 10,000,000 KRW with a cumulative ceiling of 100,000,000 KRW per user. Remittance caps were set at 1,000,000 KRW per transfer and 5,000,000 KRW per day for individuals FSC.
Scope also broadens. Phase 2 will include the first real government disbursements. The kickoff use case is EV charging subsidies, which are well suited to programmability so funds can be restricted to eligible operators or stations. Peer-to-peer transfers, biometric authentication, and automatic top-ups join the feature list too, according to local coverage Yonhap.
Lastly, the banking cohort grows from seven to nine institutions. That means more network coverage and a better test of interbank settlement dynamics when users hop between different bank wallets Decrypt.
- Phase 1 baseline: 81k wallets, 114,880 transactions
- Phase 2 scale: up to 500k wallets, nine banks
- Limits raised: higher holding and remittance caps
- New features: P2P, biometrics, auto top-ups, programmable rules
- Use case: real EV subsidy payouts
What limits, fees, and protections should users expect?
Limits are explicit. Per the FSC’s July 15 approval, you can hold up to 10,000,000 KRW in a single deposit-token wallet, with a cumulative cap of 100,000,000 KRW across wallets. For remittances, individuals are capped at 1,000,000 KRW per transaction and 5,000,000 KRW per day. These numbers are designed to keep the pilot practical without letting it become a shadow banking system overnight FSC.
Fees are not the centerpiece here. Pilots typically keep or waive fees to observe behavior. If you see charges in your bank’s app, they will likely mirror domestic transfer pricing rather than crypto network fees. Because this is a permissioned ledger with bank operators, there is no public gas market like Ethereum.
On protections, your counterparty remains your bank. Expect the normal stack of KYC, transaction monitoring, and customer support. Biometric authentication tightens access control, but it is not magic. Compromised devices still pose risks. Dispute and refund flows should look familiar, though programmability may ringfence some funds, for example a subsidy that cannot be refunded to a random account.
If you are testing the waters, start small and stay within limits. Watch for any bank-specific rules that differ from the pilot’s headline caps.
How does tokenized won compare with stablecoins and regular bank transfers?
Tokenized won in this pilot sits somewhere between a bank account and a smart-contract wallet. It is not a free-floating asset you can move to any chain. It is a bank-issued token inside a closed loop that settles on rails coordinated with the central bank. That sounds restrictive, but for domestic payments and government payouts, constraint can be a feature.
Stablecoins win on openness and composability. You can route them across exchanges or into DeFi. They also carry market, issuer, and smart contract risks, and in Korea they live outside the mainstream bank stack. Traditional bank transfers are near universal and reversible, but they are batchy and less programmable.
Here is a quick side-by-side to ground the tradeoffs:
| Feature | Tokenized won (pilot) | Stablecoin (typical) | Bank transfer/card |
|---|---|---|---|
| Access | KYC’d bank customers in pilot | Wallet holders globally | Banked users and cardholders |
| Settlement | Ledger-native, interbank via central rails | On-chain finality per network | Batch or near real time via bank processors |
| Programmability | Yes, scoped rules in pilot | Yes, full smart contracts | Limited, depends on merchant systems |
| Compliance | Bank KYC and monitoring | Varies by issuer and venue | Bank and card network compliance |
| Interoperability | Closed loop among pilot banks | Wide, across chains and apps | Domestic and cross-border via networks |
| Reversibility | Bank policy dependent, subsidies may be locked | Generally irreversible on-chain | Often reversible or disputable |
Bottom line, the pilot is not here to replace open crypto. It is testing if bank-grade programmable money can shave friction off domestic payments and public disbursements.

Who benefits first, and what should businesses do now?
In the near term, government agencies and utilities stand to gain the most. EV charging subsidies are a clean pilot case because the money has a clear purpose. Programmable rules reduce leakage and speed up reconciliation at the operator level. If it works, expect other targeted benefits to follow.
Merchants that already accept bank app payments could see faster settlement and fewer chargeback headaches if the token rails hold up. Fintechs might find new hooks for loyalty or just-in-time top-ups. But remember, the loop is closed. There is no guarantee you can pull funds into crypto exchanges or external wallets during the pilot.
- Check with your bank on developer access or sandbox programs tied to the pilot.
- Map refund and reconciliation flows. Programmable restrictions may change how you handle returns.
- Train support teams. Customers will ask why a subsidy cannot be spent everywhere.
- Start with low-risk use cases like stored value, gift balances, or targeted discounts.
None of this replaces the basics. Good KYC, clear receipts, and honest pricing still matter more than shiny rails.
What risks and open questions should we watch?
Privacy is the loud one. Bank-mediated tokens plus central settlement can feel like extra eyes on your spend. Regulators may publish guardrails, but users will want specifics on data retention, analytics scope, and whether programmable rules creep into everyday transactions.
Resilience and vendor risk come next. If a single ledger component stalls, do transfers freeze mid-queue? We will not really know until the network hits heavier loads with nine banks and 500,000 potential wallets online Decrypt.
Interoperability is another hinge. Inside the pilot, things should be smooth. Outside, not so much. Will cross-border corridors show up later, perhaps via BIS-style projects, or does this stay domestically focused? Expect a cautious approach.
Finally, policy drift. The FSC raised limits to make the pilot useful, but those can change fast if abuse patterns appear. Programmability can be a double-edged sword if rules are too aggressive or inconsistent across banks FSC.
Warning: Do not build business-critical flows that depend on any single pilot parameter staying constant. Treat everything as subject to change until there is a formal production spec.
Common Mistakes
- Assuming it is a new currency. It is still KRW in a bank context. Do not treat it like a speculative token.
- Overlooking limits. Hitting the 1,000,000 KRW per transfer cap can derail payroll or vendor runs. Split payments or use existing rails where needed.
- Ignoring programmability. Subsidy funds may be spend-locked. Plan refund and reconciliation flows before launch.
- Skipping device hygiene. Biometric login helps, but a rooted or malware-ridden phone is still a risk. Keep devices updated.
- Building for public chains. This pilot’s ledger is permissioned. Do not assume you can plug in DeFi or external wallets.
If you want regular, no-hype reporting on pilots like this as they move from lab to real life, bookmark Crypto Daily. We track the fine print, not just the headlines.
Frequently Asked Questions
Will tokenized-won wallets pay interest like a normal deposit?
In most deposit-token designs, the token reflects a claim on your bank deposit, not a separate instrument. If your underlying account pays interest, that policy usually carries through. Pilot documentation has not emphasized yield as a feature, so treat it like your regular account unless your bank says otherwise.
Can foreigners or non-residents join the pilot?
Pilots are typically restricted to domestic bank customers with full KYC. Expect a Korean-resident bias, and do not assume support for foreign IDs unless a participating bank explicitly offers it.
Will there be offline payments?
Some CBDC pilots test offline features, but Phase 2 details in Korea have focused on P2P transfers, biometrics, auto top-ups, and subsidies. If offline support appears, it will likely be a limited field test rather than a day-one feature Yonhap.
Can I move tokenized won to a crypto exchange or a self-custody wallet?
Do not count on it. This is a permissioned system inside bank apps. The design prioritizes compliance and control over open interoperability. Treat it as a domestic payment rail, not a bridge to public crypto.
How will refunds work if a merchant mischarges me?
Refunds should route through your bank like any other dispute, but watch for exceptions where programmable funds cannot be freely returned. Expect merchant policies to address this during the pilot.
What happens if a participating bank exits the pilot?
The pilot should have migration playbooks, but specifics are not public. Realistically, balances would be redeemable with the issuing bank or transferred within the network. Avoid holding near the cumulative cap until contingency clarity improves.
Are there tax implications for using tokenized won?
Using a deposit-token wallet for regular payments should mirror normal KRW transactions. If you receive targeted subsidies, keep records in case authorities require proofs for eligible spend. When in doubt, ask your bank or a tax professional.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.