Duplicate transaction submissions: The same transaction was processed multiple times, especially for first-time debit (FRST) transactions.
Incorrect transaction IDs: Submitting the same transaction ID more than once can lead to duplicate detection.
Delayed gateway updates: The gateway processes a transaction, but the status was not updated immediately, leading to resubmission attempts.
Ask the customer to:
Check their bank account for the successful transaction.
Contact support@chargebee.com if they need help identifying the transaction.
Internally:
Verify transaction records in Chargebee and at the payment gateway to confirm that a payment was already processed.
Ensure that transaction IDs are unique and not reused for future attempts.
Avoid retrying until you confirm that no successful collection exists to prevent further duplication.
Try to collect payment using the Pay Now
flow by creating a new transaction if there is no successful transaction recorded.