Investigate a Braintree duplicate transaction rejection
Key facts
A duplicate rejection refers to a second attempt. Inspect the original transaction and use its latest status to decide whether a balance is still outstanding.
This guide is not legal advice and laws/rules may change; consult a qualified professional for personalized assistance. Use at your own risk.
Find both attempts
In Braintree, search for the original and rejected transactions using the order reference, amount and time. Record both IDs, the processor or gateway result and the current status of the original. Braintree’s duplicate check considers a configurable time window, matching amount and order or subscription ID when applicable. The payment method can add more matching criteria.
Choose the next step from the original status
If the original is Authorized, Submitted for Settlement or Settling, have payment operations confirm its expected next status before asking the buyer to retry. If it is Settled, reconcile it against the invoice. If it is Voided or later declines, confirm that no other payment covers the invoice before arranging a new payment. Braintree can reject the duplicate while the first attempt is still in flight. If the original later declines, those attempts are not automatically retried. Confirm the correct recovery path after the outcome is known.
Keep one owner for the exception
If the customer reports two pending entries, send the two transaction references to payment operations and ask them to confirm which is eligible to settle. Keep invoice follow-up tied to the confirmed balance. Recurring duplicate reports with the same checkout or order flow should go to the team that owns that flow, with timestamps and transaction IDs.
For help prioritizing the remaining balances, see Debitura’s accounts receivable guide.


.webp)