Simple Membership Plugin › Forums › Simple Membership Plugin › Legacy PayPal Hosted Button subscriptions and missing item_number in SWPM 4.8.6
- This topic has 2 replies, 2 voices, and was last updated 3 weeks ago by
zequk.
-
AuthorPosts
-
October 28, 2026 at 10:30 pm #32435
zequk
ParticipantI have been using Simple Membership for approximately 11 years. My original PayPal recurring subscription buttons were created directly in PayPal, following the SWPM documentation available at that time.
After upgrading to SWPM 4.8.6, recurring payments from these existing subscriptions are completed successfully in PayPal, but their IPN notifications fail to be processed by SWPM.
The IPN contains:
–
txn_type=subscr_payment
–payment_status=Completed
–subscr_id=I-...
–custom=subsc_ref=3
–item_name=...However, it does not contain
item_number, and SWPM logs:FAILURE: Error: Empty item number received! Cannot handle this IPN data.The payment is not recorded in the SWPM Transactions list.
I noticed that the SWPM 4.7.7 changelog says the deprecated/legacy PayPal hosted button code was removed. Older SWPM forum examples also show that some Hosted Button notifications with an empty
item_numberwere successfully processed usingsubsc_ref.Could you please clarify:
1. Was support for recurring payment IPNs from existing legacy PayPal Hosted Button subscriptions intentionally removed in version 4.7.7?
2. Is there a supported way for SWPM 4.8.6 to process and record renewal payments from these existing subscriptions?
3. Is there a recommended migration or compatibility workaround that does not require immediately cancelling existing PayPal subscriptions?
4. Are cancellation and payment-failure notifications from these legacy subscriptions affected as well?I would like to preserve existing member accounts and recurring subscriptions while ensuring that payments can be reconciled correctly.
October 29, 2026 at 5:04 am #32436admin
KeymasterHi, Your reading of the changelog is correct, and the log entry you are seeing is expected for subscriptions that were started from buttons created directly in your PayPal account.
1) Was this intentional in 4.7.7?
Yes. Version 4.7.7 tightened the PayPal Standard IPN validation as a security fix (so forged IPN data can’t be used to create or extend memberships), and the old code for PayPal hosted buttons was removed at the same time. Every IPN must now point back to a PayPal button that was created inside the Simple Membership plugin:
– The
item_numbermust be the ID of a payment button created in the plugin.
– Thesubsc_refvalue must match the membership level configured on that button.
– Thereceiver_emailmust match the PayPal email address configured on that button.Your legacy subscriptions don’t send an
item_number, so the plugin has no button to verify them against and rejects the IPN. That is the “Empty item number received” line in your log.2) Is there a supported way to record these renewals in 4.8.6?
Not automatically. PayPal keeps sending the same data for an existing subscription profile, so there is no setting that will make these renewal IPNs pass validation.
The payments are still collected in your PayPal account. Until those subscriptions are moved over, you can apply each renewal to the member’s profile manually: edit the member, set the access start date to the renewal payment date, and make sure the account status is active. This page explains how the expiry is calculated from the access start date:
https://simple-membership-plugin.com/manually-activating-expired-members-account/
3) Migrating without cancelling everything at once
You can move members over gradually, one renewal at a time:
1. Create a PayPal subscription button inside the plugin for each membership level (same PayPal account, same pricing and billing cycle):
https://simple-membership-plugin.com/simple-membership-documentation/#membership-payment-options2. Leave the existing PayPal subscriptions running and reconcile their renewals manually (as explained in point 2).
3. As each member approaches their next renewal date, ask them to log in to your site and subscribe using the new button, then cancel the old subscription from their PayPal account (or you can cancel it from your PayPal account once the new one has started). Because the member is logged in when they pay, the new subscription is applied to their existing member account, so their profile and history are kept.
4) Are cancellation and payment failure notifications affected too?
Yes. The same validation runs on every IPN before the transaction type is checked, so
subscr_cancel,subscr_eot,subscr_failedand refund notifications from these legacy subscriptions are also rejected. Until a member is migrated, their account won’t be updated automatically when they cancel or a payment fails. Please keep an eye on these events in your PayPal account and update the member’s account status manually when needed.Let me know if you have any questions.
October 30, 2026 at 1:13 am #32437zequk
ParticipantThank you very much for your detailed and helpful explanation.
Your reply has clarified why the renewal and cancellation notifications from my legacy PayPal subscriptions are being rejected in SWPM 4.8.6. I now understand that this is related to the security changes introduced in version 4.7.7, rather than a configuration mistake on my part.
I have also confirmed that both renewal and cancellation notifications from these legacy subscriptions result in the same “Empty item number received” error, and that the corresponding member records remain unchanged.
Your explanation has helped me understand the situation and plan how to manage my existing members going forward. I really appreciate you taking the time to explain the technical details and suggest practical options.
Thank you again for your support!
-
AuthorPosts
- You must be logged in to reply to this topic.