Skip to content
Nasfam Business

Appearance

Crypto Payouts API

Crypto Payouts will pay wallets in crypto through the same account and integration as your orders, with one status for every payout.Crypto Payouts is coming soon.

Example: one business balance with a route to each destination, BTC on Bitcoin, ETH on Ethereum, BNB on BNB Smart Chain, SOL on Solana, USDT on Tron (TRC-20) and GRAM on TON, and one payout at a time. Its request names the asset, the network, the amount, the destination address and a reference; the payout travels its route, and the activity shows it accepted, processing and ending as an example result. The figures and addresses are examples.

One business balance. Payouts across multiple blockchains.

Manage cryptocurrency payouts from one account, with one API for requests, tracking and status updates.

Destination wallets, each on its own network

  • BTCBitcoin

    bc1qexa…a8z62

  • ETHEthereum

    0xabcde…def01

  • BNBBNB Smart Chain

    0x12345…45678

  • SOLSolana

    ExampLe…11111

  • USDTTron (TRC-20)

    TExampL…7VqfX

  • GRAMTON

    UQAExam…1AG-a

These destinations are examples. Each network and asset will be named on this page before you can use it.

A payout is one request

It names the asset, the network, the amount, the destination address and your own reference, under an idempotency key, so a request sent twice pays once. The answer is the payout it created, accepted and not yet sent.

Illustrative: a payout request for BTC on Bitcoin, sent under an idempotency key with the asset, the network, the amount, the destination address and a reference. The answer is the payout it created, under the same reference, with the status accepted: recorded, and not yet sent.

Illustrative. The published request may name its fields differently.

From request to final result

Each payout will move through six steps, one at a time, and say where it stands at each.

  1. Request validation

    The asset, the network, the amount and the address will be checked against that network's rules.

  2. Funding check

    Your account will be checked for the amount, which is set aside for this payout before anything is sent.

  3. Processing under your key

    Only a request made with your API key, within what that key may do, will be processed, and only once.

  4. Blockchain submission

    The transfer will be sent to its network once. A late answer will be looked up, never sent again.

  5. Confirmation tracking

    The payout will be followed on its network as it confirms, until it is final.

  6. Final result

    Each payout will end final or failed. A payout that fails releases what was set aside for it.

Where you will follow each payout

In the places you already follow your orders, in the same words.

  • In your dashboard

    Each payout will be listed with its status, amount, destination and your reference, beside your orders.

  • By API

    You will look a payout up by its id or by your own reference.

  • By webhook

    A signed event will reach your endpoint each time a payout's status changes, as your order events do.

  • In your request logs

    Each payout request will be logged with its request id and the answer it got, as your order requests are.

How to begin

There is nothing to integrate today, and no network, asset, fee or date is published yet. Payouts will use the account, API keys and webhooks you set up for Telegram Stars and Premium, so begin there. The price will be on this page before you can request a payout.

Tell us how your business pays out.

It tells us which networks and uses to support first.