Supported pairs
Which networks and assets a payout can be sent on, in each environment, and how to tell: the server says.
Sandbox: test money only. No request moves real money.
Sandbox. The payout operations are in the API's contract and built for the sandbox, where a payout is simulated and never a real transfer. Until Nasfam switches payouts on in an environment, every request there answers 503 payouts_unavailable and nothing is written or held. Live: not yet available.
Availability: Sandbox. Built for the sandbox, on synthetic money. Not live.
The pairs payouts know are the pairs GET /payout-networks lists, each with its status in the environment you ask. This list is the only source of the accepted asset and network values. This page names no network or asset, because a list in prose would go out of date.
The list
One row per pair, by network then asset:
| Field | Description |
|---|---|
| Assetasset · string · required | The asset the recipient receives, one GET /v1/payout-networks lists. Its issuer's own token on the named network, never a bridged one. |
| Networknetwork · string · required | The network the transfer is made on, one GET /v1/payout-networks lists. An address approved on one network authorises nothing on another. |
| Network namenetwork_ | The network's name, as people say it. |
| Statusstatus · string · required | planned (known, not payable here), sandbox (simulated on the sandbox host only, never a real transfer) or live (real transfers). |
| Decimalsdecimals · integer · required | The decimal places the asset has here. |
| Memo rulememo_ | required, optional or forbidden. |
| Token contracttoken_ | The issuer's token contract, jetton master or mint paid from here, or null where the issuer publishes none. |
| Token issuertoken_ | Who issues the token: Circle or Tether. |
| Finalityfinality · string · required | The rule that makes a payout completed here: evm_finalized_tag, tron_solidified, ton_masterchain_final or solana_finalized. |
Read the list when you build your form. A pair the server does not list is refused with network_not_supported.
curl "https:// sandbox-api. nasfampay. com/ v1/ payout-networks" \ -H "Authorization: Bearer $NASFAM_ SANDBOX_ KEY"Where each pair is payable
Offer a pair only where its status says it is payable in this environment:
| Status | What it means here |
|---|---|
| Plannedplanned | Known, not payable here. A payout on it is refused with network_not_supported. |
| Sandboxsandbox | Payable on the sandbox host only, simulated: never a real transfer. |
| Livelive | Real transfers. No pair is live yet. |
Memos
Some destinations need a text comment with the transfer, such as a shared exchange address. The row's memo_rule says what to send:
| Rule | What to send |
|---|---|
| Requiredrequired | Send a memo. A request without one is refused with memo_required. |
| Optionaloptional | Send a memo only if your recipient gave you one. |
| Forbiddenforbidden | Send no memo. A request with one is refused with memo_not_allowed. |
When a payout is final
The row's finality names the rule that makes a payout completed on that network, such as evm_finalized_tag: the block holding it is behind the network's finalized tag. Read the value the server sends; new rules may be added.
A token on each network
An asset means its issuer's own token on the named network, never a bridged one. The same asset on two networks is two different tokens, each with its own token_contract and decimals. An address approved on one network authorises nothing on another. Ask your recipient which network they expect, and never send on another.
Related guides
- Validate an address: check it for the pair you chose.
- Fees and limits: what a payout may charge and be.
- Crypto Payouts: how a payout works.
