Payment methods should be able to control payment status updates through the UI, because manually updating the status does not work well with any payment method.
In the simplest form, we can just add a form of access control: if a payment has no payment method, access is denied. If it does, the payment method plugin decides whether or not to grant access.
A more complex solution would allow plugins to define which statuses the payment can be set to.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | payment_2294413_2.patch | 15.34 KB | xano |
Comments
Comment #1
xanoAs with #2293215: Let payment methods support authorization and capture separately, add an interface that payment methods can implement and that lets them specify whether a payment's status can be updated, and which statuses can be set.
When this is done, remove the warning in the update status form, and consider merging the form with the payment edit form. Consult UX experts to make sure a form of which components are only available under certain conditions is not bad for UX.
Comment #2
xanoComment #4
xano