3DS

Verify your customer's identity simply and seamlessly to minimize fraud. Use our strong customer authentication to benefit from liability shift.

Note: Make yourself familiar with ourAPI Principlesto ensure a resilient integration.

Set your headers

Setting your headers is an important part of an API request. The headers represent the meta-data associated with your API request.

Copied!
Authorization: {your_credentials}
Content-Type: application/vnd.worldpay.verifications.customers-v2.hal+json
Accept: application/vnd.worldpay.verifications.customers-v2.hal+json
HeaderDescription
AuthorizationThe Authorization header is used for authentication and identification of our merchants within Access Worldpay. You must use the Authorization header for any request you send to our 3DS API.
Content-TypeThe Content-Type header is required if the request you're sending includes a request body, and if the HTTP method is a POST or a PUT.
AcceptThe Accept header is used to identify which version of our 3DS API you are using. You must use the Accept header for any request you send to our 3DS API.

If you're using both the Content-Type and Accept headers, they must match.

Note: Replace {your_credentials} with your base64-encoded Basic Auth username and password. To get your Access Worldpay credentials contact yourImplementation Manager.

Query the root resource

Our APIs guide you by providing you with links to the next available actions.

To discover and start using our APIs you must first query the root resource. This returns the available resources within Access Worldpay.

Request

GET https://try.access.worldpay.com/

Note: No request body is needed for this request.

Response

You receive all our available API resources in the response.

Copied!
{
    "_links": {
        "payments:authorize": {
            "href": "https://try.access.worldpay.com/payments/authorizations"
        },
        "service:payments": {
            "href": "https://try.access.worldpay.com/payments"
        },
        "service:tokens": {
            "href": "https://try.access.worldpay.com/tokens"
        },
        "service:verifications/accounts": {
            "href": "https://try.access.worldpay.com/verifications/accounts"
        },
        "service:verifications/customers/3ds": {
            "href": "https://try.access.worldpay.com/verifications/customers/3ds"
        },
        "service:verifiedTokens": {
            "href": "https://try.access.worldpay.com/verifiedTokens"
        },
        "service:payouts": {
            "href": "https://try.access.worldpay.com/payouts"
        },
        "curies": [{
            "href": "https://try.access.worldpay.com/rels/payments/{rel}",
            "name": "payments",
            "templated": true
        }]
    }
}

Query the 3DS root resource

Query the service:verifications/customers/3ds action link for the 3DS root resource.

Request

GET https://try.access.worldpay.com/verifications/customers/3ds

Note: No request body is needed for this request.

The response

Copied!
{
    "_links": {
      "resourceTree": {
        "href": "https://try.access.worldpay.com/verifications/customers/3ds/resourceTree"
      },
      "3ds:deviceDataInitialize": {
        "href": "https://try.access.worldpay.com/verifications/customers/3ds/deviceDataInitialization"
      },
      "curies": [
        {
          "href": "https://try.access.worldpay.com/rels/verifications/customers/3ds/{rel}",
          "templated": true,
          "name": "3ds"
        }
      ]
    }
  }

Resources

The response contains a link to initialize the 3DS Device Data Collection (DDC):

Action Link (resources)Description
3ds:deviceDataInitializeDDC is used by the card issuer to fingerprint the device used by the customer when placing the order. Starting link for 3DS2 with a 3DS1 fallback.

Next steps


Device Data