
Suawave vs Plisio: invoice and deposit-address APIs
Sources checked
Quick verdict
| Suawave: Choose when... | Plisio: Choose when... |
|---|---|
| You want to render the deposit address in your checkout and track orders with your callback URL. | You need an invoice URL returned by the provider. Plisio documents txn_id and invoice_url in its invoice creation response. [p-invoice] |
For a Plisio alternative, start with what your payment screen consumes. Suawave returns a deposit address and provides a QR endpoint. Keep your order amount, reference and fulfillment state in your application.
Build with SuawaveAPI differences
| Boundary | Suawave | Plisio |
|---|---|---|
| Requests | Public GET endpoints need no authentication and return JSON. | Plisio documents GET requests with api_key in the query and JSON responses under /api/v1. [p-auth] |
| Create | GET /{ticker}/create/ takes address and callback. | Plisio documents GET /api/v1/invoices/new with order_name, order_number and api_key. [p-create] |
| Response identity | Persist address_in with the ticker, callback and your internal order reference. | Plisio documents txn_id and invoice_url in its invoice creation response. [p-invoice] |
| Notifications | GET callbacks by default; post=1 selects form POST and json=1 selects JSON POST. | Plisio sends invoice updates by POST and allows callback_url to override the configured Status URL. [p-callback] |
In Suawave the callback URL is part of the permanent mapping identity, not just a notification destination. Encode your order reference and nonce in it and store the exact URL. The first create call fixes the options for the ticker/callback pair. A new order identity needs a new callback URL.
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
Replace the invoice boundary and payment screen
Select a supported Suawave asset and network from the generated ticker list and read the minimum. Store the expected amount on your own order. Render the returned address and QR instead of expecting Suawave to provide a hosted invoice URL. Build a separate Suawave callback handler that verifies the signature before processing the event.
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
Plisio lists Gateway API and White Label as separate pricing options. [p-fees]
Use the provider pricing source below and our fee documentation for the asset and deposit size you expect. Fees and minimums
FAQ
Can I keep my own order number?
Yes. Store it in your application and include it in the URL-encoded callback alongside an unguessable nonce. Suawave sends your custom query parameters back on callbacks; verify them against the stored order.
Must Suawave callbacks use GET?
No. Set post=1 for form POST or json=1 for JSON POST when creating the mapping. JSON mode takes precedence if both are set. Preserve the raw POST body for signature verification.
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.
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.
- [p-invoice] Plisio: Create an invoice. Sources checked .
- [p-auth] Plisio: Introduction. Sources checked .
- [p-create] Plisio: Create an invoice. Sources checked .
- [p-callback] Plisio: Manage invoice updates and cash-in. Sources checked .
- [p-fees] Plisio: Pricing. Sources checked .
USDT payment networks and fees · Shop plugins and developer tools · Payment integration guides