Getting Error "U16: Risk Threshold Exceeded" in BHIM, Google Pay & Amazon Pay

[jatinyadav25]

Getting U16 error in BHIM, Google Pay & Amazon Pay. Although payment was successfully transferred in Phonepe.

UpiTransactionResponse txnResponse = await UpiPay.initiateTransaction(
amount: "10.00",
app: UpiApplication.bhim,
receiverName: "Birendra Singh",
receiverUpiAddress: "xxxxxxx@upi",
transactionRef: 'ORD4',
transactionNote: 'Test transaction'
);

[drenther]

Probably due to the same reason as #18

[mangeshsvk]

Hi, I am new to flutter but have a good understanding of programming. I was working with embedded c developments before. If you provide me some sort of documentation for this, I would like to contribute to this issue.

[reeteshranjan]

Have you verified that your issue is not related to any of these?

https://www.quora.com/How-can-I-resolve-the-issue-of-risk-threshold-exceeded-from-the-BHIM-app-I-am-not-able-to-do-any-transactions

And this excerpt from https://www.npci.org.in/what-we-do/bhim/faq:

"Why Do I See ‘Risk Threshold Exceeded’?
A user on BHIM can make only 10 financial transactions per day and the total of these transactions cannot exceed Rs. 40,000.

Once you’ve exceeded your daily transaction limit, you’ll receive the ‘Risk threshold exceeded’ notification."

[jatinyadav25]

@reeteshranjan Yes, I verified it was not because of the transaction limit and also tested the same with first transaction of the day; Although payment was successful through Phonepe app but failed in BHIM, Google Pay & Amazon Pay;

[mangeshsvk]

I also noticed editing the amount at the time of payment also does not work. So why don't you break this problem into pieces and try? It's just a suggestion. When the code was running I was able to edit the amount in UPI App which is not possible right now.

1. Like invoke GooglePay using intent and then add payment amount and then try. If that works we can figure a way out.
2. If that also doesn't work don't pass anything just open google pay from the app and try.

[manojsinghal2003]

Please let me know what is the workaround, I am also facing the same issue.

[manojsinghal2003]

Please let us know the plan, I need to fix this issue on urgent basis... if there is no plan to fix, Please highlight so that I can explore other options. Thanks.

[drenther]

This is not an issue that can be fully resolved from our end i.e. not something a plugin can handle.

Feel free to look for alternative.

[manojsinghal2003]

can you suggest any workaround that will help us to fix this?

[drenther]

If you are using this for P2M kind of payment, make sure to pass the correct merchantCode (mcc). For P2P payments, we are already doing what we can and any failure means you will need to actively avoid that app for now.

[drenther]

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.

[reeteshranjan]

Please see and review #17

[drenther]

Addressed in #17. Any further issue on the same ground should be raised separately.

[reeteshranjan]

@jatinyadav25 @mangeshsvk @manojsinghal2003 wanted to add my update as contributor for recent update that includes multiple apps. And add some more data on why this bug is OK to close here.

Based on testing it's very clearly understood that these errors have nothing to do with this package's logic/code. Please see the following:

1. It's seen that when these apps give this error, other working apps payments go through within next 5 minutes, without any bank account specific issue. So the errors reported by these apps do not reflect a real bank account related issue; but it's got to do something with the protocol between the UPI payment app and the banks.

2. The package only provides form-filling data which is seen to be clearly filled in the UPI payment app. The security error reported seems to be due to using non-merchant payments. I am very close to verifying this theory with already some testing done that clearly shows that.

However; if you think that the package must support merchant payments, too, before closing this bug, please feel free to indicate so by re-opening the bug.

[reeteshranjan]

@jatinyadav25 @mangeshsvk @manojsinghal2003 please follow #38

[reeteshranjan]

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

@jatinyadav25 @manojsinghal2003 @mangeshsvk