You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have subs with paypal billing agreements from an old site (cratejoy), that we're trying to migrate onto our woocom site. Our paypal account has reference transactions enabled.
It seems the paypal payments plugin has different data requiements to what is written in this guide. Due to vaulting it seems to need a paypal payment_token_id.
In the woocom guides it says this new paypal plugin has a migrate layer that can migrate paypal subscriptinos from the old paypal checkout plugin. So we tried using your plugin to import them into the old paypal checkout plugin first. That failed as well. The error we got is:
So maybe paypal checkout has stopped working and we can't input data in there?
Another question is, is there a way to generate payment token ids from billing agreements. As perhaps that migration could work?
The text was updated successfully, but these errors were encountered:
We went through PayPal Braintree and other testing to determine this isn't possible. So we couldn't migrate.
We're letting them churn out and encouraging to move site.
We have subs with paypal billing agreements from an old site (cratejoy), that we're trying to migrate onto our woocom site. Our paypal account has reference transactions enabled.
It seems the paypal payments plugin has different data requiements to what is written in this guide. Due to vaulting it seems to need a paypal payment_token_id.
In the woocom guides it says this new paypal plugin has a migrate layer that can migrate paypal subscriptinos from the old paypal checkout plugin. So we tried using your plugin to import them into the old paypal checkout plugin first. That failed as well. The error we got is:
So maybe paypal checkout has stopped working and we can't input data in there?
Another question is, is there a way to generate payment token ids from billing agreements. As perhaps that migration could work?
The text was updated successfully, but these errors were encountered: