Complete Live activation
How a workspace reaches Live: the four tiers, the automated checks, and what a restriction means.
Sandbox: test money only. No request moves real money.
Live access is obtained by activation: you activate Live from your dashboard, and the server checks your workspace and decides. Activation asks for a verified email, an authenticator and one completed Sandbox order. Once Live is active, you create Live keys there.
This page states what the contract and the design define and nothing more. The contract publishes no launch date, no pricing for live orders and no list of countries or payment methods, so these pages promise none.
How a workspace reaches Live
Sandbox and live are separate environments. Each has its own host, its own keys and its own data. A sandbox key never works on the live API, and a live key works only there.
Live is not a setting you change. It is an activation the server grants to a workspace, and it is designed to be self-service:
- Build and test in the sandbox, with a key you create yourself, and complete one Sandbox order.
- Activate Live from your dashboard: an Owner or an Admin sends it, after a sign-in within the last 5 minutes. It asks for a verified email, an authenticator and one completed Sandbox order, and shows what is left.
- The server runs its checks and answers.
- Once the workspace is active, create a live key there and fund it with GRAM.
- From then on, an order sent to the live host is real.
Nothing your code or your browser sends can make an account live. The contract has no operation for activation, and a request without a live key is refused on the live host. Nothing on this page promises that an account will be approved, or when.
From activation to your first real order
Once the server has activated your workspace, the rest is yours to do, in this order:
- Add real funds: the one way a Live balance is funded.
- Create a Live API key: only the scopes you need, kept on your server.
- Send real orders: a read that proves the key and the host, the Go Live readiness checklist, then your first Live order.
- Monitor orders and webhooks: your Live endpoint, the statuses that need you, and the daily reconciliation.
Tiers
| Tier | For | Asks for | Allows |
|---|---|---|---|
| Developer | Anyone, as an individual or a business | A verified email and a workspace | The sandbox: test keys, test money, test orders and test events. No real money. |
| Limited Live | Individuals, sole proprietors and registered businesses | Two-step sign-in; your legal name and date of birth, or your business's registered name and number; one automated identity check; sanctions screening; a funding source you control, a TON address or a declared exchange account | Live keys, a GRAM deposit address, and live orders of the products allowed, within low limits. |
| Verified Business | Registered businesses | Limited Live, plus an automated match in the business registry, with its directors and owners screened | Higher limits. |
| Enhanced Review | An account the automated checks cannot settle, or one that needs more than its tier's limits | What the case calls for, such as evidence of the source of funds | Limits set for the case, once people have reviewed it. |
Tiers are product tiers. Reaching one is not a finding that you are legally eligible for anything, and approval is never automatic for every account.
Limits follow the verified person or business, not the workspace: opening another workspace does not raise them. The figures are set by the server and shown in your dashboard; this documentation publishes none.
What each tier asks for in detail is set by the server's policy for your country and your account, so this page names no document, fee or country. No tier asks for an uploaded document as a matter of course: one is asked for only when an automated check cannot establish a fact.
Automated checks
- The server checks your request against its policy, a versioned set of rules, and records every decision with the version it used.
- The answer is one of four: approved, with a tier and its limits; one item needed, named, which you can supply; a review by people; or declined, with a reason you can read.
- When every check returns a clear result, the server decides without a person. People see only the exceptions.
- A check provider that does not answer is never a decline: the request waits and is checked again.
- Nothing in your browser or your code decides. The dashboard shows the server's answer.
Declare your country of residence or registration as it is. The checks compare it with what the identity check and, for a business, the registry find.
Restriction messages
When something stops your account at a step, the dashboard says what is needed, why it is needed, and what still works. No message asks you to contact support to activate.
| What you see | What it means | What still works |
|---|---|---|
| One item is needed | The item is named, with the reason for it: the law, a provider's rules, or our own safety check. Supply it from the message. | The sandbox, and any Live access you already have. |
| Live is not available where you are | Live is not offered in your country, because of international sanctions, or while a rule there is confirmed. | The sandbox. |
| A deposit is on hold | The amount held, the limit or check that holds it, and what releases it. | Everything else. |
| A review is needed | People must complete a review before Live can open. Some reviews cannot be explained in more detail. | The sandbox. |
On the API, a request the account may not make is refused with account_restricted, and kyb_status on GET /account shows the organisation's state.
Verification
The verification state of the organisation is kyb_status on GET /account. No event announces a change, so read it again when you need it.
In the sandbox it is sandbox_only for an organisation in good standing. In live it is the activation state, active once the organisation is activated. restricted, suspended and closed can appear in either. The contract does not describe the other states or the steps between them, so their meanings below follow their names.
| Verification state | Meaning |
|---|---|
| Sandbox onlysandbox_ | A sandbox organisation in good standing. No verification is recorded in the sandbox. |
| Draftdraft | Verification started, not yet submitted. |
| Submittedsubmitted | Submitted, waiting for review. |
| In reviewin_ | Being reviewed. |
| Needs infoneeds_ | Something more is needed from you. |
| Verifiedverified | Verified. |
| Activeactive | Activated for live. |
| Rejectedrejected | Not approved. |
| Restrictedrestricted | Restricted in what the account may do. |
| Suspendedsuspended | Suspended. |
| Closedclosed | Closed. |
Live keys
A live key exists only once your workspace is active on Live; see Create a Live API key.
Limits
GET /account returns the one limit the server keeps for the account, max_queued: the most orders that may be processing at once. Read it rather than hard-coding it; the sandbox value is not a promise for live. Rate limits are not in the account: each response names the buckets it drew on in RateLimit-Policy. Spending limits, the platform's and your own, are on GET /limits.
The limits of each Live tier come from the server and are shown in your dashboard; see Tiers.
First order checklist
The Go Live readiness checklist is the short list to make true before your first real order, and Your first Live order walks the order itself.
What you should see
Nothing on this page makes an account live. The state to watch is kyb_status:
{ "id": "org_ 01K7SAMP000000000000000090", "name": "Example Business Ltd", "environment": "sandbox", "kyb_ status": "sandbox_ only", "limits": { "max_ queued": 50 }}If it fails
| What you see | What to check |
|---|---|
key_environment_mismatch | A nbk_test_ key was sent to the live host, or a nbk_live_ key to the sandbox. Each key works on its own host only. |
| You are looking for an operation that makes an account live | There is none. You ask in your dashboard, and the server decides. |
| Your request for Live needs one more item | The dashboard names it and says why. Supply it there; the sandbox keeps working meanwhile. |
account_restricted | The account may not do this. Read kyb_status on GET /account, and the reason in your dashboard. |
| You are looking for supported countries or funding methods | The contract lists none. Live is designed to be funded with GRAM on the TON network; whether your country may activate Live is the server's policy, and your dashboard says where yours stands. |
| You are looking for the live price of an order | A price is the quote's, and a sandbox price is synthetic; see Pricing and costs. |
Next step
Live step 2 of 5: Add real funds. Fund your account with crypto, sent to your own deposit address. Your balance is updated once the deposit is verified.
Related concepts
- Authentication and keys: one key per environment.
- Funding with GRAM: how a Live balance is designed to be funded.
- Rate limits: how to back off.
