PayRam Helper MCP Server
REMOTE · MCP.PAYRAM.COM · 3 COMPONENTS · SCANNED AUG 3
Remote MCP server to integrate and validate self-hosted PayRam deployments.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 52 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3402 tokens (~63/item across 54 items; 52 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.payram.com
claude mcp add --transport http payram-payram-helper-mcp https://mcp.payram.com/mcp
[mcp_servers.payram-payram-helper-mcp] url = "https://mcp.payram.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"payram-payram-helper-mcp": {
"type": "remote",
"url": "https://mcp.payram.com/mcp",
"enabled": true
}
}
} openclaw mcp add payram-payram-helper-mcp --url https://mcp.payram.com/mcp --transport streamable-http
mcp_servers:
payram-payram-helper-mcp:
url: "https://mcp.payram.com/mcp" {
"mcpServers": {
"payram-payram-helper-mcp": {
"type": "http",
"url": "https://mcp.payram.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.payram.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.payram.com | CN=YR2,O=Let's Encrypt,C=US | 22 Jun 2026 | 20 Sept 2026 | RSA 2048 | SHA256-RSA | 56a9d28243feae2d5ded05790c6124fbb52 |
| SANs: mcp.payram.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.payram.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| payram.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.payram.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.payram.com/mcp | HTTPS enforced | 308 | https://mcp.payram.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
assess_payram_project Assess Payram readiness in an existing codebase ~28
Inspects dependency files, frameworks, and .env status to suggest the next integration actions.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| detectedFiles | array | — | — |
| envStatus | object | yes | — |
| frameworks | array | yes | — |
| packageManagers | array | yes | — |
| payramDependencies | array | yes | — |
| recommendedNextSteps | array | yes | — |
| summary | string | yes | — |
No examples provided.
check_node_sync Check Node Sync ~117
Per-chain node health verdict: healthy / lagging / unreachable / listener-down. Computes how old each RPC node’s last block is — any non-BTC chain older than 10 minutes (BTC: 90 minutes, since BTC blocks every ~10m) is flagged as lagging or not syncing. Also checks the chain’s listener worker. When something is wrong it names the exact remediation (usually restart_payram_worker). Read-only — run this first; restart second; re-run this ~60s after a restart to confirm recovery.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| chains | array | yes | — |
| healthy | boolean | yes | — |
| issues | array | yes | — |
| workers | array | yes | — |
| workersAvailable | boolean | yes | — |
No examples provided.
check_payment_readiness Check Payment Readiness ~89
Diagnoses what is NOT yet set up to accept payments, per blockchain: missing deposit wallet, chain/currency not enabled for the project, or a stopped listener worker. Read-only — reports gaps and points to the CLI for wallet setup; it does not create wallets itself.
| Name | Type | Req | Description |
|---|---|---|---|
| externalPlatformId | string | — | Project/platform ID to check currency enablement for (auto-resolved if omitted) |
| Name | Type | Req | Description |
|---|---|---|---|
| allReady | boolean | yes | — |
| chains | array | yes | — |
| projectId | string | yes | — |
| readyChains | array | yes | — |
No examples provided.
create_payment_link Create Payment Link ~146
Creates a PayRam checkout (payment) link and returns the hosted URL plus a reference_id. Authenticates with the Merchant API-Key (set PAYRAM_API_KEY). This WRITES — it creates a real payment request. The customer chooses the chain/currency on the hosted checkout. Poll status later with lookup_payment (or GET /api/v1/payment/reference/{reference_id}).
| Name | Type | Req | Description |
|---|---|---|---|
| amountInUSD | number | yes | Payment amount in USD (must be > 0) |
| customerEmail | string | yes | Customer email (required — the backend validates it as a non-empty email) |
| customerID | string | yes | Your internal customer identifier (sent as customerID, required) |
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | — | — |
| reference_id | string | yes | — |
| url | string | yes | — |
No examples provided.
explain_payment_flow Payment Flow Guide ~19
Describe how payments move from customer initiation through settlement.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| notes | string | — | — |
| sections | array | yes | — |
| title | string | yes | — |
No examples provided.
explain_payram_basics Payram Basics Overview ~26
Explain Payram's product pillars, architecture, payments, and payouts capabilities.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| notes | string | — | — |
| sections | array | yes | — |
| title | string | yes | — |
No examples provided.
explain_payram_concepts Core Payram Concepts ~22
Glossary-backed explanation of Payram terminology and constraints.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| notes | string | — | — |
| sections | array | yes | — |
| title | string | yes | — |
No examples provided.
explain_referral_flow Referral Flow Guide ~21
Detail the referrer/referee lifecycle and required APIs.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| notes | string | — | — |
| sections | array | yes | — |
| title | string | yes | — |
No examples provided.
explain_referrals_basics Referral Basics Overview ~24
Summarize how Payram referral campaigns are configured and managed.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| notes | string | — | — |
| sections | array | yes | — |
| title | string | yes | — |
No examples provided.
generate_env_template Generate Payram .env Template ~30
Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| envExample | string | yes | — |
| notes | string | — | — |
| title | string | yes | — |
| variables | array | yes | — |
No examples provided.
generate_mock_webhook_event Generate mock Payram webhook event ~64
Generates a snippet to send mock Payram webhook events to your local endpoint for testing.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | yes | Language/tool for the mock webhook request (curl for command-line testing) |
| status | string | yes | Payment status to simulate in the mock webhook event |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_payment_http_snippet Generate HTTP payment snippet ~42
Generates a raw HTTP sample for creating a Payram payment in the requested language.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | yes | Programming language for the HTTP payment creation snippet |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_payment_route_snippet Generate payment route snippet ~54
Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Web framework for the payment route handler (Express.js or Next.js) |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_payment_sdk_snippet Generate SDK payment snippet ~52
Generates backend code using the official Payram JS/TS SDK to create a payment.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Target framework for the SDK payment snippet. generic-http provides a framework-agnostic example. |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_payment_status_snippet Generate payment status snippet ~48
Generates backend code to query the status of a Payram payment.
| Name | Type | Req | Description |
|---|---|---|---|
| style | string | yes | Style of code snippet: sdk uses the Payram SDK, http uses raw HTTP requests |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_payout_recipient_flow_snippet Generate 3-step recipient payout flow snippet ~55
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_payout_sdk_snippet Generate payout SDK snippet ~44
Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Target framework for the payout SDK snippet |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_payout_status_snippet Generate payout status SDK snippet ~28
Generates backend code to query the status of a payout using the Payram SDK.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_referral_route_snippet Generate referral route snippet ~48
Generates a backend route such as /api/referrals/create for logging referral events.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Web framework for the referral route handler (Express.js or Next.js) |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_referral_sdk_snippet Generate referral SDK snippet ~44
Generates a backend route or service snippet to create a referral event using the Payram SDK.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Target framework for the referral SDK snippet |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_referral_status_snippet Generate referral status snippet ~49
Generates code to fetch referral progress, rewards, or status.
| Name | Type | Req | Description |
|---|---|---|---|
| style | string | yes | Style of code snippet: sdk uses the Payram SDK, backend-only shows direct API calls |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_referral_validation_snippet Generate referral validation snippet ~25
Generates a snippet to validate referral IDs, statuses, and eligibility.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_setup_checklist Generate Payram Setup Checklist ~28
Returns a step-by-step checklist of everything a merchant must configure to start using Payram.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| items | array | yes | — |
| notes | string | — | — |
| title | string | yes | — |
No examples provided.
generate_topup_integration_snippet Generate top-up wallet integration ~157
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? Use the checkout/plugin path instead.)
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | — | Server framework for the webhook handler + settle function. |
| part | string | — | Which piece to emit: 'schema' (ledger DDL), 'webhook' (cumulative-credit handler), 'settle' (atomic invoice debit), or 'all'. |
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | yes | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_webhook_event_router Generate Payram webhook event router ~27
Generates a backend event router that dispatches Payram webhook events to domain handlers.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
generate_webhook_handler Generate Payram webhook HTTP handler ~35
Generates backend code to handle Payram webhook HTTP requests.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Web framework for the webhook handler code |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
get_agent_setup_flow Get Agent Setup Flow ~75
Returns the step-by-step setup flow for deploying PayRam as an agent. Covers install, wallet creation, faucet funding, contract deployment, and first payment. Includes chain recommendations (ETH Sepolia for testnet, Base for mainnet), faucet URLs, card-to-crypto prerequisites, and status/recovery commands for interrupted sessions.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| markdown | string | yes | — |
| title | string | yes | — |
No examples provided.
get_daily_volume Get Daily Volume ~83
Returns the total payment volume for a given date, with breakdowns by network and currency. Only counts FILLED (completed) payments. Defaults to today if no date is specified.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | — | Date in YYYY-MM-DD format. Defaults to today (UTC). |
| externalPlatformId | string | — | Optional. Auto-discovered from your account if omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| byCurrency | array | yes | — |
| byNetwork | array | yes | — |
| date | string | yes | — |
| totalPayments | number | yes | — |
| totalVolumeUSD | number | yes | — |
No examples provided.
get_payment_summary Get Payment Summary ~50
Returns payment counts: total, open, closed, and cancelled. Useful for a quick overview of payment activity.
| Name | Type | Req | Description |
|---|---|---|---|
| externalPlatformId | string | — | Optional. Auto-discovered from your account if omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| cancelledCount | number | yes | — |
| closedCount | number | yes | — |
| openCount | number | yes | — |
| totalCount | number | yes | — |
No examples provided.
get_payram_doc_by_id Get Payram Doc By ID ~40
Returns the markdown for a Payram doc given its id, e.g. "features/payouts".
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | — |
| markdown | string | yes | — |
| path | string | yes | — |
| url | string | — | — |
No examples provided.
get_payram_links Payram Important Links ~20
Surface official documentation, website, and community links.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| notes | string | — | — |
| sections | array | yes | — |
| title | string | yes | — |
No examples provided.
get_referral_dashboard_guide Referral Dashboard Guide ~23
Explain how to embed and manage the referral dashboard experience.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| notes | string | — | — |
| sections | array | yes | — |
| title | string | yes | — |
No examples provided.
get_unswept_balances Get Unswept Balances ~108
Returns unswept (unsettled) balances across all wallets, broken down by blockchain and currency. Shows sweep readiness per entry (sweep, sweep_in_progress, sweep_not_allowed, no_balance) AND why stuck funds are stuck: lastSweepError (e.g. HOT_WALLET_LOW_GAS with the hot-wallet address to fund), pending SCW deployment, or missing cold wallet. Use this to answer "where is my money / why has it not swept".
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| balances | array | yes | — |
| totalWallets | number | yes | — |
No examples provided.
list_currencies List Supported Currencies ~64
Lists every blockchain currency PayRam supports on this node (chain code, network, currency code). Public endpoint — works with only PAYRAM_BASE_URL set, no API key or JWT required. Use this to discover valid blockchainCode/currencyCode values before creating payments or payouts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | — |
| currencies | array | yes | — |
No examples provided.
list_payram_docs List Payram Docs ~44
Lists the available Payram doc ids relative to docs/payram-docs-live. Optionally scope by a prefix such as "features".
| Name | Type | Req | Description |
|---|---|---|---|
| prefix | string | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | — |
| docs | array | yes | — |
| prefix | string | — | — |
No examples provided.
list_platforms List Platforms ~38
Lists all external platforms (projects) for the authenticated user. Use this to discover your platform ID, which other tools auto-resolve if omitted.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | — |
| platforms | array | yes | — |
No examples provided.
list_recipients List Payout Recipients ~55
Lists saved withdrawal recipients (payout beneficiaries). Use this to find a recipient ID for the 3-step payout flow, or to check whether a beneficiary is already OTP-verified (status "active") before creating a payout.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | — |
| recipients | array | yes | — |
No examples provided.
lookup_payment Lookup Payment ~94
Look up payments by transaction hash, email, reference ID, customer ID, or invoice ID. Returns up to 5 matching payments with full details.
| Name | Type | Req | Description |
|---|---|---|---|
| externalPlatformId | string | — | Optional. Auto-discovered from your account if omitted. |
| query | string | yes | Search query: transaction hash, email address, reference ID (UUID), customer ID, or invoice ID. The backend auto-detects the query type. |
| Name | Type | Req | Description |
|---|---|---|---|
| payments | array | yes | — |
| totalCount | number | yes | — |
No examples provided.
onboard_agent_setup Get Payram Agent Onboarding Guide ~28
Returns the complete autonomous agent setup guide for deploying Payram without any web UI or human interaction.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| markdown | string | yes | — |
| title | string | yes | — |
No examples provided.
payram_doctor Diagnose a PayRam setup (one call) ~134
Staged, read-only health diagnosis: server reachability -> merchant API key -> admin JWT -> payment readiness (wallets + listener workers). Returns ranked likely causes with exact fix commands for the first failing stage. Run this FIRST when anything PayRam-related fails.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | Merchant API key (per-project). Defaults to PAYRAM_API_KEY. Obtain headlessly: ./setup_payram_agents.sh ensure-api-key |
| baseUrl | string | — | PayRam server base URL. Defaults to PAYRAM_BASE_URL. The installer publishes on port 80 (http://localhost), not :8080. |
| Name | Type | Req | Description |
|---|---|---|---|
| failedStage | — | yes | First failing stage: reachability | api-key | jwt | readiness; null when healthy |
| findings | array | yes | — |
| healthy | boolean | yes | — |
| likelyCauses | array | yes | Ranked causes for the first failing stage |
| nextSteps | array | yes | — |
No examples provided.
prepare_payram_test Payram Test Readiness Checklist ~23
Confirm hosting, credentials, and environment variables before generating demo apps.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | — |
| notes | string | — | — |
| sections | array | yes | — |
| title | string | yes | — |
No examples provided.
restart_payram_worker Restart PayRam Worker ~169
REMEDIATION ACTION (write): restarts a blockchain listener worker via supervisor — the minimal fix when check_node_sync reports a chain as lagging or listener-down. Workflow: run check_node_sync first → restart the named worker → wait ~60s → run check_node_sync again to confirm recovery. A restart does NOT fix an unreachable RPC (fix the RPC config in the dashboard instead). Requires admin JWT with write_system_settings.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | — | Restart ALL workers. Use only when multiple chains are unhealthy. |
| worker | string | — | Worker to restart: a chain code ('BASE', 'ETH', 'BTC', 'TRX', 'POLYGON' → restarts that chain's listener) or a full worker name ('base-listener'). Omit when using all=true. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | — |
| restarted | string | yes | — |
No examples provided.
scaffold_payram_app Scaffold Payram Payments & Payouts App ~119
Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.
| Name | Type | Req | Description |
|---|---|---|---|
| appName | string | — | Name for the generated application. If not provided, defaults to payram-{framework}-starter |
| framework | string | yes | Web framework to use for scaffolding the application |
| includeWebhooks | boolean | — | Whether to include webhook handler code in the scaffolded application |
| language | string | yes | Programming language for the application (node for JavaScript/TypeScript) |
| Name | Type | Req | Description |
|---|---|---|---|
| appName | string | yes | — |
| files | array | yes | — |
| framework | string | yes | — |
| instructions | string | yes | — |
| language | string | yes | — |
No examples provided.
search_payments Search Payments ~344
Search and filter payments with full control over status, network, currency, dates, webhook status, and pagination. Returns a paginated list of matching payments.
| Name | Type | Req | Description |
|---|---|---|---|
| createdBy | array | — | Filter by creator type. |
| currency | array | — | Filter by currency code (e.g. USDC, USDT, BTC, ETH, TRX, CBBTC). |
| dateFrom | string | — | Start date filter (ISO 8601, e.g. 2024-01-01T00:00:00Z). |
| dateTo | string | — | End date filter (ISO 8601, e.g. 2024-12-31T23:59:59Z). |
| externalPlatformId | string | — | Optional. Auto-discovered from your account if omitted. |
| limit | integer | — | Number of results per page. Defaults to 50. |
| network | array | — | Filter by blockchain network (e.g. BTC, ETH, TRX, BASE, POLYGON). |
| offset | integer | — | Pagination offset. Defaults to 0. |
| paymentStatus | array | — | Filter by payment status (FILLED = completed). |
| query | string | — | Free-text search: tx hash, email, reference ID, customer ID, or invoice ID. |
| sortBy | string | — | Sort field. Valid: created_at, updated_at, payment_status, currency, network, block_id, from_address, to_address, invoice_id, reference_id, customer_id, email, created_by. |
| sortDirection | string | — | Sort direction. Defaults to DESC. |
| webhookStatus | array | — | Filter by webhook delivery status. |
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | yes | — |
| offset | number | yes | — |
| payments | array | yes | — |
| showing | number | yes | — |
| totalCount | number | yes | — |
No examples provided.
snippet_express_payment_route Express create-payment route snippet ~28
Returns an Express router that posts to Payram's /api/v1/payment endpoint.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
snippet_fastapi_payment_route FastAPI create-payment route snippet ~26
Returns a FastAPI handler that calls Payram's create-payment HTTP API.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
snippet_go_payment_handler Go (Gin) create-payment route snippet ~28
Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
snippet_laravel_payment_route Laravel create-payment route snippet ~29
Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
snippet_nextjs_payment_route Next.js create-payment route snippet ~29
Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.
snippet_spring_payment_controller Spring Boot create-payment controller snippet ~28
Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object | yes | — |
| notes | string | — | — |
| snippet | string | yes | — |
| title | string | yes | — |
No examples provided.