A white-label swap exchange lets you offer token swaps under your own brand without designing an exchange from scratch. The real choice is between routing through existing liquidity (aggregator APIs and widgets) and deploying your own pools (a forked AMM), and for most teams routing is the better start.
This is a buyer's comparison. If you want to understand how to build an exchange from first principles, read the decentralized exchange development guide; if you are evaluating packaged exchange software more broadly, see decentralized exchange software.
The four options
| Option | Liquidity source | Your contracts | Revenue model | Time to launch |
|---|---|---|---|---|
| Swap widget | Provider's aggregator | None | Integrator fee on each swap | Days |
| Aggregator API + custom UI | Provider's aggregator | None or a thin fee wrapper | Integrator fee | Weeks |
| Forked AMM | Your own pools | Factory, pools, router | Swap fees, token | Weeks to months |
| Vendor "exchange script" | Varies | Vendor's code | Varies | Weeks |
Swap widgets
Several aggregators publish embeddable widgets: a ready-made swap box that queries their routing engine and hands the user a transaction to sign. You configure tokens, chains, theme and a fee recipient. Nothing touches your servers and you deploy no contracts. The trade-offs are limited design control and dependence on the provider's uptime, routing quality and policies.
Aggregator APIs
Aggregator APIs (from providers such as 0x, 1inch, LI.FI and others) return a quote and executable calldata for a swap routed across many DEXs and sometimes bridges. You build your own interface, choose which chains to show and attach an integrator fee, usually in basis points of the trade. This is how most wallets add swaps. You get competitive prices on day one because you are borrowing the whole market's liquidity. Read the guide to 1inch-style aggregators for how routing and split orders work.
Forked AMM
Deploying your own Uniswap- or PancakeSwap-style pools gives you swap-fee revenue and control, but your pools start empty. Without liquidity your prices are poor and aggregators will not route to you. This route makes sense when you are the main venue for a token ecosystem or a new chain. The PancakeSwap-like DEX guide covers what forking involves.
The three designs most white-label AMM offerings are based on:
- Uniswap (v2 constant product, v3 concentrated liquidity, v4 singleton pools with hooks). The reference implementation; later versions carry business source licenses for a period after release.
- SushiSwap, originally a Uniswap v2 fork that added the MasterChef farm and a fee share for token stakers.
- PancakeSwap, a v2 and later v3 derivative on BNB Smart Chain with farms, a native token and many add-on products.
Underneath the branding, a "Sushi clone" and a "Pancake clone" are mostly the same Uniswap v2 math with different farm contracts and front ends.
Vendor exchange scripts
Many sellers offer "clone scripts". Some are competent repackagings of open-source code; some contain owner backdoors, unaudited modifications or license violations. Treat any vendor code as untrusted until reviewed.
Things the marketing pages leave out
- Approvals. A swap UI asks users to approve a spender contract. If that contract is malicious or compromised, approvals become a drain. Prefer well-known router contracts, exact-amount approvals or Permit2-style signatures with expiry, and show users exactly what they are approving.
- MEV and slippage. Default slippage that is too loose invites sandwich attacks. Offer MEV-protected submission where the chain supports it and sensible slippage defaults per pair type.
- Token lists. Letting users swap any token by address exposes them to scam tokens that impersonate real ones. Curate a default list, warn on unverified tokens and detect fee-on-transfer tokens before quoting.
- Front-end integrity. Your domain and hosting are attack surface. A hijacked front end can swap in a malicious spender. Lock your DNS registrar, use subresource integrity where possible and monitor deployed bundles.
- Compliance. Charging a fee on swaps you route may bring obligations in some jurisdictions, and many providers screen addresses against sanctions lists. Understand what your provider screens and what you are responsible for.
How to evaluate a provider or vendor
- Ask for audits of every contract users will approve, with dates and the commit hashes audited.
- Confirm custody. User funds should never pass through an address controlled by the vendor or by you.
- Check admin powers. Who can upgrade the router or change fee recipients, and is there a timelock?
- Test routing quality by comparing quotes against other aggregators across trade sizes and chains.
- Read the terms: rate limits, fee splits, what happens if they deprecate an API version, and whether they can block your users.
- Verify licensing of any forked code you are handed.
Recommendation
If you are a wallet, app or community that wants swaps as a feature, use an aggregator API with your own UI and a modest integrator fee. If you are launching a token ecosystem or a chain and need to be the primary venue, fork a proven AMM, keep changes minimal and fund an audit. Avoid buying closed-source scripts you cannot review.
Frequently asked questions
What is a white-label swap exchange?
A branded token swap interface built on existing technology, either a provider's aggregation API or widget, or a licensed copy of an AMM. The user experience is yours; the routing or pool logic comes from someone else.
How do white-label swaps make money?
Usually through an integrator fee added to each swap, expressed in basis points. Forked AMMs earn a share of swap fees from their own pools instead.
Do I hold user funds?
You should not. In a properly built non-custodial swap, users sign transactions from their own wallets and tokens move directly through audited contracts. If a vendor's design requires deposits to an address you control, it is a custodial exchange with very different obligations.
Can I support several chains?
Yes. Most aggregator APIs cover many EVM chains and some include Solana and cross-chain routes via bridges. Cross-chain swaps add bridge risk, so show users which bridge is used.