Problem with Subtotal mismatch behavior after 2.9.1

Hello @dol4ar

No, this is not a known bug, and we have not received any reports regarding this problem in the current update. As a workaround, I recommend downgrading the plugin to version 2.9.0 and checking if the problem persists. You can download the previous version from this link: WooCommerce PayPal Payments v2.9.0.

For us, it would be valuable knowledge to see if the problem persists in that version. If it does, it would suggest that the issue is likely not caused by the plugin update, but rather something else, and this is the only way to verify that.

Please let us know how it goes, and if you have any further questions or need assistance, feel free to reach out.

Kind Regards,

Krystian

Thank you. I will try downgrading to see how it goes.

Can you just tell me the right way to do it? Do I delete the plugin first and then install from the .zip file?

Or I can install 2.9.0 without deleting 2.9.2 so I can keep my settings?

Hello @dol4ar

You can follow these steps:

1. Download the Plugin: Download the package from the following link: WooCommerce PayPal Payments 2.9.0.
2. Go to Your WordPress Dashboard: Log in to your WordPress admin area.
3. Navigate to Plugins: Click on “Plugins” in the left-hand menu, then select “Add New.”
4. Upload the Plugin: Click on the “Upload Plugin” button at the top of the page.
5. Choose the .zip File: Click on “Choose File” and select the downloaded .zip file for version 2.9.0.
6. Install the Plugin: Click on “Install Now.”
7. Activate the Plugin: Once the installation is complete, click “Activate” to enable the plugin.

There’s no need to uninstall the current version (2.9.2) first; your settings will remain intact.

If you have any further questions or need assistance, feel free to reach out.

Kind Regards,

Krystian

Switching to 2.9.0 didn’t help, unfortunately. It may be a conflict with something else that was updated lately but there is no way for me to know that.

The interesting part is that some payments for a certain amount go though sometimes and other times don’t because of subtotal mismatch (as written in order status info). Even though this amount doesn’t require a line for subtotal mismatch in Paypal.

Now I removed the tax percentages which will make calculations easier, and it will probably avoid the problem. We’ll see.

• This reply was modified 1 month, 3 weeks ago by dol4ar.
• This reply was modified 1 month, 3 weeks ago by dol4ar.

Hello @dol4ar

Yeah, it seems the plugin update wasn’t the cause of the issue, but rather some external factor.

Please feel free to update us if you discover the source of the problem, or we can explore other solutions if needed. There must have been some change that triggered this behavior.

Kind Regards,

Krystian

Just to let you know, removing tax calculations didn’t help. There are payments that fail with mismatch. There is no mismatch at all, and not all payments fail, although they have the same total amount.

Is there a log or something in the database about the failed transaction so I can see where this mismatch comes from? I don’t understand, because there is no mismatch at all.

• This reply was modified 1 month, 1 week ago by dol4ar.

Hello @dol4ar

Is there a log or something in the database about the failed transaction so I can see where this mismatch comes from??

Yes. Please note that log files are generated only if the “Logging” feature is activated in your plugin settings. To enable Logging:

• Go to the “Connection” tab in your plugin settings and activate “Logging.”
• Every transaction will now generate a log entry, which you can access by navigating to WooCommerce > Status > Logs.
• Select the most recent “woocommerce-paypal-payments” file corresponding to the date of the transaction in question.

It’s important to understand that if “Logging” wasn’t enabled before, there will be no previous records of the transactions. In that situation, we’ll need to wait for upcoming failed orders to generate new log entries.

Please provide those log entries on our PrivateBin. After uploading, send us the link, so we can review them in detail.

If you do not wish to share this information publicly, we suggest you contact us directly for further assistance. We may need to examine your system report or logs to better understand what’s happening. You can open a ticket with our service desk. Here’s how you can request support: Request Support. Please make sure to include the URL of this thread in your ticket for reference.

Kind regards,
Krystian

Thank you. I enabled the logs now, and we will let you know when we have more information.

I have the log and this seems to be the error message:

Response Body: {“name”:”UNPROCESSABLE_ENTITY”,”details”:[{“issue”:”PAYER_ACTION_REQUIRED”,”description”:”Payer needs to perform the following action before proceeding with payment.”}],”message”:”The requested action could not be performed, semantically incorrect, or failed business validation.

WARNING Failed to capture order. PayPal API response: [UNPROCESSABLE_ENTITY] The requested action could not be performed, semantically incorrect, or failed business validation.

Considering that some payments go through, others don’t I guess it is not caused by failed business validation.

What does “unprocessable entity” mean, actually?

In the order notes the following message appears:

Payer action required, possibly overcharge. Payer needs to perform the following action before proceeding with payment.

Before I removed the tax calculation, I notice another message in the order notes “Item amount mismatch. Items ditched.” which I don’t get now.

Hello @dol4ar

It would be crucial to determine if you can reproduce the order with the same parameters, such as price and products, using a sandbox account on a staging site. This will help us identify which factor triggers the problem.

If you need our assistance, please let us know. You can also open a ticket with our service desk by following this link: Request Support. Be sure to include the URL of this thread in your ticket for reference.

Looking forward to your response!

Kind Regards,

Krystian