Shadow testing reports

Last updated: June 10, 2026

You can download the results of your shadow testing with Fraud Detection as a CSV report. This report enables you to assess the performance of a test risk strategy.

The report is available on demand in the Dashboard.

Sign in to the Dashboard.
In the Business entity selector, select the client view.
Go to the Payments > Fraud > Strategy section.
On the Strategy builder tab, go to the Outcome comparison section.
Select the Shadow testing tab.
For the relevant test, select View results.
Select Download report: Time frame.

The shadow testing report includes the following fields in this order:

Field name Description

Field name	Description
Timestamp date-time	The date and time when the payment was requested, in UTC. Standard – ISO 8601 code Format – `yyyy-mm-ddThh:mm:ss.sss`
PaymentId string	The payment's unique identifier, prefixed with `pay_`. If you have updated your live strategy since the payment date, you can use this ID to search for the payment in the Dashboard or in the report to view the real outcome.
LivePreThreeDSDecision string	The pre-authentication outcome from your current live strategy. This can be one of: `TRY_EXEMPTIONS` – The payment was authenticated successfully. `Decline` – The authentication failed. `3DS Frictionless` – The payment underwent the 3DS frictionless flow. `3DS Challenge` – The payment underwent the 3DS challenge flow.
LabPreThreeDSDecision string	The pre-authentication outcome from your test strategy. This can be one of: `TRYEXEMPTIONS` – The payment was authenticated successfully. `Decline` – The authentication failed. `3DS Frictionless` – The payment underwent the 3DS frictionless flow. `3DS Challenge` – The payment underwent the 3DS challenge flow.
ThreeDSOutcome string	The outcome if the live payment underwent 3DS authentication. This can be one of: `Authenticated` – The payment was authenticated successfully. `Expired` – The authentication expired. `Failed` – The payment failed authentication. `No 3ds` – 3DS was not applicable to the payment. Empty – The payment did not undergo 3DS authentication.
AuthorisationOutcome string	The outcome if the live payment underwent authorization. This can be one of: `Authorised` – The payment was authorized successfully. `Declined` – The payment was declined. `Terminated` – The authorization attempt failed. Empty – The payment did not undergo authorization.
LivePostAuthDecision string	The post-authorization outcome from your current live strategy. This can be one of: `TERMINATED` – The payment did not progress to the post-authorization stage. `Capture` – The payment was authorized and you can capture the funds. `Flag` – The payment was flagged for review. `Void` – The payment was deemed high risk and therefore voided. Empty – The issuer declined the payment.
LabPostAuthDecision string	The post-authorization outcome from your test strategy. This can be one of: `TERMINATED` – The payment did not progress to the post-authorization stage. `Capture` – The payment was authorized and you can capture the funds. `Flag` – The payment was flagged for review. `Void` – The payment was deemed high risk and therefore voided. Empty – The issuer declined the payment.
CurrentStatus string	The payment's current status. This can be one of: `Captured` `Pending` `Terminated`
LivePreThreeDSResponse string	The last pre-auth rule group assessed from your current live strategy. Example – `3DS rules`
LabPreThreeDSResponse string	The last pre-auth rule group assessed from your test strategy. Example – `Decline rules`
ThreeDSDetails	The additional 3DS details you provided in the payment request. See Request a payment – `3ds` object.
AuthDetails	The additional authentication details you provided in the payment request. See Request a payment – `3ds` object.
LivePostAuthResponse string	The last post-auth rule group assessed from your current live strategy. Example – `Flag rules`
LabPostAuthResponse string	The last post-auth rule group assessed from your test strategy. Example – `Void rules`
CheckoutFraudScore number	The payment's risk score. If the payment did not meet the data or transaction requirements to receive a score, this field is empty.
FraudReportedOn date-time	The date and time when the fraud issue was reported, in UTC. Standard – ISO 8601 code Format – `yyyy-mm-ddThh:mm:ss.sss` This field is empty if the payment was not reported as fraudulent.
FraudReason string	The reason for identifying the payment as fraudulent. This field is empty if the payment was not reported as fraudulent.
FraudType string	The scheme fraud code for the type of fraud reported. This field is empty if the payment was not reported as fraudulent.
Scheme string	The card scheme the payment was processed with.
CardType string	The type of card type used to make the payment. This can be one of: `Credit` `Debit`
CardCountry string	The country where the card was issued. Standard – ISO alpha-3 country code Example – `USA`
BIN string	The identifier for the financial institution that issued the card. Format – Six digit number
Issuer string	The name of the financial institution that issued the card.
Amount string	The payment amount, in the major currency unit.
Currency string	The payment's currency. Standard – ISO 4217 code Example – `USD`
AmountInUSD number	The payment amount, converted to US dollars.
PaymentType string	The type of payment. Example – `Credit Cards`
RequestReference string	The reference you provided in the payment request.
CardHolderName string	The cardholder's name.
CustomerName string	The customer's name.
CustomerEmail string	The customer's email address.
CustomerIP string	The customer's IP address. Example – `198.51.100.2`
BillingLine1 string	The first line of the billing address.
BillingLine2 string	The second line of the billing address.
BillingCity string	The city of the billing address.
BillingZip string	The zip or post code of the billing address.
BillingState string	The state of the billing address.
BillingCountry string	The country of the billing address.
PhoneCountry string	The country code of the customer's phone number. Example – `44`
PhoneNumber string	The customer's phone number.
ShippingLine1 string	The first line of the shipping address.
ShippingLine2 string	The second line of the shipping address.
ShippingCity string	The city of the shipping address.
ShippingZip string	The zip or post code of the shipping address.
ShippingState string	The state of the shipping address.
ShippingCountry string	The country of the shipping address.
Metadata string	The metadata you provided in the payment request.
PaymentIpCountry string	The country of the payment's IP address. Standard – ISO alpha-3 country code Example – `USA`
PaymentIpCity string	The city of the payment's IP address.
PaymentIpTimezone string	The time zone of the payment's IP address. Example – `Europe/London`
PaymentIpIsTor boolean	Indicates whether the payment's IP address is a known Tor IP.
PaymentIpIsVpn boolean	Indicates whether the payment's IP address is a known virtual private network (VPN) IP.
PaymentIpIsProxy boolean	Indicates whether the payment's IP address is a known proxy IP.

