- Connect and verify in a single SDK call In this case, the wallet account is only added to the wallet accounts list once it passes the verification step.
- Connect without verifying In this case, the wallet account is added to the wallet accounts list as soon as the user accepts the connection, but it will only be persisted in the local session and not associated to a Dynamic user.
-
Verify a wallet account that has been connected but not verified before
In this case, the wallet account remains in the wallet accounts list, no matter if the verification step is successful or not.
The difference is that the wallet account will have a new
verifiedCredentialIdproperty, be persisted in the Dynamic server and associated to a Dynamic user.
1. Connect and verify a wallet in a single SDK call
On mobile,
connectAndVerifyWithWalletProvider throws a DeeplinkConnectAndVerifyUnsupportedError
for deep link wallet providers (e.g. Phantom redirect). This is because it triggers two sequential
deep links and iOS will not honor the second one. Use options 2 and 3 below to connect and verify
separately. See the Phantom Redirect Extension docs
for a full example.2. Connect a wallet without verifying it
3. Verify a connected wallet account
You can use this function to verify a wallet account that was connected but not verified before.Hardware wallet connections
BothconnectWithWalletProvider and connectAndVerifyWithWalletProvider accept an optional
hardwareWalletVendor parameter to connect via a hardware wallet (e.g., Ledger) through a
compatible software wallet: