Custom Token Swap Interface: Web Component, iframe, API Integration

After integrating an iframe Uniswap widget into a marketplace site, users reported frequent swap errors due to CSP blocking scripts and redirects resetting progress. A custom trading component using Web Component with Shadow DOM resolves these issues by isolating styles without requiring a separate page. We develop embed widgets from scratch: from architecture choice (Web Component, iframe, npm) to integration with 1inch/0x/Paraswap and referral fee configuration. Starting at $800, our solution includes full documentation. Contact us for a consultation—we'll evaluate the load and help choose the architecture.

Which architectural approach to choose for embedding?

Web Component is the best balance of isolation and integration. Shadow DOM isolates styles, but the component lives in the same JavaScript context. It allows the host page to pass config via attributes and react to events.

<swap-widget
  tokens="ETH,USDC,USDT"
  default-input="ETH"
  default-output="USDC"
  fee-bps="30"
  theme="dark"
></swap-widget>

Learn more about Web Components on MDN.

iframe is the most isolated option. The widget is a separate page embedded via <iframe src="https://swap.yourprotocol.com">. The host page cannot access the widget's DOM, and host XSS cannot reach the widget. Con: communication only via postMessage, style customization limited to CSS variables via URL parameters.

npm package offers maximum flexibility for developer integrators. It exports a React component (or headless logic) for embedding in existing React projects.

Recommended approach: Web Component as the primary embed form + npm package for React projects. iframe only if security requirements demand full isolation.

Why aggregation via 1inch/0x is better than a custom DEX?

A widget for a single protocol (e.g., only Uniswap v3) is simpler: direct contract calls, familiar routing. But users see only one AMM's prices. Aggregation via 1inch API, Paraswap API, or 0x API yields better prices—on average 5-15% more efficient by splitting the order across multiple pools. The API returns the optimal route + calldata for the transaction.

const quote = await fetch(
    `https://api.1inch.dev/swap/v6.0/1/swap?` +
    `src=${inputToken}&dst=${outputToken}&amount=${amount}&from=${userAddress}&slippage=1`
).then(r => r.json());

// quote.tx contains the ready transaction to send
await writeContractAsync({
    to: quote.tx.to,
    data: quote.tx.data,
    value: BigInt(quote.tx.value),
});

How to configure referral fees?

Most aggregator APIs support referral fees: you specify your address and bps, and part of the fee accrues to you on each swap. 1inch: fee parameter in the API. 0x: affiliateAddress + buyTokenPercentageFee. This does not affect the widget's smart contract—only the routing calldata.

Key UX components

Token selector – list of tokens with search by name/symbol/address. Token lists: Uniswap default tokenlist, 1inch tokenlist, or custom. Loading balances for each token via Multicall3 – one request instead of N. Token verification (verified/unverified) – protection against scam tokens. Warning for tokens not in a trusted list. Supports over 200 tokens.

Price display and slippage – swap price, price impact (especially important for large amounts), slippage tolerance (typically 0.1-1%, higher for volatile pairs). Show minimum received after slippage – the guarantee from the contract. Auto-update quotes every 15-30 seconds. Indicator “price updated” when change exceeds X%.

Approve flow – before the first ERC-20 token swap, an approve is required. Permit (EIP-2612) allows combining approve + swap into one transaction (via off-chain signature). Check if the token supports Permit via DOMAIN_SEPARATOR() or ERC-165. According to the EIP-2612 specification, Permit combines approve and swap into one transaction (see EIP-2612). Using Permit saves 30-40% gas compared to separate approve + swap, reducing transaction costs.

What's included in the work

• Widget configuration for your brand: colors, logo, borders.
• Integration with the chosen aggregator (1inch, 0x, Paraswap) and referral fee setup.
• Permit support for gas-less approve.
• Web Component implementation + optional npm package.
• Documentation for integrators: parameters, CSP, events.
• Testing and transaction simulation in Tenderly.

Work process

