Report fraudulent events (legacy)

During the normal process of reviewing requests and operations that have completed, it is possible that new evidence proves that certain events were fraudulent. This could also be reported by the user, for example, after reviewing their user account.

To improve the chances of detecting these fraudulent events before they are performed, it is important that all fraudulent events are declared in Risk Management.

For this, a dedicated API call exists that flags a past request as fraudulent. To perform this call, it is important for the tenant to keep track of the visitid used when the operation was evaluated by Risk Management. See the tutorial to understand when this visitid is generated and used.

REST API

See the REST API reference for POST /api/v1/tenants/{tenantId}/visits/{visitId}/feedback/fraud. The request has no body: the visitId of the fraudulent operation is passed in the URL.

The API returns HTTP 201 when the request is processed. Always check the result field in the response body: OK means the fraud was recorded, and NOK means it was rejected, with the cause in the reason field (for example, Visit not found).