PayRam

Start here to install PayRam on a VPS. Returns an ordered, personalised plan — prepare server → install → claim admin + set public URL → wallets (incl. Smart Bridge review) → API key + first payment link → hardening → store/app integration — with who runs each step (agent shell vs human/dashboard), exact commands, what success looks like, and hard stops that need the human (cold wallet, mainnet sp

Read-only diagnosis of a PayRam server by its public URL — works from the hosted MCP without credentials: reachability, health, TLS certificate, installed vs latest version, worker states. Optionally validates an API key without creating anything. Returns ranked likely causes and exact fixes for the first failing stage. Run this first when anything PayRam-related fails.

Something is not working? Describe the problem in plain words and/or paste the error or log text. Returns the known PayRam problems it matches, what each usually means, how to confirm it and the fix, plus which tool to use next. Needs no credentials and no access to the server; what you paste is not stored. Call with nothing to list known problems. For a live check of a running server use payram_d

Step-by-step procedures for changes to a running PayRam, each step marked agent vs human with hard stops: set_site_url, change_domain, ssl_setup, ssl_renewal_fix, firewall_ports, upgrade, backup, restore, add_chain, smart_bridge, mainnet_cutover, operator_setup, rotate_api_key, reset_test_install, shopify_connector, woocommerce_plugin, secure_analytics_mcp, install_failed, custom_port_or_proxy, ex

Exact, copy-paste recipes for day-2 operations and troubleshooting that YOU run against the merchant's PayRam API with credentials that stay on your machine: which endpoint, which credential (public / dashboard JWT / project API key), a curl+jq command, how to read the answer, and what not to do. Start with "connect". Tasks: connect, health, version_check, workers, restart_worker, node_sync, site_

Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.

Returns a step-by-step checklist of everything a merchant must configure to start using Payram.

Suggests a recommended backend folder/file structure for integrating Payram.

Returns the canonical PayRam headless-agent guide: agent CLI commands, env vars, merchant vs operator mode, wallet flows, adding chains, troubleshooting. Long (~11k tokens). For a short personalised plan use payram_setup_plan.

Generates backend code using the official Payram JS/TS SDK to create a payment.

Generates a raw HTTP sample for creating a Payram payment in the requested language.

Generates backend code to query the status of a Payram payment.

Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.

Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.

Returns an Express router that posts to Payram's /api/v1/payment endpoint.

Returns a FastAPI handler that calls Payram's create-payment HTTP API.

Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.

Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.

Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.

Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.

Generates backend code to query the status of a payout using the Payram SDK.

Generates the recommended OTP-verified payout flow: create recipient → validate OTP → create payout against the saved recipient. Use this for repeat beneficiaries; use generate_payout_sdk_snippet for one-off direct payouts.

Generates a backend route or service snippet to create a referral event using the Payram SDK.

Generates a snippet to validate referral IDs, statuses, and eligibility.

Generates code to fetch referral progress, rewards, or status.

Generates a backend route such as /api/referrals/create for logging referral events.

Generates backend code to handle Payram webhook HTTP requests.

Generates a backend event router that dispatches Payram webhook events to domain handlers.

Generates a snippet to send mock Payram webhook events to your local endpoint for testing.

For EXISTING apps: emits the recommended top-up wallet integration — ledger schema + cumulative-credit webhook handler + atomic invoice-settle function. Credits crypto payments to a user's balance first, then debits invoices from it, so over/under/late/duplicate payments become balance states, not payment exceptions. Pair with the payram-topup-wallet-integration skill. (New store with no users? Us

Explain Payram's product pillars, architecture, payments, and payouts capabilities.

Answer "is PayRam safe / trustworthy / audited?": why an agent can use it without holding secrets, the independent smart contract audit (what it covers and what it does not), and how to verify the report.

Surface official documentation, website, and community links.

Describe how payments move from customer initiation through settlement.

Glossary-backed explanation of Payram terminology and constraints.

Summarize how Payram referral campaigns are configured and managed.

Detail the referrer/referee lifecycle and required APIs.

Explain how to embed and manage the referral dashboard experience.

Confirm hosting, credentials, and environment variables before generating demo apps.

Returns the markdown for a Payram doc given its id, e.g. "features/payouts".

Lists the available Payram doc ids. Optionally scope by a prefix such as "features".

Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.

Deprecated: use payram_doctor, which does this and more. Read-only check that a PayRam server is reachable and healthy and, if an API key is supplied, that the key is accepted. Never creates payments.

Deprecated: use payram_setup_plan, which does this and lets you personalise it. Returns the default headless plan (testnet, USDC on Base).