A MetaMask transaction may need BE Custody approval because the wallet is controlled through the organisation’s BE Custody governance model.
Although the transaction may be initiated through MetaMask or a connected decentralised application, signing remains subject to the applicable BE Custody roles, permissions, approval workflows, and quorum requirements.
Why approval is required
BE Custody approval helps ensure that MetaMask-related activity is reviewed before it proceeds.
Depending on your organisation’s configuration, approval may be required to confirm that:
- The transaction is expected
- The connected wallet or sub-wallet is correct
- The network is correct
- The dApp interaction is authorised
- The transaction type is understood
- The asset, token, contract, amount, and recipient are correct, where applicable
- The request matches the intended instruction
- Any required internal record or approval is in place
Approval should be treated as an independent control point, not as a formality.
Does MetaMask sign the transaction?
No. In a BE Custody x MetaMask workflow, private keys are not exposed to MetaMask or to the user.
MetaMask may be used to initiate or prepare an interaction, but the signing process remains controlled through BE Custody according to the organisation’s configured custody model.
Who can approve the transaction?
Only authorised users with the required BE Custody role and permissions can approve a MetaMask-related transaction.
Approval eligibility may depend on:
- The user’s assigned role
- The wallet or sub-wallet involved
- The network
- The transaction type
- The applicable approval workflow
- Quorum requirements
- The organisation’s governance configuration
Each approver should perform their own review before approving.
What if the transaction requires quorum approval?
If quorum approval is required, the transaction will not proceed until the required approval threshold has been met.
Each approver should independently verify the request. Do not approve a transaction simply because another authorised user has already approved it.
What should approvers check?
Before approving, check:
- The transaction is expected and authorised
- The dApp is approved by your organisation
- The connected wallet or sub-wallet is correct
- The selected network is correct
- The asset, token, contract, amount, and recipient are correct, where applicable
- The smart contract interaction is understood
- The request matches the intended instruction
- The request does not appear unusual, rushed, or inconsistent with normal activity
Do not approve if any detail is unclear, unexpected, or inconsistent.
What happens if approval is not completed?
If the required approval is not completed, the transaction will not proceed.
Depending on the workflow and configuration, the request may remain pending, expire, be rejected, or require further action.
What should I do if I do not recognise the transaction?
If you do not recognise a MetaMask-related transaction, do not approve it.
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, dApp, 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.