Going live
Work through this checklist in the sandbox first. When every item is done, send the results to NAS. NAS then opens production for you.
Before you ask for production
Integration
- You get, store and renew tokens correctly. An
NB40102answer makes your client refresh and retry once. See Authentication. - Your calls come from fixed outbound IP addresses that you can give to NAS. See Environments.
- Every create call carries an
Idempotency-Keyor a unique reference, and retries reuse it. See Idempotency, pagination and limits. - You read
codeas text and handle eachNBcode on Errors. - You wait for
Retry-Afteron a429. - You page through lists with
limitandpage. - No sandbox-only call runs in production. The simulators do not exist there.
Webhooks
- Your endpoint is on https and answers
2xxwithin 10 seconds. - You verify
X-NAS-Signatureon the raw body and reject old timestamps. See Webhooks. - You save each event
idand ignore repeats. - You do not rely on event order.
- You do not log webhook secrets or the codes in
CARD.3DS.OTP. - You have seen each event type you rely on arrive at your endpoint in the sandbox.
- You catch up by reading the object again after an outage.
Customers and cards
- KYC works end to end, and you handle each result state on KYC, including
CANCELED. - You never send share tokens. You send real data and real images.
- Your app shows card details only through the secure display, and never stores them. See Card details.
- You told NAS the web domains where the secure display will load.
- You reconcile transactions from events and from a daily list call. See Transactions.
Money
- NAS has confirmed with you how your card account balance is funded.
- Your funding flow is money in only. You do not expect an API call to send funds out.
- Your withdrawal addresses are ready for NAS to whitelist, and NAS has your registered contact.
- You know your request limit. See Idempotency, pagination and limits.
What NAS does
- NAS reviews your results.
- NAS registers your production IP addresses and your https webhook URL.
- NAS issues your production client id and webhook secret. Each is shown once.
- NAS confirms your request limit.
End-to-end check in production
After NAS opens production, run one full pass with a single test cardholder that you control.
- Get a token from
https://api.nas.cards. - Verify the cardholder and create a card.
- Fund the card with a small amount, using the funding route NAS confirmed with you at onboarding. Skip this step until NAS has confirmed it.
- Open the card details through the secure display.
- Make one real purchase and check the transaction and its events.
- Freeze and unfreeze the card, then delete it.
- Check your records match the transaction list.
Keep this pass small. Production uses real money and real identity data.
After go-live
- Keep your webhook secret and client id in a secrets manager.
- Ask NAS to rotate a credential if you think it has leaked.
- Watch
429,5xxand webhook failures. Alert when they rise. - Read the changelog for changes to the API.