Try to create an invoice with v1 server

Oct 13, 2025 by magicalceylontours.com 134 views

BUG: v1.0.0rc8 using lnbits v0.12.12 as funding source returns error when creating invoice due to key mismatch

Introduction In this article, we will discuss a bug that occurs when using lnbits v0.12.12 as a funding source to lnbits v1.0.0rc8. The bug results in an error when attempting to create an invoice, due to a key mismatch between the two versions.

Describe the Bug When using lnbits v0.12.12 server as a funding source to lnbits v1.0.0rc8, attempting to create an invoice returns an error. This bug is a critical issue that affects the functionality of the lnbits v1.0.0rc8 version.

To Reproduce To reproduce this bug, follow these steps:

Spin up v1.0.0rc8: Start the lnbits v1.0.0rc8 server.
Use v0.12.12 server as funding source: Configure the lnbits v1.0.0rc8 server to use the lnbits v0.12.12 server as a funding source.
Try to create an invoice with v1 server: Attempt to create an invoice using the lnbits v1.0.0rc8 server.
See 520 error: The server will return a 520 error.

Expected Behavior The expected behavior is that the server should return an invoice.

Screenshots

Desktop (please complete the following information):

LNbits version: v1.0.0rc8
Database: sqlite

Additional Context The error seems to be due to "bolt11" not being in the dict. The v1.0.0rc8 version replaces payment_request with bolt11. The code snippet below shows the difference between the two versions:

- if r.is_error or "payment_request" not in data:
+ if r.is_error or "bolt11" not in data:
      error_message = data["detail"] if "detail" in data else r.text
      return InvoiceResponse(
          False, None, None, f"Server error: '{error_message}'"
      )

The code snippet above shows that the v1.0.0rc8 version checks for the presence of "bolt11" in the data dictionary, whereas the v0.12.12 version checks for the presence of "payment_request".

Conclusion In conclusion, the bug occurs due to a key mismatch between the two versions. The v1.0.0rc8 version replaces payment_request with bolt11, but the v0.12.12 server does not return the "bolt11" key in the data dictionary. This results in a 520 error when attempting to create an invoice.

Fix To fix this bug, the v1.0.0rc8 version should be modified to check for the presence of "payment_request" in the data dictionary, instead of "bolt11". This can be achieved by changing the code snippet above to:

- if r.is_error or "bolt11" not in data:
+ if r.is_error or "payment_request" not in data:
      error_message = data["detail"] if "detail" in data else r.text
      return InvoiceResponse(
          False, None, None, f"Server error: '{error_message}'"
      )

By making this change, the v1.0.0rc8 version will be able to correctly handle the response from the v0.12.12 server, and the bug will be resolved.

Related Issues This bug is related to the following issues:

link
link

Commit Message The commit message for this fix should be:

Fix bug: v1.0.0rc8 using lnbits v0.12.12 as funding source returns error when creating invoice due to key mismatch

API Documentation The API documentation for this fix should include the following information:

Endpoint: /api/v1/payments
Method: POST
Request Body: {"payment_hash": "c43fd3f069dc0504b96be1f29b4418b26c4c6787797d4220d0b62c7f104e9eb0", "payment_request": "lnbc1u1pnumcg4pp5csla8urfmszsfwttu8efk3qckfkyceu80975ygxskck87yzwn6cqdq2f38xy6t5wvcqzzsxqrrsssp54jyvpd7znqzyt3vpmq8290fas0syth7xp8sau7lurqt88exh2uyq9p4gqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqpqysgqagqdna9nmhjhqkcmfj9h2r6zyxptzevg7fnyp2fc797s02pp05jrlwac0d8la5kvr80s3lkcxew53tcua2c659w85sun9xtjd8a6r3qqrv7fjp", "lnurl_response": null, "checking_id": "c43fd3f069dc0504b96be1f29b4418b26c4c6787797d4220d0b62c7f104e9eb0"}
Response: {"payment_hash": "c43fd3f069dc0504b96be1f29b4418b26c4c6787797d4220d0b62c7f104e9eb0", "payment_request": "lnbc1u1pnumcg4pp5csla8urfmszsfwttu8efk3qckfkyceu80975ygxskck87yzwn6cqdq2f38xy6t5wvcqzzsxqrrsssp54jyvpd7znqzyt3vpmq8290fas0syth7xp8sau7lurqt88exh2uyq9p4gqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqpqysgqagqdna9nmhjhqkcmfj9h2r6zyxptzevg7fnyp2fc797s02pp05jrlwac0d8la5kvr80s3lkcxew53tcua2c659w85sun9xtjd8a6r3qqrv7fjp", "lnurl_response": null, "checking_id": "c43fd3f069dc0504b96be1f29b4418b26c4c6787797d4220d0b62c7f104e9eb0"}
Q&A: v1.0.0rc8 using lnbits v0.12.12 as funding source returns error when creating invoice due to key mismatch

