Fees are charged where they should not

  • Resolved newtimedesignscherrerundgrasso

    (@newtimedesignscherrerundgrasso)


    1 year, 2 months ago

    We have the plugin in use at one of our customers benke.ch. Since about 4 weeks we have the problem that now and then the fee for the payment is booked for an order, although the customer has chosen a payment method that has no fee.

    For most orders (and there are many) it works fine. But with about every 50 orders the fee is suddenly charged even though no payment method with the fee was selected.
    Unfortunately, we can not generate the error even in the frontend and are therefore dependent on help.
    Is this problem known?

    Thank you for your support.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Karolina Vyskocilova

    (@vyskoczilova)

    Hi! I’m really sorry to hear that. May it be the case that the problem failed, customer got back to the payment method and selected different one without the fee?

    The problem with the current approach with WooCommerce fees is that it “doesn’t work on “Pay for order” pages (manually created orders or canceled payments), because of?WC limitations” (as written on the main plugin listing). They take the fee, store it in DB, and keep it with the order, which cannot be changed. I finally got some ideas on how to fix it and will implement it in the new version, but that’s not ready for shipping out.

    Give me your thoughts
    Karolina

    Thread Starter newtimedesignscherrerundgrasso

    (@newtimedesignscherrerundgrasso)

    ello Karolina

    Thank you very much for your quick reply.
    Yes our suspicion is the same. That this happens when the user changes the payment options. Unfortunately this is not traceable. So we are waiting for your update of the plugin and hope that the problem is solved.

    Thanks again for your quick support.

    Plugin Author Karolina Vyskocilova

    (@vyskoczilova)

    Yeah, in this case, it’s a known issue (usually not a problem for many); for this case, the upcoming premium version will solve adding a surcharge as a product instead of adding it as a fee (requires kind a lot of coding).

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fees are charged where they should not’ is closed to new replies.