Why
The ordering flip is right and it is the whole point. Ask "where can we use a won stablecoin?" and the answers arrive immediately — retail payments, remittance, games, tourist payments, local currency vouchers — because that question cannot fail. Any transaction can be routed through a token. Ask instead "which transactions in today's finance are uncomfortable enough to be worth changing?" and the question can return nothing, which is exactly what makes it useful. A screen that never rejects is not a screen.
The three-part test in the source is the strongest version of it. Size and count alone select for large volume, not for pain. Adding how large is the existing friction and does a won-denominated token actually reduce it turns a wish list into something that can disqualify, and the closing line is the disqualifier stated plainly: if time and cost do not fall and reconciliation does not improve, it is a can, not a needs.
But the test has to be run, and running it on the source's own four candidates kills or reshapes three of them. That is not a criticism of the list — it is the test working, which is the best thing that can be said about a test.
Corporate cross-border payments have the most friction and the weakest answer to "why won." Business hours, FX, correspondent banks and pre-funded liquidity are real costs, and none of them sit on the domestic leg. The far side wants dollars. A won token improves the half of the journey that is already instant and nearly free in Korea, and the half that hurts is displaced by a dollar stablecoin plus an FX venue, not by a won one. The honest form of this candidate is a two-token design where the won leg is a settlement convenience, not the source of the saving.
Policy funds and subsidies have the clearest answer to "why won" and the least fashionable friction. The currency is not a choice — a government disburses in won, to won-denominated recipients, under audit. And the friction is not speed. It is control and proof: what may this money be spent on, was it, and who can show that later. That is programmability rather than settlement, and it is the one candidate where the money being a token changes what the money is rather than how fast it moves. The catch is that the incumbent is not a bank transfer — Korea already restricts purpose with cards and vouchers, so the bar is a merchant-category rule that works today, and the gain has to be measured against that rather than against nothing.
Agent and machine-to-machine payments cannot be screened by this method at all, and saying so is more useful than fudging it. The friction of a transaction nobody makes is unmeasurable. These are not use cases with hidden pain; they are transactions that do not exist because the approval model makes them impossible, and the correct label is an option, not a candidate. agentic-intent-veto is where the actual hard part lives, and it is not settlement.
Repo, collateral and securities settlement is the largest and the one whose instrument is probably not a stablecoin. The won leg here is genuine — domestic bonds settle in won — and the friction is real, but it needs the central bank and the market infrastructure to move together, which makes it market-structure change rather than something to pilot. And when that moves, the instrument is more likely a deposit token issued by banks under central-bank settlement than an issuer-backed stablecoin. japan-t0-settlement and tokenized-money-banks are the two cards already holding that thread.
One thing the source is right about deserves extending further than it goes. Dollar stablecoin growth carries global dollar demand inside it, so the cases do not transfer. But the method does not transfer either — a US stablecoin is measured against ACH, which is slow and expensive, while a won stablecoin is measured against real-time account transfer that already costs almost nothing. Import the friction estimates along with the use cases and every Korean candidate is scored against the wrong incumbent. That is the trap underneath the trap the source names.
How it works
The screen, with the disqualifier made explicit
| Question | Selects for | Fails if |
|---|---|---|
| Is the transaction large or frequent? | Volume | — (necessary, never sufficient) |
| How large is the friction today? | Pain | The incumbent is already instant and free |
| Does a won token reduce it? | Currency necessity | The painful leg is denominated in something else |
| Do time, cost and reconciliation all move? | Need over possibility | Any one row stays flat → it is a can, not a *needs* |
The four candidates, scored on the source's own test
| Candidate | Friction | Why won? | Verdict |
|---|---|---|---|
| Corporate cross-border / treasury | High — hours, FX, correspondents, pre-funding | Weak — the far leg wants dollars | Reshape: the saving is in the FX leg, not the won leg |
| Policy funds and subsidies | Moderate, and it is control, not speed | Strongest — disbursement is legally won | Best candidate, measured against cards and vouchers rather than transfers |
| Agent / machine-to-machine | Unmeasurable — the transactions do not exist | Neutral | Not a candidate — an option. The method does not apply |
| Repo, collateral, securities settlement | High, and genuinely won-denominated | Strong | Market-structure change, and the instrument is likely a deposit token |
The trap underneath the trap
The source warns against importing dollar-stablecoin use cases. The sharper version is that importing the method fails too, because the incumbent differs:
| United States | Korea | |
|---|---|---|
| Domestic retail baseline | ACH — slow, batched, priced | Real-time transfer, effectively free |
| So a stablecoin must beat | A weak incumbent | A strong one |
| Which means | Retail payment cases score well | Retail payment cases mostly fail the screen |
This is why retail payments and tourist payments keep appearing on Korean lists and keep going nowhere: they are scored against the wrong baseline. The candidates that survive here are the ones where the incumbent is weak for a structural reason — a border, an audit requirement, a market infrastructure — not for a technical one.
What this catalogue already holds on the same thread
| Card | What it settles that this one assumes |
|---|---|
two-currencies-one-ledger |
The same "why this currency" question, asked of a euro stablecoin — and the four different products the answers imply |
stablecoin-redemption-desk |
Circulation is won at the redemption desk; a use case with no redemption path is not a use case |
korea-digital-asset-act |
Who may issue a won stablecoin at all — unresolved, and it changes which candidates are even reachable |
tokenized-money-banks |
The deposit-token alternative for the settlement candidate |
agentic-intent-veto |
Why the agent candidate's hard problem is authority, not payment |
The one-day version
Pick the policy-fund candidate, since it scores best, and fill four rows for a single real disbursement — time, cost, institutions touched, human confirmations — first as it happens today, then as it would with a token, ramps included. Publish the row that does not move. That row is the finding, and it is worth more than a list of possibilities.