Overview
The NAS card-issuing API lets your app and backend issue NAS cards to your own customers. You create the customer's account, verify them, issue a virtual or physical card, fund it, and read what they spend. NAS handles the card programme behind it.
This site has two parts. The guides explain how things work and in what order. The API reference lists every call, field and error. The same definition is available as an OpenAPI file for code generators and API clients.
How the account model works
Everything you create hangs off your own account.
Your client (the credentials NAS issues to you)
└── Your programme account
└── Customer account (one per customer, verified once)
├── Cardholder (the person named on the cards)
│ └── Cards (virtual or physical)
└── Wallets (deposit addresses and balances)
- Client. The credentials NAS issues to you: a client id, and the list of IP addresses your calls come from. Each client can see only its own accounts, cardholders and cards.
- Account. Holds balances, wallets and verification state. Every call that touches money or cards names an
accountId. - Cardholder. The person a card is issued to. A cardholder must be verified before a card can be issued.
- Card. A virtual or physical card on a card BIN. A BIN is a card product: it fixes the network, currency and whether physical cards are available.
What you can do
| Step | What it does | Guide |
|---|---|---|
| Authenticate | Exchange your client id for a short-lived access token. | Authentication |
| Verify a customer | Upload ID images, submit KYC, read the result. | KYC |
| Fund | Take deposits into wallets, convert, and put money on cards. | Wallets and funding |
| Issue cards | Create, freeze, limit and close cards. | Cards |
| Show card details | Display the number and security code without handling them. | Card details |
| Order plastic | Order, ship and activate physical cards. | Physical cards |
| Read spend | List transactions and reconcile. | Transactions |
| React to events | Receive signed webhooks. | Webhooks |
What the API does not do
These limits are deliberate. They protect your programme as well as ours.
- Money moves in only. No call sends funds to an external address. You can take deposits, convert inside your own wallets, and move money between your wallet, your cards and your budgets. Withdrawals are a request to NAS: see Wallets and funding.
- Card data is never returned as API data. There is no call that returns a full card number, expiry date or security code, and none that reads a PIN. You show card details with a secure display: see Card details.
- Your client sees only its own data. A call that names an account or resource that is not yours is refused.
From sandbox to production
You build and test in the sandbox, then NAS opens production for you.
- NAS issues sandbox credentials. See Environments.
- You follow the Quick start and build against
https://sandbox-api.nas.cards. - You test the flows you will use with the sandbox simulators.
- You work through the going live checklist, and NAS issues production credentials.
Sandbox and production share no credentials, data or hostnames. A sandbox key never works on production, and a production key never works on the sandbox.
Where to go next
- New here? Start with the Quick start.
- Stuck on a response? See Errors.
- Questions about limits or retries? See Idempotency, pagination and limits.