WordPress WooCommerce升级Sagapay插件后遇Error3097问题求助

Hey Ritaja, let's work through this Error 3097 issue you're hitting after upgrading your Sagapay plugin for PSD2 compliance. The error clearly points to the VPSProtocol value being outside the valid 2.00-3.00 range, which ties directly to PSD2's Strong Customer Authentication (SCA) requirements. Here's what you should check step by step:

1. First, Verify Your Sagapay Merchant Account Settings #

Start with the source of the protocol configuration—your Sagapay backend:

• Log into your Sagapay merchant dashboard. Look for sections labeled PSD2 Settings, SCA Configuration, or Protocol Version (the exact name might vary slightly by region).
• Confirm that the VPSProtocol value is set to something between 2.00 and 3.00 (common valid values are 2.2 or 3.0). If it’s set to a number below 2.0 or above 3.0, adjust it to a valid range and save the changes.

2. Check the Sagapay Plugin Configuration in WooCommerce #

Next, make sure your plugin is syncing the correct protocol value:

• Head to your WordPress admin panel, go to WooCommerce > Settings > Payments > Sagapay.
• Look for a setting like Protocol Version, VPS Protocol, or similar. Ensure this matches the value you set in your Sagapay merchant account, and that it falls within the 2.00-3.00 range.
• Even if the plugin is supposed to pull this setting automatically, sometimes upgrades can break sync—try saving the plugin settings again to force a refresh.

3. Rule Out Plugin Upgrade Compatibility Issues #

If your account and plugin settings look correct, the problem might lie with the upgraded plugin itself:

• Double-check that you’re running the latest official version of the Sagapay plugin, and that it’s listed as compatible with your current WooCommerce and WordPress versions.
• If you have a backup, try rolling back to the previous stable version of the plugin. If the error goes away, that confirms the new version has a bug related to VPSProtocol handling.
• Check the plugin’s official changelog or support forums to see if other users have reported this exact Error 3097. Often, developers will post quick fixes or acknowledge the issue there.
• If the plugin doesn’t expose a VPSProtocol setting at all, it might be hardcoding an invalid value. In this case, reach out to the plugin developer directly to report the bug, or (as a temporary measure only, after backing up your site) search the plugin’s code for references to VPSProtocol and adjust the value to a valid one.

4. Dig Into Transaction Logs for Clarity #

To get more context, enable WooCommerce logs:

• Go to WooCommerce > Status > Logs and find the log file associated with Sagapay.
• Look for the transaction request that failed—check what exact value is being sent for VPSProtocol. This will tell you if the plugin is pulling an incorrect value from your settings, or generating an invalid one on its own.

Start with the first two steps—they’re the most likely fixes for this specific error. If those don’t resolve it, move on to checking the plugin’s compatibility and logs.

内容的提问来源于stack exchange，提问作者user2656743