Skip to content

REM Payments

How to use REM Payments, screen by screen: from your first app and plan to refunds, credits and reports.

How to use REM Payments, screen by screen: from your first app and plan to refunds, credits and reports.

User guide

User guide overview

  • Getting started: Sign in with REM Auth, open your organization, add an app and a plan, connect a gateway and take a first test payment.

  • Organizations and your team: Team & Settings - members and their roles, invitations, billing details, tax rules and deleting an organization.

  • Apps and plans: Create an app, add plans with prices in several currencies, trials and setup fees, and use the Features, Credits and Integration tabs.

  • Changing a plan's price: Change Price & Features with an impact preview, choose who moves and when, see Price History, and retire, archive or delete plans safely.

  • Gateways: Connect Sandbox, Razorpay, Stripe, PayPal, PhonePe, Paytm, Cashfree or PayU with your own credentials, test the connection and set up the gateway's webhook.

  • Checkout and payment links: Checkout Sessions, payment links, the hosted payment page your buyers see, and how sessions end.

  • Customers: Who bought or was invoiced, how customers are created, and what a customer page shows.

  • Subscriptions: Recurring plans: statuses, who bills the renewals, cancel, pause, resume and renew now, and the Price Versions history.

  • Invoices: Automatic invoices for every paid checkout and renewal, manual invoices, mark paid, void, and the printable copy.

  • Payments and refunds: Every payment a gateway reported, its timeline, syncing with the gateway, and refunding all or part of a payment.

  • REM Credits: The one credits ledger for REM apps - how credits are granted from purchases, spent on AI actions, clawed back on refunds, and where you see them.

  • Webhooks: Endpoints that receive signed events, their deliveries and retries, and the inbound webhooks gateways send.

  • API tokens: Make ptk_ tokens for your servers and for AI agents over MCP, choose scopes and an organization, revoke them.

  • Ledger, reports and funnel: The dashboard, the append-only ledger, revenue reports and CSV exports, promotions and the purchase funnel.

Developer docs

Developer docs overview

  • Authentication and tokens: Publishable keys (pk_) for your site, API tokens (ptk_) for your server, scopes, organization pinning, CSRF and error answers.

  • Checkout sessions: Read the catalogue, open a checkout session, send the buyer to the hosted page, verify the result, and make payment links from your server.

  • Subscriptions and plan changes: Read and manage subscriptions over the API, price versions and version history, plan changes with an impact preview, retirement and entitlements.

  • Webhooks: Signed events REM Payments sends to your endpoints - the event list, the envelope, headers, verification in Python and Node, retries and replays.

  • REM Credits API: The /internal/v1 contract apps use to read balances, quote, hold, settle and release REM Credits, with examples.

  • Python SDK: rem_payments 0.2.0 - link an app with one token, open checkouts, read subscriptions, spend REM Credits and verify webhooks from Python.

  • MCP server: Connect Claude or any MCP client to REM Payments - 96 tools that do exactly what your ptk_ token may, with confirmation for risky changes.

Last updated 18 Nov 2026

REM Payments · REM Platforms Blog