BE Custody x MetaMask should be used only where your organisation has approved MetaMask-based workflows and the relevant wallet, network, and user permissions are configured for that use.
It is intended for controlled interaction with supported Web3 workflows while keeping custody governance, approval, and signing controls within the BE Custody operating model.
Typical use cases
Depending on your organisation’s setup, BE Custody x MetaMask may be used for activities such as:
- Connecting a BE Custody-controlled wallet to an approved decentralised application
- Preparing a transaction through a MetaMask-supported workflow
- Interacting with supported smart contracts
- Reviewing transaction details before approval
- Routing signing activity through BE Custody approval workflows
- Supporting operational separation between initiation and approval
Use cases should be approved internally before users connect wallets or initiate activity.
When should I not use it?
Do not use BE Custody x MetaMask if:
- The decentralised application has not been approved by your organisation
- The network is not supported or not intended for the activity
- The wallet or sub-wallet is not approved for the workflow
- The transaction type is not understood
- The smart contract interaction cannot be reviewed
- The request does not match an internal instruction or approval record
- You are asked to bypass normal BE Custody approval workflows
- Transaction details shown in MetaMask and BE Custody appear inconsistent
If anything is unclear, stop and escalate before proceeding.
What should be approved internally?
Before using BE Custody x MetaMask, your organisation should define which users, wallets, networks, and decentralised applications are approved for use.
This may include internal decisions on:
- Approved dApps
- Approved wallets or sub-wallets
- Supported networks
- Permitted transaction types
- Transaction value limits
- Required approval workflows
- Required records or ticket references
- Escalation routes for unexpected activity
What should initiators check?
Before initiating a MetaMask-based transaction, check:
- The dApp is approved by your organisation
- The connected wallet or sub-wallet is correct
- The selected network is correct
- The transaction details match the intended action
- The asset, token contract, amount, and recipient are correct, where applicable
- The smart contract interaction is understood
- The transaction aligns with your organisation’s internal process
Do not initiate a transaction if the details are unclear or unexpected.
What should approvers check?
Before approving a MetaMask-related request in BE Custody, approvers should check:
- The request is expected
- The dApp interaction is authorised
- The wallet, network, asset, and amount are correct
- The contract interaction is understood
- The request matches the intended instruction
- Any required internal record is in place
- The request does not appear unusual, rushed, or inconsistent with normal activity
Each approver should perform their own review. Do not approve solely because another authorised user has approved.
Does using MetaMask change custody control?
No. Using BE Custody x MetaMask does not mean private keys are exposed to MetaMask or to the user.
Users interact through MetaMask-supported workflows, but signing remains subject to the applicable BE Custody controls, permissions, and approval processes.
What should I do if something looks wrong?
If anything looks wrong in MetaMask, the Snap, or BE Custody, do not continue.
Follow your organisation’s internal escalation process. If support is required, contact Bitpanda Enterprise Custody Support through the approved support channel.
Do not include passwords, PINs, private keys, seed phrases, API keys, API secrets, access tokens, or other sensitive authentication information in a support request.