Working with environments that have both v1 and v2 embedded wallets
This article is for developers who are working with environments that have both v1 and v2 embedded wallets. You can check the version of the wallet by checking the version parameter in the verified credential of the wallet.
Overview
Key difference between V1 and v2 embedded wallets
v1 embedded wallets require transaction MFA. This means that before a transaction can be signed by the end user, they must perform an additional MFA step. Currently we support Passkeys and One Time Codes for transaction MFA.
v2 embedded wallets allow transaction MFA to be configured as optional. This means that after an end user logs in/ signs up and obtains a valid JWT, they will be able to perform actions with their embedded wallet without any additional MFA steps.
Currently adding transaction MFA is disabled for v2 embedded wallets. Configuring this will be possible in a future update.
Example of signing a transaction using v1 embedded wallets
Example of signing a transaction using v2 embedded wallets
Was this page helpful?