
Suawave vs NOWPayments: payment API migration
Sources checked
Quick verdict
| Suawave: Choose when... | NOWPayments: Choose when... |
|---|---|
| You want to show a deposit address in your own checkout and forward each eligible deposit to one payout address. | You need a provider-generated invoice URL for the customer. NOWPayments POST /v1/invoice returns an invoice_url for the customer. [n-invoice] |
For a NOWPayments alternative, compare the object your checkout needs: a deposit address that you display, or a hosted invoice link. Suawave gives you the address and signed callbacks; your application owns the order and payment screen.
Build with SuawaveAPI differences
| Boundary | Suawave | NOWPayments |
|---|---|---|
| Create | GET /{ticker}/create/ with address and callback; no authentication is required. | NOWPayments creates direct payments with POST /v1/payment, JSON and an x-api-key header. [n-create] |
| Order reference | Put your order reference and nonce in callback and persist the returned address_in. | NOWPayments payment creation accepts price_amount, price_currency, pay_currency, ipn_callback_url and order_id. [n-fields] |
| Create response | Store address_in with the ticker, payout address, callback and provider. | NOWPayments returns payment_id and pay_address when creating a direct payment. [n-result] |
| Buyer screen | Render the returned address, selected asset, network, amount and QR in your checkout. | NOWPayments POST /v1/invoice returns an invoice_url for the customer. [n-invoice] |
| Reconciliation | GET /{ticker}/logs/ uses the stored callback URL. | NOWPayments exposes GET /v1/payment/{payment_id} for payment status. [n-status] |
| Callback verification | Verify RSA-SHA256 over the original URL or raw POST body with the public key from Suawave. | NOWPayments verifies IPNs using x-nowpayments-sig and HMAC-SHA512 over sorted JSON with an IPN secret. [n-signature] |
Rebuild the payment adapter around Suawave’s ticker and callback pair. Your order amount remains application state: create returns a deposit address, not an invoice lifecycle. Replace any status-to-fulfillment mapping with verified per-deposit callbacks and track partial payments using decimal arithmetic.
Supported assets: bep20/usdc (BSC), bep20/usdt (BSC), trc20/usdt (TRON). Check the documentation for the current request and response contracts. Tickers and networks · API reference
Migration steps
Select the checkout and amount flow
Use the generated Suawave ticker list to match the exact asset and network your buyer will send. Read its minimum. Display your own checkout UI and store the expected amount on the order. If you need a currency quote, review the separate conversion documentation; a quote does not exchange deposited funds.
Create new orders with a payout address and callback
Send address and a URL-encoded HTTPS callback to GET /{ticker}/create/. Put your order reference and an unguessable nonce in the callback URL and store them server-side. Persist the returned address_in alongside the provider and ticker. Do not reuse a deposit address from another provider.
Replace callback verification and fulfillment
Verify x-ca-signature with the key from the Suawave GET /pubkey/ endpoint. For GET callbacks preserve the full original URL; for POST preserve the raw body before parsing. Check the order, nonce, asset, address and amount, then deduplicate by uuid. Fulfill only for pending equal to 0 and acknowledge with HTTP 200 and *ok*.
Cut over new orders and reconcile old ones
Keep the original provider attached to existing orders and keep their callback handler active. Direct only newly created orders to Suawave. Exercise valid and tampered signatures, duplicate deliveries, pending after confirmed, smaller deposits and callback failures before opening the new flow to buyers. Use Suawave logs as a polling fallback.
Use these guides while replacing the adapter: Quick start · Callback contract · Signature verification examples
Fees and minimums
NOWPayments publishes its service fee on its pricing page. [n-fees]
Use the provider pricing source below and our fee documentation for the asset and deposit size you expect. Fees and minimums
FAQ
Will Suawave return an invoice link?
The Suawave create response contains the deposit address for your checkout. Your application displays the payment instructions and maintains the order lifecycle. Follow the quickstart for the address and QR flow.
Can existing deposit addresses move with the integration?
Create a new deposit address through Suawave for each new ticker and callback pair. Keep existing payment instructions and outstanding orders with their original provider until you have reconciled them.
When should my shop mark an order paid?
After a valid Suawave signature and matching order, nonce, asset, address and amount, process the confirmed callback where pending is 0. Store uuid before fulfillment so retries cannot repeat the work.
How do I compare the total cost?
Read the linked provider pricing source and Suawave fees and minimums for the exact asset and expected deposit size. Include the service fee, network fee and minimums rather than comparing a headline rate alone.
Sources and method
This is a documentation comparison published by Suawave. The selection advice follows the documented features; it is not a payment benchmark. Each footnote links to the provider’s own public docs or pricing page and records when it was checked.
- [n-invoice] NOWPayments: API and endpoint description. Sources checked .
- [n-create] NOWPayments: API and endpoint description. Sources checked .
- [n-fields] NOWPayments: API and endpoint description. Sources checked .
- [n-result] NOWPayments: API and endpoint description. Sources checked .
- [n-status] NOWPayments: API and endpoint description. Sources checked .
- [n-signature] NOWPayments: IPN and how to setup. Sources checked .
- [n-fees] NOWPayments: Pricing. Sources checked .
USDT payment networks and fees · Shop plugins and developer tools · Payment integration guides