Last updated: 30 September 2024 | Change log
POST your request to the exemptions:assess action link.
POST  https://try.access.worldpay.com/exemptions/assessment
Risk assessment request body:
- Test (Try)https://try.access.worldpay.com/exemptions/assessment
 - Livehttps://access.worldpay.com/exemptions/assessment
 
- Payload
 - curl
 - Python
 - Java
 - Node.js
 - Go
 - PHP
 - Ruby
 - C#
 
Exemption assessment using the card instrument
{ "transactionReference": "Memory265-13/08/1876", "merchant": { "entity": "default" }, "doNotApplyExemption": false, "exemption": { "capability": "authorizationAndAuthentication", "request": { "placement": "authorization", "type": "lowValue" } }, "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" }, "riskData": { "account": { "email": "sherlock.holmes@example.com", "dateOfBirth": "1990-09-09" }, "transaction": { "firstName": "Sherlock", "lastName": "Holmes", "phoneNumber": "00000000000000" }, "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" } } } }
Full API Reference here
A unique reference for authentication. For example, e-commerce order code.
An object that contains information about the merchant and API level configuration.
Used to route the request in Access Worldpay, created as part of on-boarding.
An object that contains information about the type and placement of the requested exemption.
Note: If this object is not used in the request the capability is limited to authorizationOnly.
Indicates whether the exemption requested from us, can return a placement of authorization (payment) and/or authentication (3DS).
| Enum Value | Description | 
|---|---|
| authorizationOnly | The SCA Exemptions service can only return a   | 
| authenticationOnly | The SCA Exemptions service can only return a   | 
| authorizationAndAuthentication | The SCA Exemptions service can return either a   | 
An object used to control the placement and type of the requested exemption. If not provided, we decide the best placement and type (optimized).
The object that contains all the payment information related to the authentication request.
An object that contains information about the value of the authentication.
An object that contains the card details or token location.
Request an exemption but don't apply it in the payment. Used for the initial go-live to build up the data model and have more reliable exemption predictions.
An object that holds risk related information that might help in improving the accuracy of fraud assessment.
Object containing all customer account related risk data.
Object containing all customer transaction related risk data.
Object containing all data related to how the order is shipped.
Object containing custom fields
Object containing device data information.
Use the sessionId specified in the ThreatMetrix Device Data Collection to link this data to the assessment.
We return 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.
You can see the full response schema in the API Reference.
The response contains the outcome of your assessment request.
The outcome of the exemption assessment request.
| Enum Value | Description | 
|---|---|
| noExemption | no exemption granted, proceed to 3DS authentication  | 
| exemption | exemption granted, follow placement and type  | 
A unique reference for assessment that was passed in the request.
A resource you can use in the payment authorization request that represents the outcome of the exemption assessment. Used to:
- apply the exemption (if provided)
 - update the data model so future assessments are more accurate
 
A link to a resource to be used in the payment authorisation request that represents the outcome of exemption assessment.
An object that holds information about the exemption if it is granted.
Indicates whether the exemption is provided to be placed in a payment authorization request or 3DS authentication request.
| Enum Value | Description | 
|---|---|
| authorization | Apply the exemption in the payment authorization  | 
| authentication | Apply the exemption in the 3DS authentication  | 
The type of exemption to apply.
| Enum Value | Description | 
|---|---|
| lowValue | Apply a lowValue exemption, (only applicable to a placement in authorization)  | 
| lowRisk | Apply a lowRisk exemption.  | 
- apply the 
riskProfilein the payment authorization request. 
In the event that the exemption is not successful (honoured + authorized) when applied in the payment, the issuer responds with a soft decline (refusal code 65). The next logical step is, to proceed with 3DS authentication.
- set the 
challenge.preferencein 3DS authentication tonoChallengeRequestedTRAPerformed - apply the 
riskProfilein the payment authorization request 
- perform 3DS authentication
 - apply the 
riskProfilein the payment authorization request. Without this, the data model will not improve over time 
Next steps