MFA strengthens account authentication and protected actions by requiring an additional verified factor. In NordBalticum, enabling MFA does not replace wallet-device approval, the wallet PIN or recovery information—it adds another independent decision layer.
Optional user setting
Required for protected access when enabled
Independent from wallet keys
01
More than a login checkbox
A verified MFA factor raises the assurance required for protected account access.
02
Sensitive actions step up
Relevant device, recovery, staking and wallet-security actions can request MFA authorization first.
03
No false substitution
MFA cannot recover a lost self-custody wallet or make an unapproved wallet device trusted.
Why an additional factor matters
An email account or sign-in token can be compromised. MFA requires another verified factor, reducing the chance that one stolen credential is enough to access protected account functions.
NordBalticum treats MFA as account authentication assurance. It stays separate from the cryptographic material used for device trust and wallet access.
Where MFA fits in the full model
First comes account authentication, then session-device trust, then wallet-device authorization and wallet confirmation. MFA strengthens the authentication side of that model and can be required before sensitive actions when enabled.
This separation is intentional: no single factor is described as a universal key to the product.
NordBalticum product view
An additional factor with a defined job
MFA raises account assurance and protects sensitive decisions without pretending to become the wallet key.
Practical flow
What to do next
1
Enroll a supported factor
Enable MFA from account security and complete verification.
2
Store recovery options carefully
Protect any authenticator recovery method separately from wallet recovery material.
3
Expect step-up prompts
When MFA is on, complete it before protected access and relevant sensitive actions.
Security, in plain English
Controls with defined responsibilities
AAL2 for protected access
Verified MFA raises the required authentication assurance when the factor is enabled.
No trusted-device bypass
Device possession is not treated as a replacement for the enabled MFA factor.
Purpose-bound prompts
Sensitive actions ask for authorization in the context of the action being performed.
Clear answers
Frequently asked
Is MFA required for every NordBalticum user?
MFA is optional. When a verified factor is enabled, protected access requires the stronger authentication level.
Does MFA replace my wallet PIN?
No. They protect different boundaries and may both be required for a sensitive wallet action.
Does MFA approve a new wallet device?
No. A new wallet device still needs the supported wallet approval or recovery flow.
