-
Notifications
You must be signed in to change notification settings - Fork 6
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
Payment STAGE - When I click failure button it is cancelling the order #1
Comments
Hi Santhosh, Not sure if this still helps you, but here's how we have solved these two problems on our side. We had to modify the source code.
Solution: Paytm plugin source code does that, so we commented it (file: PaymentPaytmController.cs)
Solution: paytm does not allow paytment retry on the same order number. Hence, when sending the order number to paytm, we attach a random 8 digit after a hiphen everytime. When the data is returned from paytm, we remove that random 8 digit and hiphen on our side. a) add 8 characters to orderid in file: PaytmPaymentProcessor.cs `
... b) remove code in file: PaymentPaytmController.cs `... //This code ensures that if OrderId was generated to include a random 8 characters in the end with a "-" separator string orderIdx = parameters["ORDERID"]; if (orderIdx.Contains("-")) #endregion Hope this helps. @LalitChaudhary1 @MayankGupta1 Please note and suggest if there is a better way to do this. |
Thanks for the comments, Can you please share source code for 4.3 |
Dear All,
I have integrated the 4.3 version into my nop commerce application. I have configured the Paytm STAGE keys to complete the testing process.
Issue: It goes to payment screen successfully and Paytm asks two options (Failure / Success) , when I choose Failure it is cancelling the order on its callback method. And we could not able to do the re-pay. Please help how to set the current as failure instead of cancel so that user can try re-pay.
Also Please upload source code for 4.3 paytm plug in code.
Thanks in Advance
The text was updated successfully, but these errors were encountered: