You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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:
A Member of the lnbits group mentioned:
The text was updated successfully, but these errors were encountered: