Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Contributor angelleye

    (@angelleye)

    The standard option does not send over itemized details, so that’s why you’re not getting the error there.

    Looking at this log I can see that the values simply aren’t adding up, which is why PayPal is returning this error. I’m not familiar with the deposit plugin, so I can’t support that, unfortunately.

    What I’m seeing, though, is that the item on the cart was 45.00, but then the subtotal sent (which is the PAYMENTREQUEST_0_ITEMAMT parameter) is only 10.00. Then you’ve got 30.00 for shipping, but still only sending 10.00 for the grand total.

    PayPal’s system is not going to accept that sort of thing when sending line items like we’re doing here in Express Checkout. You’re going to need to make sure that ITEMAMT + SHIPPINGAMT + HANDLINGAMT + TAXAMT = AMT in order for it to work.

    You’re the first to bring this sort of thing to my attention, but the only way I can fix it would be to add an option in the plugin where you can specify whether or not you want to include itemized details with the Express Checkout request. In your case you would disable item details and that would fix this problem, but then you wouldn’t have those nice details available inside the PayPal account. They would still be available in WooCommerce, of course.

    I’m going to go ahead and add that as a feature update on my list for future releases of the plugin. I can’t say for sure how long it’ll be before I get it done, though.

    Sorry I don’t have a better immediate answer.

    Thread Starter jeffreyd000

    (@jeffreyd000)

    That is a great and helpful answer, I thank you for your willingness to support this in the future.

    Mate please I just discovered that I receive this error 10413 anytime 2 products or more are in the cart. Paypal express would revert back to the checkout page. Please is there any fix around it?

    Plugin Contributor angelleye

    (@angelleye)

    @poola,

    There must be something more going on than just 2 items added to the cart. Are you using a discount plugin of any kind, or are people using a coupon code when this happens by chance?

    Do you have logging enabled in the plugin? I’d like to get a look at the log file saved at /wc-logs on your server.

    I have seen the problem. if I add two or more items, the total is always different to the item amounts.

    Example, I added two items selling for 15.63. Instead of 31.26, the total is showing 31.25.

    Please do you know how I can correct it to show the correct amount?

    Plugin Contributor angelleye

    (@angelleye)

    So you’re not using any discounts at all? That typically only happens if the calculation wound up being something like 31.256666 or something like that, but then the WC system just chopped off the end instead of truly rounding. That typically only happens when there is percentage discounts involved one way or another. So you’re saying that nothing like that is going on?

    I am using opencart a customer email us that when he purchased an item and when he click on checkout button the page did not redirect to paypal and an error show which is ” The totals of the cart item amounts do not match order amounts. ” and order cant be placed .

    so i check it and i noticed that below $1000 usd order placing properly but when we order of $1000 or grater this error ” The totals of the cart item amounts do not match order amounts.” come and order did not place can any one tell about this problem ?

    Plugin Contributor angelleye

    (@angelleye)

    This thread is for support of our PayPal for WooCommerce plugin. Sounds like you’re using an entirely different solution.

    I can tell you that the amount being greater than $1k would not cause the problem. You must have something else going on that’s causing the request to so invalid values at that point. You would need to get a look at a sample of your API request log to see what might be causing this.

    I could help you more directly, but I would need you to submit an order for general consulting on my site.

    I am also getting the same error on this. What I believe is causing this is that I have a free sample that does charge $1.99 for shipping. Paypal does not seem to like this. This is using PayPal Website Payments Pro (DoDirectPayment). It works fine on other quantities of the item that do charge, but the free one gives the 10413 error. I changed the price to a penny and it worked fine so it must be the free part. Any idea on how to fix this?

    Plugin Contributor angelleye

    (@angelleye)

    @vjamesv, PayPal will not accept a $0 ITEMAMT, which is what it sounds like you’re getting. Unfortunately, the only way to do the sort of thing you’re trying to do would be to create a line item called shipping and set the shipping amount there instead of in the actual shipping field that WC provides.

    In the next update we will have the option to simply eliminate sending line item details to PayPal altogether, so that will allow you to do what you’re trying to do, but then you wouldn’t be able to see any line item details in the PayPal transaction details.

    Now that I have somebody working full time on this plugin you’ll start seeing more consistent updates, but it may be another couple of weeks before 1.1.6.3 is released.

    If you want to get it working before then you could edit the plugin code directly to exclude line item details in the PayPal request. If you need help with that you can submit an order for premium support and I could take care of it for you.

    Wow, thanks for the fast response! It sounds like this will be taken care of in the next update, so that will be fine. What file should I look in though if I want to try and fix this myself before then?

    Plugin Contributor angelleye

    (@angelleye)

    For Express Checkout it would be /paypal-for-woocommerce/classes/wc-gateway-paypal-express-angelleye.php

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Error Code: 10413 – cart item amounts do not match order amounts’ is closed to new replies.