How is a white-label gateway different from a payment facilitator?

A white-label gateway is about the branding and deployment model — you ship someone else’s tech under your own name. A Payment Facilitator (PayFac) is about the merchant-account structure — one master merchant onboards many sub-merchants under its own acquiring relationship. PayRam lets you be both: a white-label, self-hosted, PayFac-style operator on crypto rails.

Can I use a white-label payment gateway for high-risk industries?

Traditional white-label gateways inherit the category restrictions of their underlying processor and sponsor bank — iGaming, adult, creator platforms are typically blocked. Crypto-native white-label deployments with PayRam don’t pass through those gatekeepers; you decide what categories you serve.

White-label · Self-hosted

White-label payment gateway. Your brand, end to end.

Q: Is PayRam fully brandable?

Yes. You deploy on your own domain, configure the checkout theme to match your product, issue API keys under your own name, and route webhooks through your own infrastructure. Your merchants and their end-users see your brand throughout — PayRam is invisible.

Launch your own branded payment gateway in under 10 minutes. Your domain, your checkout styling, your API keys, your support relationship. PayRam runs underneath — your customers never know. Self-hosted, non-custodial, no vendor revenue share.

Book a call Deploy in 10 minutes Operator playbook

White-label stackYour domain·Your checkout theme·Your API keys·Your pricing·Zero vendor revenue share

The model

What is a white-label payment gateway?

A white-label payment gateway is payment infrastructure you brand and ship as your own product. Your sub-merchants sign up for your gateway, pay you, and never know which vendor's tech sits underneath. It's how PSPs, ISVs, SaaS platforms, and agencies launch payments without building from scratch.

The traditional options: vendor-hosted white-label platforms (Spreedly, Corefy, and branded PSP stacks) charge tens to hundreds of thousands in setup plus a revenue share on volume. You get a branded checkout fast, but you don't own the rails — the vendor does.

PayRam is the self-hosted alternative. Same branding outcome, no vendor in the middle, no setup cost beyond the VPS, no revenue share. Every dollar of margin stays with you.

Side-by-side

Vendor-hosted white-label. Self-hosted PayRam.

Both give you a branded gateway. Only one lets you own the rails, the data, and the full spread.

Feature	Vendor-hosted white-label	PayRam (self-hosted)
Setup cost	$50k–$250k	~$20–$150/mo VPS
Time to launch	3–6 months	~10 minutes
Revenue share to vendor	10–40 bps or more	Zero
Vendor lock-in	High (proprietary APIs)	None (your infra)
Category restrictions	Vendor + sponsor bank ToS	You decide
Fund custody	Vendor or pooled	Merchant-controlled wallet
Rolling reserve	5–10% of GMV	Zero
Chargeback liability	Shared with vendor	None on crypto rails
Customization	Vendor theme engine	Full source-level control
Branded checkout on your domain	Yes (with vendor branding risk)	Yes, end-to-end
Data ownership	Shared	100% yours (your VPS)

What you get

Everything a white-label should be. Nothing it shouldn't.

Your domain

Deploy on pay.yourcompany.com, checkout.yourbrand.io — anything you own. DNS + SSL, one-time setup.

Your checkout theme

Customize colors, logo, copy, and layout. End-users see a payment page that feels native to your product.

Your API keys

Issue API keys under your company name. Merchants integrate your API, not PayRam’s. Webhooks are signed by your service.

Your merchant dashboard

The operator dashboard runs under your brand. Your merchants log into your.payments.app, not payram.com.

Multi-tenant sub-merchants

50+ merchants per instance, each with isolated wallets, API keys, webhooks, and reference namespaces.

Drop-in widget

Ship the Add Credit widget on your merchants’ sites. The script tag is branded with their data attributes, never PayRam’s name.

MCP server (agent-ready)

Built-in support for AI-agent integrations via Model Context Protocol. Your merchants can expose their payment rails to OpenClaw, Claude, and other MCP clients.

Card-to-crypto onramp

Accept Visa / Mastercard payments and settle as USDC in the merchant’s wallet. Unique to PayRam among self-hosted gateways.

REST API + webhooks

Full REST API under your domain. Webhook payloads HMAC-signed by your secret. Standard retry schedule.

Who ships white-label