Timestamp

date-time

The date and time when the payment was requested, in UTC.
Standard – ISO 8601 code
Format – yyyy-mm-ddThh:mm:ss.sss

PaymentId

string

The payment's unique identifier, prefixed with pay_.

If you have updated your live strategy since the payment date, you can use this ID to search for the payment in the Dashboard or in the report to view the real outcome.

LivePreThreeDSDecision

string

The pre-authentication outcome from your current live strategy. This can be one of:

TRY_EXEMPTIONS – The payment was authenticated successfully.
Decline – The authentication failed.
3DS Frictionless – The payment underwent the 3DS frictionless flow.
3DS Challenge – The payment underwent the 3DS challenge flow.

LabPreThreeDSDecision

string

The pre-authentication outcome from your test strategy. This can be one of:

TRYEXEMPTIONS – The payment was authenticated successfully.
Decline – The authentication failed.
3DS Frictionless – The payment underwent the 3DS frictionless flow.
3DS Challenge – The payment underwent the 3DS challenge flow.

ThreeDSOutcome

string

The outcome if the live payment underwent 3DS authentication. This can be one of:

Authenticated – The payment was authenticated successfully.
Expired – The authentication expired.
Failed – The payment failed authentication.
No 3ds – 3DS was not applicable to the payment.
Empty – The payment did not undergo 3DS authentication.

AuthorisationOutcome

string

The outcome if the live payment underwent authorization. This can be one of:

Authorised – The payment was authorized successfully.
Declined – The payment was declined.
Terminated – The authorization attempt failed.
Empty – The payment did not undergo authorization.

LivePostAuthDecision

string

The post-authorization outcome from your current live strategy. This can be one of:

