fintech
MaxelPay
Crypto payment product · backend + checkout
MaxelPay: session-based crypto checkout with QR, wallet, and transfer — I worked the API + checkout, not the entire processor.
Maxel
Context
MaxelPay is a no-KYC crypto payment gateway (multi-chain, invoices, merchant API). Public docs: REST v1 at api.maxelpay.com, X-API-KEY, POST /payments/sessions, GET session status, webhook callbacks. I contributed on the backend session/API side and the frontend checkout — not custody, chain nodes, or the full commercial product.
Problem
Merchants needed a reliable way to start a payment session and let a buyer pay without writing custom chain code.
- —Contribution-scoped: backend + checkout, not “I built MaxelPay”
- —Session auth via merchant API key
- —Checkout must present QR, wallet, and transfer against live session status
- —No invented volume, fee, or chain-count metrics
What I worked on
- →Backend: payment-session flow (create session, status, webhook/callback wiring) against the v1 payments API
- →Frontend: checkout UI for QR, pay-via-wallet, and direct transfer on session state
- →Merchant-facing confirmation path so status lands back on the checkout
Modules
maxelpay-backend
Payment sessions and status: create a session, authenticate with X-API-KEY, expose status and callbacks for merchants.
Node.js · REST APIs
maxelpay-frontend
Checkout UI on top of those sessions — QR, wallet pay, and transfer — driven by session status.
JavaScript · React
Architecture & approach
Node/REST session API (X-API-KEY) plus a checkout frontend that starts a session, shows the 3D pay options, and waits on status. Laravel/WooCommerce plugins exist in MaxelPay’s public catalog; I do not claim those unless a repo here proves them.
Outcome
- ✓Merchants can start a crypto session and complete checkout without owning chain code
- ✓Backend and frontend work is framed as product contribution, not sole ownership