Critical Bugs: Incorrect Transaction ID Handling and Payment Hook Failures

  • Resolved Mudit Kumawat

    (@mudit-kumawat)


    11 months, 3 weeks ago

    Hi,

    This plugin has several bugs. Let me list a few:

    1. woocommerce_payment_complete not firing:
      The plugin does not trigger the woocommerce_payment_complete hook, which is a WooCommerce default. This hook should fire only when the payment is successfully Authorized or Captured. It should not fire if the payment is pending, failed, or not fully authorized/captured.
    2. Incorrect Transaction ID (_transaction_id) Handling:
      The plugin does not save the correct transaction ID in the WooCommerce order (_transaction_id meta key).
      • If a customer makes multiple attempts to complete payment, the plugin saves the first transaction ID (regardless of success or failure).
      • It should only save the successful transaction ID.
      • Because of this error, the payment capture fails later — the system tries to capture payment using an incorrect transaction ID.
    3. Incorrect Handling of _wlop_transaction_status_code:
      The plugin is saving the transaction status code from the first attempt (even if it failed) and does not update it when a subsequent payment attempt succeeds.
      It should always update to reflect the latest transaction status.
    4. Incorrect Handling of _wlop_transaction_id:
      The meta key _wlop_transaction_id should store all attempted transaction IDs (in case the customer tries multiple times).
      Currently, it only saves the first transaction ID.

    Please fix these issues as soon as possible.

    Thanks!

    • This topic was modified 11 months, 3 weeks ago by Mudit Kumawat.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Krystian Syde

    (@inpsydekrystian)

    11 months, 3 weeks ago

    Hello @mudit-kumawat

    Thank you for your report and for taking the time to outline the problems.

    I have passed this information along to our developers for further investigation. Once I receive updates from the team, I will make sure to let you know.

    Kind Regards,
    Krystian

    Syde Joost

    (@joostvandevijver)

    11 months, 2 weeks ago

    Dear @mudit-kumawat,

    Thank you for bringing up the four issues. Our engineering team has reviewed them, and here is a summary of their findings:

    1. Issue with woocommerce_payment_complete Hook:
    We were already aware of this issue (WOL-582 –> internal reference). While it was reproducible and initially investigated, it was not implemented in our last release. However, it is still in our backlog and expected to be picked up sometime in the near future. The reason for the delay is that significant refactoring efforts are required, and it is a rather bigger task.

    2 & 3. Webhooks and Related Issues:
    Recent plugin versions include some improvements that may address these problems. However, some residual issues might still exist. Please ensure you’re running the latest version and verify whether the webhooks function as expected. If this issue persists, please let us know the exact steps you are taking when making multiple payment attempts and the payment method being used, so we can try to reproduce it.

    4. Meta Field (_wlop_transaction_id) Behavior:
     This point is considered more of a product improvement request than a bug. The _wlop_transaction_id meta field was intended for internal use, and we’ve not communicated it as something external systems should rely on. Currently, only the most recent successful transaction ID is stored. If you have a specific business requirement for storing multiple attempted transaction IDs, we’d be happy to consider it as a feature request.

    Please let us know if this helps you further and how you would like to proceed.

    Best regards,
    Joost van de Vijver

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

The topic ‘Critical Bugs: Incorrect Transaction ID Handling and Payment Hook Failures’ is closed to new replies.