NAS Card Issuing API
Issue and manage cards for your customers: onboard accounts and cardholders, issue virtual and physical cards, set spending controls, fund cards and budgets, and read transactions.
Environments
| Environment | Base URL | Notes |
|---|---|---|
| Production | https://api.nas.cards | Calls are accepted only from the IP addresses registered for your client. |
| Sandbox | https://sandbox-api.nas.cards | The IP allow-list is optional. Browser calls are allowed from https://docs.nas.cards only. |
Paths are the same in both environments and begin with /open-api/v3. Sandbox and production share no credentials, data or hosts. Operations tagged Testing exist only in the sandbox.
Authentication
- Ask for a one-time code with
GET /open-api/v3/oauth/authorize?clientId=<your client id>. - Exchange it with
POST /open-api/v3/oauth/access-tokenand the body{"clientId": "...", "code": "..."}. The answer holds anaccessToken, arefreshTokenand the token lifetime. - Send the token in the
x-access-tokenheader on every call. Renew it withPOST /open-api/v3/oauth/refresh-tokenand{"refreshToken": "..."}.
When a call is refused with code NB40102 (invalid access token), fetch a new token and retry once.
Responses
Every answer, success or failure, uses one envelope: {"code": "...", "message": "...", "data": ...}. Success has code 000000. Failures carry a code beginning with NB and a message written by NAS; the codes are listed under each error response. The code is a string. A code that is not listed here is still a real answer: use the HTTP status and the message, and quote the code, the time and the path when you contact NAS.
Idempotency
Calls that create something take an Idempotency-Key header, or a unique reference id in the body. Send the same value on a retry and the original result is returned instead of a duplicate.
Money in only
This API moves money in: deposits to your wallets, transfers between your wallet, cards and budgets, and conversions. It has no call that sends funds to an external address.
Card data
Full card numbers, expiry dates and security codes are not returned by any call. Use the card access token to show them in a secure display. PINs can be set but not read.
Authentication
- API Key: accessToken
The access token from the token exchange described in the API overview. Send it on every call.
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | x-access-token |