PayRam MCP — Sovereign Crypto Payments for Agents & Humans setup

9 min read Original article ↗

Self-Hosted · No Signup · Permissionless

Own Your
Payment Stack.
Forever.

The world's first self-hosted stablecoin payment gateway with MCP integration. No signup. No KYC. No middleman. Deploy in 10 minutes. Built for humans and autonomous agents.

agent_config.json



{
  "mcpServers": {
    "payram": {
      "url": "http://mcp.payram.com"
    }
  }
}

🔑

No Keys. No Accounts. No Permission.

Other gateways require signup, API keys, KYC verification, and ongoing compliance reviews that can revoke your access at any time. PayRam deploys on your server. There is no account to create and no authority that can disable it. Your agent's payment capabilities are permanent and sovereign.

🤖

MCP-Native Agent Integration

PayRam ships a production MCP server that exposes payment tools directly to any MCP-aware client — Claude, Copilot, custom agents, n8n workflows. Tools include create-payee, send-payment, get-balance, generate-invoice, and test-connection. Your agent discovers capabilities automatically via the MCP handshake.

🛡️

Identity Isolation vs x402

In x402, every HTTP payment call inherently exposes client metadata: IP addresses, request headers, timestamps, and wallet signatures — creating traceable patterns that link web2 identity to on-chain activity. With PayRam, your agent generates unique deposit addresses and monitors deposits server-side. The payer and the infrastructure never touch a third-party facilitator. Complete identity isolation.

⛓️

Multi-Chain, Stablecoin-Native

While BTCPay Server requires complex plugins for non-Bitcoin assets, PayRam supports USDT/USDC natively across Ethereum, Base, Polygon, Tron, and TON — the chains where real commercial volume flows. Bitcoin is also supported. Agents can specify chain preference per transaction.

Integrate With Your Store in Minutes

Drop PayRam into any stack — Express, Next.js, FastAPI, Laravel, Go, Spring Boot. The MCP server generates ready-to-use payment routes, status-checking endpoints, and webhook handlers for your framework. Minutes to integrate, not weeks.

🔔

Webhooks, Deposit Status & Payouts

Real-time deposit detection with automatic webhook callbacks on payment confirmation. Track payout status, monitor the full payment lifecycle, and get notified at every stage — from invoice creation through settlement. Your agent or backend stays in sync without polling.

🧠

The Skill Every Agent (and Builder) Needs to Master

The internet is entering its payments era. Protocols like x402 are making HTTP-native payments a reality. But protocols need infrastructure. PayRam is to crypto payments what WordPress is to web publishing — neutral, self-hosted infrastructure that you own and operate permanently. Whether you're building an AI agent marketplace, a SaaS platform with embedded payments, or an autonomous commerce system, mastering self-hosted payment infrastructure isn't optional. It's the foundational skill for internet commerce in the agent age. PayRam is the fastest path to acquiring it.

01

Zero Signup

No accounts, no onboarding forms, no waiting for approval. Deploy the binary, connect your wallets, start accepting payments. Your agent or your team can be live in under 10 minutes.

02

Zero KYC

PayRam is infrastructure, not a financial institution. Like a web server, it doesn't ask who you are. Operator compliance is your responsibility — PayRam gives you the tools without the gatekeeping.

03

Full-Stack Ownership

Your server. Your database. Your SSL. Your cold wallets. Every byte of transaction data lives on infrastructure you control. No third party can access, freeze, or censor your payment operations.

04

No Middleman

Payments flow directly from payer to your smart contracts, then sweep to your cold wallet. No facilitator taking a cut. No intermediary holding your funds. Peer-to-peer by architecture, not by marketing.

05

Permissionless

Runs on public blockchains. No entity can revoke your ability to receive payments. Unlike hosted gateways, there's no terms-of-service that can be changed to exclude your industry overnight.

06

Human + Agent Native

Hosted checkout for human buyers. Headless API for programmatic flows. MCP server for autonomous agents. x402-compatible for HTTP-native payments. One infrastructure, every use case.

⚠ The x402 Privacy Gap

Every HTTP Call Leaks Identity

The x402 protocol embeds payment data directly into HTTP headers. This creates traceable links between web2 metadata and on-chain transactions.

  • Client IP address exposed to resource server on every request
  • Wallet signatures tied to HTTP session metadata (timestamps, user-agent)
  • Coinbase-hosted facilitator becomes a centralized chokepoint
  • EIP-3009 dependency limits token choice — currently USDC only
  • Running without a facilitator requires heavy blockchain infrastructure

✓ PayRam as Your x402 Layer

Sovereign Settlement, Total Isolation

PayRam acts as your self-hosted facilitator and settlement engine. You get x402 compatibility without the privacy tradeoffs.

  • Generate unique deposit addresses per transaction — no wallet signatures in HTTP
  • Your server handles verification — no external facilitator needed
  • Support USDT, USDC, BTC, and 20+ tokens — not just USDC
  • Smart contracts sweep funds to cold wallets — no keys on the server
  • Complete isolation between payer identity and merchant infrastructure
ClientHTTP GET /resource → Server returns 402 Payment Required
Client → Signs payment with wallet → X-PAYMENT header includes wallet + amount
Server → Sends to Coinbase Facilitator for verification ← 
Result: Client IP + wallet + timestamp + resource = 


Agent  → Calls PayRam MCP: create_payment → Gets unique deposit address
Payer  → Sends stablecoin to deposit address → 
PayRam → Detects deposit, confirms, triggers webhook → 
PayRam → Smart contract sweeps to cold wallet → 
Result: Payer sees only a deposit address. No facilitator. No identity linkage.

