Create a hot wallet, connect a hardware wallet, or follow an existing wallet.
sats
Send only bitcoin on to this address.
Choose how you want to hold your bitcoin on . To use another Bitcoin wallet, create another LNbits onchain wallet.
Check the address and amount before sending on . Bitcoin payments cannot be reversed.
| 50 | |
This LNbits server holds your private keys and can spend your bitcoin. Only use a server you trust. Your recovery phrase lets you recover independently.
Anyone with this phrase can spend your bitcoin. Keep your backup somewhere private.
Recovery: ·
·
· no passphrase
Save this address type and path with your recovery phrase.
checkout.session.completed
invoice.paidpayment_intent.succeededCHECKOUT.ORDER.APPROVEDPAYMENT.CAPTURE.COMPLETEDPAYMENT.SALE.COMPLETEDpayment.updatedinvoice.payment_madeORDER_AUTHORISED,
ORDER_COMPLETED, and
SUBSCRIPTION_INITIATED.
ORDER_AUTHORISED
ORDER_COMPLETED
SUBSCRIPTION_INITIATED
Refresh Interval and History Size are for
historical purposes only.
API URL and JSON Path fields can use the
{to} and {TO} placeholders for the code of the
currency
{TO} is the uppercase code and {to} is the
lowercase code
LNbits encrypts hot wallet recovery phrases with this key. Generate it once, then keep a recovery copy somewhere safe. Setup and backup actions take effect immediately; use Save to apply the payment toggle.
Restoring an instance? Restore its database and upload its original key backup. Existing keys cannot be replaced.
Keep this file in a secure place, separately from your database backup. Anyone with both can recover the hot wallets.
If this key is lost, LNbits cannot unlock its hot wallets. Users can still recover with their own wallet recovery phrases.
Wallet users can select only these Mempool-compatible HTTP(S) URLs. Adding a local or private URL allows wallets to contact that service. Removing a URL blocks wallets using it until they select another approved explorer.
Use the read key to list Bitcoin accounts, addresses and cached activity. The admin key can sign payments and export hot wallet recovery phrases.
GET /api/v1/onchain/stateGET /api/v1/wallet/onchainPOST /api/v1/onchain/sync
GET /api/v1/wallet
{"X-Api-Key": ""}{"id": <string>, "name": <string>, "balance":
<int>}
curl api/v1/wallet -H "X-Api-Key:
"
POST /api/v1/payments
{"X-Api-Key": ""}{"out": false, "amount": <int>, "memo": <string>,
"expiry": <int>, "unit": <string>, "webhook":
<url:string>, "internal": <bool>}
{"payment_hash": <string>, "payment_request":
<string>}
curl -X POST api/v1/payments -d
'{"out": false, "amount": <int>, "memo": <string>}' -H
"X-Api-Key:
"
-H "Content-type: application/json"
POST /api/v1/payments (reveal
admin keys
{"X-Api-Key": ""}
{"out": true, "payment_request": <string>}
{"payment_hash": <string>}
curl -X POST api/v1/payments -d
'{"out": true, "payment_request": <string>}' -H "X-Api-Key:
" -H "Content-type: application/json"
POST
/api/v1/payments/decode
{"data": <string>}
curl -X POST api/v1/payments/decode
-d '{"data": <bolt11/lnurl, string>}' -H "Content-type:
application/json"
GET
/api/v1/payments/<payment_hash>
{"X-Api-Key": ""}
{"paid": <bool>}
curl -X GET
api/v1/payments/<payment_hash>
-H "X-Api-Key:
"
-H "Content-type: application/json"
WS
/api/v1/ws/<invoice_key>
wscat -c /
{"balance": <int>, "payment": <object>}
()
Fees and withdrawals spend funds backing LNbits wallets. Channel closure removes its liquidity. Check your liabilities before continuing.
Management controls require a recognised Phoenixd version of 0.7.3 or later.
Phoenixd payment and liquidity history. More pages become available as you browse.
Authorization
header.
| Header Name | Header Value |
|---|---|
| Authorization |
Bearer
|
`name` and
`sort description` fields are what the users will
see when browsing the list of extensions.
`id` field is used internally and in the URL
of your extension.
created_at, updated_at and
extra.
Wallet will
be shown.
Currency will
be shown.
Integer and
Float will be shown.
Boolean will
be shown.
is requesting an invoice:
Validate after receiving the cash.
Authenticate with ?
For every website and for every LNbits wallet, a new keypair will be deterministically generated so your identity can't be tied to your LNbits wallet or linked across websites. No other data will be shared with .
Your public key for is:
is
requesting
and a
-char comment
is requesting
between
and
and a
-char comment