Each time the paystack opens canGoBack is false and the app cannot route back to the app like it is in Flutterwave. The implication is that if the modal fails to connect to paystack gateway and brings something like net::err_blocked_by_response instead of the paystack payment UI, the app becomes stuck until one closes the app and relaunches it. This is not good UX
Describe the solution you'd like
There should be a way to snap out of the paystack modal if the modal fails at every point.
Describe alternatives you've considered
An alternative is to always make sure the modal launches the paystack payment UI, that can probably be some local components
Each time the paystack opens canGoBack is false and the app cannot route back to the app like it is in Flutterwave. The implication is that if the modal fails to connect to paystack gateway and brings something like net::err_blocked_by_response instead of the paystack payment UI, the app becomes stuck until one closes the app and relaunches it. This is not good UX
Describe the solution you'd like There should be a way to snap out of the paystack modal if the modal fails at every point.
Describe alternatives you've considered An alternative is to always make sure the modal launches the paystack payment UI, that can probably be some local components