Help migrating from paypal checkout for subscriptions

Hello @kattouf

Our subscription migration layer within PayPal Payments is designed to allow for the automatic renewals of existing PayPal Checkout subscriptions by taking over the subscription renewals once PayPal Checkout is no longer active. After disabling the PayPal Checkout Gateway, there should be no additional steps required on your part for this migration.

To confirm that the process was successful after disabling PPEC, go into the subscription and check the “Payment method.” It should be listed as PayPal Legacy. The screenshot below shows a subscription that was originally purchased through PPEC and is now being processed by PCP.

However, in some edge cases due to recent updates and the implementation of Vault v3, the migration of subscriptions from PayPal Checkout Gateway (PPEC) to WooCommerce PayPal Payments Gateway (PCP) is not functioning for some users at this moment. The solution, for now, is to continue processing subscriptions through the PayPal Checkout plugin.

To verify if this is the case for you, please open a ticket with our service desk. You can request support here: Request Support. Be sure to include the URL of this thread in your ticket for reference.

I’m looking forward to your response.

Kind regards,
Krystian

Thanks! good to know about the Paypal Legacy. It does not show that for me. If i deactivate the Checkout plugin, it shows Manual Renewal

These are imported subscriptions using the CSV importer/exporter. They work 100% otherwise.

I studied the plugin code and i see it looks for the ppec_paypal meta value and created a mock gateway. Here is one meta record:

https://ibb.co/fdCPyzs
It’s possible they are missing a specific meta value that plugin looks for.

When you say “is not functioning for some users at this moment” do you mean it won’t show “Legacy” or it won’t process the order? (probably both) maybe step one is to get it to detect the subscriptions correctly? (i’m not using new order tables)

I’ll open a ticket as suggested as well

thanks

/J

Hello @kattouf

These are imported subscriptions using the CSV importer/exporter. They work 100% otherwise.

That’s the problem. PayPal Payments scans all subscriptions to find any with the ppec-paypal payment method. Then it stores a transient with the result for 30 days:
_transient_ppcp_has_ppec_subscriptions

When this transient is set to false and you only import the subscriptions afterward, then the subscription migration layer will not be active because the last time the plugin checked there were no subscriptions to migrate. So all you must do for the migration layer to initialize is change the transient to true or delete it so it gets recreated with true.

When you say “is not functioning for some users at this moment” do you mean it won’t show “Legacy” or it won’t process the order? (probably both) maybe step one is to get it to detect the subscriptions correctly? (i’m not using new order tables)

When updating the transient, the payment method of the subscription will switch from “Manual renewal” to “PayPal (Legacy)”, but it won’t be possible to process the order. It will stay at “Pending Payment” without any log indicators for the renewal process.

We have an open issue for this, and our QA team is currently investigating. I assigned this ticket to the issue and to update you once it is resolved.

Kind regards,
Krystian

Thank you!

Changing the transient cache to true resolved the payment type issue!
But I’ll will wait to process those with PP Payment,

thanks

/J

Hello @kattouf

In connection with your ticket, I have added it to an issue related to “Subscriptions migrated from PPEC fail to renew with PCP after Vault V3 implementation in version 2.5.0.”

It looks like we’ve managed to resolve the issue with migrating subscriptions from the WooCommerce PayPal Checkout Payment Gateway to the PayPal Payments plugin. We’ve created a package that should fix this problem, and the update will also be included in the upcoming plugin update in the next two weeks.

You can install the package like any other plugin: Subscription Migration Package.

For more information about the problem you can check the pull request here: PR #2699.

Let us know if the issue persists after installing the package. If you have any questions, feel free to reach out.

Kind Regards,
Krystian