NexxPay

Problem Statement

Unified Cross-Chain PaymentsAcross the world, thedemand for stable value digital paymentsis rising — fromWeb3 ecosystems,Web2 fintechs, and evengovernmentsexploring digital currency rails.Yet, the biggest challenge remainsliquidity 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 tofix that.🪶 Our VisionOne balance. Any chain. Every token.We’re building aunified cross-chain payment layerthat removes the boundaries between blockchains.UsingAvail Nexus, weaggregate and unifythe 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 integrateAcross Protocolas across-chain bridge.Across routes liquidity efficiently between chains (starting withBaseas the intermediary), ensuring every payment finds a path — withminimal feesandhigh reliability.🔐 Trust via IdentityPayments aren’t just about sending funds — they’re aboutknowing who you’re paying.That’s whereENS (Ethereum Name Service)comes in.Each merchant registers abusiness subname(likeacme.pay.eth), which acts as both anidentityand apayment endpoint.Every merchant’s payout configuration — preferred chain, token, and gateway — is stored as averifiable recordwithin their ENS resolver.In future versions, this will extend toDNS imports, allowing verified Web2 business domains (likeacme.com) to link directly to their ENS, creatingtrust bridges between Web2 and Web3.💳 Payment ExperienceWe designed the flow to besimple and universal— familiar for Web2 users yet fully Web3-native.Merchant OnboardingRegisters a business name viaENS subname.Selects preferredchainandtokenfor settlement (e.g., USDC on Base).Instantly receives multiple payment gateways:ENS Pay(enter the ENS name)QR codeNFC tap-to-payShareable LinkUser PaymentConnect wallet (any supported chain).We fetch andunify balancesacross Nexus-supported networks.User selectsany tokento pay.If the merchant’s payout configuration exists within Nexus → transfer executes natively.If not → payment isbridged via Across(via Base) to complete the settlement.SettlementMerchant receives the chosentokenon the chosenchain, automatically routed and bridged if needed.The transaction hash, source route, and metadata are written back to theENS recordfor full verifiability and history.🌍 Why It MattersSolves 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.

Solution

We built the project usingAvail Nexus,ENS, andAcross Protocol.Nexusunifies liquidity across its connected rollups, giving users one aggregated balance to pay from any chain.ENSprovides 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, -JustanameAcrossbridges 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.