Keep secrets server side
Store API keys in environment variables or a secret manager. Rotate keys and use server IP allowlists where configured.
Good payment experiences need clear boundaries. Understand how keys, confirmations, and treasury operations fit together.
Store API keys in environment variables or a secret manager. Rotate keys and use server IP allowlists where configured.
Check webhook signatures, reject stale timestamps, and make deposit crediting idempotent.
Wait for the configured confirmation threshold and canonical receipt checks before treating a deposit as confirmed.
The collection relayer cannot move treasury funds. Settlement requests require their own approval process.
USDT payments must use BNB Smart Chain. Confirm the exact address and network before sending funds.
Sensitive merchant actions and settlement changes are captured in audit logs for operational review.
The current project requires end-to-end chain testing and independent security review before accepting real funds. This landing site does not imply an audit, certification, or production readiness.
Read the security guide →The gateway is designed around USDT deposits on BNB Smart Chain. Review treasury and settlement requirements with your team before accepting payments.
No. This website is an interactive product preview. Currency selection, wallet connection and payment confirmations are simulations. Never send funds to an illustrative address.
The current backend targets USDT on BNB Smart Chain (BEP-20). Other assets in the demo illustrate the checkout design and are not a statement of production support.
The backend checks blockchain receipts and waits for its configured confirmation threshold before recording a confirmed deposit. Integrations should credit customers only after a verified deposit.confirmed event.
Explore the experience before you integrate.