Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Pass payment details #21

Open
DoktorShift opened this issue Jun 22, 2024 · 0 comments
Open

[Feature request] Pass payment details #21

DoktorShift opened this issue Jun 22, 2024 · 0 comments

Comments

@DoktorShift
Copy link

DoktorShift commented Jun 22, 2024

Description:
Right now i am using lnbits with lnurlp extension to receive sats for sold products out of my eCommerce store. I use a Plugin which is handeling the process with WooCommerce. From the Plugin i receive the sats by lnaddress (lnurlp) to my lnbits server.

Alongside the Payment flow i get the Order ID my eCommerce Shop created inside the memo. It´s stored in a JSON in lnbits db.

Now i use SplitPayment extension to forward the sats for example to my friend pieter because he is the manufactor of that product.
Pieters wallet now do not get forwarded the order id since the order id is handeled as an extra information json in lnbits db which is not part of the LN payment flow. Instead pieters receives only the message the SplitPayment extension is generating by default as a memo "Split payment: 50.0% for..."

Expected Result:
The extension should somehow handle the extra information inside the JSON and forward it alongside the LN payment flow in a way all/most lightning wallets can handle.

@arcbtc once mentioned:

I wonder if these could be an optional toggle to records in splitpayments - "on/off pass all payment data"?

A Member of the lnbits group mentioned:

I guess it would be nice to have optional callback URLs. Which could be triggered and have the params ready. It would be useful to do analytics or even connect with other services through zapier etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant