Skip to content
RUSign inGet started

Developers

From API call to payment status.

One REST API, JSON in and out, signed with an API key. Six steps take you from a key to a confirmed payment; every route, field and error is in the OpenAPI document.

  1. 1

    Quickstart

    Create a key in the cabinet, keep the secret on your server, sign requests with HMAC-SHA256.

    Start here →
  2. 2

    Create a payment

    One POST /v1/invoices with the amount in a coin or a fiat currency; the response carries checkout_url.

    Create a payment →
  3. 3

    Customer payment

    Send the payer to checkout_url: the page shows the address, QR, exact amount, network warning and live status.

    The checkout page →
  4. 4

    Status model

    new → pending → paid; underpaid stays open until the TTL; expired and cancelled are terminal. Terminal states are named explicitly.

    Statuses →
  5. 5

    Webhooks

    Signed events with retries and the same event id: verify the signature, act once, answer 2xx within 10 seconds.

    Webhooks →
  6. 6

    Errors

    One envelope: a human message, a machine code and the recovery action — details.field names the bad field.

    Errors →
POST /v1/invoices
POST /v1/invoices
Idempotency-Key: order-10042
X-API-Key: ck_live_…   X-Timestamp: 1758000000   X-Signature: <hmac-sha256>

{ "amount": "49.90", "currency": "USD", "order_id": "10042", "return_url": "https://shop.example.com/orders/10042" }

→ 201 { "id": "4e2b…", "status": "new", "checkout_url": "https://cryptolike.net/pay/4e2b…", … }

API reference

Every route, field and error in the OpenAPI document, browsable as Swagger UI.

Open Swagger UI ↗