Skip to content
APIs/FraudSight/
Fraud assessment

Last updated: 30 September 2025 | Change log

Fraud assessment

POST your request to the fraudsight:assess action link.

Assessment example request

POST https://try.access.worldpay.com/fraudsight/assessment

Risk assessment request body:

application/vnd.worldpay.fraudsight-v1.hal+json

Assessment using the card instrument

{
  "transactionReference": "Memory265-13/08/1876",
  "merchant": {
    "entity": "default"
  },
  "instruction": {
    "paymentInstrument": {
      "type": "card/front",
      "cardHolderName": "Sherlock Holmes",
      "cardNumber": "4444333322221111",
      "cardExpiryDate": {
        "month": 5,
        "year": 2035
      },
      "billingAddress": {
        "address1": "221B Baker Street",
        "address2": "Marylebone",
        "address3": "Westminster",
        "postalCode": "NW1 6XE",
        "city": "London",
        "state": "Greater London",
        "countryCode": "GB"
      }
    },
    "value": {
      "currency": "GBP",
      "amount": 250
    }
  },
  "deviceData": {
    "collectionReference": "0_4XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX8G6",
    "ipAddress": "192.0.0.0"
  },
  "riskData": {
    "account": {
      "email": "sherlock.holmes@example.com",
      "dateOfBirth": "1854-01-06",
      "shopperId": "id123"
    },
    "transaction": {
      "firstName": "Sherlock",
      "lastName": "Holmes",
      "phoneNumber": "02031234321"
    },
    "shipping": {
      "firstName": "James",
      "lastName": "Moriarty",
      "address": {
        "address1": "The Palatine Centre",
        "address2": "Durham University",
        "address3": "Stockton Road",
        "postalCode": "DH1 3LE",
        "city": "Durham",
        "state": "County Durham",
        "countryCode": "GB",
        "phoneNumber": "01911234321"
      }
    },
    "custom": {
      "number1": 1,
      "number2": 2,
      "number3": 3,
      "number4": 4,
      "number5": 5,
      "number6": 6,
      "number7": 7,
      "number8": 8,
      "number9": 9,
      "string1": "text1",
      "string2": "text2",
      "string3": "text3",
      "string4": "text4",
      "string5": "text5",
      "string6": "text6",
      "string7": "text7",
      "string8": "text8",
      "string9": "text9"
    }
  }
}

View the full API request schema

Assessment responses

The response contains the outcome of your assessment request.

Linking the payment

You must apply the riskProfile from the FraudSight assessment response in the Card Payments API to link the Worldpay payment. This allows the data model mature and identify fraudulent transactions. Alternatively make additional FraudSight update requests.

See linking the FraudSight assessment for details.

Note:

  • When manually created risk assessment rules are triggered, the score is ignored. It is therefore possible to see an assessment with a low score but still with a highRisk outcome.

  • The outcome is always specific to the fraud assessment. If an exemption is provided the exemption.type and exemption.placement is included in the response.

  • We return a WP-CorrelationId in the headers of service responses. We highly recommend you log this. We can use the WP-CorrelationId to examine individual service requests.

    {
        "outcome": "lowRisk",
        "transactionReference": "123456",
        "score": 44.2,
        "riskProfile": {
            "href": "https://access.worldpay.com/riskprofile/eyJrIjoxLCJkIjoialRBL0FFelBzcnZ"
        }
    }

If the exemption object is used in the request:

    {
        "outcome": "lowRisk",
        "transactionReference": "123456",
        "score": 44.2,
        "exemption": {
            "placement": "authorization",
            "type": "lowValue"
        },
        "riskProfile": {
            "href": "https://access.worldpay.com/riskprofile/eyJrIjoxLCJkIjoialRBL0FFelBzcnZ"
        }
    }

View the full API response schema

Linking the FraudSight assessment

To improve future risk assessments we need to know the outcome of the payment authorization.

Applying the exemption (if applicable)

This is only a consideration if you're using the exemption object in the request:

If the placement is authorization

In the event that the exemption is not successful (honoured + authorized) when applied to the payment, the issuer responds with a soft decline (refusal code 65). The next logical step is to proceed with 3DS authentication.

If the placement is authentication

If no exemption is provided

Next steps

FraudSight testing