Skip to main content
Customers represent the people or businesses you move money for — senders, recipients, merchants, or internal entities. Every organisation gets a primary customer at signup (representing the organisation itself). Existing routes without a customer are attributed to this primary customer. Required scopes: api:read (list / get), api:write (create)

Why customers matter

  • Attach customerId to payment routes, payment links, and local fiat orders for per-counterparty tracking
  • Filter lists with ?customerId= — transactions, payment routes (+ deposits), collections, swaps, local fiat offramps/onramps, and all cNGN money lists
  • Reconcile by customer name in the transactions ledger

List customers

Response:

Get a customer

Replace {customerId} with the RemitFlex customer UUID from list or create.
Includes the cngn block when enablement has been started or completed (enabled, status, evmWallet, virtualAccount, syncedAt).

Create a customer

Dashboard

View and filter activity per customer at dashboard.remitflex.io. On the customer cNGN tab you can enable with BVN to create the Smart Wallet and NGN deposit account. Completion is webhook-first (cngn.customer.enabled).

Enable cNGN

Use the RemitFlex customer UUID from the list or create response as {customerId}. Use the BVN holder’s full legal name (first and last) on the customer — after KYC, RemitFlex only exposes StRails profile data when names match under a strict check.
See cNGN for fields, wallets, and webhooks.

API reference

List customers

GET /customers

Get customer

GET /customers/{customerId}

Create customer

POST /customers