payram.com

Checks the /api/v1/payment endpoint on a Payram server using baseUrl and apiKey.

Staged, read-only health diagnosis: server reachability -> merchant API key -> admin JWT -> payment readiness (wallets + listener workers).

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.

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.

Inspects dependency files, frameworks, and .env status to suggest the next integration actions.

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

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.

Lists the available Payram doc ids relative to docs/payram-docs-live.

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 step-by-step setup flow for deploying PayRam as an agent.

Returns the complete autonomous agent setup guide for deploying Payram without any web UI or human interaction.

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

Lists all external platforms (projects) for the authenticated user.

Returns payment counts: total, open, closed, and cancelled.

Look up payments by transaction hash, email, reference ID, customer ID, or invoice ID.

Search and filter payments with full control over status, network, currency, dates, webhook status, and pagination.

Returns unswept (unsettled) balances across all wallets, broken down by blockchain and currency.

Returns the total payment volume for a given date, with breakdowns by network and currency.

Lists every blockchain currency PayRam supports on this node (chain code, network, currency code).

Lists saved withdrawal recipients (payout beneficiaries).

Creates a PayRam checkout (payment) link and returns the hosted URL plus a reference_id.

Per-chain node health verdict: healthy / lagging / unreachable / listener-down.

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.

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.