Ordergroove will retry all payment requests that return a 140 error response a set number of times based on your store settings. The first retry will take place 3 days after the initial attempt, and the last retry will take place 3 days after the first retry attempt. The customer will receive an email trigger to update their payment method between attempts (pending setup in Ordergroove). You must ensure the 140 response is correctly mapped for your order placement endpoint. If all retries fail or the customer clicks send now for the same item(s), the original order is marked as rejected.
If you do not want an order to be retried with this flow, you will need to use the 160 error response which indicates no retries should be attempted.
Note: Ordergroove may cancel the customer's subscription after repeated rejections based on Disengaged Subscriptions configurations.
Please refer to the detailed flowchart below for additional context. Click here for the full-size resolution.
What happens when a customer updates their credit card?
When a customer updates their credit card, Ordergroove immediately re-attempts payment on any of that customer's orders that are already in the retry flow, rather than waiting for the next scheduled retry attempt. This behavior is called Auto Retry.
As of July 22, 2026, Auto Retry is the standard behavior on all Ordergroove accounts. It was previously available only in Early Access.
With Auto Retry, Ordergroove attempts payment as soon as the customer successfully updates their payment method—restoring the subscription sooner rather than waiting for the next scheduled attempt.
If the payment succeeds, the subscription resumes its normal lifecycle. If it fails, the order continues through the standard retry schedule described above.
Auto Retry only applies to orders that are actively in a retry state. Orders that have already exhausted the retry flow and been marked as rejected are not affected, and your standard retry rules and payment safeguards continue to apply.
Now that Auto Retry is standard, here's what to check
Ordergroove doesn't send customers any notification when Auto Retry runs, and it now applies to every way a payment method can be updated—the customer portal, frictionless card updates, and updates your support team makes on a customer's behalf. A few things to review:
Remove "Send Now" prompts from your customer communications. If any of your payment-failure or card-update emails ask customers to click Send Now to reprocess their order, remove that step. Auto Retry now re-attempts payment automatically the moment the card is updated, so a manual Send Now afterward can create a duplicate order the customer didn't want.
Disable any custom retry workflows. If you listen for payment-update webhooks and trigger your own Send Now (or another retry mechanism), disable it. Running it alongside Auto Retry can cause duplicate payment attempts.
Update any messaging about retry timing. If your emails tell customers to wait a few days or to expect a charge at the next scheduled attempt, revise that copy. Payment is now re-attempted immediately after the card is updated.
Brief your support team. Agents who update a payment method on a customer's behalf no longer need to trigger a retry—Auto Retry handles it automatically, and the manual Send Now step is no longer available to them.
Notice something off? Duplicate or unexpected payment attempts are most often a sign that a custom retry workflow is still active. Confirm any custom workflow is fully disabled, then contact your CSMCSM or Ordergroove Support with the affected subscription IDs.