Thanks a lot, this is very helpful to say the least! I have a few follow-up questions to make sure that we’re testing the correct integration:

1. If a valid Greenfield endpoint returns 404, can an invalid/nonexistent Store ID cause that, or should it always return 401/403?
2. What is the minimum API-token permission set required to create a BTC-LN invoice and subsequently verify its payment status?
3. For Lightning invoice creation, is the standard POST /api/v1/stores/{storeId}/invoices endpoint preferable to the direct /lightning/BTC/invoices endpoint?
4. What is the authoritative API response/status we should use to determine that a Lightning invoice has actually been paid?
5. Is there any known limitation with creating and settling real Lightning invoices on the public demo, assuming the Store and wallet are correctly configured?
6. If we provide the exact HTTP method, URL, request body and redacted response we're receiving, can you confirm whether the request is correctly formed?
7. Are there any important considerations around webhooks, invoice expiry, duplicate payments, replay protection or reconciliation that we should account for when using this API?

Thank you again! 🙏🏻