Suspected fraud update

Deprecated Section: This section is deprecated! For new integrations or migrations, please use the new documentation.

The suspected fraud update updates a suspected fraud status.

Suspected fraud update

patch

Authorizations

bearerAuth

AuthorizationstringRequired

JWT Authorization header using the Bearer scheme.

Path parameters

tokenstring · uuidRequired

Body

application/json

statusstring · enumRequiredPossible values:

Responses

200

Suspected fraud update occurred successfully.

application/json

messagestringRequired

Human readable message informing about the operation.

400

Suspected fraud update failed due to a bad request.

application/json

401

Unauthorized.

application/json

422

Suspected fraud update failed, but the request was processed by the API, just not by the peer.

application/json

500

Suspected fraud update failed due to an unexpected error in the API.

application/json

503

Suspected fraud update failed due to an unexpected error in the Peer.

application/json

patch/suspected-fraud/{token}

HTTPcURLJavaScriptPython

PATCH /fraud/suspected-fraud/{token} HTTP/1.1
Host: api.prd.combateafraude.com
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 28

{
  "status": "CONFIRMED_FRAUD"
}

{
  "message": "text",
  "requestStatus": {
    "status": "SUCCESS",
    "token": "123e4567-e89b-12d3-a456-426614174000"
  }
}

Options

As demonstrated in the example request, in the URL a path parameter must be passed and PATCH HTTP method used. The token parameter must be a UUID that's identify a Suspected Fraud, this token can be retrieved on the Suspected Fraud Query passing query mode as LOCAL or DELETED. In the data object you should include de Suspected Fraud Status must be passed using the status property. Possible status values ares:

• CONFIRMED_FRAUD: indicates a confirmed fraud occurrence;
• SUSPECTED_FRAUD: indicates a suspected fraud occurrence.