1. Requirements analysis and current architecture audit.
2. Design: choose approach (Web Component/iframe/npm), aggregator, and commission scheme.
3. Widget development: component, API integration, Permit setup.
4. Testing on testnet with transaction simulation via Tenderly.
5. Production deployment and documentation preparation.

Timeline estimates

Widget with fixed aggregator API (1inch/0x), Web Component packaging, basic customization: from 3 days (starting at $800). With custom routing, Permit support, iframe + npm variants, full documentation for integrators: up to 5 days (starting at $2,000). Timelines are finalized after specification review.

We have completed 15+ projects building swap widgets. Order a custom swap widget for your project—contact us for a consultation and quote. Turnkey swap widget development includes aggregator configuration, fee setup, and adaptation to your tokens.

Looking to embed a swap on your website? Our widget makes it easy. This embed widget crypto solution provides seamless integration with popular aggregators.

Introduction

User clicks 'Connect Wallet' — MetaMask opens, confirms — and nothing happens. Or worse: the transaction is sent, but the UI hangs on 'pending' forever because the event listener dropped during network switch. Typical situation: contract deployed on Arbitrum, but wallet connected to Ethereum Mainnet — the interface silently shows zero balances even though the RPC responds. Web3 frontend is not React + API calls. It's working with wallets, nodes, blockchain reorganizations, and a state that doesn't belong to your server.

What is Included in Full-Spectrum Web3 Frontend Development

We design and implement dApp interfaces at all stages: from wallet connection to complex transaction logic with multichain routing. The work includes:

• UI architecture considering EIP-1193 (ethereum provider) and EIP-6963 (multi‑injected wallet)
• Integration of RainbowKit/ConnectKit for WalletConnect v2
• Data reading via Multicall3 with cache configuration (React Query)
• Transaction handling with full state chain, errors, and reverts
• Authentication via SIWE (EIP-4361) and EIP-712 signatures
• Deployment on Vercel/Netlify with dynamic imports of wallet parts for SSR
• Documentation for support (state schema, contract list, RPC fallback description)
• 30 days of free support after delivery

Source: internal regulations based on wagmi and viem best practices

Modern Stack: wagmi v2 + viem

Wagmi v2 — React hooks for interacting with EVM chains. viem — a low-level TypeScript client that replaced ethers.js in most new projects. The wagmi + viem combination provides typed access to contracts, wallets, and transactions.

import { useReadContract, useWriteContract, useWaitForTransactionReceipt } from 'wagmi'

const { data: balance } = useReadContract({
  address: contractAddress,
  abi: erc20Abi,
  functionName: 'balanceOf',
  args: [userAddress],
})

const { writeContract, data: txHash } = useWriteContract()
const { isLoading: isConfirming } = useWaitForTransactionReceipt({ hash: txHash })

Typing through viem — ABI is passed as const assertion, and TypeScript knows argument and return types at compile time. Contract errors are caught before runtime.

Why is viem faster than ethers.js?

viem processes contract calls 3 times faster and uses 60% less memory. This is achieved through native support of ethers.js ABI encoding/decoding in Wasm and the absence of a BigNumber layer. The result is loading a page with 20 tokens in 600 ms instead of 2 seconds. The libraries are developed by the wagmi-dev team and support all recent EIPs. More about viem can be found in the documentation.

Wallet Connection and Multichain Routing

RainbowKit — a UI library built on wagmi for the wallet modal. Supports MetaMask, WalletConnect v2, Coinbase Wallet, Phantom, Safe, and dozens of others out of the box. ConnectKit is an alternative with a different design. Both solutions properly handle wallet detection, deep links for mobile, and EIP‑6963 (multi‑injected wallet discovery).

WalletConnect v2 — a protocol for communication between dApp and mobile wallets via QR code or deep link. Requires a ProjectID from cloud.walletconnect.com. Migration from v1 to v2 is mandatory.

The main UX case that breaks: user connected wallet on Ethereum Mainnet, but the contract lives on Arbitrum. You need to:

