This endpoint implements the LNURL-pay well-known discovery step — the first step in the Lightning Address payment flow. When a wallet wants to payDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/nicosaporiti/buda-lightning-invoice/llms.txt
Use this file to discover all available pages before exploring further.
username@domain.com, it fetches this URL to discover payment parameters and the callback URL it should use to request an invoice. All usernames resolve to the same underlying Buda.com account, so the username portion of the address is cosmetic and only affects the metadata description returned.
Path parameters
Any username string. All usernames resolve to the same Buda.com account regardless of what value is supplied here. This value is interpolated into the
metadata description field as "Pago Lightning a {username}".Response (200 OK)
The URL wallets must call to request a Lightning invoice. Constructed dynamically from the
DOMAIN environment variable (or the request’s Host header if DOMAIN is not set): {protocol}://{domain}/callback.Maximum payable amount in millisatoshis:
100000000 (equivalent to 100,000 satoshis). Wallets will not offer amounts above this value.Minimum payable amount in millisatoshis:
1000 (equivalent to 1 satoshi). Wallets will not offer amounts below this value.A JSON-encoded array of metadata tuples as required by the LNURL-pay spec. Returns
[["text/plain", "Pago Lightning a {username}"]] with the path :username interpolated.Always
"payRequest". Identifies this response as an LNURL-pay endpoint per the LUD-06 specification.Maximum number of characters allowed in the
comment field when calling /callback. Set to 140 characters per LUD-09.Amounts in this response —
minSendable and maxSendable — are in millisatoshis, not satoshis. 1 satoshi = 1000 millisatoshis. When calling the /callback endpoint, pass the amount in millisatoshis as well.The
DOMAIN environment variable controls the hostname used to build the callback URL. If DOMAIN is not configured on the server, the callback is constructed from the incoming request’s Host header instead.Example
RequestSpec compliance
This endpoint conforms to two LNURL specifications:- LNURL spec LUD-06 — Defines the
payRequesttag and the base LNURL-pay flow: the wallet fetches this well-known URL, readsminSendable/maxSendable/callback, then calls the callback with a chosen amount to get a BOLT11 invoice. - LUD-09 — Extends LNURL-pay with an optional
commentfield. ThecommentAllowed: 140field in the response signals that the/callbackendpoint accepts acommentquery parameter of up to 140 characters.