PayPal assigning wrong upgrade name and not working

beerForo

Well-known member
Affected version
2.3.4
Switched to the new API and some subscriptions have the wrong name, they are of older subscriptions and from another XF instance. Once you get to the checkout page if you click the details it will show the wrong name for the subscription being purchased (for some). If it actually goes through it only goes through for PP and not XF, there is no record of the upgrade in the admin panel and the user is not upgraded. I have a ticket open with full details but was told to start a new bug report, the file edit to PayPalRest.php did not address it.

It's a bit urgent since subscriptions are currently disabled. Thanks
 
If it’s urgent, just switch back to the original PayPal or a different payment processor.

I’m still fairly sure you shouldn’t be seeing this anymore though given the code changes we directed you to make.

I think it was @est3ban129 that originally reported this kind of issue and as far as I know those issues are no longer present.

We will look into it further but going back to a payment method that works in the meantime would be sensible.
 
I’m still fairly sure you shouldn’t be seeing this anymore though given the code changes we directed you to make
It looks like that's a slightly different issue, with this one the names are wrong and the subscription (recurring) does not go through. The issue in that thread mentioned the price as well. For my issue the price is correct but the name is wrong.

So let's say for example on site A I have a $5 sub called Premium.
On site B I have a $10 sub called Upgrade.
What is happening is, someone will check out on site A but the sub is called Upgrade instead of Premium but the price is correct at $5, but it does not go through in XF, only PP.
Also note the wrong name being shown is an older name, as, I edited my subscriptions slightly and it is showing one where the title has since been edited. So it is reading it from a past transaction/current subscription in PP (using Legacy) I presume. Please let me know in the ticket if you need further login details etc. but I left details on reproducing. Thanks!
 
File fix was a partial fix. I uploaded the old file and the prices are all set to the low tier price. They also all have the name of the low tier, but from the wrong XF site. That's the original issue which caused a price mismatch error and no upgrade. Now with the file edit the prices are correct, but the names are not. A few are correct but others still have the wrong name.
 
This is probably because they've already been created as products in PayPal with the wrong parameters. This might not be trivially fixable by us. Can they be edited in PayPal?
 
Of course this doesn't explain why the payments aren't going through on the XF side. That will be a separate troubleshooting bit.
 
Of course this doesn't explain why the payments aren't going through on the XF side
Well I have not had one since the file edit. The first one was the price mismatch error. So they might now just with the wrong name in PP, not sure.
Can they be edited in PayPal?
Apparently products created by API are not visible in PP. I tried a new API instance and also edited the names in XF to see if they took, but no.
 
A little troubleshooting. If I change the price of the misnamed product (upgrade) it fixes it. In the cart now will be the product with correct name but new price. However that is not the price I want to charge so I still can't do anything because even a new product gets appended the wrong parameters once you put that price in. So let's say the messed up product is $5/month but it has the wrong product name (the title references a different XF and subscription). If I change that to $5.01, bam, fixed! In the cart, correct title. BUT, if I take a different user upgrade, one that is correct with no mismatch, and make that one $5/month it adopts the bad title. So the ones that are messed up are locked by the price even if I try to create new ones with that price it takes that title. Hopefully there's way to "clear" this somehow. Thanks
 
I tired adding a brand new upgrade which is fine unless it is the $5/month price and then it shows the same wrong product name that is somehow saved in PP and not editable on their end.

I tried new API and deleting and re-adding the webhooks.

It would seem others may have this issue but not know it yet.
 
There's no reply to my ticket and no one from XF logged into my admin panel to troubleshoot so for now I've reverted to Legacy.
 
Previously, payment via PayPal was ok in XF2.2...
Then I updated to 2.3.4 and it stopped working...
I have the same problem, a member makes a purchase via PayPal, but nothing happens for a member/VIP member.
I have to do it manually.
I'm very ignorant about this.
If anyone has a solution, please let me know.
 
If you changed your gateway from Legacy to the new one, this would likely be related, but if you didn't change anything, it is likely a different issue.
 
Got it...
After the 2.3.4 update I didn't change anything.
I'm a layman.
like PayPal, it's easy to set up, just enter your email (account).
I'll wait for the next VIP member (Paypal).
I'll post the result here soon.


Screenshot_269.webp
 
So as not to confuse the context of this thread, that would be better posted in the troubleshooting forum in its own new thread. This one is exclusively for the new PayPal REST API which was introduced in 2.3. The only change we made to the original PayPal processor is we added (Legacy) to its name.
 
@Chris D any advice on how to "clear" the old product info from being used whenever I create a product at this price? I searched and can't find anything, I don't even think there is a delete product via API option. I would delete them if I could as have not even used them yet since this API created them, but the wrong subscriptions show any time I put the price. I can do a $4.99 sub and it's fine but once I put $5 it reverts to the old wrong product that was saved in PP when this bug was reported.
 
Last edited:
Frankly, I think this issue is more of a PayPal issue at this point than an XF issue.

It is by far one of the most terrible experiences I've had developing any API integrations. The documentation is terrible, the feature set is terrible, and it literally pains me that we have to support it. To be honest, I wish we hadn't bothered implementing it. There's barely any difference between the legacy approach and the new approach -- apart from the fact that one does and has been working flawlessly for 1.5 decades at this point.

Anyway, I will stop the bitter rant now. I would at least try to see if PayPal can redeem themselves by doing anything here.

My best idea at this point is seeing if we can routinely synchronise the current upgrade settings across, including the name, but I'm not even sure at that point if this is possible.
 
It is by far one of the most terrible experiences I've had developing any API integrations. The documentation is terrible, the feature set is terrible, and it literally pains me that we have to support it.
Nothing has changed with PayPal since I last had the misfortune of having to integrate with them then.

1738374041121.webp
 
Back
Top Bottom