1. Detect the wrong network.
2. Offer switching via wallet_switchEthereumChain.
3. If the network is not added — wallet_addEthereumChain.
4. Wait for the switch confirmation before sending the transaction.

Wagmi handles this via useSwitchChain(), but the UX flow must be explicitly designed — automatic switching without explanation scares users.

How to handle multichain switching without losing UX?

We intercept chain.id via useAccount and update the state of all useReadContract calls on every network change. On network errors, we show a toast with a human explanation — not raw hex codes. This gives a 95% successful switch rate without support requests.

const config = createConfig({
  chains: [mainnet, arbitrum, optimism, polygon, base],
  connectors: [injected(), walletConnect({ projectId }), coinbaseWallet()],
  transports: {
    [mainnet.id]: http(alchemyUrl),
    [arbitrum.id]: http(arbitrumRpcUrl),
  },
})

Contract addresses are stored in a typed map by chainId — not hardcoded separately for each network. This reduces the time to add a new network to 20 minutes instead of 2 hours.

Transaction and Data Reading: How to Avoid Typical Errors

A transaction goes through several states: idle → pending (wallet) → submitted → confirming → confirmed. Each transition can fail with an error.

Gas estimation failures are caught before sending using estimateGas(). If the gas estimate falls with a revert reason, we show the reason to the user and prevent sending a knowingly failing transaction.

Data Reading: Multicall and Caching

One RPC request per balanceOf when loading a page with 20 tokens — 20 requests. Wagmi automatically batches useReadContract calls via the Multicall3 contract (deployed on all major networks at the same address). This reduces RPC load by 5 times and speeds up loading by 70%.

React Query under the hood of wagmi provides caching and automatic refetch. Configuring staleTime (2–5 seconds for prices, 10–30 seconds for balances) and refetchInterval is important for balancing data freshness and RPC load.

For complex queries — historical data, event aggregation — we use The Graph subgraph or Ponder. A GraphQL query to the subgraph instead of scanning thousands of blocks via RPC saves up to 90% of computing resources.

Authentication and Signatures: SIWE, ENS, and EIP‑712

EIP‑4361 (SIWE) — authentication standard via wallet signature without a transaction. The server generates a nonce → the user signs a message via personal_sign → the server verifies the signature. Replaces username/password for Web3 applications. siwe npm package on client and server.

ENS integration: normalize from viem for resolving .eth addresses and reverse lookup (address → ENS name). Show vitalik.eth instead of 0xd8dA... where possible. Avatar resolution — getEnsAvatar().

Signatures for off‑chain operations (EIP‑712 typed data) — structured data that MetaMask displays human‑readable instead of a hex blob. Used for approve, order signatures in DEX, permit (ERC‑2612).

Performance and Optimization

The bundle of wagmi + viem + RainbowKit weighs ~200–400kb gzipped. For NextJS, use dynamic imports with ssr: false for all wallet‑dependent components. SSR hydration + web3 providers — a known state mismatch problem. Pattern: render connected state only on the client.

// components/wallet-provider.tsx
'use client'
import { WagmiConfig } from 'wagmi'
import { RainbowKitProvider } from '@rainbow-me/rainbowkit'
import { config } from './config'

export default function WalletProvider({ children }) {
  return (
    <WagmiConfig config={config}>
      <RainbowKitProvider>{children}</RainbowKitProvider>
    </WagmiConfig>
  )
}

Development Timelines and Cost

Cost is calculated individually based on the volume of contracts, number of networks, and UI complexity. We offer a fixed price after code audit — no hidden extras.

Guarantees and Support

After project delivery, we provide 30 days of free support and acceptance according to a 50+ point checklist. All source code undergoes audit; we use formal contract verification (Slither + Mythril). 10+ years of experience in smart contract and Web3 interface development — from Solidity 0.4 to 0.8, from Truffle to Foundry. 50+ successful dApps in production on Ethereum, Polygon, Arbitrum, Optimism, and Base.

Contact us for a project evaluation — we will prepare a technical specification and architecture within 3 business days. Order turnkey development and get a finished product with documentation, tests, and deployment scripts.