Skip to content

Funding with GRAM

The asset, your deposit address, what is safe to send, and when a deposit is credited.

Sandbox: test money only. No request moves real money.

Fund your account with crypto. Once your deposit is verified, your available balance is updated. The one asset that funds it is native GRAM, on the TON network. Each verified deposit becomes credits at the rate we record at the moment of crediting. Credit is never instant: it waits for the network and for two independent sources. In the sandbox the same requests work with simulated deposits.

Availability: Available. Live and verified in production.

What GRAM is

Gram (GRAM) is the native coin of the TON network. It was called Toncoin (TON) until 15 June 2026, when it was renamed. The coin itself did not change: nothing was swapped, bridged or migrated, and the network is still TON.

GRAM is never a token. Tokens with names like Gram exist on TON and on other networks, and none of them is GRAM. Only the native coin, sent on the TON network, can fund a balance.

Your deposit address

Take your address only from your dashboard or the API. Your deposit address is the one your own dashboard shows under Funding, and the one GET /funding/deposit-address returns to your own key. These pages never print one. An address given to you as ours in an email, a chat, a document or a search result is not ours. Nobody ever needs to claim GRAM or migrate TON: a site, bot or message that asks you to is a scam.

GET /funding/deposit-address returns your address, allocated on the first request and never changed. Your dashboard shows the same one.

  • One address per organisation. The server allocates it automatically; no person assigns it.
  • The server computes the address, then checks it independently before showing it. Until then state is preparing and address is null: read it again later.
  • The address does not change, and nobody can edit it.
  • It is shown in its non-bounceable form, which begins UQ on the TON network and 0Q on the test network. Send to it exactly as shown.

minimum_nanogram is the smallest deposit that is credited, confirmation says when one is credited, and warnings are to be shown to whoever sends. Copy the address from the API or your dashboard each time: an address in an email, a chat or a document may have been changed on the way.

What the request answers depends on where your workspace stands. The server decides each case, and your dashboard shows the same answer:

Where your workspace stands`GET /funding/deposit-address`Your dashboard, under Funding
Sandbox200. network is TON testnet, and warnings opens by saying so. Real GRAM sent to a sandbox address is never credited and may not be recoverable.Add test funds, and a simulated deposit. No real coin is asked for.
Live, the organisation active and allowed to receive GRAM200. state is active, network is TON, and address is your own address.The address, with its QR code, the minimum and the warnings.
The address is allocated and still being checked200. state is preparing and address is null. Read it again later, and send nothing until it is shown.Being prepared. No address is shown.
Live, the organisation not active yet, or suspended, closed or rejected, or not allowed to receive GRAM403 account_restricted. No address is allocated, and a retry changes nothing.Funding is not available in Live yet, with a link to Go live. No address is shown.
GRAM funding is switched off for the environment, or cannot allocate an address right now503 service_unavailable with Retry-After, or 429 rate_limited with Retry-After. Wait, then read it again.No address is shown until the read succeeds.
Code for Your deposit address
GET /v1/funding/deposit-addressSandbox, test key
// npm install axiosimport axios from 'axios';try {  const { status, data: address } = await axios.get(    'https://sandbox-api.nasfampay.com/v1/funding/deposit-address',    {      headers: {        Authorization: `Bearer ${process.env.NASFAM_SANDBOX_KEY}`,      },    },  );  console.log(status, address);} catch (error) {  if (!axios.isAxiosError(error) || !error.response) throw error;  const problem = error.response.data;  throw new Error(`${problem.status} ${problem.code}: ${problem.title} (request ${problem.request_id})`);}

Sending a deposit

  1. Send native GRAM, on the TON network, to your address exactly as shown.
  2. Send at least 1 GRAM. A smaller amount is recorded but not credited. minimum_nanogram gives the same figure.
  3. Your wallet charges its own network fee to send. On our side nothing is deducted: the amount credited is exactly the amount that arrived at your address, and Nasfam Business pays the network fees of moving it on.
  4. On Live, your dashboard may first ask who holds the account, and it shows your address only once funding is available to your organisation. A deposit that a limit or a check does not allow is held, never refused; see Deposit states.

Network safety

A blockchain transfer cannot be recalled once it is sent. Check the network and the asset before you send:

What you sendWhat happens
Native GRAM on TON, at least the minimum, to your address as shownCredited once the network has finalised it and two sources agree.
Native GRAM on TON, less than the minimumRecorded on your address, never credited automatically.
Any token, including one named GRAM, or an NFTNot credited. It is recorded for review, and it may not be recoverable.
GRAM on another network, a wrapped GRAM, or test coinsIt never reaches your address on TON, and it may not be recoverable.
GRAM sent as bounceable, to the address in a form beginning EQThe network may return it to the wallet that sent it. Nothing is credited; send it again to the address as shown.