TERMINATED – The payment did not progress to the post-authorization stage.
Capture – The payment was authorized and you can capture the funds.
Flag – The payment was flagged for review.
Void – The payment was deemed high risk and therefore voided.
Empty – The issuer declined the payment.

LabPostAuthDecision

string

The post-authorization outcome from your test strategy. This can be one of:

TERMINATED – The payment did not progress to the post-authorization stage.
Capture – The payment was authorized and you can capture the funds.
Flag – The payment was flagged for review.
Void – The payment was deemed high risk and therefore voided.
Empty – The issuer declined the payment.

CurrentStatus

string

The payment's current status. This can be one of:

Captured
Pending
Terminated

LivePreThreeDSResponse

string

The last pre-auth rule group assessed from your current live strategy.
Example – 3DS rules

LabPreThreeDSResponse

string

The last pre-auth rule group assessed from your test strategy.
Example – Decline rules

ThreeDSDetails

The additional 3DS details you provided in the payment request.

See Request a payment – 3ds object.

AuthDetails

The additional authentication details you provided in the payment request.

See Request a payment – 3ds object.

LivePostAuthResponse

string

The last post-auth rule group assessed from your current live strategy.
Example – Flag rules

LabPostAuthResponse

string

The last post-auth rule group assessed from your test strategy.
Example – Void rules

CheckoutFraudScore

number

The payment's risk score.

If the payment did not meet the data or transaction requirements to receive a score, this field is empty.

FraudReportedOn

date-time

The date and time when the fraud issue was reported, in UTC.
Standard – ISO 8601 code
Format – yyyy-mm-ddThh:mm:ss.sss

This field is empty if the payment was not reported as fraudulent.

FraudReason

string

The reason for identifying the payment as fraudulent.

This field is empty if the payment was not reported as fraudulent.

FraudType

string

The scheme fraud code for the type of fraud reported.

This field is empty if the payment was not reported as fraudulent.

Scheme

string

The card scheme the payment was processed with.

CardType

string

The type of card type used to make the payment. This can be one of:

Credit
Debit

CardCountry

string

The country where the card was issued.
Standard – ISO alpha-3 country code
Example – USA

BIN

string

The identifier for the financial institution that issued the card.
Format – Six digit number

Issuer

string

The name of the financial institution that issued the card.

Amount

string

The payment amount, in the major currency unit.

Currency

string

The payment's currency.
Standard – ISO 4217 code
Example – USD

AmountInUSD

number

The payment amount, converted to US dollars.

PaymentType

string

The type of payment.
Example – Credit Cards

RequestReference

string

The reference you provided in the payment request.

CardHolderName

string

The cardholder's name.

CustomerName

string

The customer's name.

CustomerEmail

string

The customer's email address.

CustomerIP

string

The customer's IP address.
Example – 198.51.100.2

BillingLine1

string

The first line of the billing address.

BillingLine2

string

The second line of the billing address.

BillingCity

string

The city of the billing address.

BillingZip

string

The zip or post code of the billing address.

BillingState

string

The state of the billing address.

BillingCountry

string

The country of the billing address.

PhoneCountry

string

The country code of the customer's phone number.
Example – 44

PhoneNumber

string

The customer's phone number.

ShippingLine1

string

The first line of the shipping address.

ShippingLine2

string

The second line of the shipping address.

ShippingCity

string

The city of the shipping address.

ShippingZip

string

The zip or post code of the shipping address.

ShippingState

string

The state of the shipping address.

ShippingCountry

string

The country of the shipping address.

Metadata

string

The metadata you provided in the payment request.

PaymentIpCountry

string

The country of the payment's IP address.
Standard – ISO alpha-3 country code
Example – USA

PaymentIpCity

string

The city of the payment's IP address.

PaymentIpTimezone

string

The time zone of the payment's IP address.
Example – Europe/London

PaymentIpIsTor

boolean

Indicates whether the payment's IP address is a known Tor IP.

PaymentIpIsVpn

boolean

Indicates whether the payment's IP address is a known virtual private network (VPN) IP.

PaymentIpIsProxy

boolean

Indicates whether the payment's IP address is a known proxy IP.

Shadow testing reports

Download the report

Report fields