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
I noticed the callback event is not as effective in catching failing payments as the docs describe, and a scenario you might want to consider is Mobile money payment, e.g. MPesa and MTN Ghana MoMo, as flutterwave returns a pending payment payload, and does not mean a payment failure since the user still has to go input their PIN on their phone, thus eventually letting the web hook tell you it's final status
A suggestion will be to have an explicit callback function for each payment status and currently, the onclose event behaves as a better replacement for specifying the callback event.
I will suggest onclose should listen to the modal close event, as it is the default confirm box is in place for now
Overall, great work.
The text was updated successfully, but these errors were encountered:
I noticed the callback event is not as effective in catching failing payments as the docs describe, and a scenario you might want to consider is Mobile money payment, e.g. MPesa and MTN Ghana MoMo, as flutterwave returns a pending payment payload, and does not mean a payment failure since the user still has to go input their PIN on their phone, thus eventually letting the web hook tell you it's final status
A suggestion will be to have an explicit callback function for each payment status and currently, the onclose event behaves as a better replacement for specifying the callback event.
I will suggest onclose should listen to the modal close event, as it is the default confirm box is in place for now
Overall, great work.
The text was updated successfully, but these errors were encountered: