---
title: "Cancel fraud marker"
method: POST
path: "/v2/pix/fraud-markers/{id}/cancel"
tags: ["Anti-fraud"]
---

# Cancel fraud marker

`POST /v2/pix/fraud-markers/{id}/cancel`

The participant who created the fraud marker can call this endpoint. In the case of a fraud marker created as a result of closing an infraction report, the participant who created it can cancel it, in addition to the participant who closed the notification.

On PSP timeout, a `202 Accepted` response with a fraud marker ID is returned. The process continues asynchronously and, if it doesn't succeed, a failure event is emitted.

This endpoint generates a <a href="https://developers.pismo.io/events/docs/pix-dict-fraud-marker-status-change-1" >Fraud Marker registration event</a> or <a href="https://developers.pismo.io/events/docs/pix-dict-fraud-marker-status-change-failure-1">failure event</a>.

## Path parameters

- `id` string, uuid, required

## Headers

- `Authorization` string, required

## Response `200`

OK

- FraudMarkerResponse
  - `id` string, uuid, required — Fraud marker ID
  - `document_number` string, required — Cardholder government document number. This can be from any document that identifies the cardholder such as a Tax ID, State ID, or driver's license.
  - `fraud_type` 'APPLICATION_FRAUD' | 'MULE_ACCOUNT' | 'SCAMMER_ACCOUNT' | 'OTHER' | 'UNKNOWN', required — Verified fraud type
  - `status` 'REGISTERED' | 'CANCELLED', required — Fraud marker status
  - `key` string — Key to which the fraud marker will be associated. It must be reported, if known
  - `bacen_creation_datetime` string, date-time, required — Date of infraction report creation. RFC 3339 date-time value. For example - `2023-04-12T23:20:50.52Z`.
  - `bacen_last_modified_datetime` string, date-time, required — Date of infraction report modification. RFC 3339 date-time value. For example - `2023-04-12T23:20:50.52Z`.

## Other responses

- `202` — Accepted
- `401` — Access token is missing or invalid
- `403` — The request has been lost
- `404` — Resource Not Found
- `429` — Too many reqquests
- `500` — Internal Server Error
- `502` — Bad Gateway
- `503` — Service Unavailable
- `504` — Gateway timeout

---

[API](https://skmtc.dev/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.dev/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)