Versioning

Xellar has introduced an upgrade version of our Embedded Wallets, Version V2 as of 24 June 2024. V2 has multi-chain capability, refresh token, upgraded encryption system and user permission system. See below for more details.

V2

Updated 24 June 2024

• Multi-chain capability
• Refresh Token
• Upgraded Encryption System
• Change file name

Refresh Token & Wallet Token

Using the refreshToken, you can get a new walletToken without the need to re-authenticate the user. The walletToken is used to authenticate the user's wallet actions, and it will be expired directly after one wallet operation is executed

By default the walletToken will be expired after 1 minute, and the refreshToken will be expired after 7 days.

Multi-chain Capability

The V2 Embedded Wallets support multiple chains including :

• Ethereum
• Binance Smart Chain
• Polygon
• Avalanche
• Fantom
• Arbitrum
• Optimism
• Solana
• Tron
• Bitcoin
• Immutable zkEVM
• OKX X-Layer
• Lisk

more to come

User Permission System

V2 introduces a permission system that requires users to explicitly grant permission to your application before wallet operations can be performed.

Permission Fields in walletToken Payload:

• isPermissionGranted (boolean): Indicates whether the user has granted permission to your app
• acceptPermissionPage (string): URL link that users must visit to accept the permission request

Important Implementation Notes:

• When integrating Xellar Embedded Wallet V2, you must redirect users to the acceptPermissionPage URL to grant permission
• Users cannot perform wallet operations without granting permission first
• If permission is not granted, wallet operation endpoints will return error code 407 with a URL link in data.message
• Always check the isPermissionGranted field and handle the permission flow before attempting wallet operations

Legacy

• EVM Compatible
• Basic Auth