-
Notifications
You must be signed in to change notification settings - Fork 151
Closed
Description
LUD-[TBD]: verify
base spec.
author: [TBD]
discussion: [TBD]
The idea here is that a SERVICE
can verify an invoice has been paid by contacting the LN SERVICE
.
A SERVICE
can verify a payment was made without access to the user's node. Users can give their LNURL or Lightning Address to a SERVICE
and allow the SERVICE
to create and verify invoices on their behalf.
This allows users to re-use existing wallets and SERVICE
s to facilitate P2P payments without being an intermediary.
LNURL-verify
An optional field verify
is added to the callback
response:
{
"status": "OK",
"routes": [],
"pr": "lnbc10...",
+ "verify": "https://example.com/verify/894e7f7e...",
}
The field verify
provides an URL to a SERVICE
to check if the invoice has been settled:
https://example.com/verify/894e7f7e...
Response
{
"status": "OK",
"settled": true,
"preimage": "123456...",
"pr": "lnbc10..."
}
{
"status": "OK",
"settled": false,
"preimage": null,
"pr": "lnbc10..."
}
or
{
"status": "ERROR",
"reason": "Not found"
}
Looking forward to hear your feedback!
bumi, MoritzKa, ngutech21, MickMorucci, cameri and 7 morefiatjaf, Semisol, hsjoberg and RajGoodF
Metadata
Metadata
Assignees
Labels
No labels