Skip to main content
Remitflex gives you programmable money movement over HTTPS. You create payment intents — collection routes, pay links, or local fiat orders — fund them, and read status from one ledger. Your integration never talks to blockchains, exchanges, or bank networks directly. You talk to Remitflex.

​
Mental model

Every product follows the same five steps:
  1. Authenticate with an API key (rmf_test_ / rmf_live_)
  2. Create a payment intent, optionally tied to a customer
  3. Fund — send crypto to a deposit address, or instruct your user to transfer to a bank account
  4. Track status until the order settles
  5. Reconcile via GET /v1/transactions — filter by customerId when needed

​
Core objects

​
Authentication layers

Dashboard: dashboard.remitflex.io API base: https://api.remitflex.io/v1

​
Products

​
Scopes

Secret API keys use api:read and/or api:write (write implies read). Publishable keys (rmf_pk_*) are embed-only (collections:read). See Authentication for key format and idempotency rules.

​
Limits

  • API keys — create and manage keys in the dashboard (JWT), not via the public API
  • Prefer one full-access secret key per environment until you need a read-only reporter
For push updates, see Webhooks.