This article describes Authorize.net's duplicate transaction logic.
Disclaimer
This article is provided for educational and informational purposes only. For the most accurate information about Authorize.net duplicate transaction logic, please see their documentation.
Duplicate Transactions
For Authorize.net to flag a transaction as being a duplicate, the following fields must be the same in the second transaction. The second transaction must also occur in a two-minute window.
API Login ID
Credit Card Number
Expiration Date
Transaction Type
Bank Account Number
Routing Number
Purchase Order Number
Amount
Invoice Number
Customer ID
First Name
Last Name
Company
Address
City
State
Postal Code
Country
Duplicate Window
When CivicPlus Payments processes a transaction through the hosted form, a new invoice number is generated every time. The assumption is that when a user clicks “Pay Now,” they intend to make a purchase, even if it is the second purchase, which means that a duplicate will not be flagged.
However, it is possible to check out using a card-on-file and to have two transactions back-to-back in a two-minute window. These will be flagged as duplicates.