Skip to content

Knowledgebase

Resolve duplicate recurring payment subscriptions

whmcs, resellers

If a customer appears to pay twice each renewal period, compare the actual provider transactions and recurring agreements. A duplicate callback for one transaction is different from two separate subscriptions sending real money.

01 Identify the source

  1. Open the customer's invoices, transactions and credit history for the affected periods.
  2. List the distinct provider transaction IDs, amounts and dates. Check whether WHMCS logged one transaction more than once or received two different payments.
  3. Inspect the provider's active subscriptions or payment agreements for the customer and match their identifiers to the WHMCS services.
  4. Check for manual payments made while an automatic subscription was still scheduled.
  5. Review recent gateway migrations, service price changes and billing-cycle changes that may have left an old agreement active.

02 Stop the unintended future payment

Once the intended agreement is identified, cancel only the redundant subscription through the supported provider or module process. Confirm the cancellation at the provider. Removing a Subscription ID from a WHMCS service record is not proof that the provider will stop sending money.

For legacy PayPal Basic subscriptions, the recurring amount and schedule may be fixed at the provider. A price or tax change can therefore require an updated agreement. Newer PayPal integrations use different payment models, so follow the documentation for the exact module.

How should I reconcile payments already collected twice?

Compare the client's credit balance with the excess payments. Decide whether the approved outcome is retained credit or a refund of a specific transaction. Do not remove credit and issue a refund independently without checking the combined effect on the account.

A duplicate-notification message for an already recorded transaction can be a normal protective response. It does not by itself prove a second charge occurred. Use the provider's actual transaction list to establish the financial event.

03 Prevent recurrence

Update invoice emails so customers understand whether payment will be collected automatically. Verify the next renewal and record the subscription retained, the duplicate cancelled and the treatment of prior overpayments.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution