• If a customer pays through Sumup’s gateway, after payment confirmation is sent:

    • 2 identical order confirmation emails, with the same ID, to the store owner
    • 2 order confirmation emails to the customer (this causes disruption as the customer is often afraid of having paid twice)
    • the stock of the purchased product is updated twice notwithstanding the quantity of the purchased product is 1. All the process is visible in order notes, inside order page.

    I had reported this issue before and was told that the problem stemmed from Woocommerc and was not your responsibility. This seems very strange to me as all other payment methods work correctly, on this site and all other sites I manage.

    I look forward to your support thank you.

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • I have the exact same issue!

    This causes me even more disruption since my website sells tickets to events with The Events Calendar/Event Tickets: when paying with SumUp Gateway two tickets/attendees are generated and emailed to the customer, the stock gets messed up letting me think that the event is full when in fact is not.

    Interestingly i when was managing order state via code (auto completing virtual orders), it was happening with almost every order. Now i disabled that feature for SumUp gateway and happens more rarely, but still i can not rely on this payment method. Having to keep checking on every order when everything should be automatic is absurd.

    I agree with @aconte91 in believing the issue is on your end, all of my other gateways work with no issues. Just yours keeps duplicating stock, mails and notifications

    I am experiencing the same issue, not always, but most of the times the same email goes out twice.
    Any update on the fix or even they planning on fixing it? This issue is very annoying do we have any workaround?

    • This reply was modified 3 weeks, 2 days ago by tvarga.
Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.