Steven Bell :pci: on Nostr: nprofile1q…0mp2c okay, that's very helpful. So, putting the boost metadata aside, ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqu889jx72l4rn6vsva3jqxyhtekq4qhanwh296lz30ajpsrlhuvfqe0mp2c (nprofile…mp2c)
okay, that's very helpful. So, putting the boost metadata aside, for just payments to multiple recipients, for EACH recepient I would
1) get the callback through .well-known (this seems like it can be cached per session)
2) request an invoice by sending a request to the callback
3) pay the invoice
Does the Alby api have functions to auto pay each invoice, or does the user have to approve each one?
okay, that's very helpful. So, putting the boost metadata aside, for just payments to multiple recipients, for EACH recepient I would
1) get the callback through .well-known (this seems like it can be cached per session)
2) request an invoice by sending a request to the callback
3) pay the invoice
Does the Alby api have functions to auto pay each invoice, or does the user have to approve each one?