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. Set your markup, and it's split on-chain at settlement, straight to your wallet. Be the Stripe for your niche, without the Stripe overhead.
Live production network — the same rails your merchants will run on.
You set the fee. The chain pays you.
Pick a markup — per chain, with per-merchant overrides. When funds are swept, a smart contract splits the transaction: the merchant's share settles to their cold wallet, your cut settles to your collector. Same transaction. No invoicing. No middleman holding either side.
Each payment is swept by the smart contract and split in one transaction: the merchant's share to their cold wallet, your markup to your collector. No middleman, no reconciliation. (Fee share enlarged for legibility.)
Card processors take 2.9% + 30¢ and hold your money for days. You set your own rate, settle in seconds, and hold nothing — the chain does the splitting.
Illustrative figures. Drag the markup to model your own economics.
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. It's the Payment Facilitator / Payment ISO / white-label gateway pattern — on stablecoin rails, with no sponsor bank and no underwriting.
Every transaction carries a reference tag that ties it back to the merchant it belongs to. Reconciliation is automatic — no spreadsheets, no manual matching.
A full financial engine. Not a checkout button.
Everything a processor does — onboarding, settlement, payouts, reconciliation, and your own take rate — running on infrastructure you control. Here's what ships in the box.
Operator fee engine
NewSet a markup per chain with per-merchant overrides. Settled on-chain at sweep time, straight to your collector address. The split happens in the same transaction that pays the merchant.
Operator analytics
NewLive earnings, per-merchant performance, and settlement status in one dashboard — with websocket hot-refresh, so the numbers move as the money does.
Multi-merchant dashboard
Create, configure, and monitor every merchant from a single operator view. Each has their own section with wallet, API keys, webhooks, and full transaction history.
Per-merchant wallets & keys
Each merchant designates their own cold wallet at onboarding; PayRam derives deposit addresses from their xPub. API keys are scoped per merchant — rotate, revoke, rename. You never hold their funds.
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.
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",
"operator_fee": 2.49,
"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, and operator_fee is your cut on that settlement.
A Stripe Connect alternative — that you actually own.
Hosted platforms like Stripe Connect and card-rail PayFacs let you run payments for sub-merchants — until they hold the funds, set the rate, and decide who stays on. PayRam gives you the same multi-merchant model with none of the leash.
Three shapes. Pick yours.
Same infrastructure, three go-to-market postures — each priced through the on-chain fee engine. 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. Price it with a per-transaction markup, a monthly retainer, or both.
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. Your markup on each sub-merchant’s volume is your take rate.
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, plus your on-chain markup, is the margin.
Best for: remittance products, gig-economy payout platforms, diaspora-focused fintech.
“The future of internet commerce runs on infrastructure you own, not services you rent. PayRam exists to widen access to commerce — helping merchants and builders become their own payment processor.”
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.
Set your fees, onboard merchant one
Set a markup per chain in the operator dashboard, then create a merchant. They designate their cold wallet, you issue their API key, the webhook gets wired up.
Ship their integration
Drop the widget script tag, 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+. Your fee settles on-chain on every sweep — reconciliation scales with your DB, not your ops team.
bash <(curl -fsSL https://payram.com/setup_payram.sh)
Someone's going to own this. Why not you?
Stablecoin settlement has crossed Visa. Stripe, Revolut, Flutterwave are live on-chain. Almost none of that volume flows through independently operated, self-hosted infrastructure — the businesses behind those numbers either built their own stack or signed an enterprise contract.
The permissionless, operator-owned layer for the next wave of merchant services is still wide open. The window to build it is now, while the traditional gatekeepers are still designing their approval workflows.
Figures from public stablecoin-market data, 2025. Directional context — not a forecast of your results.
Supported Chains & Tokens
20+ tokens across 6 networks. Stablecoin-native — USDT and USDC on every supported chain.
USDT
USDCOperator questions.
Can I charge my own fees to merchants?+
How does the on-chain fee split actually work?+
Is PayRam a Payment Facilitator (PayFac)?+
How does this differ from a Payment ISO agent program?+
Is PayRam an alternative to Stripe Connect?+
Can I white-label the gateway with my own brand?+
Do I need a sponsor bank?+
How many merchants can one instance handle?+
Do I need to hold custody of merchant funds?+
How is operator mode different from running PayRam for myself?+
What about compliance?+
You operate the service. Compliance is your responsibility.
PayRam is self-hosted 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.
Keep reading.
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 — and earn on every transaction after.