Q: What is the bug that occurs when using lnbits v0.12.12 as a funding source to lnbits v1.0.0rc8? A: The bug occurs due to a key mismatch between the two versions. The v1.0.0rc8 version replaces payment_request with bolt11, but the v0.12.12 server does not return the "bolt11" key in the data dictionary.

Q: What is the expected behavior when creating an invoice using lnbits v1.0.0rc8 with v0.12.12 as a funding source? A: The expected behavior is that the server should return an invoice.

Q: What is the error message that is returned when attempting to create an invoice using lnbits v1.0.0rc8 with v0.12.12 as a funding source? A: The error message is a 520 error.

Q: How can the bug be reproduced? A: To reproduce the bug, follow these steps:

Spin up v1.0.0rc8
Use v0.12.12 server as funding source
Try to create an invoice with v1 server
See 520 error

Q: What is the fix for the bug? A: The fix is to modify the v1.0.0rc8 version to check for the presence of "payment_request" in the data dictionary, instead of "bolt11".

Q: What is the commit message for the fix? A: The commit message for the fix is: Fix bug: v1.0.0rc8 using lnbits v0.12.12 as funding source returns error when creating invoice due to key mismatch

Q: What is the API documentation for the fix? A: The API documentation for the fix includes the following information:

Endpoint: /api/v1/payments
Method: POST
Request Body: {"payment_hash": "c43fd3f069dc0504b96be1f29b4418b26c4c6787797d4220d0b62c7f104e9eb0", "payment_request": "lnbc1u1pnumcg4pp5csla8urfmszsfwttu8efk3qckfkyceu80975ygxskck87yzwn6cqdq2f38xy6t5wvcqzzsxqrrsssp54jyvpd7znqzyt3vpmq8290fas0syth7xp8sau7lurqt88exh2uyq9p4gqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqpqysgqagqdna9nmhjhqkcmfj9h2r6zyxptzevg7fnyp2fc797s02pp05jrlwac0d8la5kvr80s3lkcxew53tcua2c659w85sun9xtjd8a6r3qqrv7fjp", "lnurl_response": null, "checking_id": "c43fd3f069dc0504b96be1f29b4418b26c4c6787797d4220d0b62c7f104e9eb0"}
Response: {"payment_hash": "c43fd3f069dc0504b96be1f29b4418b26c4c6787797d4220d0b62c7f104e9eb0", "payment_request": "lnbc1u1pnumcg4pp5csla8urfmszsfwttu8efk3qckfkyceu80975ygxskck87yzwn6cqdq2f38xy6t5wvcqzzsxqrrsssp54jyvpd7znqzyt3vpmq8290fas0syth7xp8sau7lurqt88exh2uyq9p4gqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqpqysgqagqdna9nmhjhqkcmfj9h2r6zyxptzevg7fnyp2fc797s02pp05jrlwac0d8la5kvr80s3lkcxew53tcua2c659w85sun9xtjd8a6r3qqrv7fjp", "lnurl_response": null, "checking_id": "c43fd3f069dc0504b96be1f29b4418b26c4c6787797d4220d0b62c7f104e9eb0"}

Q: What are the related issues for this bug? A: The related issues are:

link
link

Q: What is the solution for the bug? A: The solution is to modify the v1.0.0rc8 version to check for the presence of "payment_request" in the data dictionary, instead of "bolt11".