Coinetic documentation

Everything you need to accept crypto on your website, app or bot. The integration is two API calls and one webhook handler.

How a payment works

 Your server                     Coinetic                           Customer
 ───────────                     ────────                           ────────
 1. POST /v1/invoices  ────────▶ creates the invoice, returns checkout_url
 2. redirect to checkout_url ─────────────────────────────────────▶ checkout page
                                 3. customer picks a currency ◀──── (USDT, USDC, BTC…)
                                    and pays to the issued address
                                 4. the network confirms the payment
 5. invoice.paid webhook ◀────── POST to your URL (HMAC-signed)
 6. GET /v1/invoices/{id} ─────▶ re-check the status
 7. fulfill the order
                                 8. “Return to store” ─────────────▶ your return_url

Four rules

• Your API key secret stays on your server. Never in the browser, a mobile app or git.
• Payment status comes only from Coinetic. Don't trust return_url parameters, and don't take a webhook at its word: verify the signature, then re-check the status via GET /v1/invoices/{id}.
• Money is a string. Amounts arrive as decimal strings ("49.99") or as strings in the smallest units ("49990000"). Never convert them to floats.
• Every mutating request carries an Idempotency-Key. Retrying after a timeout returns the same invoice instead of creating a second one.

Base URLs

All responses are UTF-8 JSON; timestamps are RFC 3339 in UTC. The full formal contract is an OpenAPI 3 spec (openapi.yaml): request it from support or in the dashboard.

All merchant endpoints