Skip to main content
RaaS (Remittance-as-a-Service) exposes REST APIs your backend calls to onboard users, manage funding methods, and run Ask (request money) flows. You authenticate with a tenant api_key and, for user-scoped routes, a userToken issued by the platform.

​
How a typical Ask flow works

1

Get credentials

Obtain a sandbox api_key and confirm your base URL with Leap (see Testing & sandbox).
2

Resolve or create the user

Call getUserTokenV2 with phone or email; use registerUserV2 when the user does not exist yet.
3

Model funding and execute

Create contacts, add cards or UBN accounts, then call requestV2 / related operation endpoints for your corridor.
4

Go live

Swap base URLs and keys for production, complete security review (no secrets in clients), and register webhooks if you consume events.

​
Core concepts

The api_key identifies your tenant on every request. userToken scopes routes to one end user and is obtained from auth endpoints—never log or expose it in browsers.
Sandboxes use non-production hosts (for example https://raas-partner-cv.nomas.cash/v1). Your contract may use a different hostname; confirm with your integration contact.
API Reference is generated from swagger-partner.json. Widget and Client Interfaces specs live in separate tabs and describe optional or partner-implemented surfaces.

​
Next steps

Quickstart

Make your first authenticated calls in minutes.

Authentication

Headers, errors, and safe handling of credentials.

API overview

mTLS, happy path, and common HTTP errors.

Testing & sandbox

Base URLs, sample cards, and integration tips.

​
Environments

EnvironmentExample REST base URLNotes
Sandbox / CVhttps://raas-partner-cv.nomas.cash/v1Illustrative; your tenant may differ.
mTLS (same API)https://mtls-partner-cv.nomas.cash/v1Send client certificate data as required by your integration.
Do not use production API keys or user data in development tools, shared sandboxes, or source control.