Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
PatrickRQ Posted June 17, 2023 Posted June 17, 2023 (edited) Hi IPS, Since last 2-3 updates where you touched PayPal/MaxMind code, many customers is unable to pay using their usual PayPal accounts. In logs I find plenty of such: IPS\nexus\Gateway\PayPal\Exception::400 {"name":"INSTRUMENT_DECLINED","message":"The instrument presented was either declined by the processor or bank, or it can't be used for this payment.","information_link":"https://developer.paypal.com/docs/api/orders/v1/#error-INSTRUMENT_DECLINED","debug_id":"82948bc189e09"} Your payment was refused by the payment processor. Please try a different payment method, or contact us for further assistance. Backtrace #0 /srv/www/public_html/applications/nexus/interface/gateways/paypal.php(164): IPS\nexus\Gateway\_PayPal->api() #1 {main} And customers see that Also, logs in the ACP show issue happened to Guest where I am sure, tested it with our client, issue happened to logged it member How come so many PayPal accounts started being refused? Also, in past you printed better information to end-user instead what we see above. You printed actual reason for being unable to pay instead general one that raises questions to us as admins. Hoping for some quick resolution. Edited June 17, 2023 by PatrickRQ The Old Man 1
PatrickRQ Posted June 17, 2023 Author Posted June 17, 2023 P.S. weren't you switched to V3 api? In PayPal logs I see POST /v2/checkout/orders
Stuart Silvester Posted June 17, 2023 Posted June 17, 2023 I would recommend trying 4.7.11, we did update an authorize endpoint to the v2 API instead of v1. It's possible that it may be related to this since the error response mentions the v1 API. REST API v2 is the latest version, v3 does not exist.
PatrickRQ Posted June 18, 2023 Author Posted June 18, 2023 Version 4.7.11 has too many issues from what I observed in forums. About V3, my bad, I meant V1 vs V2. I will try to compare the two versions and update the endpoint manually, without patching to 4.7.11.
Solution Stuart Silvester Posted June 22, 2023 Solution Posted June 22, 2023 We were able to see some other logs and identified the issue. It's specifically related to a customer having their card/payment declined by PayPal then trying to execute the same transaction again. We'll make some changes for a future release, but they still won't be able to purchase if their payment is being declined. PatrickRQ 1
PatrickRQ Posted June 23, 2023 Author Posted June 23, 2023 Was about to post the logs you requested but I assume you do not need them anymore? SJ77 1
Stuart Silvester Posted June 23, 2023 Posted June 23, 2023 2 hours ago, PatrickRQ said: Was about to post the logs you requested but I assume you do not need them anymore? No, thank you. We've got an issue open and we'll improve the handling for this situation in a future release.
PatrickRQ Posted June 27, 2023 Author Posted June 27, 2023 Can you restore in further update more meaningful output message to the payer? Previously it was like this and it was self-explanatory. Now we get many questions why they can't pay. Please restore back to "The instrument presented was either declined by the processor or bank, or it can't be used for this payment." @Stuart Silvester I sent you message. I need urgent fix on the issue, more details in priv.
Stuart Silvester Posted June 28, 2023 Posted June 28, 2023 A fix for this issue will be available soon after testing has been completed.
PatrickRQ Posted July 3, 2023 Author Posted July 3, 2023 (edited) On 6/28/2023 at 12:34 PM, Stuart Silvester said: A fix for this issue will be available soon after testing has been completed. @Matt Can you release a hotfix 4.7.11.2? The 4.7.12 includes many breaking changes so I won't be able to update quickly. I get many doubled payments.. issue is critical, PLEASE Edited July 3, 2023 by PatrickRQ
Recommended Posts