Frequently asked questions
Find answers about accepting crypto payments with Suawave, from creating a deposit address to handling the confirmed callback.
Getting started
How do I accept USDT TRC20 payments without an account?
Suawave lets you accept USDT TRC20 payments without registration, an account or an API key. Call GET /trc20/usdt/create/ with your payout address and a public HTTPS callback URL, then show the returned address_in and minimum_transaction_coin to the payer, together with the asset and network from the selected ticker.
Read the documentationHow do I create a different payment address for each order?
Use a unique callback URL for each Suawave order, with your order reference and an unguessable nonce. Repeating create with the same ticker and callback returns the same deposit address and preserves the original options; retain the exact callback URL on your server.
Read the documentationCoins and networks
Which coins and networks does Suawave support?
Suawave supports these enabled payment routes: USDC on BNB Smart Chain BEP20 (bep20/usdc); USDT on BNB Smart Chain BEP20 (bep20/usdt); USDT on TRON TRC20 (trc20/usdt). Use the exact lowercase ticker for the selected token and network; a wallet address alone does not identify the token standard.
Read the documentationWhat happens if a customer sends the wrong token or uses the wrong network?
Suawave only processes the token and network selected for the order. Transfers of another token are not forwarded and generate no public callback or log entry; do not assume a payment on another network can be recovered or accepted.
Read the documentationFees and minimums
What does Suawave charge per payment?
Suawave charges each deposit separately: a service fee, subject to a minimum, plus a network fee in the payment token. Service fee tiers by previous 30-day USD volume: Under $250,000: 0.50%; $250,000 to $999,999: 0.45%; $1,000,000 to $2,499,999: 0.40%; $2,500,000 to $4,999,999: 0.35%; $5,000,000 to $9,999,999: 0.30%; $10,000,000 to $19,999,999: 0.20%; $20,000,000 or more: 0.13%. Published token fees: BNB Smart Chain BEP20 USDC: minimum service fee 0.05 USDC, network fee 0.05 USDC; BNB Smart Chain BEP20 USDT: minimum service fee 0.05 USDT, network fee 0.05 USDT; TRON TRC20 USDT: minimum service fee 0.05 USDT, network fee 1.00 USDT. Fees are resolved per deposit; fee_coin and value_forwarded_coin report the actual charge and payout.
Read the documentationWhat is the minimum crypto payment Suawave accepts?
Suawave has a separate minimum deposit for each token and network: BNB Smart Chain BEP20 USDC: 1.00 USDC; BNB Smart Chain BEP20 USDT: 1.00 USDT; TRON TRC20 USDT: 10.00 USDT. Check minimum_transaction_coin from create or info before showing a payment request; the applicable minimum is snapshotted when each deposit is first detected.
Read the documentationCan several deposits below the minimum add up to a valid payment?
No. Suawave evaluates the minimum separately for each deposit, so several below-minimum deposits do not combine into an eligible payment. A below-minimum deposit is not forwarded or paid out, sends no callback and is absent from public logs.
Read the documentationConfirmations and finality
When can I mark a Suawave payment as paid?
Mark an order paid only after verifying a Suawave confirmed callback with pending equal to 0 and checking the order, token, address and amount. This event means the eligible deposit was forwarded and the forwarding transaction is confirmed; a pending callback alone does not authorize fulfillment.
Read the documentationHow many confirmations does Suawave need, and can I change the number?
Suawave follows the selected chain’s finality policy rather than a confirmation count chosen by the caller. TRON waits for solidified evidence and BNB Smart Chain uses finalized headers; the public create endpoint does not accept a custom confirmation count or priority setting. Indexing and forwarding add time, so a block interval is not a payment completion deadline.
Read the documentationDoes a pending webhook mean the customer has paid?
A Suawave callback with pending equal to 1 means the indexer detected an eligible deposit, not that forwarding has confirmed. Request this optional event with pending=1 on the first create call; pending and confirmed events can arrive out of order and have different UUIDs.
Read the documentationCallbacks and signature verification
Can Suawave send webhooks as JSON or form POST?
Yes. Suawave sends GET callbacks by default, form POST with post=1, or JSON POST with json=1; JSON takes precedence when both are set. The first create call fixes these options for the ticker and callback pair, and your custom query parameters stay in the callback URL.
Read the documentationHow do I verify a Suawave webhook signature?
Verify the x-ca-signature header as a base64 RSA-SHA256 PKCS#1 v1.5 signature using Suawave’s public key from GET /pubkey/. GET callbacks sign the full original request URL; POST callbacks sign the exact raw body. Verify before parsing or trusting fields, cache the key, and refresh it once if verification fails before rejecting the request.
Read the documentationHow do I acknowledge a webhook, and does Suawave retry it?
Return HTTP 200 with *ok* within 30 seconds to acknowledge a Suawave callback; plain ok is also accepted without case sensitivity. There are 8 attempts in total: the initial send, then delays of 30 s, 2 min, 10 min, 30 min, 2 h, 6 h, 24 h, with up to 10% added jitter. Retries keep the same uuid, so persist it to prevent duplicate work.
Read the documentationHow can I check a payment if the webhook never arrives?
Use Suawave’s GET /trc20/usdt/logs/ with the original callback URL to reconcile eligible deposits. The result pending means forwarding has not confirmed, sent means forwarding confirmed without an acknowledged confirmed callback, and done means that callback was acknowledged. Empty logs do not prove no transfer was sent: below-minimum, unsupported and late transfers can be absent.
Read the documentationUnderpayments, overpayments and late payments
What if a customer pays less than the order total?
Your shop decides whether the confirmed amount satisfies the order total; Suawave’s public create endpoint does not take an invoice amount. Add eligible confirmed deposits using value_coin for a gross policy or value_forwarded_coin for a net policy, and deduplicate callback UUIDs. Every additional deposit must meet its own minimum and is charged separately.
Read the documentationWhat happens if a customer sends too much crypto?
Suawave forwards an eligible deposit minus its fees, including any amount above your shop’s order total. The public API does not automatically refund the excess; your shop must decide how to reconcile it and arrange any refund from its own wallet.
Read the documentationWhat happens if a customer pays after the payment address expires?
A Suawave deposit outside the order’s accepted expiry window is held for review, not forwarded, and produces no public callback or log entry. Eligibility uses the transfer’s effective time and the stored expiry plus configured grace, so an on-time transfer may still finalize later. Stop showing expired addresses and reconcile late payments manually; no automatic payer refund is promised.
Read the documentationPayouts and forwarding
How does Suawave forward payments to my wallet?
Suawave forwards each eligible deposit separately to the single payout address supplied at create, after fees and chain checks. The confirmed callback includes txid_out and value_forwarded_coin so your server can identify the forwarding transaction and the net amount received.
Read the documentationCan I change the payout address or split a payment between wallets?
Suawave binds one payout address to each ticker and callback pair, and that address cannot be changed for the existing pair. Create a new order with a new callback URL to use another payout address; split shares and multiple payout destinations are not supported by the public API.
Read the documentationSecurity and custody
Does Suawave hold crypto before forwarding it?
Suawave receives payments at a gateway-controlled deposit address before forwarding eligible funds to your payout wallet. Forwarding is not instant or unconditional: chain checks, fees, minimums and expiry rules apply, and ineligible deposits can remain held.
Read the documentationWhy should I keep my full callback URL secret?
The full Suawave callback URL grants access to the order’s public API logs, so keep it server-side and include an unguessable nonce. Signature verification is still required for incoming callbacks; a valid signature must also be matched to your stored order, expected token, address and amount.
Read the documentationPlugins, SDKs and MCP
Can I accept crypto payments with WooCommerce, Magento, OpenCart or PrestaShop?
Suawave provides shop integrations for WooCommerce, Magento 2, OpenCart and PrestaShop. Use the matching integration guide to install and configure the plugin, show the payment address and QR code, and process signed payment callbacks.
Read the documentationWhich SDKs can I use to integrate Suawave?
Suawave has Go and JavaScript/TypeScript SDKs for the public API. You can also call the HTTP endpoints directly and use the signature verification examples in Go, JavaScript, PHP or C# for your callback handler.
Read the documentationCan an AI assistant use Suawave through MCP?
Yes. Suawave’s MCP server exposes tools for its public payment API, including creating deposit addresses and checking payment logs. The public payment flow needs no merchant key and exposes no administrator operations; keep callback URLs and their secret nonces out of shared prompts and public output.
Read the documentationMigrating from CryptAPI
How do I migrate a CryptAPI integration to Suawave?
Update the API origin to Suawave, create new orders and deposit addresses, and verify callbacks using Suawave’s own key from /pubkey/. Review ticker availability, expiry, callback retries and unsupported parameters before switching; do not reuse CryptAPI’s public key or IP allowlist.
Read the documentationLimits, expiry and refunds
Does Suawave limit API requests or new payment addresses?
Yes. Suawave applies request limits per client IP and callback host, plus separate quotas for creating new ticker and callback pairs. On HTTP 429, back off and respect Retry-After when supplied; reusing an existing pair avoids new-pair quotas but still counts toward request limits.
Read the documentationCan Suawave automatically refund a crypto payment?
Suawave’s public API has no payer refund endpoint and does not automatically return excess or late payments. For an eligible payment already forwarded, your shop must arrange any refund from its own wallet; a held late transfer requires manual reconciliation and is not an automatic refund.
Read the documentationDoes creating the same Suawave address again extend its expiry?
No. Repeating create for an existing ticker and callback pair returns the original deposit address and expires_at without extending the order. Use the returned UTC expiry in your checkout, stop displaying the expired address, and use a new callback URL for a new order.
Read the documentation