The Fraud Report section of the Payments tab only renders values for CVV and AVS if the most recent transaction was successful (auth or auth/capture). This is due to GetLastTransaction() only returning the array index if the transaction was successful.

It would be more useful the way it rendered in Gold, always showing CVV and AVS values regardless of success or failure. It's not intuitive to have to look down at each individual transaction to determine the actual CVV/AVS response codes when there's already a section above that shows field labels, but no values, when the last transaction failed.

Testing was done with the Sandbox AuthNet gateway operating in Live - Test Mode.

I have the AuthNet gateway set for a sandbox account with gateway settings configured for Test Gateway/Live Mode

Use card # 4111 1111 1111 1111
Use Expire: 01/22
Use CVV 900 for a success
Use CVV 901 for a failure

When you have a success response from AuthNet, you see the AVS and CVV response codes in the 'Fraud Report'

But when the payment has failed, you do not see the AVS or the CVV response codes. You have to look at the transaction below to find them. So the 'Fraud Report' dialog serves no purpose in even being on the page.

The use of the words 'Fraud Report' is very misleading. Just because the transaction failed doesn't make it fraud. The merchant can control what CVV and AVS response codes are 'acceptable' at the merchant gateway. So just because the transaction was rejected by the gateway, that doesn't make it 'fraud'. It just makes it a transaction that was declined.

Here are screenshots from a successful capture and a failed capture. You can see when the capture failed, there's no AVS or CVV response codes rendered to the page.

Capture.JPG (16kb) downloaded 0 time(s). Capture2.JPG (17kb) downloaded 0 time(s).

Ideally the response codes should be displayed regardless of success or failure of the last transaction. It's important to the merchant to know the exact AVS and CVV response either way.