Create an Infraction Report

DEPRECATED: This endpoint is deprecated and will be removed in a future release due to MED 2.0 changes. The MED 2.0 specification introduces a new flow where infraction reports are replaced by a simplified dispute resolution mechanism handled through the Special Return flow.

Use this endpoint to report infractions associated to Pix transfers. This endpoint must be used when there is a fraud related to a transaction in scenarios where the client is the payer PSP, meaning the transaction was initiated and sent from an account within your arrangement.

Notes:

• Transactions can only be reported within 80 days from the transaction date

POST /v1/dict/infraction-reports

Create an Infraction Report

cURL

curl --request POST \
  --url https://api.example.com/v1/dict/infraction-reports \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "contactInformation": {
    "email": "[e-mail]",
    "phone": "[phone]"
  },
  "reason": "REFUND_REQUEST",
  "situationType": "SCAM",
  "transactionId": "E12345678202411241430ABCDEFGHIJK",
  "reportDetails": "Customer reported receiving a call from fake bank employee requesting PIX payment for supposed security verification"
}
'

201

{
  "accountId": "550e8400-e29b-41d4-a716-446655440000",
  "contactInformation": {
    "email": "[e-mail]",
    "phone": "[phone]"
  },
  "counterpartyParticipant": "87654321",
  "createdAt": "2023-11-07T05:31:56Z",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "reason": "REFUND_REQUEST",
  "reporterParticipant": "12345678",
  "situationType": "SCAM",
  "status": "OPEN",
  "transactionId": "E12345678202411241430ABCDEFGHIJK",
  "updatedAt": "2023-11-07T05:31:56Z",
  "analysisDetails": "Analysis confirms fraudulent activity pattern",
  "analysisResult": "AGREED",
  "bacenFundsRecoveryId": "91d65e98-97c0-4b0f-b577-73625da1f9fc",
  "fraudMarkerId": "FM123456789",
  "infractionAmount": "1500.00",
  "reportDetails": "Customer reported receiving a call from fake bank employee requesting PIX payment for supposed security verification",
  "transactionDepth": 1
}

Autorizaciones

Authorization · string · header · requerido

JWT bearer token issued by the identity provider.

Cuerpo

application/json

contactInformation · object · requerido

Contact information of the person reporting the fraud

Show child attributes

reason · enum<string> · requerido

Report reason type

Opciones disponibles: REFUND_REQUEST, REFUND_CANCELLED

Minimum string length: 1

Ejemplo:

"REFUND_REQUEST"

situationType · enum<string> · requerido

Type of fraud situation

Opciones disponibles: SCAM, ACCOUNT_TAKEOVER, COERCION, FRAUDULENT_ACCESS, OTHER, UNKNOWN

Minimum string length: 1

Ejemplo:

"SCAM"

transactionId · string · requerido

Pix End-to-End transaction ID (32 characters)

Minimum string length: 1

Ejemplo:

"E12345678202411241430ABCDEFGHIJK"

reportDetails · string

Detailed description of the fraud incident (max 2000 characters)

Maximum string length: 2000

Ejemplo:

"Customer reported receiving a call from fake bank employee requesting PIX payment for supposed security verification"

Respuesta

201

application/json

Created

accountId · string · requerido

Account ID (UUID) of the contested Pix transfer when the report arrived through BTG; empty when it was opened through this API

Ejemplo:

"550e8400-e29b-41d4-a716-446655440000"

contactInformation · object · requerido

Contact information of the person reporting the fraud

Show child attributes

counterpartyParticipant · string · requerido

ISPB of the counterparty PSP (8 uppercase alphanumeric characters)

Ejemplo:

"87654321"

createdAt · string<date-time> · requerido

Creation timestamp (ISO 8601 UTC)

Ejemplo:

"2023-11-07T05:31:56Z"

id · string · requerido

Unique identifier for the infraction report (UUID)

Ejemplo:

"550e8400-e29b-41d4-a716-446655440000"

reason · string · requerido

Report reason type

Ejemplo:

"REFUND_REQUEST"

reporterParticipant · string · requerido

ISPB of the PSP reporting the infraction (8 uppercase alphanumeric characters)

Ejemplo:

"12345678"

situationType · string · requerido

Type of fraud situation

Ejemplo:

"SCAM"

status · enum<string> · requerido

Current status of the infraction report

Opciones disponibles: OPEN, ACKNOWLEDGED, CLOSED, CANCELLED

Ejemplo:

"OPEN"

transactionId · string · requerido

PIX End-to-End transaction ID (32 alphanumeric characters)

Ejemplo:

"E12345678202411241430ABCDEFGHIJK"

updatedAt · string<date-time> · requerido

Last update timestamp (ISO 8601 UTC)

Ejemplo:

"2023-11-07T05:31:56Z"

analysisDetails · string

Detailed analysis from counterparty (max 2000 characters)

Ejemplo:

"Analysis confirms fraudulent activity pattern"

analysisResult · enum<string>

Analysis result from counterparty (if closed)

Opciones disponibles: AGREED, DISAGREED

Ejemplo:

"AGREED"

bacenFundsRecoveryId · string

BACEN/BTG funds-recovery identifier linking this infraction to its MED Funds Recovery process

Ejemplo:

"91d65e98-97c0-4b0f-b577-73625da1f9fc"

fraudMarkerId · string

Unique fraud marker identifier from BACEN

Ejemplo:

"FM123456789"

infractionAmount · string

Monetary amount of the infraction in BRL

Ejemplo:

"1500.00"

reportDetails · string

Detailed description of the fraud incident

Ejemplo:

"Customer reported receiving a call from fake bank employee requesting PIX payment for supposed security verification"

transactionDepth · integer<int64>

Depth of the infraction's transaction in the DICT tracking graph (root = 1). Set by DICT; absent until DICT provides it.

Ejemplo:

1