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

All UPI apps are failing #18

Closed
yashwp opened this issue Oct 23, 2020 · 23 comments
Closed

All UPI apps are failing #18

yashwp opened this issue Oct 23, 2020 · 23 comments

Comments

@yashwp
Copy link

yashwp commented Oct 23, 2020

The Problem
No matter what UPI app I trigger, it just says, "Maximum limit exceeded...." and the transaction just got failed.
NO ERROR MESSAGE IS LOGGING

Just to cross-check I manually went to GPay & Paytm app to transfer money. It was successful.

@prince-vishal
Copy link

prince-vishal commented Oct 23, 2020

Yes, for me too

"Maximum limit exceeded...."

Just to cross-check I manually went to Amazon Pay & GPay app to transfer money. It was successful.

@prince-vishal
Copy link

@yashwp did you find any solution? or Alternatives?

@yashwp
Copy link
Author

yashwp commented Oct 24, 2020

@prince-vishal Nope.

@drenther
Copy link
Owner

This issue is not related to the library. It is an issue with your merchant account ot incorrect usage of merchant code.

@prince-vishal
Copy link

UPI spec has added a sign parameter, I think you should check it

@drenther drenther reopened this Oct 26, 2020
@drenther drenther added high priority issue bug Something isn't working labels Oct 26, 2020
@drenther
Copy link
Owner

We are looking into it.

@drenther
Copy link
Owner

UPI spec has added a sign parameter, I think you should check it

sign parameter is not something that we can add or do anything about. It is either handled by the acquiring bank or PSP app (in case of intent, which is precisely how this plugin works)

@prince-vishal
Copy link

UPI spec has added a sign parameter, I think you should check it

sign parameter is not something that we can add or do anything about. It is either handled by the acquiring bank or PSP app (in case of intent, which is precisely how this plugin works)

Yes, that's what I don't understand, the PSP app should handle it and add the sign. But I think it is not doing it when invoked using intent. They have also added a mode parameter. I played around with different mode values, but none works

@drenther
Copy link
Owner

Yes, I tried with secure intent. Assuming that's what was needed for the PSP to trigger addition of a digital signature. But it did not work as expected.

@prince-vishal
Copy link

Someone mentioned in another issue that it worked with Phonepe. I didn't get a chance to test that

@drenther drenther pinned this issue Oct 27, 2020
@reeteshranjan
Copy link
Collaborator

reeteshranjan commented Oct 28, 2020

I have tested today with my version as in the pending pull request #17. Things work fine for several apps (Yes Pay, BOB, iCICI, bpay, Cointab, SBI Pay tried), and some apps do not work. Google Pay and Phone Pe gave some vague security error, while other apps successfully did the payment. I am talking about payments initiated on Android through the code in this package. Be reasonable when saying "All UPI apps" are failing. It's misleading especially because you don't mention which apps are failing.

For sake of completeness of argument, my pull request modifies 2 things: 1) does not encode the VPA, and 2) adds mode=00 as per the UPI linking spec. While doing this after going through the UPI linking spec, I did notice that the merchant code and signature are values that needed to be passed; but it is not straightforward, at least for me, to get these values for individual to individual payment.

There is no pandemic going on in UPI yet, is what I can see as of today. I would give some credit to Google Pay and Phone Pe's vague errors, if they really told what the exact issue is. The real security lies at the UPI PIN onwards workflow, and not in making a software call to fill a form to do the same, which is what flutter packages like these are anyway doing. So at best one should not use such vague error giving apps and use others.

@AnandMG02
Copy link

Issue is because of MCC. You need to give correct MCC which 4 digit. If you use merchant code or id in MCC it will give error.

merchantCode: '****',

@AnandMG02
Copy link

Can someone help me with response code we are receiving. Where can we get the list of all response code ?

@drenther
Copy link
Owner

drenther commented Nov 9, 2020

This issue is not related to the library. It is an issue with your merchant account or incorrect usage of merchant code.

I had mentioned this previously as well.

@lzzy12
Copy link

lzzy12 commented Nov 12, 2020

no workaround yet?

@drenther
Copy link
Owner

There is no workaround that can be done from a plugin point of view as of now. I am keeping this issue open so that we don't have duplicate issues opened for the same.

But, we won't be replying to any more comments on status update as there is nothing to update here.

Feel free to add on if you have any findings. But as of now this thread is in "READ-ONLY" mode.

@drenther drenther added wontfix This will not be worked on can not be fixed and removed high priority issue wontfix This will not be worked on bug Something isn't working labels Nov 17, 2020
@reeteshranjan
Copy link
Collaborator

Please see and review #17

@drenther
Copy link
Owner

drenther commented Jun 4, 2021

Closing this since #17 is merged!

@drenther drenther closed this as completed Jun 4, 2021
@drenther drenther unpinned this issue Jun 4, 2021
@reeteshranjan
Copy link
Collaborator

Can someone help me with response code we are receiving. Where can we get the list of all response code ?

Here is the doc that contains all error codes https://github.com/reeteshranjan/upi_pay/files/6338492/PHN6WKI7_UPI_Error_and_Response_Codes_V_2_3_1.pdf. Please note that these are applicable to non app-to-app workflows only; however, somehow they are flowing through the app-to-app workflows that this package implements.

@reeteshranjan
Copy link
Collaborator

@yashwp @lzzy12 @AnandMG02 @prince-vishal please see my comment on a related issue #19 (comment), and indicate your opinion on closing/re-opening this bug.

@reeteshranjan
Copy link
Collaborator

@yashwp @lzzy12 @prince-vishal please follow #38

@lzzy12
Copy link

lzzy12 commented Jul 9, 2021

Sorry I don't have acess to the project where this was needed anymore, can't help

@reeteshranjan
Copy link
Collaborator

Is #38 relevant and important for you?

If yes, could you please respond to my twitter thread with UPI and NPCI handles included in your response asking how these must be solved and how it helps you? https://twitter.com/reeteshr08/status/1488746633068089345

@yashwp @lzzy12 @AnandMG02

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

6 participants