Latest Update (2.5.0) Causing Error: NOT_ENABLED_TO_VAULT_PAYMENT_SOURCE

Just started happening to me as well.

I do not see any settings in the backend for “Vault”.

Is this actually a PayPal problem?

• This reply was modified 10 months ago by jmunsonii.

Happened on the 2 of my sites that use PayPal. Support at PayPal knew nothing about it and I wasted too much time before checking here. Rolled back like the parent and it is working again.

Here is the implementation (I believe) that is causing the problem:

• Enhancement – Enable Vault v3 and Card Fields by default for US merchants #1967
• Enhancement – Vault v3 WC Subscriptions integration #1920

Replying here: had same issue: Downgrade to 2.4.3 and it is magically resolved. Very frustrating! I followed step in https://kinsta.com/knowledgebase/download-older-versions-of-wordpress-plugins/#repository go to plugin home page > Advanced View > scroll to the bottom: download old version ZIP of 2.4.3. Delete 2.5.0 from website. Upload 2.4.3. Re activate. Fixed.

ARGH

WP Rollback is a handy tool! Addressed the problem for now.

Hello @hollysieck

Our team has acknowledged this and a bug request has been created for our developers to investigate and resolve. Downgrading the plugin to the previous version is a correct solution. We apologize for any inconvenience this might have caused.

We are committed to resolving this issue promptly and will keep you updated through this thread with any new information regarding a fix or a workaround.

In any case you can download the stable version from the following link: WooCommerce PayPal Payments Plugin Version 2.4.3

Kind Regards,

Krystian

commenting for updates.

Yes something has to be done about this.

Also following for updates—I updated to 2.5.0 right before a customer tried to order and I spent hours trying to figure out the issue until I saw this post.

Hello all,

we have reverted to the previous version to avoid this situation to cause any more problems. We will further investigate this issue now and do a new release when we have resolved this issue. The current 2.5.1 release is the same version as 2.4.3, but this is done to minimize the damage.

I am confident our developers will get this sorted soon and get the fixed release out ASAP. We will keep you up to date on this.

Kind regards,
Joost

Hello All,

quick update: we are testing the fix for this issue that should be added to the release 2.5.2. We expect that a beta becomes available today or tomorrow here and the official release to pushed out on Monday. This is of course only happening if testing is done successfully, so we cannot promise anything at this moment. If you decide to test the beta, please share your findings with us.

Kind regards,
Joost

Gone round and round trying to fix… reverted and it works now.

This problem has already been resolved in the latest version 2.5.3.

Since we have not received any further communication from you, we are assuming that your issue have been resolved.

Therefore, we mark this thread as resolved. If you still have any questions or if a new problem arises, don’t hesitate to open a new thread or reply to this one. We are here to help at any time.

Kind regards,
Krystian

Running version 2.5.3 and got this problem…

“NOT_ENABLED_TO_VAULT_PAYMENT_SOURCE The API caller or the merchant on whose behalf the API call is initiated is not allowed to vault the given source. Please contact PayPal customer support for assistance.”

This started for us on the 6th Feb, 3 days ago, auto-updates on.
I’ve rolled back to 2.4.3 which has fixed it.

Interestingly I have two sites using WPP, the other one is using 2.5.3 and seams to be working fine. not sure what the difference might be.