Retail stablecoins · design tradeoffs between regulatory control and open UX

Wiki route

This entry sits under fintech index. Read it with Japan’s financial regulation — legal framework for tokens, crypto-assets and payments for adjacent context and Japan’s three-tier stablecoin legal framework (JPYC, USDC and Project Pax) for the broader system boundary.

[!info] TL;DR A retail stablecoin in Japan must coordinate the issuing entity, intermediary registration, identity verification, redemption and wallet UX. The design is not, however, a binary choice between bank issuance and a fully permissionless system. Issuance routes through banks, funds-transfer providers, trust companies and similar entities can be combined in several ways with registered intermediaries and wallets.

Conclusion

The following is not a legal binary classification, but an analytical model showing two design poles.

It is based on the FSA’s materials on electronic payment instruments, registry of electronic payment instrument service providers, and registry of funds-transfer providers. Registration does not automatically mean that every product has been issued or made available.

Design options:

• KYC × wallet integration → My Number wallet model (maina-wallet-kyc-permissionless-ux-bridge)
• Smart-contract controls → escrow, conditional payments, reversibility and controls for large-value payments
• ID integration + product-specific amount conditions → for high-value or conditional transactions, compare requirements with those for prepaid payment instruments and funds-transfer businesses

Reasoning

• Existing domestic options include cards, bank transfers, prepaid payment instruments and funds-transfer services, so a new product must identify its target customers and incremental value.
• Bank issuance alone does not determine competitiveness; compare redemption, acceptance, fees, recoverability and conditional payments.
• Do not generalize transaction counts from an individual experiment into demand or future adoption across Japan.
• Evaluate KYC, wallet recovery, conditional payments and external-service integration individually as candidates for incremental value.
• When using a high-value or conditional transaction as an example, identify the applicable issuance category, product limit, identity-verification requirement and consumer protection.

Applicable When

• Before designing a retail stablecoin business, when comparing combinations of issuance, intermediation, redemption and wallet design
• Preparing a response to “Isn’t PayPay enough?”
• Designing the retail axis / retail use cases of a commercial stablecoin (for protocol UX foundations, see ERC-7702 / Privy embedded wallet)
• When regulators ask what social value a retail stablecoin provides and concrete benefits and user protection must be organized

Source

• Alignment: Minna Bank TD/SC strategy (retail stablecoins and retail deposit tokens face the same tradeoff axis)
• Alignment: Two tracks for AI payments (as with Stripe vs stablecoins, differentiation lies outside payment alone)
• Public framework materials: https://www.fsa.go.jp/policy/virtual_currency02/index.html

Related

• Wiki Index
• Institutional stablecoin = deposit token
• My Number wallet KYC × UX bridge
• onchain-finance-vs-crypto-bifurcation
• Minna Bank BaaS model