BAD_REQUEST: The order is already paid

  • Resolved Catalin B

    (@catalinbaciu)


    1 year, 4 months ago

    I don’t think this is a bug per se, but a built in feature that is conflicting with how we manage WC orders.

    In order to keep things clean and due to the nature of the business we will often update existing WC orders to add more products instead of creating new orders. Most times people pay only once for their orders so we didn’t encounter the issue up to this point.

    Basically the issue is that someone will pay for an order using a credit card, but then they would like to add more products to the same order. If they try to pay the updated amount using a credit card, Square won’t let them thinking the order was already paid, hence the title of this topic: Square Payment Failed (Status code BAD_REQUEST: The order is already paid.)

    I understand why this is set in place, but in our (and I believe others) case it makes things harder rather than easier.

    Is there a way to allow customers to pay for a WC order twice. The amounts are different, the products on the order are different. In theory the only thing that is the same is the WC order name so they’re not really paying for the same thing twice.

    I have not tested this, but would removing the original Transaction ID from the WC order help? Would it also break anything between WordPress/Square/WooCommerce?

    Any help in finding a fix would be highly appreciated. I couldn’t find the same problem posted on the forums.

Viewing 6 replies - 1 through 6 (of 6 total)

  • Hello @catalinbaciu ??

    Most times people pay only once for their orders so we didn’t encounter the issue up to this point.

    Yes, that would be the typical scenario, generally speaking also.

    Is there a way to allow customers to pay for a WC order twice. The amounts are different, the products on the order are different. In theory the only thing that is the same is the WC order name so they’re not really paying for the same thing twice.

    It is my understanding that a CRM software could be used, in tandem with your WooCommerce store:

    Please let us know if you have any further questions about this matter, or if we misinterpret your concern in any way. We will be happy to help you further.

    Thread Starter Catalin B

    (@catalinbaciu)

    @anastas10s thank you for replying. We already have a CRM, thanks for your recommendation, but my question was related only to the WooCommerce order and Square payments.

    My question was if it is possible to let our customers pay for the “same” WooCommerce order twice. Here’s the customer journey for what I’m referring to.

    1. Customer creates a WC order (WC-001) with 2 products.
    2. Customer pays for the WC order. Square processes the payment as it should.
    3. The WC order (WC-001) is edited in WooCommerce admin, it is set back to pending payment then more products (requested by customer) are added. The WC order will have a new due amount to be paid.
      To clarify, they would be paying for the new products only, they won’t be paying for what they already paid. We add their previous paid amounts as a negative fee so the new due amount is exactly what they need to pay.
    4. The WC order (WC-001) is sent to customer who tries to pays for it, but Square doesn’t allow it because it says the order is the same. While the WC order is the same – WC-001, the products, totals, are not.

    How can we allow the customer to pay for the same WC-001 order (that has different amounts and products)?

    Does clearing the Square transaction ID from the Transaction ID field in WooCommerce order edit screen then updating the order do anything? Would this be enough for Square not to see the order as paid and allow the customer to pay for it?

    If this does work, does it break anything between Square and WooCommerce? Would there be any conflicts?

    Thanks again!

    Thread Starter Catalin B

    (@catalinbaciu)

    @anastas10s it’s been a week and I was wondering if you had a solution to my issue?

    Plugin Support Douglas I. a11n

    (@imodouglas)

    Hi @catalinbaciu, thank you for checking in again. My colleague sent a reply to your previous questions but it looks like it never got you. In this regard, I will share the reply here again.

    In response to your question about clearing the Square transaction ID from the Transaction ID field in the WooCommerce order edit screen and updating the order, it could be a possible workaround, but there might be unforeseen consequences. Before proceeding, you should consider that it might interfere with the synchronization between Square and WooCommerce, possibly leading to issues with tracking and reconciling transactions.

    As an alternative, you may want to look into using the WooCommerce Deposits extension, which allows customers to make partial payments or pay in installments on an order. Moreover, it handles multiple payments for the same order very smoothly.?

    There is also the WooCommerce Order Status & Actions Manager extension that may be useful in this case. This extension gives you more flexibility in managing your orders and their statuses.?

    Another plugin that might be helpful is the WooCommerce Name Your Price plugin, which allows the customers to pay what they want for products. They could pay their outstanding amount using this feature.?

    Please ensure that you thoroughly test any changes to your payment process on a staging or development site before implementing them on your live store.?

    As a reminder, we have a 30-day refund policy during which I encourage you to evaluate the plugins to see if they will fit your needs.

    You can read more about our refund policy on our website here: https://woocommerce.com/refund-policy/

    Please note that it is highly recommended to perform tests on a staging environment before implementing it on your live site. Many hosts provide staging facilities, so it’s worth checking in with them. It’s also possible to do it using the free WP Staging plugin.

    Please let us know if this answers your questions or if you need further assistance.

    Thread Starter Catalin B

    (@catalinbaciu)

    Hi @imodouglas thank you for the reply. I didn’t see @anastas10s ‘s reply on the tread so I had no idea he did reply.

    Yes, he answered my questions. I now know what’s the downside of messing with the Transaction ID field. We’ll have to discuss internally and see what’s the best solution.

    We’ve tried most of the plugins/addons he recommended and they don’t fit nicely with our WC-CRM system.

    Plugin Support Douglas I. a11n

    (@imodouglas)

    Hi @catalinbaciu,

    It is understandable, I noticed the reply did not go through so there is no way you could have seen it. ??

    I am happy to hear that we were able to answer your question but I am sorry to hear that our recommendations do not fit your CRM system.

    In this regard, I believe the internal communication is necessary. Maybe creating a new order and canceling the previous one may be the best next step.

    Please do not hesitate to let us know if you further assistance or clarification with this issue.

    Best regards.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘BAD_REQUEST: The order is already paid’ is closed to new replies.