
Migrate from CryptAPI to Suawave: API differences
Sources checked
Quick verdict
| Suawave: Choose when... | CryptAPI: Choose when... |
|---|---|
| You want a single payout address per order and can implement payment handling against the supported Suawave tickers. | You need the documented split-payout or caller-selected confirmation controls. CryptAPI documents split payouts, caller-selected confirmations, priority and multi_token options. [c-options] |
This migration compares CryptAPI at cryptapi.io with Suawave. Similar route names are a starting point: inspect parameters, response formats and callback verification before changing a production integration.
Build with SuawaveAPI differences
| Boundary | Suawave | CryptAPI |
|---|---|---|
| Create | GET /{ticker}/create/ takes address and callback; unsupported query options are refused. | CryptAPI creates payment addresses with GET /{ticker}/create/ using address and callback parameters. [c-create] |
| Address identity | The canonical ticker and callback pair identifies a permanent address; use a new callback to change payout settings. | CryptAPI returns the same address_in for the same callback URL and requires a new callback URL to change address_out. [c-reuse] |
| Payout controls | One payout address; no split payouts, caller-set confirmations, priority selection or multi-token acceptance. | CryptAPI documents split payouts, caller-selected confirmations, priority and multi_token options. [c-options] |
| Callbacks | RSA-SHA256 with x-ca-signature; fetch the Suawave public key and preserve the original signed bytes. | CryptAPI documents x-ca-signature as a base64 RSA-SHA256 signature over the full GET URL or raw POST body. [c-signature] |
CryptAPI requires a verified callback domain for new payment addresses; existing payment addresses keep working. [c-domain]
Suawave fixes options on the first create call for each ticker and callback pair. Remove unsupported parameters rather than relying on them being ignored. Pending detection uses indexed chain data. Test your buyer-facing QR rendering as well as the server call, because the data URI handling differs.
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
Endpoint mapping
Each source route maps to a documented Suawave route or is marked as having no equivalent, with the nearest supported alternative. Review the notes before migration.
| CryptAPI: Documentation | Suawave: Route | Migration check |
|---|---|---|
| CryptAPI creates payment addresses with GET /{ticker}/create/ using address and callback parameters. [c-create] | GET /{ticker}/create/ | Review every query option; supply one payout address and the encoded HTTPS callback. |
| CryptAPI exposes GET /{ticker}/logs/ with callback as the lookup parameter. [c-logs] | GET /{ticker}/logs/ | Look up the Suawave mapping using the callback stored for this provider. |
| CryptAPI exposes GET /info/ for service information. [c-info] | No equivalent. Nearest alternative: GET /{ticker}/info/ | Suawave has no global info endpoint. Select a supported ticker from the generated asset list, then request its information individually. |
| CryptAPI exposes GET /{ticker}/info/ for ticker information. [c-ticker-info] | GET /{ticker}/info/ | Read the current minimum and use decimal strings for amounts. |
| CryptAPI exposes GET /{ticker}/qrcode/ and documents qr_code as base64 image data without the data URI prefix. [c-qr] | GET /{ticker}/qrcode/ | Suawave returns qr_code as a complete data URI; do not add the prefix again. |
| CryptAPI exposes GET /{ticker}/estimate/ for blockchain fee estimates, excluding its service fee. [c-estimate] | GET /{ticker}/estimate/ | Suawave returns a conservative configured ceiling in the native coin; it is not the deposit deduction. |
| CryptAPI exposes GET /convert/ with value, from and to parameters. [c-convert] | GET /convert/ | Check Suawave’s supported conversion pairs and rounding; conversion quotes do not exchange funds. |
| CryptAPI exposes GET /{ticker}/convert/ with value and from parameters. [c-ticker-convert] | GET /{ticker}/convert/ | Use the Suawave ticker and validate the returned decimal string. |
| CryptAPI publishes its callback verification key at GET /pubkey/. [c-pubkey] | GET /pubkey/ | Replace the cached key with the Suawave key; a matching algorithm does not make keys interchangeable. |
Migration steps
Inventory the current request options
List every create parameter your application sends. Remove split-payout syntax, confirmations, priority and multi_token from the Suawave flow; also check every optional parameter against the Suawave API reference. Confirm the asset in the generated ticker list and read its minimum. No registration, no account and no API key are needed for Suawave.
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
CryptAPI lists volume-based service fees separately from blockchain/network fees. [c-fees]
Use the provider pricing source below and our fee documentation for the asset and deposit size you expect. Fees and minimums
FAQ
Is changing only the API hostname enough?
Review unsupported parameters, generated deposit addresses, QR data URI handling and the verification key as separate changes. Keep the exact callback bytes for signature verification and add regression coverage for the supported Suawave response fields.
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.
- [c-options] CryptAPI: Create New Payment Address. Sources checked .
- [c-create] CryptAPI: Create New Payment Address. Sources checked .
- [c-reuse] CryptAPI: Create New Payment Address. Sources checked .
- [c-signature] CryptAPI: Verify Webhook Signatures. Sources checked .
- [c-logs] CryptAPI: Check Payment Address Logs. Sources checked .
- [c-info] CryptAPI: CryptAPI Service Information. Sources checked .
- [c-ticker-info] CryptAPI: Get Ticker Information. Sources checked .
- [c-qr] CryptAPI: Payment QR Code Generator. Sources checked .
- [c-estimate] CryptAPI: Estimate Blockchain Fees. Sources checked .
- [c-convert] CryptAPI: Convert Price. Sources checked .
- [c-ticker-convert] CryptAPI: Convert Prices Using Ticker. Sources checked .
- [c-pubkey] CryptAPI: Verify Webhook Signatures. Sources checked .
- [c-domain] CryptAPI: Create New Payment Address. Sources checked .
- [c-fees] CryptAPI: Fees. Sources checked .
USDT payment networks and fees · Shop plugins and developer tools · Payment integration guides