Braintree Duplicate checking logic
Our duplicate checking logic runs within a specific time frame. If all of the general and relevant payment method-specific conditions are met within the designated timeframe, any suspected duplicate transactions will be Gateway Rejected.
The timeframe for duplicate checking logic is set to 30 seconds by default, but can be updated to meet your needs in the Control Panel.
General conditions for Duplicate Transaction
In order for a transaction to be Gateway Rejected as a duplicate transaction, it must meet all of the following conditions within the designated timeframe:
- Amount is the same as the initial transaction
- Order ID is the same (if collected and if the transaction was not
created by Braintree's recurring billing functionality)
- Subscription ID is the same (if the transaction was created by
Braintree's recurring billing functionality)
- The initial transaction was successful (status can be Authorized,
Submitted for Settlement, Settling, Settled, or Voided)
Payment method-specific conditions
In addition to the general conditions listed above, there are conditions specific to supported payment methods. For the following payment methods, the listed condition must also be true in order for our duplicate transaction logic to reject the transaction:
- Google Pay or Apple Pay – DPAN is the same
- PayPal – payer email address is the same
- Credit card – number and expiration date are the same
Configuring duplicate transaction checking
Duplicate transaction checking is enabled by default with a 30 second window in both the sandbox and production environments. These settings can be updated or disabled by users with Account Admin permissions.
- Log into the Control Panel
- Navigate to Settings > Processing > Duplicate Transaction Checking
- Click the toggle to turn this feature on and off, or click Options
to adjust the time window
I hope this will help