> For the complete documentation index, see [llms.txt](https://support.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.trybit.com/payments/static-wallets.md).
# Static Wallets
Learn how to accept cryptocurrency payments to a single address without creating a new invoice each time.
### What it is and how it differs from a regular invoice
**A static wallet** is a permanent address for accepting payments in a specific cryptocurrency, tied to a user. Unlike a regular invoice, which is created anew for each payment and is valid for a limited time, a static wallet exists permanently: the user can send any amount to it at any time — each one is converted into a successful balance top-up, without creating a new invoice or going to the payment page.
### Use cases
This solution works well for projects that involve topping up a user's internal balance — for example, iGaming projects, deposit-based platforms, or services with a prepaid balance.
### How it works
1. The user goes to top up their balance on the merchant's website.
2. A static wallet is created for them in the needed cryptocurrency (or already exists, if it was created earlier).
3. The user transfers an amount to the wallet address — manually or via QR code.
4. Any amount received in the currency tied to the wallet is automatically credited as a successful balance top-up — fees (service and transfer) are deducted automatically.
5. A POSTBACK notification is sent, and the user receives a successful-payment notification.
### One address for all transactions
A static wallet has one permanent address in one currency and network tied to it — all incoming payments to this address are processed the same way, without creating a separate invoice for each transaction.
### Managing static wallets
You can manage static wallets in the project settings, under "Static Wallets" — this same section also shows wallets created via the API.
To create one manually, choose the project, currency, and network, and specify an identifier — a unique number corresponding to the user in your system (3 to 200 characters).
### Creating static wallets via API
This method lets you create a static wallet with the specified parameters directly via the API, without using the dashboard interface.
To create a wallet, you pass: the shop identifier (shop\_id), the currency code (currency — static wallets aren't supported on the TON network), and a customer identifier (identify), which is later included in the payment postback in the order\_id field.
In response, the system returns the created wallet's data: the generated address for receiving funds, the wallet's unique identifier, and its status (active/inactive).
Funds received at such a wallet are automatically credited to the merchant's balance, net of all fees, with a postback notification sent — without creating a new invoice or going to the payment page.
Technical details on creating wallets via API are in the developer documentation at [docs.trybit.com](https://docs.trybit.com/).
{% hint style="success" %}
If you have any questions or need help, you can contact our support via chat on the website and in your personal account, as well as reach us on Telegram. Support contacts are listed [on our website](https://trybit.com/support).
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.trybit.com/payments/static-wallets.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
