Pay an invoice
Pays a BOLT11 invoice from your BTC balance. max_fee caps the routing fee. Reusing a reference returns the original payment. Invoices without an amount can’t be paid.
Authorizations
Your workspace client id.
All calls must include four headers:
X-Auth-Client— your workspace client idX-Auth-Timestamp— Unix secondsX-Auth-Nonce— 16-byte random hexX-Auth-Signature— hex(HMAC-SHA256({client_id}:{timestamp}:{nonce}:{raw_body}, client_secret))
The playground computes the timestamp, nonce and signature for you.
Your sandbox client secret. The playground uses it to sign the request in your browser and removes it before the request is sent. Never send your client secret as a header in your own integration.
Body
Your unique reference; the idempotency key for the send.
100BOLT11 invoice to pay. A leading "lightning:" scheme is stripped. Between 90 and 2000 characters, with an ln + bc, tb, bcrt or sb prefix.
2000Optional customer the payment is for. When set, the customer_lightning customer product must be enabled.
100Optional routing fee cap in sats, as a number or numeric string. Must be non-negative.
x >= 0Response
Created
Successful responses are wrapped in this envelope, and so are errors a handler answers itself (request body and field validation, some not-found and conflict cases, ORG_NOT_ACTIVE): success is false and error carries a code and message. Errors raised by authentication and by the services behind a handler are a Problem instead.
true on success
When the response was written.
The payload; its shape is given per operation. Omitted when there is none.
Human-readable summary; omitted when empty.
List metadata. Page lists set page, per_page, total and total_pages; offset and cursor lists set limit, offset, has_more and next_cursor. Zero and empty fields are omitted, and metadata is absent when nothing is set.
Set on error envelopes: the request's correlation id (req_ followed by a UUID), the same value as the X-Correlation-ID response header. Quote it to support.