Q1 Do you need to own your payment infrastructure, or is renting acceptable?

→ I need to own it

You need a self-hosted solution. Hosted gateways (Stripe, Coinbase Commerce, NOWPayments) can change terms, freeze funds, or shut you down. Continue to Q2.

→ Renting is fine

Consider hosted options: Coinbase Commerce for simple crypto, NOWPayments for multi-coin, or Stripe for fiat + limited crypto. Accept the tradeoffs of third-party dependency.

Q2 Are stablecoins (USDT/USDC) your primary payment currency?

→ Yes, stablecoins first

PayRam is stablecoin-native. It supports USDT/USDC on EVM, Tron, and TON out of the box — no plugins needed. BTCPay Server requires complex third-party integrations for stablecoin support. Continue to Q3.

→ Bitcoin only

BTCPay Server is excellent for Bitcoin-only use cases. It pioneered self-hosted Bitcoin payments and has a mature Lightning Network integration. PayRam also supports BTC but is optimized for stablecoin-first workflows.

Q3 Do AI agents or automated systems need to initiate or manage payments?

→ Yes, agent-driven payments

PayRam + MCP is purpose-built for this. Agents discover payment tools via the MCP handshake. Headless APIs support programmatic flows. No human-in-the-loop required for standard operations. BTCPay has no MCP integration. x402 alone exposes client identity.

→ Humans only

PayRam's hosted checkout works beautifully for human buyers. But if you don't need agent capabilities, BTCPay Server is also a strong choice for human-facing Bitcoin payments.

Q4 Are you in a "high-risk" industry (iGaming, adult, forex, crypto services)?

→ Yes

PayRam is built for you. No terms of service that excludes your industry. No compliance review that can revoke access. Permissionless architecture means nobody can shut your payments down. You handle your own compliance — PayRam provides the neutral infrastructure.

→ No, mainstream industry

You have more options, but the sovereignty argument still applies. Any hosted gateway can change policies. PayRam's self-hosted architecture means no platform risk — your payments can't be frozen or revoked.

Q5 Do you need to process payments without exposing your identity or your users' identity?

→ Privacy is critical

PayRam wins decisively. Unique deposit addresses per transaction, no third-party facilitator logging metadata, all data on your server. x402's HTTP-based flow creates identity graphs. Hosted gateways log everything.

→ Transparency is fine

Any solution works. But even transparent businesses benefit from data sovereignty — knowing that only you hold your transaction data, not a third party that could be breached or subpoenaed.

If You Answered "Yes" to Two or More → PayRam

Self-hosted. Stablecoin-native. Agent-ready. Privacy-first. Permissionless. Deploy in 10 minutes and own it forever.

Capability PayRam BTCPay Server NOWPayments x402 (Protocol)
Self-Hosted Full stack on your VPS Self-hosted Hosted SaaS ~ Server-side only
Stablecoin Native USDT/USDC first-class ~ Via plugins Multi-token ~ USDC only (EIP-3009)
No Signup / No KYC Deploy and go Self-managed Account required Wallet-based
MCP Integration Production MCP server None None Not applicable
Agent-Friendly API Headless + MCP ~ REST API ~ REST API HTTP-native
x402 Support As settlement layer No No Native
Privacy / Isolation No identity leakage Self-hosted data They hold data HTTP metadata exposed
Multi-Chain BTC, EVM, Tron, TON ~ BTC + limited alts 200+ coins ~ Base, Solana
Deploy Time ~10 minutes ~ 30–60 min Instant (hosted) ~ Varies
High-Risk Friendly Permissionless Permissionless Subject to ToS Open protocol
Cold Wallet Sweeps Smart contract policy ~ Manual N/A N/A

01

Deploy PayRam

For AI Agents (Automated): End-to-end setup with MCP auto-configuration. Ubuntu 22.04+, 8 CPU cores, 8GB RAM, 100GB SSD.

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/PayRam/payram-scripts/main/setup_payram_agents.sh)"

OR Manual Setup:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/PayRam/payram-scripts/main/setup_payram.sh)"

02

Register MCP Server

Add the PayRam MCP endpoint to your agent's configuration file. Works with Claude, Copilot, custom MCP clients, and n8n. (Auto-configured if using setup_payram_agents.sh)

{ "payram": { "url": "https://mcp.payram.com" } }

03

Start Accepting Payments

Your agent discovers tools automatically. Create invoices, monitor deposits, manage payouts — all via natural language or programmatic calls.

"Create a 50 USDC payment link on Base"

🤖 AI Agent Builders

Building agents that need to pay for APIs, data, or compute? PayRam's MCP server gives your agent autonomous payment capabilities without external dependencies or identity leakage.

🎰 iGaming & High-Risk Operators

Traditional processors reject you. Hosted gateways can freeze your funds. PayRam runs on your infrastructure — nobody can shut your payments down or change the rules on you.

🏗️ Payment Service Providers

White-label PayRam to offer stablecoin payment infrastructure to your own clients. Transform from a payment user into a payment service provider with complete infrastructure ownership.

🛒 E-Commerce & SaaS Platforms

Embed sovereign payments into your platform. Accept payments from 195+ countries without geographic restrictions or platform dependency.

🏦 Neo-Banks & Fintech

Build your payment infrastructure instead of renting it. Full data sovereignty, complete audit trails on your own database, and no dependency on third-party uptime or policy changes.

🌐 Marketplaces & Platforms

Multi-merchant settlement with on-chain reconciliation. Unique deposit addresses per seller, automated sweeps, and real-time analytics — all without trusting a middleman with your float.

"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."

— Siddharth Menon, Co-founder PayRam · Ex Co-founder WazirX (15M users)