Pay anyone on earth, straight from your wallet.
Crypto payouts for contractors, sellers, affiliates, and merchants — stablecoins that settle in minutes, not T+1. Self-hosted and private, with approvals, OTP, and volume limits guarding every dollar that leaves.
Self-custody · No signup · No KYB · Settles on-chain in minutes
From your wallet
Not a processor’s.
Every payout, under your control.
On-chain money is final — so PayRam puts the checks before the money moves. Dual-control approvals, a second factor, and an allow-list of verified recipients. Watch a payout travel the rail:
Requested: A team member requests a payout to a verified recipient. Nothing moves yet.
Watch money ask for permission.
This is the payout approval screen, on loop. A request lands, an approver clicks, an email OTP confirms — and only then does money move. The person who requested it is never the one who approves it.
A re-staging of the real screen — Payouts → Requests. Yours ships with the install.
Security that makes your CFO smile.
Irreversible rails demand reversible decisions. The payout approval workflow most finance teams keep in a policy doc lives here in code — and code doesn’t make exceptions.
Maker/checker approvals
The person who requests a payout can never be the one who approves it. Role-based, project-scoped dual control on every payout.
Email OTP on funds movement
A one-time code confirms the moment money actually moves — a second factor on your treasury, not just your login.
Thresholds & volume limits
Routine payouts flow; large or unusual ones stop for a human. Auto-approve thresholds plus daily and hourly volume limits, enforced server-side.
Verified recipients only
Payouts can only go to recipients you’ve saved and email-verified — a built-in allow-list that stops funds going to the wrong address.
Tamper-safe retries
A stuck payout is re-broadcast, never re-signed — so a retry can never double-pay. Every attempt and failure reason is tracked.
Role-based access
Ops can request, admins approve, and every permission is scoped per project. Your org chart, enforced by the gateway.
Walking your finance team through it? Talk to us
One API call. Money on its way.
Marketplaces, affiliate networks, and gig platforms drive payouts entirely through the payout API — recipients created on the fly, policy checks enforced server-side, webhooks confirming every landing.
Payouts at scale, through one API
Fan out payouts programmatically — the API creates the recipient, runs your policy engine, and settles on-chain. Your platform pays hundreds of sellers while you sleep.
Real-time webhooks
Your systems hear every status change — created, approved, sent, confirmed — with automatic retries backing off for up to 48 hours. No polling, no blind spots.
Operator & affiliate payouts
Pay your merchants and your promoters from the same engine — approvals, OTP, and on-chain settlement included. The payout half of Operator Mode.
→ Operator ModeTracked end to end
Every payout is visible from request to on-chain confirmation, with explorer links, status filters, and full-history search in the dashboard.
curl -X POST https://your-server.com/api/v1/withdrawal/merchant \
-H "API-Key: <your-project-key>" \
-d '{
"customerID": "seller_8412",
"email": "maria@example.com",
"currencyCode": "USDC",
"amount": "862.50",
"network": "BASE"
}'Every payout clears the same gate — auto-approve under your threshold, manual review above it. Full docs at docs.payram.com, or let an AI agent drive it via MCP.
Your recipients already hold dollars.
Contractors in Lagos, sellers in Manila, affiliates in Istanbul — stablecoins are how they save. Pay them in USDT or USDC on rails they already use: funds go straight from your wallet to theirs, no custodian in between — cross-border payouts that settle on-chain in minutes, not days.
International wire
- Cost structure
- $30–50 per transfer
- Settlement
- 1–5 business days
- Availability
- Banking hours only
PayPal / platforms
- Cost structure
- 2–5% + FX spread
- Settlement
- 1–3 days to local bank
- Availability
- Unsupported in many markets
PayRam payout
- How it moves
- Wallet to wallet — no custodian, no holds
- Settlement
- Minutes, on-chain
- Availability
- 24/7, anywhere with a wallet
Private by architecture
Who you pay, how much, and how often is your business — literally. PayRam runs on your server, so no processor accumulates your payout graph, and there’s no third party to report, monitor, or freeze it. The compliance load is yours to own, run to your jurisdiction’s rules, not outsourced to a processor’s policy team.
Built for businesses where money flows out.
One self-hosted engine for crypto disbursement — stablecoin payouts for affiliate networks, marketplaces, creator platforms, and operators. The same install accepts your revenue, too: money in and money out, one treasury.
Affiliate & CPA networks
The pain: A 500-publisher month costs $15k–25k in wire and platform fees — with your float parked at a processor.
With PayRam: Pay every publisher on Tron in minutes, keep your float in your own wallet, and gate big payouts behind approvals.
→ PayRam’s own affiliate programMarketplaces & gig platforms
The pain: Sellers churn when payouts take a week and arrive short. Cross-border banking makes it worse.
With PayRam: API-driven seller payouts that settle on-chain in minutes — with maker/checker keeping your finance team in control.
Creator platforms
The pain: Creators in emerging markets lose 3–7% to intermediaries and wait days for their earnings.
With PayRam: Pay creators in USDT where they already hold dollars — straight from your treasury, settling on-chain 24/7.
Operators & PSPs
The pain: Serving merchants means disbursing to them — without becoming a custodian or building a payout stack.
With PayRam: Operator Mode pays your merchants from the same engine: approvals, OTP, webhooks, and on-chain settlement built in.
→ Operator ModeTwo stablecoins, four chains, one engine.
Pay out USDC and USDT across Ethereum, Base, Polygon, and Tron. (Accepting payments? That side spans even more chains, including Bitcoin — see the full stack.)
Asked before every launch.
The details finance teams check first. Deeper questions?Talk to us