Six shapes. Pick yours.

SaaS platform

Ship "[YourSaaS] Payments" as a feature. Every customer is a sub-merchant on your gateway.

Marketplace

Buyers pay, sellers get paid. Your marketplace brands the whole flow.

Agency

Deploy once, onboard a portfolio of client brands. Each gets a white-label sub-deployment.

PSP / ISO graduation

Existing ISO portfolio? Migrate to your own white-label gateway and own the rails.

Crypto exchange

Add a merchant-facing payment gateway on top of your exchange. New revenue line, no extra compliance.

Niche vertical

iGaming, adult, creator platforms, supplements — your white-label, your category policy.

Launch

One command. Your gateway, live.

Ubuntu VPS with 15 GB+ free disk. Your domain pointing at it. A hardware wallet for the xPub. Run the script. Brand the UI. Ship.

Deploy

bash <(curl -fsSL https://payram.com/setup_payram.sh)

Full setup guide ·Advanced setup

Supported Chains & Tokens

20+ tokens across 6 networks. Stablecoin-native — USDT and USDC on every supported chain.

Bitcoin

BTC

Variable · ~10 min

Ethereum

ETH

~$1–5 · ~15 sec

Tron

TRX

~$0.01 · ~3 sec

Base

BASE

~$0.01 · ~2 sec

Polygon

POL

~$0.01 · ~5 sec

Soon

Solana

SOL

~$0.001 · ~0.4 sec

Primary stablecoins:

USDT

USDC

+ BTC, ETH, TRX, and 15 more

White-label questions.

What is a white-label payment gateway?+

A white-label payment gateway is payment infrastructure you deploy and brand as your own product — your logo, your domain, your pricing, your customer relationship. Your sub-merchants never know which underlying software vendor powers it. PayRam is a self-hosted white-label stack for stablecoin and card-to-crypto payments, operator-ready out of the box.

What does it cost to launch a white-label payment gateway?+

Vendor-hosted white-label platforms typically charge $50k–$250k in setup, plus a revenue share on processed volume, with 3–6 months to launch. A self-hosted PayRam deployment costs ~$20–$150/month in VPS hosting, takes about 10 minutes to stand up, and you keep 100% of whatever you charge your sub-merchants.

Is PayRam fully brandable?+

Yes. Deploy on your own domain, match the checkout theme to your product, issue API keys under your brand, route webhooks through your own infrastructure. Your merchants and their end-users see your branding throughout. PayRam stays invisible.

White-label gateway vs. PayFac vs. ISO: which one do I need?+

White-label is a brandingmodel — ship someone else's tech under your own name. PayFac is a merchant-account model — one master merchant onboards many sub-merchants. ISO is a sales-channelmodel — resell a processor's service for residuals. PayRam lets you combine all three: branded (white-label), operator-owned sub-merchants (PayFac-style), running on your own rails (not reselling). PayFac explainer · ISO explainer

Can I use a white-label gateway for high-risk industries?+

Traditional white-label gateways inherit the category restrictions of their underlying processor and sponsor bank — iGaming, adult, creator platforms, supplements, high-risk e-commerce are typically blocked. Crypto-native white-label deployments on PayRam don’t pass through those gatekeepers. You decide what categories you serve based on your own operator policy.

Do I get an API to build on top of?+

Yes — the full REST API, plus webhook contracts, plus an MCP server for AI-agent integrations, plus a drop-in widget. You can build a bespoke checkout, a mobile app, an OpenClaw agent, or ship the default widget. Everything ships under your domain and your brand.

How do I start a white-label payment gateway?+

Deploy PayRam on your VPS (one bash command, about 10 minutes), point your domain at it, onboard your first merchant in the operator dashboard, issue their API key. Total time to first payment accepted through your branded gateway: under an hour. See the setup guide.

What’s the revenue model?+

Whatever you negotiate with your merchants. Setup fees, monthly retainers, volume margin, flat fees — all outside the payment stack because PayRam is non-custodial. You never touch merchant funds, so your fee collection is a separate billing relationship you control.

Your brand. Your rails. No vendor in the middle.

White-label done right is a deployment you own. Not a logo swap on someone else's dashboard.

Book a call Operator playbook Deploy now Docs