BmoniEmbeddedSdk.initialize accepts two optional parameters. You can call it as many times as needed — each call replaces the active configuration.
Parameters
Reading the active config
The current configuration is always accessible:
Use these in your UI to render a PIN input of the right length or hide PIN flows entirely.
requirePin: false — delegating auth elsewhere
When you manage authentication outside the SDK (biometrics, OS lockscreen, server-side challenge), set requirePin: false:
When requirePin is false, any supplied pin argument is silently ignored by signMessage, signTransactionHash, and deleteWallet. PIN management methods (setPin, changePin, etc.) still work — toggling requirePin only changes whether the stored PIN is used as a gate.
Changing the PIN length at runtime
You can change pinLength after a PIN is already set. However, the stored digest was created with the old length — you will need to prompt the user to remove and re-create their PIN for verification to succeed.