Paypal IPN POST variables randomly return item_number or item_number1

Paypal over the past few days accidentally began to return the POST variable from item_number1 instead of item_number and the same thing for item_name. I read on the Paypals website that they do this when it is a shopping cart transaction (multiple items). These are instant payments for Wi-Fi access of one item, so I'm not sure why, after several years of work, without seeing this, he unexpectedly started by accident. In the returned data for the IPN listener, I also get "num_cart_items = 1" if it sent "item_number1". Thus, it is definitely considered that some transactions are goods for purchases. Is there any way to stop this?

+5
source share
4 answers

Similar here. I am temporarily considering a problem with the following:

if (!$_POST['item_number']) { $_POST['item_number']=$_POST['item_number1']; } 

I still wonder why he accidentally changes item_number to item_number1, and there were no notifications or announcements for this. I had half the orders, and half not, and although this is a PayPal IPN problem, not my file!

+3
source

The same thing here. Started yesterday with random behavior. I am not interested in such "shopping cart" features, so I changed my ipn receiver to scan the first available "item_number".

+2
source

find "item_number1" if "item_number" does not exist

this page links to item_number in paypal docs https://developer.paypal.com/docs/classic/ipn/integration-guide/IPNIntro/

This page links to item_numberx https://developer.paypal.com/docs/classic/ipn/integration-guide/IPNandPDTVariables/

so annoyed with paypal! and it’s so hard to put up with paypal because you can’t even find a transaction by item_number or order order ...

+1
source

I noticed that yesterday (July 13) today it works well. Anyway, I fixed the code check, it performs two variables. It could be a joke from paypal, tomorrow it could be $ _POST ['item_number69']: D

0
source

Source: https://habr.com/ru/post/1269774/


All Articles