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

⚡☢️ "Error 500 - Could not create invoice" on lightning payment #444

Open
Tirodem opened this issue Sep 14, 2023 · 4 comments
Open

Comments

@Tirodem
Copy link
Contributor

Tirodem commented Sep 14, 2023

Context

Trying to pay a 20CHF order with Lightning, I met this error
image

Theory

Here the status on /admin/lightning:
image
Considering my cart:
image
The invoice creation error might be related to order amount > available amount on some channels.

Considerations

  • In e-commerce, the further a customer goes on a buying funnel, the more a breaking error is, and the higher the chance are that 1/ the customer won't retry this order 2/ the customer won't go back on this website if that's the 1st try ; so, it's way better to inform & warn instead of saying "oops, something broke"

Solution

Yet to be decided
2 ways :

  • help the seller to always have funded channels
    • with funding services
    • with notifications if one of X channels is under a defined treshold
  • manage lightning proposition to the customer smarty
    • pre-check lightning invoice generation availability before pushing the payment mean to the customer
      image
      • disable or warn about lightning payment if KO
    • make invoice generation call on "checkout" proceed click & process error without leaving the /checkout page in case of error (that'll allow customer to choose another payment mean)
      • 👀👍 in a general manner, this one seem very fine to me, we only display /order if there's a paid order or an order with a QR Code to display ; otherwhise, we stay on /checkout page and ask customer to change payment mean
@coyotte508
Copy link
Collaborator

We should check the logs to see the real cause of the error

@Tirodem
Copy link
Contributor Author

Tirodem commented Sep 18, 2023

Tell me where I can find them of if I have to trigger the error again for you to monitor it 👌

@coyotte508 coyotte508 added the bug Something isn't working label Oct 26, 2023
@coyotte508
Copy link
Collaborator

You can ssh into the machine and do:

  • pm2 log bootik2 for dev-bootik2 logs
  • pm2 log bootik-instance for dev-bootik logs

@Tirodem
Copy link
Contributor Author

Tirodem commented Feb 4, 2025

@AmadouAgiltoo we'll probably do nothing, I'll explain to you when we'll have time, for documentation purpose and maybe one small monitoring feature

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

No branches or pull requests

2 participants