Manual checks still need evidence
Check network, token, address, exact amount and confirmations. Balance changes or screenshots alone do not identify an order.
Product comparison
Both can receive funds directly into your wallet. The difference is who checks payments, links orders and notifies your application. Choose based on volume, fulfillment and reconciliation needs.
| Aspect | Manual wallet collection | BoltUtil gateway |
|---|---|---|
| Funds | Merchant wallet | Configured merchant wallet |
| Payment checks | Staff check chain records individually | Automated order-rule checks |
| Business notification | Staff action or custom notification flow | Signed webhook to your server |
| Duplicates | Maintain your own review and delivery records | Order and delivery records aid review; your app still deduplicates |
| Differences | Collect evidence and review manually | Qualifying review records; member processing |
| Suitable for | Low volume with individual checks | Ongoing reconciliation and system fulfillment |
Steps to follow
Manual collection can suit low volumes with individual checks. A gateway suits ongoing reconciliation, signed notifications and system-driven fulfillment.
Assess payment volume and staff capacity for individual checks.
Decide whether verified payment must trigger system fulfillment.
Compare exception review, duplicate handling and record-keeping needs.
Validate a small integration before opening suitable payment options.
BoltUtil checks payments and sends signed callbacks. Your server verifies signatures and order status, deduplicates events, then delivers goods, activates service or credits accounts.
Integration notes
Check network, token, address, exact amount and confirmations. Balance changes or screenshots alone do not identify an order.
BoltUtil checks payments and notifies your system while funds go directly to your wallet, without withdrawal authority.
BoltUtil checks payments and sends signed callbacks. Your server verifies the signature, checks the local order and payment information, deduplicates and fulfills.
Manual: transfer → staff checks → merchant delivery
Automated: order → matching / confirmation → signed callback
→ merchant verifies and delivers once
Both can receive directly into the merchant wallet.Flow and parameter illustration only. No requests are sent. Use enabled networks, assets and wallets as documented.
Read API docsProduct comparison
Not necessarily. Manual collection can work for low volumes with careful checks. Automation helps with ongoing reconciliation and system fulfillment, but still requires correct integration.
No. Customers transfer directly to your configured wallet. BoltUtil checks orders and payments without custody or access to private keys, seed phrases or withdrawal authority.
TRON supports USDT only. Other networks support the configured USDT / USDC versions. Availability depends on enabled channels and merchant wallets; use the API and checkout response as the source of truth.
returnUrl is navigation, not payment evidence. Use a verified callback or trusted server-side status query, check the order and fulfill once.
Free merchants can view their own review records. Qualifying manual-transfer differences can create review records; verify ownership when several orders are candidates. Active membership is required to accept or reject an association. Acceptance confirms payment and triggers the configured callback.
Yes. Wallet checkout prepares the recipient, token and complete payable amount on supported networks and devices. Customers review and confirm in their wallet. First use may require unlocking, connection approval or a network switch. QR codes and copied addresses remain available for manual transfer; both methods require on-chain confirmation.
Create orders, monitor transfers, and notify your backend without asking customers to send screenshots.