Token fails to update when failed order is paid

  • We use SecureSubmit with WooCommerce Subscriptions, and we have had a long time problem with repeated renewal failures. Even though the customer successfully pays for the failed order with updated payment info, the next renewal will fail again. However, the problem seems to be corrected if the customer goes to My Account and uses the “change payment” button on the subscription.

    I did some testing and it appears to me that the token on the subscription is not getting updated when the payment is put through. I think what is happening is that when it tries to retrieve the new token from the order meta (WC_Gateway_SecureSubmit_Subscriptions::updateFailingPaymentMethod line 293), the value of _securesubmit_card_token for the new order at that point is still set to the old token, which was copied from the subscription. My guess is that updateFailingPaymentMethod is getting called before the new token has been saved to the order metadata. (The way the order meta is being accessed here will also have to be updated for HPOS compatibility.)

    This has led to a lot of hassles for us and our customers. A fix would be greatly appreciated.

    Thanks.

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

  • I have the same problem and came to the same conclusion. A fix would be appreciated. As it is now, I have to go into the database, find the updated token. and attach it to the subscription. It’s annoying. I’ve posted it here and emailed HPS directly. Their reply was basically that they might get around to it eventually…

    Hello everyone,

    We’re currently investigating the issue and will follow up in due course.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Token fails to update when failed order is paid’ is closed to new replies.