Details
Improvement
Major
Description
Please review the thread here: https://www.blesta.com/forums/index.php?/topic/25775-btcpay-payment-module-forces-btc-payment-method-instead-of-allowing-store-to-use-its-default/
Note that Blesta specifies the payment type, so that when the BTCPay server payment screen with QR code appears, the payment type is already defined. This results in a BTCPay invoice being created that expect that payment type. e.g. Bitcoin, or Lightning
Instead, we should use whatever the default Invoice Settings are in the BTCPay server configuration. See screenshot. By default, this is BTC (On-Chain), but can also be Lightning, or another method if so configured.
Blesta should honor the method selected here.
If however, Blesta does not set the method, then the method may chosen by the customer.
So, by default we should honor what is set in the store settings, but perhaps we should make this a gateway configuration option.
- Allow the client to choose payment method (In this case, we simply do not set it ourselves)
- Force store default as configured in BTCPay Server (In this case, we set it to match what is configured)
Activity
Paul Phillips
created issue -
Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
Please review the thread here: https://www.blesta.com/forums/index.php?/topic/25775-btcpay-payment-module-forces-btc-payment-method-instead-of-allowing-store-to-use-its-default/
Note that Blesta specifies the payment type, so that when the BTCPay server payment screen with QR code appears, the payment type is already defined. This results in a BTCPay invoice being created that expect that payment type. e.g. Bitcoin, or Lightning Instead, we should use whatever the default Invoice Settings are in the BTCPay server configuration. See screenshot. By default, this is BTC (On-Chain), but can also be Lightning, or another method if so configured. Blesta should honor the method selected here. |
Please review the thread here: https://www.blesta.com/forums/index.php?/topic/25775-btcpay-payment-module-forces-btc-payment-method-instead-of-allowing-store-to-use-its-default/
Note that Blesta specifies the payment type, so that when the BTCPay server payment screen with QR code appears, the payment type is already defined. This results in a BTCPay invoice being created that expect that payment type. e.g. Bitcoin, or Lightning Instead, we should use whatever the default Invoice Settings are in the BTCPay server configuration. See screenshot. By default, this is BTC (On-Chain), but can also be Lightning, or another method if so configured. Blesta should honor the method selected here. If however, Blesta does not set the method, then the method may chosen by the customer. So, by default we should honor what is set in the store settings, but perhaps we should make this a gateway configuration option. - Allow the client to choose payment method (In this case, we simply do not set it ourselves) - Force store default as configured in BTCPay Server (In this case, we set it to match what is configured) |
| Rank | Ranked higher |
| Story Points | 3 |
| Sprint | 5.12.0 Sprint 5 [ 215 ] |
| Rank | Ranked higher |
| Sprint | 5.12.0 Sprint 5 [ 215 ] | 5.12.0 Sprint 4 [ 214 ] |
| Rank | Ranked higher |
| Assignee | Abdy Franco [ abdy ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 2 hours, 57 minutes [ 10620 ] | |
| Worklog Id | 17687 [ 17687 ] |
| Sprint | 5.12.0 Sprint 4 [ 214 ] | 5.12.0 Sprint 4, 5.12.0 Sprint 5 [ 214, 215 ] |
| Rank | Ranked higher |
