# Projects

A **project** is one of your crypto products, kept apart from the others. If you run a
wallet app and a payment gateway, make one project for each. Every project has:

- **its own API key** — the key decides which project a request belongs to;
- **its own webhooks** — a project's events go to that project's endpoints only;
- **its own users** — a user is created in one project and belongs to it for good.

Your dashboard shows every project together, with a project picker on Users, Deposits,
Payouts and Swaps. Make projects and their keys under **Projects & API** in the dashboard.

## Nothing changes for an existing integration

Your account has always had one project, **Default**. It holds the key, webhooks and users
you already had, so an integration that worked yesterday works the same today. New
projects start empty: generate the project's key on its page, add its webhook, and create
its users with that key.

## What a key can see

A request made with a project's key reaches only that project:

| With a project's key | What you get |
| --- | --- |
| `POST /v1/users` | the user is created in this project |
| `GET /v1/users`, `/v1/deposits`, `/v1/withdrawals`, `/v1/swap/orders` | this project's rows only |
| A user of another project (`/v1/users/{id}/…`, a payout, a swap) | `404 user_not_found`, exactly as if it did not exist |
| `/v1/developer/webhooks` | this project's endpoints; a new one is added to this project |

**User ids are unique across all your projects.** Creating user `10482` with one project's
key when another project already has a user `10482` answers `409 user_id_taken`. That way
a user id names one person wherever it appears — in your records, in support, on a card.

## Cards follow their cardholder

A card belongs to the project of the user it is issued to. A project's key reaches only its
own cardholders, cards and card orders: one of another project answers `404`, as an unknown
one does. `GET /v1/cards`, `/v1/cards/holders` and `/v1/cards/orders` list the key's project
only; each row names its `project`. `card.*` webhooks go to the cardholder's project's
endpoints. Your own cards (My Cards) belong to every project.

Each project has its own card wallet on each programme. A project's customers' cards are
paid from that project's wallet, and a closed card's balance comes back to it. Open and fund
a project's wallet from Card Issuing with that project chosen; it has its own deposit
addresses. `GET /v1/cards/wallet` answers for the key's project. The wallets you had before
are your Default project's. Money does not move between wallets: fund each one directly.

## What every project shares

Some things belong to your account, not to a project:

- **Your own balance**, your own cards, your profit and the fees you set — one of each for
  the account. Any project's key may pay out from your own balance.
- **The card fees you set** — one schedule for the account.
- **Your team** and the dashboard login.

## When a project is on hold

Cryptoinfra can pause or suspend one project without touching your others. You are emailed
the reason, and the project's page in your dashboard shows it.

| Status | The project's key | Its users' money | Its webhooks |
| --- | --- | --- | --- |
| Paused | reads work; anything else answers `403 project_paused` | cannot be sent or swapped, from the API or the dashboard; its cards cannot be issued, loaded or closed (freezing still works) | still arrive |
| Suspended | every call answers `403 project_suspended` | cannot move; its cards cannot be issued, loaded or closed (freezing still works) | stop |

Your own balance, your own cards and your other projects keep working either way.

## Keys

A project's key is shown once, when you generate it, and we keep only a scrambled copy.
Generating a new one stops the old one at once; revoking stops it with nothing in its
place. Both take your authenticator code, and every owner is emailed. A project can have up
to one live key; you can have up to 10 projects.