When a deposit is credited

A deposit is credited once the TON network has finalised its transaction and two independent sources report the same transaction, with the same amount, to the same address. Seeing a transaction is not enough: until both conditions hold, the deposit is confirming and your balance does not change. These pages promise no time for it. However many times a deposit is seen, it is credited once.

Deposit states

GET /funding/deposits lists your deposits, newest first, each with its amount_nanogram, tx_hash, network and status. deposit.confirmed is raised once a deposit is confirmed, before it is booked, and no event follows its later states, so read this list. conversion records the rate and the credits once a deposit has become credits. Tolerate a status you do not know.

StatusWhat it meansYour money
confirmingSeen, not yet final, or not yet confirmed by both sources.Not on your balance yet.
creditedFinal, confirmed and added to your balance.Available to spend.
on_holdReceived, and not yet credited: above a limit of your account, or held by a check. hold_reason says why.Shown as on hold, and not spendable until it is released.
needs_attentionCould not be credited automatically: below the minimum, a token, or the two sources disagree.Recorded on your address, not on your balance.

A deposit is never refused because of a limit: it is held, hold_reason carries its code, and your dashboard says in plain words what it waits on. One waiting on a fresh GRAM price or on the daily limit is credited automatically once that allows it; any other hold is reviewed by our team. A deposit that needs attention is reviewed as an exception: it may be placed on hold, or returned to the address it came from. Nothing is returned automatically.

Code for Deposit states
GET /v1/funding/depositsSandbox, test key
// npm install axiosimport axios from 'axios';try {  const { status, data: deposits } = await axios.get(    'https://sandbox-api.nasfampay.com/v1/funding/deposits',    {      headers: {        Authorization: `Bearer ${process.env.NASFAM_SANDBOX_KEY}`,      },    },  );  console.log(status, deposits);} catch (error) {  if (!axios.isAxiosError(error) || !error.response) throw error;  const problem = error.response.data;  throw new Error(`${problem.status} ${problem.code}: ${problem.title} (request ${problem.request_id})`);}

Uncredited deposits

Read status and hold_reason on GET /funding/deposits, and do not send the amount again to find out. See Network safety for what never reaches an address.

A deposit that is on_hold or needs_attention is recorded, not lost. Your dashboard shows it with its reference, the deposit's id, and a link to support: quote that reference, and never send the amount again to have it credited.

Spending your balance

Credits pay for orders, and cannot be withdrawn or transferred. Neither the dashboard nor the API can send a balance out. Fund what you plan to spend.

What your balance is, and how a deposit becomes USD credits, is in Balances and reference rates. What an order costs is in Pricing and costs.

In the sandbox

POST /sandbox/funding/deposits simulates a deposit to your address: no network, no coins, and it can never reach a real balance. Read your address first. It is judged by the same rules as a real deposit, so one below the minimum needs attention and is not credited. It takes up to 1,000 GRAM per request, and an Idempotency-Key: a retry returns the original deposit and credits nothing.

To pay for a test order without a deposit, use Add test funds; see Create a test order.

Code for In the sandbox
POST /v1/sandbox/funding/depositsSandbox, test key
// npm install axiosimport axios from 'axios';// One key per purchase: make it once, keep it with the purchase, and send the same key on every retry.const idempotencyKey = process.env.IDEMPOTENCY_KEY;if (!idempotencyKey) throw new Error('Set IDEMPOTENCY_KEY once for this purchase (a new UUID) and keep it for every retry');try {  const { status, data: deposit } = await axios.post(    'https://sandbox-api.nasfampay.com/v1/sandbox/funding/deposits',    { amount_nanogram: '5000000000' },    {      headers: {        Authorization: `Bearer ${process.env.NASFAM_SANDBOX_KEY}`,        'Idempotency-Key': idempotencyKey,      },    },  );  console.log(status, deposit);} catch (error) {  if (!axios.isAxiosError(error) || !error.response) throw error;  const problem = error.response.data;  throw new Error(`${problem.status} ${problem.code}: ${problem.title} (request ${problem.request_id})`);}

Common mistakes

  • Sending a token named GRAM. Only the native coin funds a balance. A token is never credited.
  • Sending on another network. GRAM on any network but TON never reaches your address.
  • Copying the address from a message. Copy it from your dashboard each time, and check it on your wallet before you send.
  • Sending less than the minimum. It is recorded and not credited.
  • Funding more than you will spend. Credits cannot be withdrawn or transferred.