IPN custom data got truncated

[blenderkit]

Recently I have got 4 payments where the IPN returned with truncated `custom` field.
I did create the (unencrypted) form with data like:
'custom': '{"user_plan_id": 310606, "plan_id": 1, "pricing_id": 1, "first_order_id": 43102, "user_email": "xxxxx(at)gmail.com"}

But i am receiving IPN with only ...&custom={&... in URL, so I can't pair the payment with the data in DB.

This works with hundreds of other payments with similar custom data and other parameters.

The failing IPNs are:

Date/time created Message ID Status Transaction ID

	5/3/2022 07:06 GMT+02:00	23X80668VS1556215	Retrying
	4/30/2022 16:21 GMT+02:00	3NR23369AR442640C	Retrying	46J959475M8289213

Date/time created Message ID Status Transaction ID

4/30/2022 04:13 GMT+02:00	8C014498NH901141N	Failed	14T934894D440894P
4/28/2022 20:38 GMT+02:00	367819057P906601F	Failed	8BF56020KR350933C
4/23/2022 14:03 GMT+02:00	59U481102W9491943	Failed
4/23/2022 13:33 GMT+02:00	2AR24010BS3706318	Failed	3W9833688E559341J

[JTTD]

I've got exactly the same problem.

After extensive research, we have concluded that Paypal is occasionally truncating the IPN, and it is causing issues with payments for subscriptions on our site ( its not sending the complete gateway ID ) . 

Our issue started the same month as yours, May 2022. We have had a ticket open for a couple of weeks but no resolution yet.

[NimL]

Anyone got a solution for this?

Is there a way to get PayPal involved?

[JTTD]

I have a ticket open with PayPal for over a month now, I keep bumping it and they keep telling me they are looking into it.

I'll update here if I hear anything back.

[NimL]

@JTTD is the data you are sending also happen to be JSON encoded?

I wonder if that is the common denominator, and we can fix it by encoding the value with, let's say, base64.

[JTTD]

I'm not a developer, so I can't help you.

But I can tell you the messages are sent by a very popular membership plugin - memberpress . We haven't had an issue with it since June, so I'm not sure if it's something Paypal fixed or not.