Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Observations #31

Open
funsholaniyi opened this issue Dec 27, 2019 · 1 comment
Open

Observations #31

funsholaniyi opened this issue Dec 27, 2019 · 1 comment

Comments

@funsholaniyi
Copy link

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.

@ashinzekene
Copy link
Owner

Hello Funsho, thanks for the feedback. I don't get most of what you said you said

A suggestion will be to have an explicit callback function for each payment status

I will suggest onclose should listen to the modal close event, as it is the default confirm box is in place for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants