Collect Fees
Integrators can pass in a collectFees object to the SDK or API to collect a fee on each transaction.
Note: Squid takes a 50% fee on any fees collected by an integratorAddress.
Example route request with `collectFees`
New objects in route response
Fee collection token Fees are collected in the bridge token, most of the time this will be axlUSDC as this is the primary bridging token, if the source or destination token is an Axelar wrapped token the fee could be taken in that token, to unwrap Axelar token see here
The API route response will tell whether it is the source or destination chain that has the fee taken
You can see the "collectFees" object returned by the api in the "params" section of the response. This specific route will take fees on destination.
Fee logic
Fees are are currently only supported on EVM chains, although fees will eventually be supported on Cosmos chains. The fee is generally taken on the chain where swaps happen. The following table outlines where the fee is taken based on the route.
swaps = some swap to or from a token to the bridge token (eg axlUSDC)
send only = no swaps
Cosmos = not supported
How to check fee balances
You can check the Squid fee collector smart contracts for the balance of each token for the integrator address. The feeCollector contract addresses are documented in the next section. You can read balances by putting in the "token address" and "integratorAddress" into the getBalance function https://testnet.snowtrace.io/address/0xf80De6D6CF6846Ae7c3243F4b6486EF662C59d29#readProxyContract
Fee Collector contract address
Last updated