Environments
NAS runs two separate environments. Paths, request bodies and responses are the same in both. Everything else is separate.
| Sandbox | Production | |
|---|---|---|
| Base URL | https://sandbox-api.nas.cards | https://api.nas.cards |
| Paths | /open-api/v3/... | /open-api/v3/... |
| Credentials | Sandbox client id | Production client id |
| Data | Test data only | Real customers, real money |
| IP allow-list | Optional | Required. Calls from other addresses are refused. |
| Browser calls (CORS) | Allowed from https://docs.nas.cards only | Not allowed. Call from your backend. |
Simulators (/vcc/simulate/...) | Available | Not available |
| Webhook URL | https or http | https only |
| Request limits | Set per client | Set per client in your agreement |
| Physical cards | Ordering is not available. See Physical cards. | Available |
Never put a production credential in a browser, a mobile app or the Try it panel on this site. Try it calls the sandbox only.
What differs in the sandbox
- No real money. Funds in the sandbox are test funds. Deposits use test networks. See Wallets and funding.
- Simulators. You can simulate a card authorisation, a refund, a reversal and a KYC review. See Sandbox testing.
- Some flows are production only. Where a flow cannot be run in the sandbox, the guide says production only next to it.
- Fixed test data. The test data page lists what the sandbox is known to accept.
Calling the sandbox from the docs
The Try it panel on each reference page sends your call to the sandbox. Paste a sandbox access token into the panel. The token stays in your browser and is never sent to the docs host.
If your sandbox client has IP pinning switched on, the browser cannot call it from a different address. Use curl from a pinned address instead.
How production access is granted
NAS opens production for you by hand once you have finished sandbox testing.
- You complete the going live checklist and send NAS the results.
- NAS registers your production IP addresses and your https webhook URL.
- NAS issues your production client id. It is shown once, so store it in your secrets manager.
- You run the end-to-end check on production with one test cardholder.
NAS rotates a credential on request. Contact NAS support if you think a credential has been exposed.