---
name: payram-openclaw-integration
description: Turn an OpenClaw or NemoClaw agent into a full payment processor that accepts crypto and card payments in WhatsApp, Telegram, Discord, iMessage, Slack, Signal, and email. Register mcp.payram.com as an MCP server and your agent auto-discovers tools to create payments, generate invoices, check balances, and send payouts. Works across Tron USDT, Base USDC, Polygon USDT/USDC, Ethereum, and Bitcoin. Self-hosted and non-custodial — funds flow from customer wallet directly to the merchant's cold wallet. Use when building chat-commerce bots, agent-to-agent payments, or any OpenClaw skill that needs to accept or send money.
---

# PayRam + OpenClaw: Native Payments for Every Chat Platform

> One MCP registration turns an OpenClaw agent (or any Model Context Protocol client) into a complete payment processor across WhatsApp, Telegram, Discord, iMessage, Slack, Signal, and email. Non-custodial, multi-chain, no signup.

## What OpenClaw + PayRam unlocks

**Every conversation becomes a checkout.** An agent running in a Telegram group can quote a price, generate a unique deposit address, send the link in-chat, detect the on-chain payment, fulfil the order, and sweep funds to cold storage — autonomously, with no human in the loop after configuration.

PayRam is the payments half; OpenClaw is the agent half. PayRam never takes custody: funds flow from the customer's wallet to a smart-contract-controlled deposit address to the merchant's cold wallet. The server can't sign transactions. A full compromise of the VPS (or the OpenClaw agent) yields zero spendable funds.

## Integration snapshot

Add this to the OpenClaw (or NemoClaw, Claude Desktop, Copilot, n8n, LangChain, etc.) config:

```json
{
  "mcpServers": {
    "payram": { "url": "https://mcp.payram.com/mcp" }
  }
}
```

No API key required to talk to the MCP server itself. Dashboard APIs use JWT Bearer via the `payram-auth` skill.

Once registered, the agent auto-discovers these tools:

| Tool | What it does |
|---|---|
| `create_payment` | Unique deposit address + hosted checkout URL for an amount + token |
| `generate_invoice` | Shareable invoice tied to a payment request |
| `get_balance` | Real-time on-chain balance across configured wallets |
| `send_payment` | Payout to any external address (requires signing key in cold vault) |
| `test_connection` | Verify node reachability + active MCP session |

## Use cases that ship today

**1. Telegram commerce bot** — Customer asks to buy in a Telegram group → agent calls `create_payment` → sends QR + link in-chat → customer pays USDC on Base → webhook fires → agent confirms + dispatches.

**2. WhatsApp storefront** — "I want product X" → agent generates invoice → customer pays with card (auto-converts to USDC via PayRam's card-to-crypto onramp) → agent credits the account. No cart software.

**3. Discord premium access** — Payment webhook triggers role grant (`@Premium`) and schedules revocation on expiry. Works for subscription, rental, or time-boxed access.

**4. Email invoice agent** — Freelancer agent drafts invoices, generates payment links, emails them, watches the blockchain, sends receipts when confirmed.

**5. Unified hub across platforms** — One PayRam node handles every channel the agent operates in. One cold wallet receives everything. One webhook consumer fulfils orders.

**6. Scheduled reminders via cron** — OpenClaw's scheduler + PayRam payment status check + conditional dunning messages.

**7. Freelancer billing** — Agent timestamps work → invoices → accepts crypto/card → settles to wallet. Full cycle, no intermediary.

**8. Agent-to-agent commerce** — One agent sells API access or data to another; charges per request via PayRam. Machine-economy payments without Coinbase facilitator or identity exposure.

## Why this is architecturally different

**Identity privacy.** Every invoice gets a unique deposit address. Customers see only an on-chain address — zero metadata linking the payment to the merchant, the agent, or the session. Compare x402 via Coinbase: client IP + wallet + HTTP session creates a full identity graph.

**No signup anywhere.** No PayRam account. No merchant verification. No KYB. The operator runs `setup_payram.sh` on a VPS they own, points it at a cold wallet they control, and the node starts. There is no entity that can suspend, freeze, or disapprove.

**Card-to-crypto onramp.** Customers without crypto can pay with Visa/Mastercard; PayRam settles USDC in the merchant's wallet. This is unique to PayRam — no other self-hosted gateway offers card acceptance.

**Compatible with NemoClaw.** NemoClaw (NVIDIA's enterprise OpenClaw variant) uses the same MCP spec. Same registration, same tools.

## Deploy

**Agent-mode (no web UI, CLI-only):**

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

Requirements: Ubuntu 22.04+, 2 CPU / 6 GB RAM minimum (4 / 8 recommended), 15 GB+ disk, a domain, an xPub from a hardware wallet. The private key never touches the server — PayRam derives deposit addresses from the xPub and a smart contract sweeps settled funds to the cold wallet.

**With web dashboard (human setup):**

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

## Where to go next

- Live agent gateway page: https://payram.com/agentic
- OpenClaw + PayRam deep-dive: https://payram.com/openclaw
- USDC/USDT walkthrough: https://payram.com/openclaw/accept-usdc-usdt-payments
- MCP endpoint: https://mcp.payram.com/mcp
- Skill-body on MCP (functional companion): https://mcp.payram.com/skills/payram-openclaw-integration.md