# Versioning and change log

This log details any breaking and non-breaking API changes we have released for our FraudSight service.

Prerequisite
Make yourself familiar with our [API principles](/access/products/reference/api-principles) to ensure a resilient integration.

## Versioning log

Our Fraudsight service is currently on version 1. We will record any upcoming breaking changes here.

## Change log (non-breaking changes)

#### Exemption in authentication support (30 September 2025)

details
summary
More details
* You can now set an [`exemption.capability`](/access/products/fraudsight/openapi/other/assessment#other/assessment/t=request&path=exemption) value of `authenticationOnly` or `authorizationAndAuthentication` to allow exemptions in authentication (3DS) to be returned. This was previously defaulted to `authorizationOnly`.
* You can now also specify the `exemption.placement` and `exemption.type` per request. See [FraudSight assessment](/access/products/fraudsight/assessment) for details.


#### Partial payment instrument support (11th April 2025)

details
summary
More details
Perform a risk assessment without the full card number. You can now use our `card/plain+masked` paymentInstrument in your [assessment request](/access/products/fraudsight/assessment).

details
summary
2024
#### Refusal description and  refusal code in the update payment request (17 Dec 2024)

details
summary
More details
You can now add the `refusalCode` and `refusalDescription` to the [payment update](/access/products/fraudsight/update/payment) request.

#### Network token support (04 July 2024)

details
summary
More details
You can now use our `card/networkToken` paymentInstrument in your [assessment request](/access/products/fraudsight/assessment).

details
summary
2023
#### Optional IP address field in fraud assessment request (15 February 2023)

details
summary
More details
You now have the option to send the IP address details of your customer's device in the [fraud assessment request](/access/products/fraudsight/assessment#assessment-example-request).

If you are not supplying device data via ThreatMetrix, you can send the IP address in this field and create manual fraud rules.

details
summary
2022
#### Optional shopperId field in fraud assessment request (15 December 2022)

details
summary
More details
You now have an option to send `shopperId` field with the account risk data in [fraud assessment request](/access/products/fraudsight/assessment#additional-fields-in-assessment-request).

Use `shopperId` to create manual fraud rules and identify your customers.