Subscriptions paid via Paypal set to manual

Hello @dabesa

Sorry for this big delay in our response, it seems this support request was missed somehow.

The reason that we created this setting, is to prevent a subscription from being sold. The default behavior of the plugin used to be: when a subscription is being sold and the payment method is not successfully being vaulted, the initial payment for the subscription will be voided, and the order will fail.
Now, because the vaulting failure occurs on the PayPal server and our plugin has little it can do to prevent or correct this, we decided to add an option, that if the vaulting fails, the plugin will still capture the initial payment manually and set the subscription to manual renewal (or ignore the renewal issue that will most likely occur; 3rd option in this setting).

The vaulting issue is not solved, and we expect this will only be solved when vaulting v3 will be available. This is something that PayPal is working on, and we are waiting for this to become available, so we can use it in our plugin. We have no ETA on this activity, but we hope to get this in the first half of 2023.

Kind regards,
Joost

Hi @joostvandevijver ,

Thanks for the explanation.

How can we recovered a subscription that was set to manual?

We have a customer that tried to pay the renewal with Paypal, and got error all the times.

In the debug logs there was trace of the attempts, but no error.

We cancelled the billing agreement in our Paypal account, but it didn’t change anything.

Thanks

Daniele

Hello @dabesa

As I tried to explain in my previous response, this issue originates on the PayPal server that fails in storing/vaulting the Payment method of the customer. The plugin has the option to not fail this subscription, but set the renewal to manual and capture the initial payment. The only way this subscription can be set to automatic renewal is if the vaulting of the payment method is done successfully, but this is not something our plugin manages, this is purely done on the PayPal server. It is triggered by making a purchase, so a new purchase could trigger this, but it is not clear why vaulting failed to begin with.

You could reach out to PayPal Merchant Technical Support to ask them why vaulting failed, but I don’t expect any answer that will help you resolve this issue. The fix for this issue is expected with vault v3 that I informed you about in my previous response. I understand this is not the response you were hoping for, but at this time there are little other options to resolve this

Kind regards,
Joost

Hello,

Since we did not receive any response or follow-up questions from you and there is not much more we can do for this situation, I will mark this thread as resolved. If you want more information or share more details on this matter, I would advise you to advise reaching out to the support team?directly for more guidance.

Kind regards,
Joost