Last Updated: 15 February 2023 | Change Log

Fraud update

POST your request to the fraudsight:fraud action link.

Fraud update example request


Fraud update request body:

  "transactionReference": "Memory265-13/08/1876",
  "merchant": {
      "entity": "MindPalaceLtd"
  "riskProfile": "",
  "source": "TC40",
  "sourceDate": "2020-12-27T00:00:00Z",
  "acquirerReference": "02691780344910023278387",
  "fraudReasonCode": "5",
  "value": {
    "currency": "GBP",
    "amount": 250
transactionReferenceA reference for the assessment. For example, e-commerce order code.
merchant.entityUsed to route the assessment request in Access Worldpay, created as part of on-boarding.
riskProfileRepresents the outcome of the original fraud assessment. Used to link subsequent Fraud related requests.
sourceSource format of confirmed fraud cases:
  • TC40
  • SAFE
sourceDateDate/time of source fraud file (TC40/SAFE).
acquirerReferenceAcquirer Reference Number (ARN) - unique value assigned to a credit or debit card transaction.
fraudReasonCodeVisa and Mastercard reason codes.
value.currencyThe three digit currency code.
See list of supported currencies.
value.amountThe payment amount. This is a whole number with an exponent e.g. if exponent is two, 250 is 2.50. You can find the relevant exponent in our currency table.

Fraud update responses

Best Practice

Access Worldpay returns a WP-CorrelationId in the headers of service responses. We highly recommend you log this. The WP-CorrelationId is used by us to examine individual service requests.

The response status is 200 OK.