It is designed to support controlled interaction with decentralised applications while keeping custody governance, approval workflows, and signing controls within the BE Custody model. Availability and behaviour may depend on your organisation’s BE Custody configuration, enabled networks, wallet setup, permissions, and the supported MetaMask Snap version.
Why use the BE Custody MetaMask Snap?
The BE Custody MetaMask Snap can help organisations interact with supported Web3 workflows while maintaining institutional custody controls.
Depending on configuration, it may support use cases such as:
- Connecting BE Custody-controlled wallets to supported decentralised applications
- Creating transaction requests through MetaMask-supported workflows
- Reviewing transaction details before approval
- Applying BE Custody approval and signing controls
- Supporting operational separation between transaction initiation and approval
- Maintaining custody governance when interacting with external applications
The Snap should only be used in accordance with your organisation’s internal policies and approved operational process.
Does the Snap expose private keys?
No. The BE Custody MetaMask Snap does not expose private keys to users.
Users interact with MetaMask and BE Custody workflows through approved interfaces. Private keys are not displayed, copied, exported, or manually handled as part of normal Snap usage.
Transaction signing remains subject to the applicable BE Custody controls and approval workflows.
Who can use the Snap?
Use of the BE Custody MetaMask Snap depends on your organisation’s configuration and the permissions assigned to each user.
Users may need appropriate access to:
- BE Custody
- The relevant wallet or sub-wallet
- The Bitpanda Custody iOS app
- MetaMask
- The supported Snap workflow
- Any relevant approval or signing process
Your organisation may also define internal rules for which users, wallets, networks, or decentralised applications are approved for use.
What should I check before using the Snap?
Before using the BE Custody MetaMask Snap, check:
- The wallet or sub-wallet is correct
- The network is supported and intended
- The decentralised application is approved by your organisation
- The transaction details match the intended action
- The asset, token contract, amount, and recipient are correct, where applicable
- The request aligns with your organisation’s internal process
- Any required approvals or records are in place
Do not proceed if the request is unexpected, unclear, or inconsistent with your organisation’s approved process.
What should approvers check?
Approvers should review the BE Custody approval request independently.
Before approving, check:
- The transaction is expected
- The dApp interaction is approved by your organisation
- The wallet, network, asset, and amount are correct
- The contract interaction is understood, where applicable
- The request matches the intended instruction
- The request does not appear unusual, rushed, or inconsistent with normal activity
Do not approve a MetaMask-related request simply because another user has initiated or approved it.
Are all dApps supported?
No. Use of the Snap does not mean that every decentralised application, network, asset, token, or transaction type is supported or approved.
Support may depend on BE Custody configuration, MetaMask behaviour, network support, Snap capability, and your organisation’s internal policy.
Users should not connect to or interact with dApps unless they are approved under the organisation’s internal process.
What should I do if something looks wrong?
If transaction details in MetaMask, the Snap, or BE Custody look unexpected or inconsistent, do not continue.
Follow your organisation’s internal escalation process. If support is required, contact Bitpanda Enterprise Custody Support through the approved support channel and include relevant wallet, network, transaction, Snap, and timing details.
Do not include passwords, PINs, private keys, seed phrases, API keys, API secrets, access tokens, or other sensitive authentication information in a support request.