- Issue created by @rszrama
Right now, if you have a malformed checkout flow configuration or a checkout flow that was configured without a payment process pane, the return handler will generate error messages when it attempts to load the configuration to determine if it should capture or not. In practice, this scenario should never exist, but we should make it fault tolerant in case a site does attempt to use this module with a different checkout flow type.
Active
2.0
Code