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
{{ message }}
This repository has been archived by the owner on Sep 13, 2022. It is now read-only.
Would like to have an option to customize the "checkout page" when completing the transaction. For now, the pin is showing at LNpos device and the link for the one that did the payment. Only the pin is showing when clicking the link. This page could have some more details:
Summary of transaction
Timestamp
Sats paid
Fees paid in sats
Sats value in local fiat currency
maybe some information of the company / client who received the sats
an Email-Form to send all this information to the person who paid and as cc or bcc to the company.
For me personally living in Germany it would be awesome to always get all transaction details from above as email.
All this is available on BTC-PayServer. Getting the transaction details should not be a problem, I think. Creating a form is simple HTML.
For me running Umbrel I was not able to find a path where I can customize the page showing when transaction is done.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Would like to have an option to customize the "checkout page" when completing the transaction. For now, the pin is showing at LNpos device and the link for the one that did the payment. Only the pin is showing when clicking the link. This page could have some more details:
For me personally living in Germany it would be awesome to always get all transaction details from above as email.
All this is available on BTC-PayServer. Getting the transaction details should not be a problem, I think. Creating a form is simple HTML.
For me running Umbrel I was not able to find a path where I can customize the page showing when transaction is done.
The text was updated successfully, but these errors were encountered: