Developer docs
The REM Payments REST API, hosted checkout, signed webhooks, the REM Credits API, the Python SDK and the MCP server.
Everything the REM Payments dashboard does is an HTTP API call, and you can make the same calls.
What | Address |
|---|---|
API base |
|
Interactive API reference (OpenAPI) | rempayments.com/api/docs, schema at |
Public checkout API |
|
Hosted checkout page |
|
REM Credits API |
|
MCP server |
|
Health |
|
Three rules
Amounts are integers in minor units.
49900INR is ₹499.00,900USD is $9.00. JPY has no minor unit. Never send floats.Never trust the browser for the outcome of a payment. Confirm on your server, by reading the session or by a signed webhook.
Retries are safe. Send an
Idempotency-Keyheader when you open checkouts; webhooks carry a stable delivery id; the REM Credits API is idempotent by key.
Pages
Authentication and tokens: publishable keys, API tokens, scopes, errors.
Checkout sessions: catalogue, open a checkout, hosted page, verify, payment links from your server.
Webhooks: events, envelope, signature verification in Python and Node, retries.
Sign-in to the dashboard goes through REM Auth; see the REM Auth developer docs if your app should sign people in the same way.
Last updated 18 Nov 2026