
Suawave vs CoinPayments: payment API migration
Sources checked
Quick verdict
| Suawave: Choose when... | CoinPayments: Choose when... |
|---|---|
| You want a deposit-address flow with a payout address and callback URL supplied on each new order mapping. | You need the documented wallet model with permanent or temporary addresses. CoinPayments documents wallets with permanent or temporary addresses in its new platform. [cp-wallet] |
Before evaluating a CoinPayments alternative, identify which API your application uses. Treat the legacy cmd flow and the new JSON API as different adapters. The target Suawave integration uses a ticker, a payout address and a callback URL.
Build with SuawaveAPI differences
| Boundary | Suawave | CoinPayments |
|---|---|---|
| Legacy requests | Use the supported GET routes directly, starting with /{ticker}/create/. | CoinPayments legacy requests use POST /api.php with form-encoded cmd operations. [cp-legacy] |
| New payment creation | GET /{ticker}/create/ returns address_in for the payment screen. | CoinPayments documents POST Invoice with JSON for its new payment creation flow. [cp-create] |
| Request signing | Public Suawave GET endpoints need no authentication; callback verification is a separate step. | CoinPayments authenticates protected calls with X-CoinPayments-Client, X-CoinPayments-Timestamp and X-CoinPayments-Signature using HMAC-SHA256. [cp-auth] |
| Currency identifier | Select a ticker from Suawave’s generated asset list and preserve its network. | CoinPayments new platform references currencies by IDs rather than symbols. [cp-currency] |
| Address model | Create a permanent ticker/callback mapping that forwards eligible deposits to one payout address. | CoinPayments documents wallets with permanent or temporary addresses in its new platform. [cp-wallet] |
Build a Suawave adapter with its own stored provider field, deposit address and callback identity. Your application must render the checkout, store the expected amount and decide whether accumulated confirmed deposits satisfy the order. Suawave creates a forwarding address rather than importing a wallet or invoice history.
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
Identify the adapter and replace its payment boundary
Record the provider and API version for every outstanding order. For new Suawave orders choose the exact asset and network from the generated ticker list, then check the minimum. Map your internal order reference to the callback URL instead of treating a provider invoice identifier as a transferable identifier.
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
CoinPayments lists To Balance, ASAP and Nightly processing modes, with network fees listed for ASAP and Nightly. [cp-fees]
Use the provider pricing source below and our fee documentation for the asset and deposit size you expect. Fees and minimums
FAQ
Which CoinPayments version does this comparison cover?
The table labels the legacy request style and the new payment flow separately. Match the row to the adapter you actually run before planning the change; the Suawave target flow is the same in both cases.
Does a provider switch copy wallet history?
This guide covers new Suawave deposit addresses and order handling. Reconcile historical payments with their original provider; keep provider identifiers and historical records attached to those orders.
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.
- [cp-wallet] CoinPayments: Migrating from Legacy. Sources checked .
- [cp-legacy] CoinPayments: Migrating from Legacy. Sources checked .
- [cp-create] CoinPayments: Migrating from Legacy. Sources checked .
- [cp-auth] CoinPayments: Authentication. Sources checked .
- [cp-currency] CoinPayments: Migrating from Legacy. Sources checked .
- [cp-fees] CoinPayments: Payment Processing Fees. Sources checked .
USDT payment networks and fees · Shop plugins and developer tools · Payment integration guides