Immutable Passport is a non-custodial wallet and sign-in system designed for games built with Immutable’s blockchain infrastructure. It lets a player create an account with familiar email or social authentication, receive a wallet and use supported onchain game features without beginning with a browser wallet extension or a seed phrase. It is not a government passport, a universal proof-of-personhood system or an identity check for every Web3 service.
This guide explains what Passport does, how its login and wallet layers fit together, what “non-custodial” means in this context and which security and privacy questions players and developers should ask.
What Immutable Passport is
Immutable describes Passport as a wallet and identity product built for games. From a player’s perspective, it combines authentication, a persistent account and an Ethereum-compatible wallet used by supported applications. From a developer’s perspective, it provides software development kits and authentication clients that a game can integrate into onboarding and onchain actions.
The product is focused on the Immutable ecosystem. A game or marketplace must integrate Passport; owning an account does not make it work on every website, blockchain or decentralized application. Compatibility depends on the application’s implementation, supported network and current product documentation.
| Layer | What it does | What it does not prove |
|---|---|---|
| Authentication | Signs a player into an integrated app using supported email or social methods | Legal identity, age, citizenship or uniqueness as a human |
| Passport account | Provides a consistent user identity across participating integrations | Compatibility with every game or Web3 service |
| Wallet | Holds addresses and authorizes supported blockchain actions | That an asset is valuable, safe or legitimate |
| Developer integration | Connects login, wallet requests and game flows | That the game itself is secure or trustworthy |
How Immutable Passport works
A typical flow has several steps. The exact screens can change as the product evolves, but the underlying roles are important.
- The game requests sign-in. An integrated application sends the player through Passport’s authentication flow.
- The player authenticates. Passport supports familiar email or social login methods. Older official documentation describes OpenID Connect and authorization flows; developers should follow the current SDK documentation rather than copy an obsolete integration.
- The application receives identity tokens. Properly validated tokens let the application identify the signed-in Passport account. Tokens are credentials and should be handled securely.
- The wallet is initialized. When needed, the application can request the player’s wallet address and supported wallet functions.
- The player authorizes an action. A game may request a transaction or typed-data signature. The interface should make the action and its consequences understandable.
The login identity and blockchain address are related but not interchangeable. A login token tells an application about an authenticated session. A wallet signature authorizes a cryptographic action. Our guide to public and private keys explains why possession of signing authority matters.
What “non-custodial” means
Immutable calls Passport non-custodial. In general, a non-custodial wallet is designed so that the service provider cannot unilaterally move a user’s assets as a conventional custodian could. That is an important distinction, but it does not mean the system has no dependencies. Account access, recovery, software availability, network support and the application’s user interface still matter.
Players should read the current terms and recovery documentation before storing meaningful assets. They should know which authentication methods are attached, how recovery works, whether an external wallet can be linked and what happens if they lose access to an email or social account. A convenient login reduces seed-phrase friction; it does not eliminate account-security responsibility.
Current Immutable terms say Passport is intended for gameplay assets rather than significant value and set an AUD 1,000 transaction and wallet-value limit, with the U.S.-dollar equivalent reviewed periodically. Terms can change, so users should check the version in force before funding the wallet and move assets above the permitted limit to an appropriate wallet they control.
Address, account and asset are different
A wallet address is a public identifier for receiving and tracking blockchain assets. It is not a username that can be corrected if mistyped. Before transferring an asset, confirm the network, asset contract and destination. Sending to an incompatible address or network can cause permanent loss. See our practical guide to using a crypto address safely.
Gas sponsorship and the player experience
Immutable promotes gas sponsorship as part of Passport’s game-focused experience. A developer or platform can cover eligible transaction fees so a player does not need to acquire a network token before performing an in-game action. This can simplify onboarding, but “gas-free” is a user-experience arrangement, not the absence of blockchain costs. Someone funds the transaction, and sponsorship policies may impose limits or change.
Players should not assume every action is sponsored. A game should state which transactions qualify, what happens when sponsorship is unavailable and whether a transaction can be retried safely. Developers should also protect sponsorship endpoints from abuse and monitor unexpected transaction patterns.
Game assets and NFTs
Passport can support game inventory and onchain actions involving tokens. Some game items use NFT standards, while others may remain in a conventional game database. An NFT can identify a token and its ownership history, but it does not guarantee that the related game will remain online, that an item will retain utility or that a marketplace will list it.
Before buying or transferring a game asset, check the official contract address, supported network, issuer and actual rights attached to the token. Metadata can point to media or attributes, but the token is not necessarily the artwork or a copyright license. Our NFT guide explains those boundaries, while the Magic Eden safety guide covers marketplace-specific checks.
What Immutable Passport does not do
- It is not a legal identity document. The name “Passport” refers to account portability and onboarding, not government-issued identification.
- It does not automatically verify a real person. Email or social authentication proves control of a login method, not a person’s civil identity or uniqueness.
- It is not universal across Web3. A service must integrate it and support the relevant network and functions.
- It does not make every transaction safe. A valid signature can still approve a malicious or mistaken action.
- It does not guarantee asset value or game continuity. Token prices, utility and application support can change or disappear.
- It is not the same as a privacy system. A blockchain address and its activity may be publicly observable even when the person’s real-world name is not shown.
Security checklist for players
- Start from an official source. Use a game’s verified site or Immutable’s official pages, and check the domain before signing in.
- Protect the connected login. Use a unique password and multifactor authentication on the email or social account when available.
- Read every transaction prompt. Check the requesting application, network, asset and action. Do not approve a vague or unexpected signature.
- Ignore unsolicited support messages. A genuine support agent should not ask for a password, recovery secret or private key.
- Test transfers with a low-value asset. Confirm the address and network before moving something difficult to replace.
- Review connected applications. Remove access you no longer use where the product provides that control.
- Keep independent records. Save transaction identifiers and official purchase details without storing sensitive secrets in plain text.
Privacy considerations
Passport’s convenience depends on linking authentication, application activity and wallet functions. Players should review the current privacy notice to understand what Immutable and the game developer each collect, why they collect it, retention periods and available rights. The game and Immutable are separate actors; one privacy policy may not describe the other’s data practices.
Public blockchains create an additional layer. Transactions associated with an address can be visible indefinitely, and analytics may connect activity across applications. Avoid treating a public wallet address as confidential, but do not publish unnecessary links between that address and personal information. Developers should minimize personal data in logs and never put sensitive information directly onchain.
Account deletion also has limits in a blockchain context. A service may be able to close an account or delete offchain profile data where law and policy permit, but it generally cannot erase confirmed public transactions from the network. A good privacy notice distinguishes mutable account records from permanent ledger data and explains how requests are handled.
Developer responsibilities
Passport can streamline onboarding, but integration quality determines whether the result is safe and understandable. Developers should use current official SDKs, follow supported authorization flows and validate identity tokens correctly. Redirect URLs, environment settings and API credentials need careful configuration. Secret keys belong on protected server infrastructure, not in public client code.
- Separate sandbox and production projects, networks and credentials.
- Use clear consent screens that describe the asset, amount and action before a signature.
- Handle expired sessions, cancelled requests and network failures without accidentally repeating transactions.
- Provide account-recovery and customer-support routes that cannot be easily impersonated.
- Explain which data belongs to the game, which belongs to Passport and which is public onchain.
- Design a migration plan for product, SDK or network changes instead of assuming an integration will remain static.
How to decide whether to use Immutable Passport
For a player, the main benefit is simpler access to supported blockchain games. The tradeoff is reliance on an integrated account system and the need to understand both login security and wallet authorization. Use it because a game you trust supports it and because you understand the recovery and transaction model—not because the product name implies universal verification.
For a developer building on Immutable, Passport may reduce onboarding friction and provide a consistent wallet layer. The decision should still account for platform support, user geography, privacy obligations, accessibility, recovery, sponsorship cost and the consequences of vendor dependency. Test the complete player journey, including error and support paths, rather than evaluating only the successful login.
Frequently asked questions
Is Immutable Passport a crypto wallet?
Yes. Immutable describes it as a non-custodial wallet and identity product for games. It also provides an authentication layer, so it is more than a standalone address viewer.
Does it require a seed phrase?
Passport is designed to avoid asking players to manage a seed phrase during typical onboarding. Users should still read current recovery documentation and secure the authentication methods connected to the account.
Can Passport be used in any game?
No. The game or application must integrate Passport and support the relevant Immutable network and wallet functions.
Are Passport transactions always free?
No. Some eligible actions may be gas-sponsored, but coverage depends on the application and its policy. Confirm the transaction details before approval.
Does Passport verify my legal identity?
Not by default. Authentication demonstrates control of a supported sign-in method. It is not the same as government identification, age verification or a formal know-your-customer check.
The bottom line
Immutable Passport is best understood as gaming infrastructure: a familiar sign-in combined with a wallet for supported Immutable applications. Its value is reduced onboarding friction, not universal identity or guaranteed safety. Players should protect the connected login and verify every wallet action. Developers should treat authentication, transaction design, privacy and recovery as core product responsibilities. That factual framing is more useful than calling Passport a ticket to every part of Web3.

Leave a Reply