Skip to content

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

https://rempayments.com/api

Interactive API reference (OpenAPI)

rempayments.com/api/docs, schema at /api/openapi.json

Public checkout API

https://rempayments.com/api/public/{publishable key}/...

Hosted checkout page

https://rempayments.com/pay/?s={checkout session id}

REM Credits API

https://rempayments.com/internal/v1 (reference at /internal/v1/docs)

MCP server

https://rempayments.com/mcp

Health

GET /api/healthz (checks the database; 503 when it is down)

Three rules

  1. Amounts are integers in minor units. 49900 INR is ₹499.00, 900 USD is $9.00. JPY has no minor unit. Never send floats.

  2. Never trust the browser for the outcome of a payment. Confirm on your server, by reading the session or by a signed webhook.

  3. Retries are safe. Send an Idempotency-Key header when you open checkouts; webhooks carry a stable delivery id; the REM Credits API is idempotent by key.

Pages

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

Developer docs · REM Platforms Blog