NexaPay
Cross-Chain Blockchain Payment Platform

01 // System Overview
What The System Does
NexaPay is a decentralized payment gateway engineered to resolve the fragmentation in crypto checkout experiences. By unifying multiple EVM blockchains into a cohesive client interface and smart-contract payment router, NexaPay allows merchants and users to settle payments across chains with transparent fee structures and instant on-chain verification.
02 // Architecture & Data Flow
End-to-End System Design
User Wallet (MetaMask / WalletConnect)
│
▼ Ethers.js Provider
┌───────────────────────────────────────────────┐
│ Next.js / TypeScript Web Application │
│ (Transaction Builder & Order Session) │
└───────────────────────┬───────────────────────┘
│
▼ RPC / Web3 Call
┌───────────────────────────────────────────────┐
│ NexaPay Router Contract (Solidity) │
│ ├── Transaction Verification │
│ ├── Platform Fee Deduction (On-Chain) │
│ └── Merchant Vault Transfer │
└───────────────────────┬───────────────────────┘
│
▼ Cross-Chain Bridge
┌───────────────────────────────────────────────┐
│ Stargate Protocol (LayerZero EVM) │
│ (Cross-Chain Liquidity & Settlement) │
└───────────────────────────────────────────────┘03 // Engineering Ownership
What I Personally Built
04 // Technical Problems Solved
Engineering Challenges & Solutions
Preventing transaction slippage and failed bridge transfers when cross-chain gas spikes occur mid-swap.
Configured Stargate router calls with configurable gas limits, slippage bounds, and client-side balance pre-checks prior to triggering the contract method.
Asynchronous block confirmation latency causing indeterminate UI states for users.
Engineered a reactive state listener tracking transaction hashes across mempool broadcast, first confirmation, and finality with optimistic visual feedback.
Security vulnerabilities and reentrancy risks in payment distribution contracts.
Followed OpenZeppelin battle-tested contracts, enforced the Checks-Effects-Interactions pattern, and implemented ReentrancyGuard on all payable external entrypoints.
05 // Trade-offs
Key Architectural Decisions
- Used Solidity with Hardhat for comprehensive contract test coverage, gas profiling, and simulated network forks.
- Leveraged Stargate for interoperability to enable cross-chain payments without requiring merchants to maintain liquidity pools on every single chain.
- Built the frontend with Next.js and TypeScript for strict typing of contract ABIs and transaction inputs.
Technologies Used
Explore Other Work
ClearPeak Trading
Trading Analytics SaaS Platform