Self-hosted stablecoin payment infrastructure.
A self-hosted stablecoin payment gateway businesses deploy on infrastructure they control.
stablepay.local · dashboard
Live128
Open intents
94
Confirmed
1.4k
Webhooks
INV-1842 · Atlas Freight
USDC · 12,400
PL-2201 · Halcyon night desk
USDT · 3,180
INT-904 · Vellum treasury
USDC · 48,000
StablePay is payment gateway software — not a hosted processor. Customers purchase the software, deploy it on infrastructure they operate, and integrate it into their own applications. The studio does not hold customer funds, run customer wallets, or act as a bank. Production signing, RPC providers, databases, and secrets stay under the customer's control.
Self-hosted deployment on customer infrastructure
Payment intents, payment links, and invoices through a versioned API
Stablecoin-native flows with configurable tokens and networks
Signed webhooks as payments move through their lifecycle
Operational dashboard for tracking, confirmation, and settlement status
Each layer has a job. The product does not hide the boundary between interface, policy, and the systems you already run.
Operator UI and payment surfaces that run inside the customer's deployment.
Create payment intents, receive signed lifecycle events, keep the host application in control.
Payment state, confirmation tracking, and operational records on infrastructure you run.
Connect the chains, tokens, and RPC providers you actually operate. Support is limited to what is implemented and tested.
Not this
Stack
Mock commercial terms for the catalog. You purchase software you operate — not a hosted processor or a seat we quietly run for you.
Several environments, one commercial conversation.
Included
The license most teams actually run.
Included
One production environment you operate.
Included
| What you get | Estate$28,000 | Most chosenCompany$12,000 | Studio$4,800 |
|---|---|---|---|
| Multi-environment license | Included | Included | — |
| Source access for the gateway you purchased | Included | Included | — |
| Quarterly upgrade brief | Included | Included | — |
| Named implementation window (two weeks) | Included | Included | — |
| Staging plus production images | — | Included | — |
| Additional tested network packs | — | Included | — |
| Operator dashboard for treasury review | — | Included | — |
| 24 months of patch releases | — | Included | — |
| Priority implementation notes | — | Included | — |
| Self-hosted gateway binary and Docker image | — | — | Included |
| Payment intents, links, and invoices | — | — | Included |
| Signed webhooks and replay tokens | — | — | Included |
| One network pack (as implemented) | — | — | Included |
| 12 months of patch releases | — | — | Included |
Clients ask for 'a payments option' as if it were a plugin. It is a long-lived responsibility. Here is how to scope it without becoming a payments company.
By Omar Farouk
Faster settlement is easy to promise. The hard part is approvals, records, and an ERP that still has to balance. Here is how a field-services company did it.
By Omar Farouk, Layla Haddad
Every network call can be repeated. The only question is whether repeating it is safe.
By Daniel Whitfield
Tell us what you are operating and we will point you to the license, the preview, or a no.
Free apps from the studio. Enter your email, get a private download link. Free for personal use.
Get them freeHave a product to sell? We review, list, and sell it for you — you keep 90% of every sale.
Apply to sell with us