Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow Placeholders in redirectURL (i.e.: invoice-id, payment status, etc.)
See original GitHub issueAt the moment the redirectURL is presented after succesfull and expired invoices. While not complying with the specification of the BitPay API documentation (only present on success), we could use it as a universal payment completion URL if we had placeholders in there.
Especially useful would be invoice-id and ´payment-status´ as placeholders to put anywhere in the redirectURL.
Extending the redirectURL with {placeholders} would not break API compatibility to BitPay, but yet would allow the payment completion page to respond to succesfull or unsucesful payments.
For reference, this has been discussed on here.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Working on it
@Kukks Yes that would be possible if I would use some kind of checkout process etc. but like I said I’m mainly using the POS “app” only - with its integrated card. It handles everything and there is no way for me to “intervene” imho and add anything custom like this. It would be possible if I could change any invoice attributes from the IPN via REST API or similar but I didn’t see any possibility of that either, so imho (optionally) adding the invoice ID to redirect URL would be the easiest and cleanest way of solving this.