Blockchain infrastructure for businesses
Each network writes its addresses, sends and confirms in its own way. Nasfam Business will bring payouts, address checks, screening and tracking under one integration, on the account and API your orders already use.
- BitcoinBegins with bc1, 1 or 3
- Ethereum0x followed by 40 hexadecimal characters
- BNB Smart Chain0x followed by 40 hexadecimal characters
- SolanaBase58, 32 to 44 characters
- Tron34 characters beginning with T
The same 0x address is well formed on Ethereum and on BNB Smart Chain, so the network you pay on is a check of its own.
Pay, check, screen and follow
Four services for a product that moves crypto. Crypto Payouts leads, and the others will work around each payout.
Crypto Payouts API
Will pay crypto wallets from your business account through one API, one payout at a time, with one status for each and a signed event when it changes.
Crypto Payouts is coming soon.
About Crypto PayoutsWallet Address Validation
Will check an address before you send to it, each check answering one question.
- Address format
- Network compatibility
- Token compatibility
A valid address is well formed. It says nothing about who holds the wallet.
Wallet Screening
Will check whether a wallet appears on sanctions or risk lists before you pay it.
- Risk screening
It needs a screening provider, and there is none yet.
Blockchain transaction tracking
Will follow each payout on its network until it is final, with a signed event at every change.
Part of Crypto Payouts
From request to final
Each payout will take the same four steps, whichever network it runs on.
Request
You will send the asset, the network, the amount, the address and your own reference, with an idempotency key.
Crypto Payouts API
Validation
The address will be checked against its network's rules before anything moves. Screening joins this step once a provider is in place.
Wallet Address Validation & Screening
Processing
The payout will be accepted, then sent on its network. Accepted is not final.
Crypto Payouts API
Tracking
It will be followed on its network until it is final, with a signed event at every change.
Blockchain transaction tracking
A payout is final when its network says so, never when it is accepted.
Start with the integration
There is nothing to integrate for these services today. Each will use the API keys, idempotency keys and signed events your orders use now, and the docs cover all three.
{ "asset": "eth", "network": "ethereum", "address": "0xabcdef0123456789abcdef0123456789abcdef01"}- Read the API docs
The docs home, where every guide and the reference begin.
- Authentication
One key per environment, sent on every request.
- Integration guides
From a new account to your first request, step by step.
- API reference
Every operation, its fields and its errors.
Controls on every request
Your Telegram Stars and Premium orders run on these today, and Crypto Payouts will use the same integration.
One request, one result
A retry with the same idempotency key returns the first result, never a second one.
IdempotencyA timeout is unknown, not failed
When an answer never arrives, the outcome is found before anything is sent again.
Failure recoveryHeld until it is known
An outcome that cannot be confirmed stays under review, with its amount held, until it is.
StatusesSigned events, read in order
Every change of status raises a signed event, numbered so your system reads it in order.
Webhooks
See the rules every request runs on.
Keys, safe retries, signed events and recovery, in the documentation.



