Run the payment gateway. Own the business.
Deploy one PayRam instance. Onboard dozens of merchants under it. Each with their own wallet, API keys, and webhooks — attributed automatically, settled non-custodially, paid out on-chain. Be the Stripe for your niche, without the Stripe overhead.
One instance. Many merchants.
You operate the software. Each merchant is a tenant with their own wallet, API keys, and end-users. Payments flow in, references tag them to the right merchant, and the smart contract sweeps settled funds to the merchant's own cold wallet.
Every transaction carries a reference tag that ties it back to the merchant it belongs to. Reconciliation is automatic — no spreadsheets, no manual matching.
Someone's going to own this. Why not you?
Stablecoin settlement has crossed Visa. Stripe, Revolut, Flutterwave are live on-chain. None of that volume flows through independently operated, self-hosted infrastructure — every business behind those numbers either built their own stack or signed an enterprise contract.
There is no permissionless, operator-owned alternative to hosted payment gateways. The infrastructure layer for the next wave of decentralised merchant services has not been built. The window to build it is now, while the traditional gatekeepers are still designing their approval workflows.
Self-hosted or hosted — both are PayRam.
Some merchants want to run it themselves. Most don't. They love PayRam's sovereignty and economics but prefer someone else to manage the VPS, the upgrades, the on-call. That's you. You become the WordPress.com to their WordPress.org — the hosted operator of the open-source stack.
Self-hosted merchant
- Technical founders who want full control
- Pay only for their VPS (~$20–$150/mo)
- Handle their own upgrades and uptime
- PayRam = the software
Your managed service
- Non-technical merchants who want to skip ops
- Pay you setup + monthly + volume margin
- You handle VPS, upgrades, monitoring
- PayRam = your product
A full financial engine. Not a checkout button.
Multi-merchant dashboard
Create, configure, and monitor merchants from a single operator view. Each merchant has their own section with wallet, API keys, webhooks, and transaction history.
Per-merchant wallet
Every merchant designates their own cold wallet at onboarding. PayRam derives deposit addresses from their xPub, the smart contract sweeps to their cold wallet. You never hold their funds.
Per-merchant API keys
Issue API keys scoped to a single merchant. Keys can be rotated, revoked, and renamed. Each key carries the merchant’s reference namespace automatically.
Dual gateway — collect + pay out
Most gateways move money one direction. PayRam does both. Marketplaces collect from buyers and distribute to sellers. Payroll products collect from employers and pay workers. Same system.
Per-merchant webhooks
Each merchant configures their own webhook URL and secret. PayRam signs the payload with HMAC-SHA256. Failed deliveries retry on a 30m → 48h schedule.
Non-custodial end-to-end
You operate the software. Merchants control their funds. End-users deposit directly on-chain. No custodian. No rolling reserves. No fund-freeze risk for anyone in the chain.
Payment references — UTM for money.
Every payment carries a structured reference tag you set at creation time. Client ID, campaign code, invoice number, project slug — any string you want. It travels with the payment on-chain and arrives in your webhook payload the moment the transaction confirms.
A single instance running on one VPS comfortably serves 50+ merchants simultaneously. Each gets their own wallet address and namespace. Reconciliation is automated — no manual matching, no cross-reference spreadsheets. Every payment arrives tagged, attributed, and ready to act on.
- Multi-merchant operators reconcile client portfolios automatically
- Agencies tie each payment to a specific project at receipt
- Platforms attribute revenue to campaigns or business units in real time
- Subscription products map recurring payments to subscriber records
{
"event": "payment.confirmed",
"reference_id": "acme:inv_48213",
"merchant_id": "mrch_abc",
"amount": 249.00,
"currency": "USDC",
"chain": "base",
"tx_hash": "0x…",
"confirmed_at": "2026-04-19T12:34:56Z"
}Your handler routes by merchant_idand posts back to the merchant's own integration. The reference_id is whatever you set at create_payment time — any string.
Three shapes. Pick yours.
Same underlying infrastructure, four go-to-market postures. Not an exhaustive list — just the shapes that have worked so far.
Managed infrastructure
Deploy and manage PayRam instances for merchants who need permissionless crypto payment infrastructure but don’t want to run their own server. Charge setup fees, monthly retainers, or a margin on volume.
Best for: devs, consultants, small-team agencies, fractional CTOs.
Your own platform
Build a marketplace, SaaS product, or commerce platform that settles in stablecoins. PayRam handles the payment layer so your engineering stays on the product. Merchants/sellers under your platform each get a reference namespace.
Best for: platform founders, marketplace builders, creator-economy products.
Cross-border payouts
Average cross-border remittance costs run 6–8%. Your cost on Polygon is fractions of a cent. Build a corridor that moves USDC in both directions across borders. The spread is the product margin.
Best for: remittance products, gig-economy payout platforms, diaspora-focused fintech.
Multi-merchant + references
- Onboard unlimited merchants under one instance
- Per-merchant wallets, API keys, webhooks
- Reference system for automated reconciliation
- Dual gateway — collect and pay out
- Multi-chain stablecoin support
Custom per-merchant fees
- Set your own % or flat fees per merchant
- Automatic fee-split on settlement
- Tiered pricing and volume-based tiers
- Operator payouts in USDC
- Real-time fee analytics in the dashboard
Roadmap item — no commitment date yet. Ship it yourself today by handling fee collection outside PayRam; the API-level fee-split feature below is a convenience add-on.
Start your service. Ship merchant one today.
Deploy your PayRam instance
One line on any Ubuntu 22.04+ VPS with 15 GB+ disk. Your domain, your cold wallet, your operator account. Ten minutes end-to-end.
Onboard your first merchant
From the operator dashboard, create a new merchant. They designate their cold wallet, you issue their API key, the webhook URL gets wired up.
Ship their integration
Drop the widget script tag, or hand them the API key for custom checkout, or register the MCP server for agent-operated flows. Each option carries the reference tag automatically.
Repeat at volume
Add merchants as fast as you can sign them up. A single instance comfortably handles 50+. Reconciliation scales with your DB, not your ops team.
bash <(curl -fsSL https://payram.com/setup_payram.sh)
Supported Chains & Tokens
20+ tokens across 6 networks. Stablecoin-native — USDT and USDC on every supported chain.
USDT
USDCOperator questions.
Who is the operator offering for?+
How many merchants can one instance handle?+
How is operator mode different from running PayRam for myself?+
Can I charge my own fees to merchants?+
Do I need to hold custody of merchant funds?+
What about compliance?+
You operate the service. Compliance is your responsibility.
PayRam is open-source software you deploy and run yourself. Licensing, registrations, KYC/AML where required, tax reporting, consumer-protection rules, and any other obligations in the jurisdictions where you or your merchants do business are entirely your responsibility.
PayRam is not a payment service provider, does not hold funds on behalf of any party, and carries no liability for how operators or merchants use the software. Always consult local counsel before launching commercially.
The window is open. Step through.
Every dollar of stablecoin volume that flows through a self-hosted operator is a dollar that doesn't get rented from a custodial gatekeeper. Start today. Onboard merchant one this week.