NexxPay

Demo

About

# Unified Cross-Chain Payments Across the world, the **demand for stable value digital payments** is rising — from **Web3 ecosystems**, **Web2 fintechs**, and even **governments** exploring digital currency rails. Yet, the biggest challenge remains **liquidity fragmentation**. Stablecoins and tokens exist on dozens of blockchains and rollups — each isolated by design. Funds can’t move freely, merchants can’t accept payments universally, and users constantly swap or bridge just to make a simple transfer. We set out to **fix that**. --- ## 🪶 Our Vision **One balance. Any chain. Every token.** We’re building a **unified cross-chain payment layer** that removes the boundaries between blockchains. Using **Avail Nexus**, we **aggregate and unify** the user’s balances across all connected rollups into one consolidated view. So when you pay, you don’t think *“which chain is my token on?”* — you just pay. For tokens and networks that Nexus doesn’t yet support, we integrate **Across Protocol** as a **cross-chain bridge**. Across routes liquidity efficiently between chains (starting with **Base** as the intermediary), ensuring every payment finds a path — with **minimal fees** and **high reliability**. --- ## 🔐 Trust via Identity Payments aren’t just about sending funds — they’re about **knowing who you’re paying**. That’s where **ENS (Ethereum Name Service)** comes in. Each merchant registers a **business subname** (like `acme.pay.eth`), which acts as both an **identity** and a **payment endpoint**. Every merchant’s payout configuration — preferred chain, token, and gateway — is stored as a **verifiable record** within their ENS resolver. In future versions, this will extend to **DNS imports**, allowing verified Web2 business domains (like `acme.com`) to link directly to their ENS, creating **trust bridges between Web2 and Web3**. --- ## 💳 Payment Experience We designed the flow to be **simple and universal** — familiar for Web2 users yet fully Web3-native. ### **Merchant Onboarding** - Registers a business name via **ENS subname**. - Selects preferred **chain** and **token** for settlement (e.g., USDC on Base). - Instantly receives multiple payment gateways: - **ENS Pay** (enter the ENS name) - **QR code** - **NFC tap-to-pay** - **Shareable Link** ### **User Payment** - Connect wallet (any supported chain). - We fetch and **unify balances** across Nexus-supported networks. - User selects *any token* to pay. - If the merchant’s payout configuration exists within Nexus → transfer executes natively. - If not → payment is **bridged via Across** (via Base) to complete the settlement. ### **Settlement** - Merchant receives the chosen **token** on the chosen **chain**, automatically routed and bridged if needed. - The transaction hash, source route, and metadata are written back to the **ENS record** for full verifiability and history. --- ## 🌍 Why It Matters - **Solves Stablecoin Fragmentation:** Global demand meets unified liquidity. - **Abstracts Chains Away:** Users don’t care where their funds live — payments just work. - **Introduces Trust via ENS:** Businesses can be recognized by name, not by wallet address. - **Cross-Rail Ready:** NFC, QR, and Link options make it usable in both Web3 and physical-world transactions. - **Future-Proof:** Expanding from Web3 identity to Web2 DNS verification, and from stablecoins to any digital asset.

How it's made

We built the project using **Avail Nexus**, **ENS**, and **Across Protocol**. **Nexus** unifies liquidity across its connected rollups, giving users one aggregated balance to pay from any chain. **ENS** provides verifiable business identities — each merchant registers a subname (e.g., `store.pay.eth`) storing payout preferences and metadata directly on-chain. For tokens or networks not yet supported by Nexus, - **Justaname** **Across** bridges the transfer efficiently (via Base as intermediary), ensuring merchants always receive the correct token on their chosen chain. Together, they enable truly unified, chain-agnostic payments with identity and trust built in.