Skip to content

Add real funds

Fund your account with crypto, sent to your own deposit address. Your balance is updated once the deposit is verified.

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

In this step you add real funds to a workspace activated for Live, with crypto sent to your own deposit address. In the sandbox you can run every part of it with a simulated deposit.

Fund your account with crypto. Once your deposit is verified, your available balance is updated. Each verified deposit becomes credits at the rate we record at the moment of crediting.

What is supported

  • Network: TON.
  • Asset: Gram (GRAM), the native coin of TON, formerly Toncoin (TON).
  • Method: a deposit to the address of your own organisation.

No other asset is credited; see Networks and assets.

Read your address

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. Copy it each time, and check it on your wallet before you send.

A workspace has a Live address only once it is active in Live. In the sandbox the address is a test address: fund it with Add test funds or a simulated deposit, never with real GRAM. Funding with GRAM says what the request answers in every case.

Code for Read your 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})`);}

Follow the deposit

GET /funding/deposits lists each deposit with its status. It is confirming until the network has finalised it and two independent sources agree, then credited. Credit is never instant, and these pages promise no time for it. Funding with GRAM has every state and every rule.

What you should see

The deposit is credited, and GET /balance shows it as available. In the sandbox a simulated deposit answers like this:

Code for What you should see
A simulated deposit
JSON
201 CreatedSynthetic sandbox data
{  "object": "gram_deposit",  "id": "dep_01K7SAMP000000000000000090",  "status": "confirming",  "asset": "GRAM",  "amount_nanogram": "5000000000",  "network": "simulated",  "tx_hash": "0000000000000000000000000000000000000000000000000000000000000000",  "explorer_url": null,  "sender_masked": "0:000000...0000",  "observed_at": "2026-10-10T10:14:00.000Z",  "credited_at": null,  "hold_reason": null}

If it fails

What you seeWhat to check
service_unavailableGRAM funding is switched off for this environment. Wait the seconds in Retry-After, then read the address again.
account_restrictedThis workspace has no address yet: it is not active in Live, or it may not receive GRAM. No retry changes that. Your dashboard says Funding is not available in Live yet, and Go live shows what is left.
address is nullThe address is still preparing: the server has not finished checking it. Read it again later, and send nothing until it is shown.
A deposit stays confirmingThat is not a failure. Do not send the amount again.
A deposit is needs_attentionIt was below the minimum, was not native GRAM, or the sources disagree. It is recorded, and not on your balance. See Funding with GRAM.

Next step

Live step 3 of 5: Create a Live API key. The key that moves real money, once your workspace is activated for Live.