You can find out why an online transaction was rejected by navigating through SecurePay Transactions, where you’ll see one of three transaction statuses. Hover over the status symbol on the far right for a description of each status, or read on for a fuller explanation of each status. You can also find information on the top causes of rejected payments below.
2. Select Transactions under SecurePay
3. To locate transactions, please select Search by period or RRN, like shown below
Here you can see the possible 3D secure responses
1. Red can actually mean two things!
A) A transaction can fail because it is not authenticated by the cardholder or the card’s issuing bank does not support 3D Secure. The transaction will not be accepted so no amount will be taken from the customer’s card. Advise the cardholder to contact the issuer of their card if they run into an issue with this.
B) A transaction is successful. If you are not a 3D Secure registered merchant transactions can appear successful but still have the red .
You simply have to check if it says it was Accepted by the transaction, to confirm if it went through or not.
When you see a yellow check mark next to a transaction, but it was still Accepted. That means that the transaction was 3D Secure compliant on the merchant side, but the card was not. Advise the cardholder to contact the issuer of their card if they run into an issue with this.
Great news! This means that the transaction was fully authenticated by 3D Secure and successfully processed
Why might online payments be rejected?
These are the main reasons for transaction rejections:
No 3D secure authentication present.
Transaction exceeds the card issuers withdrawal limits.
Incorrect card information.
Do not Honour - Issuing bank rejects the transaction.
You can find the reason for each rejected transaction Action code.
Examples of rejections and how they look