Wholesale CBDC Wrapper API Workflow

The wholesale central bank digital currency (CBDC) scenario represents currency that is distributed through a structured financial institution hierarchy.

In this scenario, the central bank approver governs all central bank operations, while financial institution approvers govern internal transfers at the institutional level. Tokens are minted by the creator and issued to financial institution officers by the issuer. Financial institution officers then issue the tokens to financial institution users. Tokens can be burned by the retirer. In the non-confidential version, all transaction details including participant account information and actual balance values are stored directly on the public ledger in plain form. There is no separation between sensitive and non-sensitive data, making it suitable for environments where transaction privacy is not required.

• Minter, burner, and notary roles are required.
• The burner role is assigned to the retirer. Regular users cannot burn their own tokens.
• All hold-based transfers run in two steps: first the holdTokens API and then either the executeHoldTokens or releaseHold API.
• The issuer acts as the distribution point, choosing whether to route tokens to the financial institution hierarchy or to the retirer.

The following diagram shows a typical process flow when using the sample non-confidential wholesale CBDC wrapper APIs.

Description of the illustration cbdc_non-confidential_-_wrapperapi.png