When you integrate DZap into a wallet, dashboard, or dApp, you can charge your own fee on top of DZap’s protocol fee. The amount accrues to an address you control — automatically, with no separate transaction.Documentation Index
Fetch the complete documentation index at: https://docs.dzap.io/llms.txt
Use this file to discover all available pages before exploring further.
Partner Fees are a pattern, not a separate product. The hooks are part of the standard SDK — you add fee fields, DZap respects them, and the fee accrues to the address you specify.
How it works
DZap returns net + gross
Quote response includes both the user-facing output (net of all fees) and the breakdown (DZap protocol fee, your partner fee, gas).
Execute as normal
Build + send via
trade() or zap(). Your fee accrues automatically — no separate transaction.Fee fields
| Field | Type | Notes |
|---|---|---|
partnerFee.recipient | string | Your address that receives the fee |
partnerFee.bps | number | Basis points (1 bps = 0.01%) |
partnerFee.flat | string | Optional flat amount in source token wei |
bps or flat; not both.
Combining with gasless
Partner Fees + gasless: your fee is committed in the EIP-712 intent (inexecutorFeesHash). Solvers can’t strip it after signing.
When to ask for a partnership
If you’re routing meaningful volume (~$1M+/month) and want a custom fee tier, joint announcements, or a dedicated support channel — see Partnership Requests.See also
- Fees — DZap’s own fee schedule.
- Partnerships — request a custom tier.
- SDK Trade — the underlying trade methods.