Understanding Declined Transactions and Subsequent Behaviors
When processing payments, declined transactions can sometimes lead to subsequent actions, such as the creation of new transaction IDs or additional authentication steps. This article explains common scenarios and how to interpret them.
Declined Transactions That Later Succeed
In some cases, a transaction that initially shows as declined may later succeed under a new transaction ID. This occurs when an initially declined authorization is later cleared by the issuer, resulting in a successful charge. To confirm the totals:
Count the successful charges on the relevant date.
If multiple successful transactions appear for the same amount, it indicates that the decline was cleared and the final count reflects all successful transactions.
This behavior is issuer-driven and is a normal part of transaction processing.
3DS Soft Declines and Subsequent Attempts
When a card payment is declined due to a 3‑D Secure (3DS) soft decline, the issuer requires additional customer authentication. This triggers a full 3DS challenge, prompting the customer to authenticate the payment. After successful authentication, the payment is attempted again, creating a second transaction record under the same merchant transaction ID. This process is expected behavior for 3DS flows and ensures that the payment complies with the issuer's authentication requirements.
Interpreting Multiple Transaction Records
When reviewing transaction records, it is important to:
Identify whether multiple transactions for the same amount are present.
Check if the transactions are linked to issuer-driven processes, such as cleared declines or 3DS authentication flows.
Confirm the final count of successful transactions to ensure accuracy.
By understanding these scenarios, you can better interpret transaction records and identify the reasons behind multiple entries.
For further assistance, please contact Paynt support.