Automated crypto top-ups let a website record a transaction and credit the balance without an administrator checking manually. The basic flow is: create the payment request, watch the blockchain transaction, verify the number of confirmations and update the balance exactly once.
Because this feature deals directly with assets, roll it out in a test environment first, read the payment gateway's latest documentation and start with small amounts.
Before you integrate
- An account with a payment gateway supported by your CMSNT source code version.
- A wallet address on the correct currency and network, for example USDT on TRON (TRC20).
- Access to the top-up configuration in the Admin Panel.
- A second account or wallet for making test transactions.
Note: Sending assets on the wrong network can lose the funds. Always cross-check the currency, the network and the address before transacting.
Connect the payment gateway to the website
- 01
Create the service account
Register an account, complete any required verification and enable two-factor authentication if the provider supports it.
- 02
Add the receiving wallet address
Select the correct asset and network, then enter the receiving address. Re-check the first and last characters before saving.
- 03
Get the connection details
Copy the token or API key and the wallet details from the management page. Never share the token in a screenshot or a public repository.
- 04
Configure it in CMSNT
Go to the crypto top-up settings, enter the token, the wallet address and the related fields, then enable the payment method.
- 05
Send a test amount
Create a new top-up request, transfer a small amount exactly as instructed and follow the status until it has enough confirmations.
Rules for handling transactions safely
- Each blockchain transaction credits the balance only once, even if the webhook is sent repeatedly.
- Only credit when the amount, the asset type, the network and the receiving address all match.
- Wait for the number of confirmations the gateway's policy requires.
- Store the transaction hash, the timestamp and the receiving account for reconciliation.
- Set up alerts for failed transactions, underpayments and processing timeouts.
A checklist before opening it to customers
- Check the exchange rate, the fees and the minimum top-up amount in force.
- Test an exact payment, an underpayment and a repeated webhook.
- Make sure the token never appears in HTML, public logs or error messages.
- Write clear instructions about the network, confirmation times and the support channel.
- Prepare a manual process for when the provider or the blockchain is disrupted.
Operational notes
Service fees, supported networks and API procedures can change. Administrators should review the provider's official documentation periodically, monitor the operating balance, and never keep all assets in a hot wallet connected directly to the system.
