Overview

Accept crypto payments with one HTTP call. There is no registration, no account and no API key: you send a payout address and a callback URL, you get a permanent deposit address back, and every deposit to it is forwarded to your payout address while your server receives signed callbacks.

Base URL: https://api.suawave.com. All endpoints use GET and return JSON. There is no version prefix in the path.

How it works

1. Call GET /{ticker}/create/ with your payout address and a callback URL. The response carries address_in, the deposit address to show to the payer, and minimum_transaction_coin, the smallest deposit that is forwarded.
2. The payer sends the asset to address_in.
3. The gateway detects the deposit, waits for finality, forwards the amount minus fees to your payout address and calls your callback URL. See Callbacks.
4. Your server verifies the x-ca-signature header with the public key from GET /pubkey/, checks its own order data, deduplicates on uuid and answers *ok*. See Verify callback signatures.

Start with the Quick start for a complete walk-through with commands you can run.

The order model

• The pair of ticker and callback URL identifies an order. The same pair always returns the same address_in. Treat the callback URL as your order ID and put your own order reference and an unguessable nonce in its query string. Custom query parameters are echoed back in every callback.
• The payout address is frozen for a pair. To change it, use a new callback URL, for example by adding &v=2.
• address_in is permanent. Every deposit of at least the minimum is forwarded on its own, with its own fees, forwarding transaction and callbacks, even when several deposits arrive close together.
• Deposits below the minimum are not forwarded, trigger no callback and are not paid out. Always show the minimum to the payer.
• Tokens other than the ticker's asset that are sent to the address are not forwarded and trigger no callback.

Where to go next

• Quick start: the whole flow in five steps.
• API reference: every endpoint with parameters, examples and responses.
• Callbacks: payloads, transports, retries and acknowledgement.
• Verify callback signatures: working code in Go, C#, JavaScript and PHP.
• Tickers and networks: which assets you can accept and their minimums.
• Fees and minimums: how the amount you receive is computed.
• Price conversion: fiat and crypto conversion and the convert fields in callbacks.
• Errors: status codes and what to do about them.

For AI agents

Every page is available as raw markdown under raw/ (for example raw/quickstart.md). llms.txt lists the pages and llms-full.txt contains all of them in one file. The OpenAPI definition is published as openapi.yaml.