The URL is the invoice. No backend. No signup. No tracking. Just a link.
VoidPay is a stateless web app that lets anyone — DAO contributors, freelancers, indie developers — generate self-contained crypto payment links. Invoice data is encoded into the URL hash fragment using a binary TLV codec with Brotli compression. It never touches a server. The recipient opens the link, sees a complete payment card decoded entirely client-side, connects their wallet, and pays peer-to-peer.
Live on Ethereum, Base, Arbitrum, Optimism, Polygon. v1.0 deployed March 28, 2026. Open-source, MIT licensed.
Build and maintain the open invoicing standard for crypto payments — privacy-preserving by architecture, permissionless by design, perpetual by commitment.
Crypto payments today have three structural problems that no existing tool solves together:
1. Professionalism gap
Sending a raw 0x… address in Telegram or Discord is the norm. It looks amateur, undermines trust, and gives the payer nothing to verify against.
2. Error exposure
Wrong network, wrong token decimals, clipboard hijacking — every unverified payment carries real risk of permanent loss. ERC-20 transfers carry no payment reference, so reconciliation normally requires a server-side match.
3. The privacy-or-convenience trade-off
Tools like Request Finance solve the professionalism problem but require KYC, accounts, and organization setup — the wrong shape for a DAO contributor sending a single invoice. More critically, centralized invoice services store your entire counterparty graph and payment history indefinitely. The invoice infrastructure becomes a surveillance layer.
The DAO and Web3-freelancer ecosystem has no privacy-respecting, permissionless invoice primitive. VoidPay is that primitive.
Four architectural pillars — not four features:
Zero-Backend: The URL hash fragment is never transmitted to any server (RFC 3986). The link is the entire database row. We cannot lose your data because we never have it.
Privacy-First: No analytics, no tracking, no accounts. Invoice history lives in your browser's localStorage only. The optional OG preview parameter contains minimal public metadata (amount, currency, network) — never wallet addresses.
Permissionless: No signup, no KYC, no approval process. Anyone with a crypto wallet can create or pay an invoice.
Perpetual: Schema v1 is locked. Links created today will resolve and verify correctly in 2030, even if voidpay.xyz no longer exists.
How reconciliation works without a server:
ERC-20 transfers carry no memo field. VoidPay solves this with Magic Dust: a deterministic micro-amount derived from the invoice via HMAC-SHA256, added to the payment total. It binds invoice to payment at the protocol level — no webhook, no callback, no third party.
The next phase (funded via grants pipeline): extract the codec into @voidpay/codec npm package, publish an EIP-style invoice standard, and release @voidpay/merchant and @voidpay/agent SDKs — making the invoicing layer usable by any developer without depending on voidpay.xyz.
opensource
Want to grow through just grant funding
Global / Internet-native
