> For the complete documentation index, see [llms.txt](https://passimpay.gitbook.io/passimpay-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://passimpay.gitbook.io/passimpay-api/direct-deposits-usdt-trc20.md).

# Direct deposits (USDT TRC20)

Direct Deposit Mode to Static USDT TRC20 Address (Callback Enabled)

This mode allows you to accept deposits directly to your main (static) USDT TRC20 wallet without generating a new address for each payment.

How It Works

When you activate this option (via the toggle in your personal account), our system will send a callback notification to your endpoint every time funds are received on your main TRC20 address. You must implement your own logic for identifying the payer by generating unique amounts.

<img src="/files/hu5rlOno28Tu6ksUoYGG" alt="" data-size="original">

Two integration methods are available:

* Seamless H2H method (link to the method in the docs) – In this case, you need to make amounts unique on your side for each payment to recognize which customer the funds came from. For example, if two of your customers want to deposit 10 USDT, you generate an invoice for 10.001 for one and 10.002 for the other. We also recommend clearly stating in the form that the customer must send the exact amount shown, otherwise automatic crediting on your side will not occur.
* Our payment links method (link to the method in the docs) – In this case, the customer receives a payment link that already includes a unique amount. This method involves a redirect to our payment form, which can be branded to match your site if needed.

Key Features

* No network fee for deposits to the main address.
* No one-time addresses are used – funds go directly to your static wallet.
* H2H initialization by amount – you trigger the payment scenario based on a specific amount.
* Invoices can also be initialized from your side.
* All invoices in this mode are valid for only 24 hours and expire automatically after that.
* The wallet must first be linked to your platform in the PassimPay dashboard.
* orderId is not used (value is always 0).
* If you previously generated addresses for each user, funds received to those addresses will still be credited to you, but under standard processing terms (with a network fee for collection to your main address).

Important Limitations (AML and Transaction Safety)

* We cannot block "dirty" crypto. It is technically impossible to block or reverse a transaction on the TRC20 network.
* We perform AML checks and will alert you about potentially risky transactions in the support chats of your personal account. Responding to this information is your responsibility.
* A callback is sent for every incoming transaction to your main address, regardless of the amount.

Workflow

1. Enable the mode in your PassimPay platform settings (toggle: "Enable callback when funds are received on the main USDT TRC20 address").
2. Implement payer identification (e.g., unique amounts for each invoice).
3. Receive and process callbacks for each deposit to your main address.

⚠️ Important Note

This mode offers flexibility and saves on network fees but places the responsibility for payer identification and AML risk handling on you. PassimPay provides signals but cannot block transactions.

<br>