When automatic payment capture fails in WHMCS, first determine whether no attempt occurred, the gateway declined the attempt or the payment succeeded without being recorded. Each situation requires a different response.
IN THIS ARTICLE
01 Inspect the invoice and attempt
- Open the invoice and confirm its balance, assigned gateway and due date.
- Check whether the client has a compatible saved payment method and whether automatic collection is intended for this account.
- Review Gateway Log and the provider's transaction history at the expected attempt time. Match amount, currency and customer reference.
- Check Automation Status and the Payment Capture Settings if no attempt appears. Review Process Days Before Due, Attempt Only Once and the configured retry interval.
- Classify the result before acting: configuration failure, missing method, issuer decline, required customer authentication or successful payment awaiting reconciliation.
02 Choose the appropriate recovery
For a missing or outdated method, ask the authorised customer to update it through the client area. For a payment requiring customer authentication, direct the customer to the unpaid invoice so they can complete the supported gateway flow. Do not repeatedly attempt to bypass an authentication requirement.
For a credential or connectivity problem, repair the integration and review the existing retry schedule before running a manual capture. Check the provider first if the earlier result was a timeout, because the charge may already exist.
How should I control retries after a failed payment capture?
WHMCS's payment-capture settings can result in one attempt or repeated attempts at the configured interval. Record the intended policy and customer notices. A manual attempt should be deliberate and should not overlap with an imminent automated retry.
After a successful payment, confirm that the invoice balance, transaction and relevant service dates agree. If the customer reports two charges, compare transaction IDs and provider subscriptions rather than deleting records. Keep the gateway's diagnostic message privately, and send the customer a clear next action without exposing internal credentials or unsupported reasons for an issuer decision.