> ## Documentation Index > Fetch the complete documentation index at: https://docs.etherfuse.com/llms.txt > Use this file to discover all available pages before exploring further. # Transaction Fees > What each trade costs: same-currency fees, FX fees by market, and partner fees. Every trade buys or sells an Etherfuse asset. A trade inside one currency pays that market's flat fee, such as the stablebond fee for leaving a stablebond, and a trade that crosses currencies pays that market's FX fee. When a trade crosses two markets, the higher of the two FX fees applies. Every quote shows its fees before you create an order. 1 bps (basis point) = 0.01%. > [!NOTE] > > This page summarizes the schedule for API integrations. The full schedule, with a table for every market, is in the support center: [Transaction fees](https://support.etherfuse.com/articles/3367253525-transaction-fees). ## Within one currency Trades that stay in one currency have flat fees. Each market has its fiat, its stablebond and its principal token. A market's stablecoins count as its fiat: | Market | Fiat | Stablebond | Principal token | | - | - | - | - | | Mexico | MXN | CETES | MEXe | | Brazil | BRL | TESOURO | BRAe | | US dollar | USDC, USDT | USTRY | USAe | | Eurozone | EURC | EUROB | None | | UK | None | GILTS | None | US dollar assets are all in US dollars, so no FX fee applies between them. USDC and USDT count as the US dollar market's fiat, so buying USTRY with them is free and selling USTRY back to them pays the stablebond fee. ## Across currencies A trade between currencies, such as MXN to USDC, pays the FX fee of the market it trades in. Your tier comes from your combined 30-day volume across all markets, in USD, and the fee gets lower as you scale: For example, converting 1,000,000 MXN to USDC with under \$5M of 30-day volume uses Mexico FX at 20 bps, so the fee is 2,000 MXN. Both tables come from [`GET /lookup/fees`](https://docs.etherfuse.com/v2/api-reference/lookup/get-fee-schedule), so your code can read the same rates. We apply your current tier automatically. The FX fee also covers price movement during the conversion, so we do not add a separate slippage charge. A cross-currency trade pays only the FX fee, not the stablebond fee as well. ### Between markets When a trade moves between two markets, the higher of the two markets' FX fees applies. CETES to GILTS uses Mexico FX, and CETES to TESOURO uses Brazil FX. ### Eurozone and UK EUROB (Eurozone) and GILTS (UK) are bought and sold against USDC, USDT or another market's assets. There are no euro or sterling bank transfers. ## Fees on a quote Quotes list the fee from the schedule above as `transactionFee`. A quote can also carry a partner fee, a wallet setup fee and a bridge fee. [`POST /organization/{organizationId}/quote`](https://docs.etherfuse.com/v2/api-reference/quotes/create-quote) returns these fee fields: | Field | Meaning | | - | - | | `feeBps` | The total fee in basis points, partner fee included. | | `feeAmount` | The total fee as a decimal string, in the **source asset**: fiat for an onramp, the source token for an offramp or swap. | | `fees` | An itemized list of applicable fees. | `destinationAmount` is already net of every fee. `rateAfterFees` is `destinationAmount / sourceAmount`, and `rateBeforeFees` is the rate before our fee. On an onramp into a stablebond, we price the bond at the end of the order's funding window, not at the time of the quote. A stablebond gains value every day, so the customer receives slightly fewer bond tokens than today's price would give. In exchange, the amount stays the same however late in the window the customer pays. `feeAmount` is rounded down to the source asset's decimals, for example two decimals for MXN. Each line in `fees` has a `type`, an `amount` (decimal string), the `asset` it is charged in, and `bps` (always `null` on a quote): | `type` | What it is | | - | - | | `transactionFee` | The Etherfuse fee from the schedule above: the same-currency fee or the FX fee. | | `partnerFee` | Your partner fee. See [Partner fees](#partner-fees). | | `walletSponsor` | A fixed fee for setting up the destination wallet when it can't receive the asset yet: a Solana wallet with no SOL or no token account, or a Stellar wallet with no account or no trustline. We charge it in the delivered token and take it out of the payout, so `destinationAmount` already accounts for it. It is part of `feeBps` and `feeAmount`. | | `bridge` | A fixed fee for moving a token from a wallet on one chain to a wallet on another. We charge it only on that kind of order. When an onramp, offramp or swap bridges to reach the wallet's chain, we pay the bridge and the quote has no `bridge` line. | | `networkFee` | Order only, for an [embedded wallet](https://docs.etherfuse.com/v2/guides/embedded-wallets.md#fees-and-billing). The network fee we paid for a transaction we sent for the wallet, in the chain's native asset (`native`). We invoice it at cost. | | `walletSigning` | Order only, for an [embedded wallet](https://docs.etherfuse.com/v2/guides/embedded-wallets.md#fees-and-billing). The key holder's approval: \$0.10 per signature, in USD. We invoice it. | We include a line only when its amount is greater than zero. A line's `asset` can differ from the quote's source and destination assets. On an MXN to USDC onramp, for example, we convert through an intermediate token, and the `transactionFee` and `partnerFee` lines are charged in that token. Compare lines with each other only when they share an `asset`, and use `feeAmount` for the total in the source asset. The order you create from the quote returns the same `fees` lines. See [Get order](https://docs.etherfuse.com/v2/api-reference/orders/get-order.md). An order from an embedded wallet can also gain `networkFee` and `walletSigning` lines once a transaction we sent for the wallet is final. We invoice those separately, so they are not part of `feeBps`, `feeAmount` or `destinationAmount`. ## Partner fees You can add a **partner fee** of up to 500 bps (5.00%) on top of the platform fee. * Set your default with [`PATCH /me`](https://docs.etherfuse.com/v2/api-reference/organizations/update-me). * Override it on one quote with `partnerFeeBpsOverride` in the [quote request](https://docs.etherfuse.com/v2/api-reference/quotes/create-quote.md). We cap values above 500 at 500. * We use the per-quote override first, then your organization's default (`partnerFeeDefaultBps`), then 0. * Read your current default with [`GET /me`](https://docs.etherfuse.com/v2/api-reference/organizations/get-me) (`partnerFeeDefaultBps`). The partner fee is part of `feeBps` and `feeAmount`, and it has its own `partnerFee` line in `fees`. Read your amount from that line. Do not add your partner fee on top of `feeBps`, and do not deduct it again from `destinationAmount`: both already include it. ## Payouts We record the partner fee on each order and pay the accumulated fees monthly. * **Schedule**: paid about **2 weeks after the end of each calendar month**. * **Currency**: paid out in the underlying currency currently in use (subject to change). * **Reporting**: the running total and a per-fee breakdown are in your dashboard under [Reports](https://app.etherfuse.com/account/reports), and in your [partner statements](https://docs.etherfuse.com/v2/api-reference/statements/list-partner-statements.md). > [!NOTE] > > Want market-specific pricing? [Book a call with our team](https://cal.com/team/etherfuse/etherfuse-demo). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.