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

MiPay does not return proper transaction data #14

Open
reeteshranjan opened this issue Sep 19, 2020 · 2 comments
Open

MiPay does not return proper transaction data #14

reeteshranjan opened this issue Sep 19, 2020 · 2 comments

Comments

@reeteshranjan
Copy link
Collaborator

reeteshranjan commented Sep 19, 2020

The raw response string contains no values for all parameters except the transaction ref which is copied back. An empty transaction ID is hence obtained by the library. This may be a blocker for client applications towards functionality.

@reeteshranjan
Copy link
Collaborator Author

reeteshranjan commented Apr 19, 2021

Like airtel, this package (https://play.google.com/store/apps/details?id=com.mipay.in.wallet&hl=en_IN&gl=US) has been working like this over last 7 months. Please see and review #17 for more.

@reeteshranjan
Copy link
Collaborator Author

@drenther I feel this issue can be closed. To the best I understand the intent and the UPI specs, this behaviour of the MiPay app is not due to any parameters sent in the intent call. It's not a forensic idea though; but just based on the behaviour of several apps covered in my testing.

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

No branches or pull requests

2 participants