Add "Buy Now" style payment widget

[RenegadeButcher]

I believe the issue with payment notes would need to be addressed first:
getAlby/lightning-browser-extension#2312

I have an idea that I think would probably be really useful in expand the WordPress LN publisher. I've attempted to make it work with the donate widget, and the twentyuno, but not quite there yet.

So, if there was a widget or shortcode that allowed you to do essentially what the donate widget does now, but also attach a string to the beginning of the payment note, it could be very useful as a "buy it now" type addition to a product listing. I'd love the ability to allow a customer to click "buy now with Lightning" and have it generate a QR code but append a product number to the note, while still allowing them to enter an email address or shipping address in the note. There may be easier ways to do that, but I think it would really expand the lightning marketplace.

One issue I found with the donation widget is that even if I pay an invoice with say, Wallet of Satoshi, the information I put in the payment note does not display in Alby. Not sure why it doesn't. (getAlby/lightning-browser-extension#2312)

Anyways, nothing critical but I thought I would pass the idea on. Perhaps there is already a solution to this I'm not yet aware of.

[reneaaron]

Interesting idea, thanks for your feedback. Would it maybe be enough if you could see the URL where the payment happened?

@rolznz Are our getalby.com APIs ready for some LUD-18 metadata? Would be quite a nice use case for the new fields maybe?

[RenegadeButcher]

Perhaps? I think the main thing from my end would be needing some sort of customer entered data to complete a sale. Product code, email address, shipping info, something like that? I'm thinking something along the lines of, custolmer clicks the buttom, and they have an opportunity to enter a note similar to sending a Nostr zap, then pay the generated invoice, and I receive the note along with the payment. But if there was some other way to have a minimal level of accounting otherwise that's fine too. For example, I have 4 or 5 different seasonings that all sell for the same price. Currently I would have no idea which product the customer wanted, or how to contact them. I have to have them contact me initially and then invoice them or have them go through a more traditional payment system. Which is fine, I do that now. But there's a lot of room for potential here I believe ☺

…

On Fri, Apr 7, 2023, 4:31 PM René Aaron ***@***.***> wrote: Interesting idea, thanks for your feedback. Would it maybe be enough if you could see the URL where the payment happened? @rolznz <https://github.com/rolznz> Are our getalby.com APIs ready for some LUD-18 metadata? Would be quite a nice use case for the new fields maybe? — Reply to this email directly, view it on GitHub <#32 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2IS4DHJYVCQLTPXLWDKI3TXACBU3ANCNFSM6AAAAAAWVVH5G4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[reneaaron]

I think this communication channel could be solved over e.g. nostr (instead of trying to attach it to a lightning invoice) where you can't reply and certain size restrictions apply (256 characters, even less for WoS lightning addresses).

I think there are already some ideas around P2P markets based on nostr. Attaching the current URI is an interesting idea though 👌

[RenegadeButcher]

That's definitely interesting, and I really like the idea of doing that nover nostr. But how would that integrate into an item on a website?

…

On Fri, Apr 7, 2023, 5:26 PM René Aaron ***@***.***> wrote: I think this communication channel could be solved over e.g. nostr (instead of trying to attach it to a lightning invoice) where you can't reply and certain size restrictions apply (256 characters, even less for WoS lightning addresses). I think there are already some ideas around P2P markets based on nostr. Attaching the current URI is an interesting idea though 👌 — Reply to this email directly, view it on GitHub <#32 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2IS4DBOXVAJRQLR7SGGFDLXACIBDANCNFSM6AAAAAAWVVH5G4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[reneaaron]

That could work very similar to how the lightning widget works now. You as a website owner get an embed code from a 3rd party website that creates those nostr widgets. (nostrwidgets.twentyuno.net? 😅) that you add to your website. (I currently have no time to work on something like that currently though 😉 )

[RenegadeButcher]

I like that idea! I wish I had the coding background, or the time 😂

…

On Fri, Apr 7, 2023, 5:35 PM René Aaron ***@***.***> wrote: That could work very similar to how the lightning widget works now. You as a website owner get an embed code from a 3rd party website that creates those nostr widgets. (nostrwidgets.twentyuno.net? 😅) that you add to your website. (I currently have no time to work on something like that currently though 😉 ) — Reply to this email directly, view it on GitHub <#32 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2IS4DFMHTGCJOY5KQUYIC3XACJE3ANCNFSM6AAAAAAWVVH5G4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[rolznz]

I have a feeling WordPress already has all this great support for purchasing products, entering customer details etc as a CMS and it would not be worthwhile to re-implement this from scratch. The only thing really missing is a payment provider integration with lightning rather than using e.g. Stripe.

I think there might be some other plugins that do support Bitcoin and lightning payments like BTCPayServer, however if we had a payment option that used lightning addresses that would be even better, and might enable some of the details to be stored on the payment using LUD-18 like @reneaaron suggested. I think it is possible now using the new alby-tools package or something similar, but I don't know enough about WordPress development to be sure.

[bumi]

I think this should be already be possible with the plugin today if you do some customization.
the plugin allows you to create invoices and add a comment. This comment is saved in the WP transactions table. You could use this comment to store payerdata.

You only have to make sure that the verify call is made because WP currently does not have any way to do this periodically in the background.

so the flow would be:

• allow user to enter some data
• request an invoice which saves that data
• prompt the user to pay
• from the user's browser periodically check if the invoice is paid
• if paid show a confirmation screen
• admin checks the transaction table which contains the user provided data in the "comment" field

This can be done with the invoices API and some custom code: https://github.com/getAlby/lightning-publisher-wordpress/blob/master/includes/rest-api/controllers/class-rest-invoices.php

the new #27 paywall button could make this even easier.

[RenegadeButcher]

This is a much better technical description of what I am envisioning.

…

On Mon, Apr 10, 2023, 8:17 AM Michael Bumann ***@***.***> wrote: I think this should be already be possible with the plugin today if you do some customization. the plugin allows you to create invoices and add a comment. This comment is saved in the WP transactions table. You could use this comment to store payerdata. You only have to make sure that the verify call is made because WP currently does not have any way to do this periodically in the background. so the flow would be: - allow user to enter some data - request an invoice which saves that data - prompt the user to pay - from the user's browser periodically check if the invoice is paid - if paid show a confirmation screen This can be done with the invoices API and some custom code: https://github.com/getAlby/lightning-publisher-wordpress/blob/master/includes/rest-api/controllers/class-rest-invoices.php the new #27 <#27> paywall button could make this even easier. — Reply to this email directly, view it on GitHub <#32 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2IS4DC3OIXVDISVAPDTLQDXAQCABANCNFSM6AAAAAAWVVH5G4> . You are receiving this because you authored the thread.Message ID: ***@***.***>