Ecommerce
SovPay
AvailableSovPay combines a local-signing Bitcoin wallet, human-readable $$handles, public pay pages, store branding, and customer checkout. Keys stay on the client; invoices and chain activity run through the API and BTCPay — not a custodial black box.
A Bitcoin-commerce buyer gets wallet + handle network + merchant storefront in one product family, with Docker/docs for standing it up.
Build vs buy
Skip designing BIP84 client signing, handle registry, mempool proxy, BTCPay invoice webhooks, and a mobile-first store admin from zero.
Differentiation
Handle registry + non-custodial hot wallet + BTCPay invoices + optional store mode in one stack. Server never holds spending keys.
Best fit
Ecommerce operators, SaaS builders, and agencies packaging sovereign Bitcoin checkout — not buyers looking for a custodial neobank.
Evidence
Screenshots are the working interface — not a pitch deck. Click to enlarge.
Click any image to open the gallery · 7 images. Use arrow keys in the lightbox.
Why it matters
Bitcoin checkout is usually either a raw address or a processor. SovPay is a handle, a wallet the user signs, and a store if they want one.
What it does
Users manage send/receive with handles or addresses. Merchants configure branding and present public checkout. Settlement is on-chain / BTCPay, not custodial balances.
Operational advantage
BTC UX usually dies at addresses and ugly invoices. Handles, receive QR, store branding, and checkout are the months of product work already spent.
Build vs buy
Skip designing BIP84 client signing, handle registry, mempool proxy, BTCPay invoice webhooks, and a mobile-first store admin from zero.
Interface advantage
Curated mobile flows: wallet home, send-to-handle, receive, store branding, public storefront, customer checkout. It feels like a consumer product, not a node dashboard.
What makes this different
Handle registry + non-custodial hot wallet + BTCPay invoices + optional store mode in one stack. Server never holds spending keys.
Where this gets used
- Peer payments via $$handle instead of raw addresses
- A merchant public storefront that settles in Bitcoin
- A PWA wallet an agency can brand
Commercial paths
- Turnkey product acquisition
- Commercial source license for a Bitcoin checkout company
- White-label handle + store network
Best buyer fit
Ecommerce operators, SaaS builders, and agencies packaging sovereign Bitcoin checkout — not buyers looking for a custodial neobank.
Current status
Available for commercial source license, exclusive acquisition, or turnkey product acquisition. Conditionally production-ready; walk the audit notes in diligence.
Notes
Screenshots are product UI evidence — not proof of live volume. Some client hardening items (PIN storage, backup UX) remain. Activity feed is invoice/transfer oriented.
Key capabilities
- Non-custodial wallet create/restore with local signing
- $$handle payment network concepts
- Public pay pages and receive QR
- Store branding and merchant admin
- Customer checkout and shipping/email-oriented store flows
Related inventory
Ecommerce / Monitoring
Merchant Survival Engine
Watch merchant sites and checkouts the way an ops team would — Playwright checks, severity, and alerts — without standing up monitoring from zero.
AI / Ecommerce
FlipThat
Put deal analysis, inventory, and profit tracking in a phone-first PWA so local resellers stop running margin math across screenshots.
Commercial source license · Exclusive acquisition · Turnkey product acquisition
Contact for pricing
View assetEcommerce
ReUp Mini
Let social sellers check out from a one-line embed instead of sending buyers to a full storefront they will never finish.