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
✅ Tenant User (TenantUser)✅ Organization User (
CustomerEmployee)✅ End 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
Response
Success
Algorand, AlgorandTestnet, Aptos, AptosTestnet, ArbitrumOne, ArbitrumSepolia, Arc, ArcTestnet, Areum, AvalancheC, AvalancheCFuji, Base, BaseSepolia, Berachain, BerachainBepolia, Bitcoin, BitcoinSignet, BitcoinTestnet4, BitcoinCash, Bob, BobSepolia, Bsc, BscTestnet, Canton, CantonTestnet, Cardano, CardanoPreprod, Concordium, ConcordiumTestnet, Celo, CeloSepolia, Codex, CodexSepolia, CosmosHub4, CosmosIcsTestnet, Dogecoin, DogecoinTestnet, Ethereum, EthereumClassic, EthereumClassicMordor, EthereumSepolia, EthereumHoodi, FlareC, FlareCCoston2, FlowEvm, FlowEvmTestnet, Hedera, HederaTestnet, HyperEvm, HyperEvmTestnet, Ink, InkSepolia, InternetComputer, Ion, IonTestnet, Iota, IotaTestnet, Kusama, KusamaAssetHub, Litecoin, LitecoinTestnet, Monad, MonadTestnet, Movement, MovementTestnet, Near, NearTestnet, Optimism, OptimismSepolia, Origyn, Plasma, PlasmaTestnet, Plume, PlumeSepolia, Paseo, PaseoAssetHub, Polkadot, PolkadotAssetHub, Polygon, PolygonAmoy, Polymesh, PolymeshTestnet, Rayls, RaylsTestnet, Robinhood, RobinhoodSepolia, SeiAtlantic2, SeiPacific1, Solana, SolanaDevnet, Sonic, SonicTestnet, Starknet, StarknetSepolia, Stellar, StellarTestnet, Sui, SuiTestnet, Tezos, TezosShadownet, Tempo, TempoModerato, Tsc, TscTestnet1, Ton, TonTestnet, Tron, TronNile, Westend, WestendAssetHub, Xdc, XdcApothem, XLayer, XLayerSepolia, XrpLedger, XrpLedgerTestnet Signs an unsigned transaction and broadcasts it to chain. This is the recommended transaction kind for EVM networks — use it instead of the deprecated Evm and Eip1559 kinds. It accepts a JSON transaction object (type 0 legacy, 2 EIP-1559, or 4 EIP-7702) as well as a hex-encoded raw transaction.
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
- <Deprecated> Canton Transfer Preapproval
- <Deprecated> EVM Transaction
- <Deprecated> EVM EIP-1559
- Create Solana Nonce Accounts
- AcceptInboundAsset
- Solana CCTP Burn
- Stellar CCTP Approve
- Stellar CCTP Burn
- Stellar CCTP Claim
- Offer Settlement
- Account Activation
- Transaction Cancellation
- Transaction Speed Up
ISO 8601 date (must be UTC). When the transaction was requested.
"2023-04-14T20:41:28.715Z"
ISO 8601 date (must be UTC). When policy evaluation resolved for this transaction (cleared or blocked).
"2023-04-14T20:41:28.715Z"
ISO 8601 date (must be UTC). When the transaction was broadcasted to the blockchain.
"2023-04-14T20:41:28.715Z"
ISO 8601 date (must be UTC). When the transaction was confirmed on chain.
"2023-04-14T20:41:28.715Z"