Skip to main content
Typically submitting transactions to a blockchain requires the sender to pay a small amount of fees called gas fees. These fees compensate network participants, such as miners or validators, for the computational resources needed to execute transactions, smart contracts, and other operations. What it means in practice is that for users to transfer some stable coins such as USDC, they must also hold a small amount of the native tokens of the blockchains used to pay the gas fees. This creates friction because you must constantly top up all your wallets in order for them to stay functional. The Fee Sponsor enables you to sponsor gasless transactions for your wallets via the Transfer API. This allows you to manage a small set of fee sponsor wallets with native tokens and use them to pay gas fees for other wallets. To sponsor a transfer,
  • Designate a DFNS wallet as the fee sponsor. See below for supported networks.
  • Fund the fee sponsor wallet with some native tokens.
  • Specify the feeSponsorId when creating a transfer request. Note that the sponsor and sponsoree wallets must be for the same network.
Finding your fee sponsor ID: feeSponsorId is the ID of the fee sponsor entity (format fs-...), not the sponsor wallet’s ID or address. It is returned when you create a fee sponsor, and you can look it up later via List Fee Sponsors / Get Fee Sponsor, or in the dashboard under Settings → Fee Sponsorship (each sponsor shows a Sponsor ID you can copy). Passing a wallet address or wallet ID is rejected.
High-volume tip: If you’re processing a high volume of transactions for a given wallet, use a single fee sponsor for that wallet. This allows DFNS to better optimize transaction scheduling and improve throughput.

​
End user access

By default, only service accounts and organization users (CustomerEmployee) can use a fee sponsor when creating transfers. If you want your end users (EndUser) to use a fee sponsor when making transfers from their delegated wallets, set allowEndUser: true when creating the fee sponsor. 
const feeSponsor = await dfns.feeSponsors.createFeeSponsor({
  body: {
    walletId: 'wa-...',
    allowEndUser: true, // Allow EndUsers to use this fee sponsor
  },
})
If you don’t set allowEndUser: true and an EndUser tries to use the fee sponsor, they will receive a 401 Unauthorized error.
The sponsoree wallet (the wallet being sponsored) must be an org-managed or delegated wallet in DFNS. External wallets cannot be sponsored.
A wallet that is registered as a fee sponsor cannot itself be sponsored. To move funds out of a fee sponsor wallet, send the transfer without a feeSponsorId so the wallet pays its own gas from its native balance.
Policy consideration: When using fee sponsorship, the fee sponsor wallet must sign a transaction to pay the gas fees. If the fee sponsor wallet has a policy that blocks or requires approval for signing (e.g., a Block action on Wallets:Sign), the sponsored transfer will fail. Ensure your fee sponsor wallet is not subject to any blocking policies.

​
Supported networks

Not all networks support this feature. You can create fee sponsors for the following supported networks.
MainnetsTestnets
ArbitrumOne 1ArbitrumSepolia
Base 1BaseSepolia
Berachain 1BerachainBepolia
Bsc 1BscTestnet
Ethereum 1EthereumHolesky, EthereumHoodi, EthereumSepolia
FlowEvm 1FlowEvmTestnet
Optimism 1OptimismSepolia
Plasma 1PlasmaTestnet
Polygon 1PolygonAmoy
SolanaSolanaDevnet
StellarStellarTestnet
Not all networks support fee sponsorship. For TRON, you can achieve a similar result using native resource delegation.

​
Getting Started

Footnotes

  1. The implementation leverages EIP-7702 that turns your EOA into a smart contract account. When you use this feature, the on chain account of the sponsoree wallet will become a smart contract. You can view the source code of the smart contract we use here. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9
Last modified on June 8, 2026