Last Updated: 15 February 2023 | Change Log
Testing
Test your FraudSight on the Try environment using the magic values provided below. Send requests and see simulated responses.
Cardholder name
Use different cardholder names to alter the FraudSight or Exemption outcome
Tokens
Use the cardholder test names below when creating the tokens. When creating tokens containing test/dummy card numbers you must delete the token before creating another with the same PAN. You will be prevented from creating another token using the same PAN. As an alternative you can also change the namespace used as part of the token creation.
FraudSight Assessment
| Magic value | Description | Outcome |
|---|---|---|
fs-lowRisk | Low risk assessment, proceed with payment | lowRisk |
fs-highRisk | High risk assessment, do not proceed with payment | highRisk |
fs-review | Proceed with payment but manual review required | review |
The reason value in the assessment response can be returned for any outcome, with multiple values as part of an array. For the Try environment it's always the same value as there are many possible combinations.
FraudSight assessment with Exemption included
As a FraudSight assessment can also return an exemption you can chain the exemption test values using a period (.) separator to get various combinations of outcomes. Examples:
lowRisk Fraud assessment including a lowRisk authorization exemption:
fs-lowRisk.ex-exemption-lowRisk-authorization
lowRisk Fraud assessment with no exemption included:
fs-lowRisk.ex-noExemption
highRisk Fraud assessment including a lowRisk authorization exemption:
fs-highRisk.ex-exemption-lowRisk-authorization