> For the complete documentation index, see [llms.txt](https://docs.blockatm.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockatm.net/readme.md).

# README

BlockATM is the world's first decentralized payment protocol based on blockchain smart contract technology, providing businesses with a secure, self-custodial cryptocurrency payment solution.

## Core Value

{% hint style="info" %}
**Decentralized Self-Custody**: You have complete control over your assets. Funds are stored in smart contracts on the blockchain, and only your designated signature address can withdraw assets. BlockATM cannot access or control your funds.
{% endhint %}

| Feature                    | Description                                                               |
| -------------------------- | ------------------------------------------------------------------------- |
| 🔐 **Self-Custody**        | Smart contracts owned by enterprise, assets fully self-managed            |
| 🔗 **Permissionless**      | No amount limit, no time limit, no authorization required for withdrawals |
| 🌐 **Multi-Chain Support** | Supports TRON (TRC20), Ethereum (ERC20), Arbitrum (ARB20)                 |
| 💰 **Transparent Fees**    | Fixed fees, no hidden charges                                             |

## Products & Services

### Collection (Safepay)

Users pay to your smart contract by connecting their wallet or scanning a QR code, with funds directly transferred to your contract address.

[Learn about Safepay →](/collection/safepay.md)

### Payout (Batch Payout)

Batch payout cryptocurrency to users, supporting both balance mode and allowance mode.

[Learn about Batch Payout →](/payout/batch-payout.md)

## Quick Integration

| Integration Method | Best For                            | Integration Time |
| ------------------ | ----------------------------------- | ---------------- |
| **Widget SDK**     | Quick cashier integration           | 30 minutes       |
| **Open API**       | Deep customization, full features   | 2-4 hours        |
| **Webhook**        | Receive payment event notifications | 1 hour           |

[View integration options →](/widget-sdk/widget-sdk.md)

## Fee Structure

| Type                        | Fee               |
| --------------------------- | ----------------- |
| Smart Contract Creation     | 200 USD/contract  |
| Collection (Wallet Connect) | 2 USD/transaction |
| Collection (Scan Payment)   | 0.4%/transaction  |
| Payout                      | 1 USD/transaction |

[View detailed fees →](/collection/fees.md)

## Changelog

| Version | Date       | Description                          |
| ------- | ---------- | ------------------------------------ |
| V2.3.0  | 2026-01-13 | Launched allowance management mode   |
| V2.2.0  | 2025-10-15 | Support for Ethereum/Tron withdrawal |
| V2.1.0  | 2025-06-10 | Initial version                      |

[View complete changelog →](/changelog/changelog.md)

***

## Need Help?

* 💬 Telegram: <https://t.me/blockatm2023>
* 📧 Email: support\@blockatm
* 📖 [FAQ](/faq/faq.md)
* 🔧 [Integration Guide](/integration-guide/collect-guide.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.blockatm.net/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.