Zap Wallet

An actual usable wallet for everyday payments and real users

Zap Wallet

Created At

ETHGlobal Cannes 2026

Winner of

Dynamic

Dynamic - Best use of Dynamic in a mobile experience

ENS

ENS - Most Creative Use of ENS 4th place

Project Description

Zap Wallet isn't just another wallet for your portfolio; it’s the wallet for your pocket. We’ve bridged the gap between DeFi and retail by building the first self-custodial, NFC-enabled mobile wallet designed specifically for real-world commerce.

Current wallets are built for degens; Zap Pay is built for humans. By integrating Dynamic for frictionless onboarding and Uniswap for background liquidity routing, we’ve eliminated the "token mismatch" headache. Whether the merchant wants USDC and you hold ETH, Zap handles the swap and the settlement in a single tap. No more fumbling with QR codes or waiting for manual confirmations—just seamless, secure, and instant P2P and C2B transactions.

How it's Made

The "magic" of Zap Wallet is a result of a highly customized React Native architecture designed to bridge the gap between hardware-level NFC protocols and decentralized finance.

The UX Engine: Our front end isn't just a skin; it's a performance-tuned environment that uses a Custom Services API to pre-fetch gas estimates and route optimizations. This allows our UI to stay responsive while the heavy lifting happens off-chain.

The Routing Layer: We integrated the Uniswap Universal Router to handle complex multi-hop swaps in a single transaction. This is what allows for our "Tap-to-Swap-to-Pay" feature, ensuring the user never has to manually exchange tokens before a purchase.

The Infrastructure: We chose Dynamic for its elite wallet abstraction, allowing us to offer a Web2-style login without sacrificing self-custody. ENS integration ensures that every transaction is verified against a human name rather than a 42-character string.

The "Secret Sauce": To achieve Apple Pay-level speed, we built a custom native module to handle Host Card Emulation (HCE). By the time the user pulls their phone away, the transaction is already being indexed. We prioritized sub-second feedback loops because in retail, every millisecond of a "loading" spinner is a failure.

background image mobile

Join the mailing list

Get the latest news and updates