
This section presents a set of use cases for a commercial reference implementation of CBDC (Central Bank Digital Currency) -
| Characterization | Cash currency | Reference CVCB* |
| suitable as legal tender | YES | YES |
| legal finality of payments | YES | YES |
| no interest | YES | YES |
| bearer financial instrument | YES | YES |
| Central Bank money | YES | YES |
| anonymity | YES | YES ** |
| no censorship | YES | YES |
| free use | YES | YES |
| accessibility to everyone | YES | YES *** |
| autonomy of payments | YES | YES *** |
| instantaneous payments | YES | YES |
| retail payments | YES | YES |
| interbank payments | NO | YES **** |
| cross-border payments | NO | YES ***** |
| payment in the same place | desperately | anywhere |
| payment at the same time | desperately | whenever |
| risk of being stolen | tall | low |
| risk of being lost | average | low |
| risk of being counterfeited | tall | null |
| level of adherence to ALM rules | low | tall |
| ALM rules support level | no | YES |
| programmability | no | YES ****** |
| nominal cost | fixed | flexible |
| production costs | high | zero |
| destruction costs | high | zero |
| support costs | high | low |
| public good | YES | YES |
| nature (of money) | Fiat | Fiat |
| equality to M0 (cash in circulation) | 1:1 | 1:1 |
| equality to M1-M0 (Central Bank reserves) | NO | market or 1:1 |
| parity to M2-M1 (bank accounts) | 1:1 with limit | market or 1:1 |
| equality to M3-M2 (savings accounts) | NO | market or 1:1 |
| source (of money) | Society | Society |
Some exotic requirements in some countries can be implemented via an API. It is assumed that each country uses its own national version of the CIRF. If a country requires something different from what the reference CBDC solution offers , it can expand and customize the functionality without violating the fundamental principles of the CIRF. Thus, national CIRFs are naturally integrated into the international (global) CIRF, and the chosen architecture ensures CBDC compatibility by design.
In addition to CBDC, CIFI allows the following:

Using CBDC is entirely digital and very similar to using cash. Additional advantages include remoteness (in time and space) and greater security.
Interbank payments in CIFR do not require any additional (and very expensive) systems.
As a rule, the decision to introduce a CBDC for retail payments is very difficult for central banks, so the option of initially implementing interbank payments is possible.
Some CBDCs can be additionally labeled as issued to finance a major project. This additional labeling makes it possible to track the use of these CBDCs and, thus, reduce corruption.
If shares are transferred to the digital space, then CIRF implements the standard “Delivery vs Payment” (DvP) option.
Legal certificates can be represented in DIGITAL as legally codified digital assets.
Payment from IoT applications is implemented as a standard process in DIGITAL.
City, territory, administrative unit, etc. can create their own digital local currency to support local producers of goods and services.
A digital asset exchange may issue its own currency.
Imagine that leading international financial institutions (IMF, BIS, FATF, SEC, etc.) agreed to adopt this architecture. Then, the CIFR could be deployed in any country, guaranteeing the international compatibility of the CBDC.
