Troubleshoot the Wholesale CBDC Application

The following information covers how to troubleshoot problems you might encounter with the application.

Sign-In Returns to an Error Page

For OIDC, verify the issuer, client, exact callback URL, audience, discovery/JWKS reachability, TLS trust, and session configuration. For LDAP, verify the LDAP configuration. If accounts are missing, make sure to preserve the Token Admin and Org Admin role-only administrator sign-in exceptions. Confirm that the user has an eligible active wallet/account for the configured organization and wallet service instance.

No Wallet Is Available

Verify UWaaS reachability, organization mapping, wallet service instance, user identity, and access scope. If multiple wallets are returned, select the wallet for the intended wholesale CBDC account.

Account Exists but an Operation Is Unvailable

Check the account status, application group, and ledger role. The central bank administrator can use the Account Actions > Sync Roles command when authorized. Log out and log in again after a role change, so that the session is rebuilt.

Organization Order Is Incorrect

Reload the live registry and check for founder tag conflicts. Check for missing, duplicate, or non-consecutive sequence values, which the application can reconcile for ordering. Display name does not control order. Multiple founders require manual data repair before the wholesale CBDC application can reconcile the registry.

Stale Balance or Pending State

Use the page refresh action and check the operation ID in the history. Confirm Besu and ORDS health before retrying. Do not submit the operation again until the first operation is fails or is in a terminal state.

Approve/Reject Is Unavailable

Confirm that the account is active, the user has the required escrow/manager role, the request is still pending, and the request is assigned to the current approval context.