API tokens
Make ptk_ tokens for your servers and for AI agents over MCP, choose scopes and an organization, revoke them.
API Tokens (Integrate section) are for your servers and for the MCP server. A token acts as you, limited to the scopes and organization you pick, and never more than your role allows.
Make a token
Choose New Token (or Create > API Token).
Give it a name that says where it is used ("Website backend").
Pick Scopes:
Scope | Allows |
|---|---|
Read | Read everything you can see |
Write | Apps, plans, gateways, endpoints, payment links, subscriptions, replays |
Finance | Refunds, invoices, ledger adjustments and exports |
Admin | Platform administration (platform admins only) |
Pick the Organization to pin it to one organization (recommended for a server that serves one business), or "Every one I am in".
Pick the expiry: 90 days by default, a year, or never.
Save. The token (
ptk_followed by 43 characters) is shown once, with a Try It command and the MCP configuration block filled in. REM Payments keeps only a hash of it.
Tokens can only be made from the browser while signed in: a token cannot make other tokens.
Use it
Send it as Authorization: Bearer ptk_.... Example:
curl https://rempayments.com/api/me -H "Authorization: Bearer ptk_..."Revoke
The list shows each token's prefix, scopes, organization, last use and expiry, under Active and Revoked or Expired. Revoke stops a token at once; anything that uses it stops working. Revoke and replace a token the moment you think it leaked.
Last updated 18 Nov 2026