Return to CBDC Benefits, Risks, and Policy Considerations

Return to Top

• How could a CBDC be designed to achieve transferability across multiple payment platforms?
• Would new technology or technical standards be needed?

Return to Top

By using a system designed roughly as outlined in section 70_dualnets, much of the current infrastructure would remain in place and to achieve transferability across multiple payment platforms would be very little different than the current system.

Table 1 provides the system components of a very simplified, theoretic ACH / CBDC network. Figure 1 graphically shows a theoretical, very simplified, dual ACH-CBDC Network Concept. A newly developed Application Programming Interface (API) and a specialized bridge going between the existing ACH Network and the new U.S. CBDC network would allow the existing platforms to work fairly seamlessly.

The existing Intermediaries would have time to adopt and adapt to the new API and use a “stubbed out” bridge as a first step toward the support of the U.S. CBDC in the future. The API and “stubbed out” bridge would connect to the existing ACH Network. As the CBDC network comes online, the existing Intermediaries would be able to join. This would allow a phased roadmap for the transition. New Intermediaries would start using the new API and the new U.S. CBDC network when it becomes available.

Figure 1: Theoretical Very Simplified Dual ACH-CBDC Network Concept.

Return to Top

The “desirements” specified in White Paper and identified by the OMG's White Paper Analysis as achieving transferability across multiple payment platforms are listed in Table 2.

Note: B = Benefit, P = Policy, R = Requirement, D = Design.

Return to Top

Table 3 provides discussion points for each of the “desirements” identified by the OMG's White Paper Analysis which apply to achieving transferability across multiple payment platforms.