If you see an error saying another Ethereum transaction is pending, it may mean that an earlier Ethereum or EVM-compatible transaction from the same wallet is still waiting to be processed.
Ethereum-style networks process transactions from the same account in nonce order. If an earlier transaction is pending, later transactions may not progress until the earlier transaction has been confirmed, replaced, cancelled, failed, or otherwise resolved through the supported workflow.
What does this error mean?
The error usually indicates that there is already a pending transaction associated with the same account or wallet context.
This may happen where:
- A previous transaction has not yet confirmed
- A previous transaction is waiting for network processing
- A transaction is pending because of network congestion
- A transaction fee was too low for current network conditions
- A replacement or cancellation workflow is required
- A later transaction is blocked by an earlier nonce
The exact behaviour depends on the asset, network, transaction status, and your organisation’s BE Custody configuration.
What is a nonce?
A nonce is a sequence number used by Ethereum and EVM-compatible networks to order transactions from the same account.
Transactions must normally be processed in nonce order. If a transaction with an earlier nonce is pending, later transactions from the same account may remain blocked until the earlier nonce is resolved.
What should I check first?
Before raising a support request, check:
- The transaction status shown in BE Custody
- Whether another Ethereum or EVM-compatible transaction is pending
- Whether the earlier transaction has a transaction hash
- Whether the earlier transaction has been submitted to the network
- Whether the network is congested
- Whether a speed-up or cancellation option is available in BE Custody Web
- Whether any internal approval or quorum workflow is still pending
Do not create repeated transactions without review.
Can I speed up or cancel the pending transaction?
Depending on the network, transaction status, and BE Custody configuration, it may be possible to speed up or cancel a pending Ethereum transaction in BE Custody Web.
Only use supported BE Custody workflows. Do not attempt to resolve nonce issues using unapproved external tools or processes.
Before approving a speed-up or cancellation request, approvers should review the transaction details and confirm that the action is expected and authorised.
What should I avoid?
Do not:
- Create duplicate transactions without review
- Approve a replacement or cancellation transaction you do not understand
- Assume the pending transaction has failed
- Attempt to bypass BE Custody workflows
- Use external tools to alter transaction state
- Share private keys, seed phrases, API keys, secrets, PINs, passwords, or access tokens
What if the transaction is urgent?
If the transaction is urgent, follow your organisation’s internal escalation process.
Check whether the relevant transaction can be resolved through the supported BE Custody workflow. If further support is needed, contact Bitpanda Enterprise Custody Support through the approved support channel.
What information should I include in a support request?
If support is required, include:
- Your organisation name
- Your name and work email address
- The relevant wallet or sub-wallet
- The asset and network
- The pending transaction hash, if available
- The transaction status shown in BE Custody
- The approximate date and time the transaction was created
- Any related transaction that appears blocked
- The exact error message shown
- Any steps already taken
Do not include passwords, PINs, private keys, seed phrases, API keys, API secrets, access tokens, device passcodes, or other sensitive authentication information in a support request.