Cancel Transfer
Cancels an EVM transfer by creating a replacement transaction with the same nonce. The new transaction sends 0 value to the same address, effectively nullifying the original transfer.
This endpoint works for:
- EVM-compatible networks (Ethereum, Polygon, BSC, etc.)
- Transfers that are in ‘Broadcasted’ status (pending inclusion in a block)
- Transfers that are in ‘Failed’ status, but failed off-chain (before being broadcasted to the network)
The cancellation works by:
- Extracting the nonce from the original transfer’s signed data
- Creating a new transaction to the same wallet address with 0 amount
- Using the same nonce to either:
- Replace the original transaction in the mempool (if it was broadcasted)
- Consume the nonce that was reserved but not used (if the transfer failed off-chain)
Note: For transfers that were broadcasted on-chain, success is not guaranteed as it depends on network conditions and whether the original transaction has already been mined.
Authentication
✅ Organization User (CustomerEmployee)✅ Delegated User (
EndUser)✅ Service Account
Required Permissions
Wallets:Transactions:Create: Always required.Wallets:Transfers:Read: Always required.Authorizations
Bearer Token: Used to authenticate API requests. More details how to generate the token: Authentication flows
User Action Signature: Used to sign the change-inducing API requests. More details how to generate the token: User Action Signing flows
Path Parameters
Wallet id.
1 - 64Transfer id.
1 - 64Response
Success
Transaction id.
1 - 64^tx-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"tx-583hu-sp2p7-slvb9nqpa3hd8bus"
Wallet id.
1 - 64^wa-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"wa-5pfuu-9euek-h0odgb6snva8ph3k"
Network the address is watched on.
Algorand, AlgorandTestnet, Aptos, AptosTestnet, ArbitrumOne, ArbitrumSepolia, ArcTestnet, AvalancheC, AvalancheCFuji, BabylonGenesis, BabylonTestnet5, Base, BaseSepolia, Berachain, BerachainBepolia, Bitcoin, BitcoinSignet, BitcoinTestnet4, BitcoinCash, Bob, BobSepolia, Bsc, BscTestnet, Canton, CantonTestnet, Cardano, CardanoPreprod, Concordium, ConcordiumTestnet, Celo, CeloAlfajores, Codex, CodexSepolia, CosmosHub4, CosmosIcsTestnet, Dogecoin, DogecoinTestnet, Ethereum, EthereumClassic, EthereumClassicMordor, EthereumSepolia, EthereumHoodi, FlareC, FlareCCoston2, FlowEvm, FlowEvmTestnet, Hedera, HederaTestnet, Ink, InkSepolia, InternetComputer, Ion, IonTestnet, Iota, IotaTestnet, Kusama, KusamaAssetHub, Litecoin, LitecoinTestnet, Movement, MovementTestnet, Near, NearTestnet, Optimism, OptimismSepolia, Origyn, Plasma, PlasmaTestnet, Plume, PlumeSepolia, Paseo, PaseoAssetHub, Polkadot, PolkadotAssetHub, Polygon, PolygonAmoy, Polymesh, PolymeshTestnet, Race, RaceSepolia, Rayls, RaylsTestnet, Robinhood, RobinhoodSepolia, SeiAtlantic2, SeiPacific1, Solana, SolanaDevnet, Sonic, SonicTestnet, Starknet, StarknetSepolia, Stellar, StellarTestnet, Sui, SuiTestnet, Tezos, TezosGhostnet, TezosShadownet, Tempo, TempoModerato, Tsc, TscTestnet1, Ton, TonTestnet, Tron, TronNile, Westend, WestendAssetHub, Xdc, XdcApothem, XLayer, XLayerSepolia, XrpLedger, XrpLedgerTestnet The user who initiated the request.
Signs an unsigned transaction and broadcasts it to chain. For EVM transactions, you may use JSON objects:
For Starknet transactions, you may use invocation request objects (https://github.com/starkware-libs/starknet-specs/blob/v0.8.1/api/starknet_api_openrpc.json#L2621):
For Concordium transactions, you may use JSON objects (from https://github.com/Concordium/concordium-node-sdk-js/blob/sdk/12.0.0-alpha.3/packages/sdk/src/transactions/Transaction.ts#L102)
- Transaction
- PSBT
- SignDocDirect
- EVM Sponsored transaction
- Function Call
- Canton Transfer Preapproval
- <Deprecated> EVM Transaction
- <Deprecated> EVM EIP-1559
- Create Solana Nonce Accounts
- AcceptInboundAsset
- Solana CCTP Burn
- Offer Settlement
- Account Activation
- Transaction Cancellation
- Transaction Speed Up
Pending, Executing, Broadcasted, Confirmed, Failed, Rejected 1 - 64^ap-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"ap-2a9in-tt2a1-983lho480p35ejd0"
The id of the replacement transaction (cancel or speed-up) issued for this transaction.
Structured representation of the data used to construct the signature (e.g. nonce, gas parameters). Shape is blockchain specific.