Configure the Wholesale CBDC Application
You configure the application by checking application and connection settings, configuring the sign-in process, and configuring user interface settings.
The Setup page acts differently depending on how the wholesale CBDC application was deployed. With one-click deployment, the installation configuration from Oracle Blockchain Platform Enterprise Edition is used, including the identity provider configured for the instance, and this configuration is used to prefill the application values. With a local deployment, the deployer must deploy or connect to the required services and enter the application configuration manually.
Application and Connection Settings
Review or enter the following settings.
The network selection is fixed by the deployed runtime environment. Do not change prefilled contract addresses, service identifiers, OIDC settings, or ORDS settings unless the replacement services belong to the same deployment and the change is part of an approved deployment procedure.
| Setting | One-Click Deployment | Local Deployment |
|---|---|---|
| Token ID | Enter the token ID deployed for this application. | Enter the token ID manually. |
| Protocol and authentication mode | Prefilled from the Oracle Blockchain Platform deployment; normally review only. | Enter the approved local protocol and authentication mode. |
| Besu wrapper API and access token URL | Prefilled by Blockchain Platform Manager. | Enter the URLs for the locally deployed services. |
| Oracle Blockchain Platform Instance client ID and client secret | Prefilled from the Oracle Blockchain Platform instance configuration; the secret remains masked. | Enter the local client values when the deployment requires them. |
| Account and wholesale CBDC contract addresses | Prefilled from the deployed Besu contracts. | Enter the addresses returned by the local contract deployment. |
| UWaaS wallet URL, organization ID, and wallet service instance ID | Prefilled from the Oracle Blockchain Platform instance setup. | Enter the local UWaaS and wallet service values. |
| Default caller address | Prefilled when required by the deployment. | Enter it when the local deployment requires a default caller. |
| ORDS OAuth URL, client ID, and client secret | Prefilled from the ORDS deployment managed by Blockchain Platform Manager; the secret remains masked. | Enter the values for the locally deployed ORDS services. |
Sign-In Process
For one-click deployment, the identity provider is the same one configured for the Oracle Blockchain Platform installation. OIDC or LDAP values are prefilled by Blockchain Platform Manager. Review the values, but do not replace these values unless the Oracle Blockchain Platform deployment configuration is intentionally changed.
For a local deployment, no identity provider configuration is inherited automatically. Enter the issuer URL, client ID, client secret if required, scopes, user-ID claim, exact redirect URI, and post-logout redirect URI. Register the same URLs in the selected identity provider.
OIDC authenticates the identity. The application still checks the selected organization, wallet service instance, active CBDC account, application group, and smart contract role before allowing an operation. Configure multi-factor authentication in the identity provider.
Application Presentation
Open the customization cards and review the following presentation settings.
| Customization Area | Controls |
|---|---|
| Token and CBDC account display names | Names shown in headers, account cards, balances, and transaction forms. |
| Currency and number format | Currency symbol, decimal display, grouping, and symbol position. For U.S. dollars, select USD — US Dollar ($) and confirm the number preview. Besu token decimals come from the deployed contract and cannot be changed during configuration. If the displayed precision is wrong, correct the contract deployment instead of changing display settings to hide the mismatch. The token’s contract-defined decimal precision is read-only in Setup and is not the same as the currency symbol and number formatting used for display. |
| Login branding | Message and image shown before sign-in. |
| Application background | Background color used across the application shell. |
| Transaction labels | User-facing names for transaction types. |
| Organization display names, logos, and order | Presentation of organizations in dropdowns and workspace navigation. Live UWaaS IDs, names, sequences, and founder tags remain authoritative. |
| Application group labels | Names shown for central bank and financial institution personas. |
| Ledger role labels | Names shown for smart-contract permissions such as Token Admin, Minter, Burner, and Escrow/Notary.
|
Apply the Configuration
For one-click deployment, the Apply Changes command validates required fields, saves the token ID and optional customizations, combines them with the configuration from Blockchain Platform Manager, and applies the resulting configuration to the application. When the configuration update or redeployment is complete, the application returns to the sign-in page.
For a local deployment, the Apply Changes command validates required fields and writes the local configuration to the .env.local file. Masked secret fields can be left blank to retain their current values. You must restart the application when requested. The application then returns to the sign-in page.