Transfer
Reference for the TransferRequest object used by the Dfns transfer endpoint to send native assets, tokens, and NFTs across supported networks.
Speed up and cancel
If a transfer is stuck in the mempool (statusBroadcasted), you can speed it up or cancel it:
- Speed Up Transfer: Rebroadcasts the transfer with higher fees
- Cancel Transfer: Replaces the transfer with a zero-value transaction (EVM only)
- EVM networks: Both speed-up and cancel are available
- Bitcoin: Only speed-up is available (via RBF)
- Transfer: call the Transfer Asset endpoint for native tokens, ERC-20/721, SPL, Cardano assets, etc. It creates a wallet transfer request, requires user action signing, supports fee sponsorship, idempotency via externalId, policy approvals, status tracking, and indexing (txHash, dateConfirmed).
- Broadcast (Sign & Broadcast): use the Broadcast Transaction endpoint when you’ve built a raw/serialized transaction (or need to call arbitrary smart contract functions, mint, deploy contracts). This endpoint signs the transaction with the wallet key and broadcasts it; it also returns request status and txHash. See Broadcast.
- Sign (Generate Signature): use Generate Signature only when you need an off-chain signature (no broadcast). Note this wallet endpoint is deprecated in favor of the Keys API; it does not submit anything to the chain. See Sign.
Transfer request object
Transfer id.
1 - 64^xfr-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"xfr-20g4k-nsdpo-mg6arrifgvid4orn"
The source wallet for this tranfer.
1 - 64^wa-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"wa-5pfuu-9euek-h0odgb6snva8ph3k"
The blockchain network this transfer is on.
Algorand, AlgorandTestnet, Aptos, AptosTestnet, ArbitrumOne, ArbitrumSepolia, ArcTestnet, AvalancheC, AvalancheCFuji, BabylonGenesis, BabylonTestnet5, Base, BaseSepolia, Berachain, BerachainBepolia, Bitcoin, BitcoinSignet, BitcoinTestnet3, BitcoinTestnet4, BitcoinCash, Bob, BobSepolia, Bsc, BscTestnet, Canton, CantonTestnet, Cardano, CardanoPreprod, Concordium, ConcordiumTestnet, Celo, CeloAlfajores, Codex, CodexSepolia, CosmosHub4, CosmosIcsTestnet, Dogecoin, DogecoinTestnet, Ethereum, EthereumClassic, EthereumClassicMordor, EthereumSepolia, EthereumHolesky, EthereumHoodi, FantomOpera, FantomTestnet, FlareC, FlareCCoston2, FlowEvm, FlowEvmTestnet, Hedera, HederaTestnet, Ink, InkSepolia, InternetComputer, Ion, IonTestnet, Iota, IotaTestnet, Kaspa, Kusama, KusamaAssetHub, Litecoin, LitecoinTestnet, Near, NearTestnet, Optimism, OptimismSepolia, Origyn, Plasma, PlasmaTestnet, Plume, PlumeSepolia, Paseo, PaseoAssetHub, Polkadot, PolkadotAssetHub, Polygon, PolygonAmoy, Polymesh, PolymeshTestnet, Race, RaceSepolia, SeiAtlantic2, SeiPacific1, Solana, SolanaDevnet, 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.
Transfer the native token of the network. All networks support the native token type.
- Native Asset
- Aptos Fungible Asset (AIP-21)
- Algorand Standard Asset
- Cardano Asset
- Canton Standard Token (CIP-56)
- CIS-2 Standard
- Concordium Protocol Level Token (CIS-7)
- Sui Coin
- EVM Fungible Token (ERC-20)
- EVM Non Fungible Token (ERC-721)
- EVM Confidential Token (ERC-7984)
- Hedera Non-Fungible Token (HIP-17)
- Hedera Tokens (HTS)
- XRPL IOU Token
- Stellar Classic Assets (SEP-41)
- Starknet SNIP-2 (ERC-20 like)
- Starknet SNIP-3 (ERC-721-like)
- Solana Program Library Token (SPL and SPL 2022)
- TON Jetton (TEP-74)
- TRON Native Fungible Token (TRC-10)
- TRON Smart Contract Fungible Token (TRC-20)
- TRON Non Fungible Token (TRC-721)
- XRPL XLS-33 Token
Additional metadata about the transfered asset.
Transfer status.
| Status | Definition |
|---|---|
Pending | The request is pending approval due to a policy applied to the wallet. |
Executing | The request is approved and is in the process of being executed. note this status is only set for a short time between pending and broadcasted. |
Broadcasted | The transaction has been successfully written to the mempool. |
Confirmed | The transaction has been confirmed on-chain by our indexing pipeline. |
Failed | Indicates either system failure to complete the request or the transaction failed on chain. |
Rejected | The request has been rejected by a policy approval action. |
Pending, Executing, Broadcasted, Confirmed, Failed, Rejected The reason for a failed transfer.
The blockchain transaction hash for this transfer.
The fee paid for this transfer in minimum denomination.
The id of the approval request if this transfer triggered a policy.
1 - 64^ap-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"ap-2a9in-tt2a1-983lho480p35ejd0"
The external id provided at transfer creation time.
The fee sponsor id used to pay for the transfer fees.
1 - 64^fs-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"fs-5vqdl-gliqk-b4rfukqauov1sp7j"
The id of the replacement transaction (cancel or speed-up) issued for this transfer.
Structured representation of the data used to construct the signature (e.g. nonce, gas parameters). Shape is blockchain specific.