---
title: "Create infraction report (outdated)"
method: POST
path: "/v2/pix/infraction-reports"
tags: ["Infraction reports"]
---

# Create infraction report (outdated)

`POST /v2/pix/infraction-reports`

This endpoint is outdated and no longer works. It is recommended you call [Create funds recovery](https://developers.pismo.io/pismo-docs/reference/post-create-funds-recovery) instead.

Creates an infraction report. Both the debited participant and the credited participant can create an infraction report.

For refund requests, the original transaction payer's payment service provider (PSP) **must** create the report. 

Only the PSP or the original transaction's recipient can cancel a refund. 

On PSP timeout, a `202 Accepted` response is returned and the process continues asynchronously, eventually emitting a success or failure event.

This endpoint generates a <a href="https://developers.pismo.io/events/docs/pix-dict-infraction-status-change-1" >Pix infraction status changed</a> event.

## Headers

- `Authorization` string, required
- `Idempotency-Key` string, required

## Response `201`

OK

- CreateInfractionReportResponse
  - `id` string, uuid, required — Infraction report ID (UUID)
  - `transaction_id` string, required — Original transaction's end to end ID.
  - `reason` 'REFUND_REQUEST' | 'REFUND_CANCELLED', required — Reason for opening infraction report
  - `situation_type` 'SCAM' | 'ACCOUNT_TAKEOVER' | 'COERCION' | 'FRAUDULENT_ACCESS' | 'OTHER' | 'UNKNOWN', required — What gave rise to the infraction notification
  - `status` 'OPEN' | 'ACKNOWLEDGED' | 'CLOSED' | 'CANCELLED', required — Infraction report status
  - `reporter_participant` string, number, required — Transaction payer participant's ISPB (Identifcador do Sistema de Pagamento Brazil) number - the Brazilian Payment System identifier, an 8-digit value.
  - `counterparty_participant` string, number, required — Transaction recipient participant's ISPB (Identifcador do Sistema de Pagamento Brazil) number - the Brazilian Payment System identifier, an 8-digit value.
  - `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`.
  - `details` string — Details that can help the receiving participant to analyze the suspected violation
  - `contact_information` ContactInformation
    - `phone` string, required — Contact phone number
    - `email` string, required — Contact email

## Other responses

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

---

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