Summary
Central bank digital currencies (CBDCs), as an emerging digital payment infrastructure, have application pathways in domain payment scenarios that are not yet mature but hold research value. This article analyzes the applicability differences between account-based and token-based CBDC architectures for domain registration payment processes, assesses the potential impact of CBDC deployment on DNS infrastructure and the ICANN governance framework, and compares CBDC payment pathways with stablecoin options such as USDT.
Problem Definition
The core research question of this page is: what are the viable technical pathways for CBDC in domain payment scenarios? How does the applicability of different CBDC architectures (account-based vs. token-based) vary for domain registration payment processes? What potential impacts could large-scale CBDC deployment have on DNS infrastructure and domain governance? The research scope covers both cross-border and local payment scenarios for retail CBDC.
Background
The Bank for International Settlements (BIS) classifies CBDCs into retail and wholesale types. Retail CBDC is intended for public use, while wholesale CBDC is used for inter-financial institution settlement. In terms of technical architecture, CBDCs can be divided into account-based (balance model based on centralized ledgers) and token-based (UTXO or similar model based on distributed ledgers). e-CNY adopts a hybrid architecture combining account-based and quasi-token-based models, implemented through designated operating institutions (commercial banks and payment platforms) in a two-tier operating model.
The DNS system managed by ICANN and the CBDC payment system belong to different infrastructure layers: DNS handles domain name resolution, while CBDC handles value transfer. The two intersect in the domain registration payment scenario: domain holders pay registration fees through CBDC, and registrars complete domain configuration through the DNS system. Existing practices of purchasing domains with cryptocurrency (such as USDT payments) provide a reference model for CBDC payment pathways.
Core Findings
-
Account-based CBDC pathways rely on intermediary integration: Account-based CBDCs (such as e-CNY) require integration with domain registrar payment systems through designated operating institutions, and registrars must establish technical connections with these institutions. This pathway offers higher compliance but lower technical flexibility.
-
Token-based CBDC pathways can enable automation: Token-based CBDCs can implement automated payment-to-configuration workflows for domain registration through smart contracts, but registrars need to deploy blockchain nodes or use oracle services, creating higher technical barriers.
-
Cross-border CBDC payments face jurisdictional challenges: Multi-CBDC interoperability architectures (such as the mBridge project) provide a technical foundation for cross-border domain payments, but CBDC policy differences across jurisdictions may lead to fragmented payment pathways.
-
Limited direct impact on DNS infrastructure: As a payment tool, CBDC deployment does not directly affect the technical architecture of DNS. However, at the governance level, cross-border CBDC usage may influence ICANN’s compliance oversight approach for domain registrars.
-
Greater complementarity than substitutability with USDT payments: CBDC and USDT serve different needs in domain payment scenarios: CBDC suits domain holders seeking legal tender assurance, while USDT suits scenarios prioritizing payment flexibility and privacy. Requirements for anonymous domain registration are more difficult to meet within the CBDC framework.
| Payment Pathway | Applicable CBDC Type | Technical Complexity | Compliance | Privacy Protection |
|---|---|---|---|---|
| Operating institution gateway | Account-based | Medium | High | Low |
| Smart contract automation | Token-based | High | Medium | Medium |
| mBridge cross-border bridge | Hybrid | High | TBD | Medium |
| Wallet direct payment | Quasi-token-based | Low | High | Low |
Risks and Limitations
| Risk Item | Impact Level | Mitigation Measures |
|---|---|---|
| CBDC payment channel not integrated | High | Choose registrars supporting multiple payment methods |
| Inconsistent cross-border CBDC policies | High | Monitor multi-CBDC interoperability projects like mBridge |
| Operating institution service disruption | Medium | Configure backup payment methods (such as USDT) |
| CBDC programmability restrictions | Medium | Understand CBDC smart contract conditional limits |
| Lower privacy protection than USDT | Medium | Use WHOIS privacy protection within compliance frameworks |
Compliance Boundaries
The research content of this article is based on publicly available documents from BIS, ICANN, and the People’s Bank of China, and does not constitute any investment or payment method recommendation. Cross-border CBDC usage must comply with foreign exchange management and anti-money laundering regulations in each jurisdiction. The need for anonymous domain purchases is constrained by stronger KYC/AML requirements within the CBDC framework. Domain holders should recognize that CBDC payment compliance is typically higher than private stablecoin payments. This article does not provide methods for evading regulations or circumventing KYC.
Related Resources
- CBDC and Domain Infrastructure Research: Overall framework for CBDC-DNS cross-cutting research
- e-CNY Domain Payment Feasibility Analysis: Specific analysis of e-CNY in domain payments
- CBDC vs Stablecoin Domain Payment Differences: Comparison of payment pathways between CBDC and stablecoins such as USDT
- USDT Glossary: Understanding the basic concepts of USDT and its differences from CBDC
- 2026 CBDC and Domain Infrastructure Report: Annual industry trends and data analysis
Frequently Asked Questions
Can CBDC be used to purchase domains
Theoretically, CBDC can be used for domain payments, but practical feasibility depends on the CBDC's technical architecture and the registrar's payment integration capabilities. Account-based CBDC (such as e-CNY) requires integration through designated operating institutions, while token-based CBDC can enable automated payments through smart contracts. Most domain registrars have not yet integrated CBDC payment channels.
What is the difference between CBDC and USDT domain payments
CBDC is issued by central banks with legal tender status and centralized management features, while USDT is a private stablecoin issued by Tether with decentralized settlement. CBDC payments are typically subject to stricter KYC/AML requirements, while USDT payment compliance varies by registrar and jurisdiction.