You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #10013 we explored the required work to implement Multibanco as a new payment method. One of the problems encountered listed in paJDYF-ged-p2 is that our gateway is not ready to handle payments with asynchronous confirmation. This is because in WC_Payment_Gateway_WCPay::update_order_status() we only return a success response when the intent is authorized, or a failure response when there’s an error. So the cart is not cleared and the customer is no correctly redirected to the thank you page when the intent still requires action.
We already have the logic to handle webhooks in place, so we only need to implement a way to finalize the order before the payment is confirmed.
Acceptance criteria
The order is placed correctly even when the intent still requires an action.
Description
In #10013 we explored the required work to implement Multibanco as a new payment method. One of the problems encountered listed in paJDYF-ged-p2 is that our gateway is not ready to handle payments with asynchronous confirmation. This is because in
WC_Payment_Gateway_WCPay::update_order_status()
we only return a success response when the intent is authorized, or a failure response when there’s an error. So the cart is not cleared and the customer is no correctly redirected to the thank you page when the intent still requires action.We already have the logic to handle webhooks in place, so we only need to implement a way to finalize the order before the payment is confirmed.
Acceptance criteria
Testing instructions
Additional context
paJDYF-ged-p2
The text was updated successfully, but these errors were encountered: