> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # 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 90 days from the transaction date ## OpenAPI ````yaml /pt/openapi/v3-current/indirect-pix.yaml post /v1/dict/infraction-reports openapi: 3.1.0 info: contact: email: contact@lerian.studio name: Lerian Studio url: https://lerian.studio description: >- API for Pix Indirect via BTG. It covers DICT keys and claims; MED infraction reports, fraud markers, refund requests, and funds recoveries; DICT statistics and reconciliation; Pix transfers, refunds, and schedules; static QR codes and QR code decoding; immediate and due-date collections; Pix Automático for the payer; transaction reports and TemposTransacoes statistics; and inbound and outbound webhook records. license: name: Lerian Studio General License title: Pix BTG API version: 1.14.0 servers: - url: https://api.example.com description: >- Replace the example host with the URL provided during environment onboarding. security: - BearerAuth: [] paths: /v1/dict/infraction-reports: post: tags: - Infraction Reports summary: Create an Infraction Report description: >- **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 90 days from the transaction date operationId: dict-create-infraction-report requestBody: content: application/json: schema: $ref: '#/components/schemas/CreateInfractionReportInput' required: true responses: '201': content: application/json: schema: $ref: '#/components/schemas/CreateInfractionReportOutput' description: Created '400': content: application/json: schema: $ref: '#/components/schemas/LegacyErrorBody' description: Bad Request '413': content: application/json: schema: $ref: '#/components/schemas/LegacyErrorBody' description: Request Entity Too Large '500': content: application/json: schema: $ref: '#/components/schemas/LegacyErrorBody' description: Internal Server Error default: content: application/json: schema: $ref: '#/components/schemas/LegacyErrorBody' description: Error deprecated: true components: schemas: CreateInfractionReportInput: additionalProperties: false properties: contactInformation: $ref: '#/components/schemas/ContactInformation' description: Contact information of the person reporting the fraud reason: description: Report reason type enum: - REFUND_REQUEST - REFUND_CANCELLED examples: - REFUND_REQUEST minLength: 1 type: string reportDetails: description: Detailed description of the fraud incident (max 2000 characters) examples: - >- Customer reported receiving a call from fake bank employee requesting PIX payment for supposed security verification maxLength: 2000 type: string situationType: description: Type of fraud situation enum: - SCAM - ACCOUNT_TAKEOVER - COERCION - FRAUDULENT_ACCESS - OTHER - UNKNOWN examples: - SCAM minLength: 1 type: string transactionId: description: Pix End-to-End transaction ID (32 characters) examples: - E12345678202411241430ABCDEFGHIJK minLength: 1 type: string required: - transactionId - reason - situationType - contactInformation type: object CreateInfractionReportOutput: additionalProperties: false properties: accountId: description: >- Account ID (UUID) of the contested Pix transfer when the report arrived through BTG; empty when it was opened through this API examples: - 550e8400-e29b-41d4-a716-446655440000 type: string analysisDetails: description: Detailed analysis from counterparty (max 2000 characters) examples: - Analysis confirms fraudulent activity pattern type: string analysisResult: description: Analysis result from counterparty (if closed) enum: - AGREED - DISAGREED examples: - AGREED type: string bacenFundsRecoveryId: description: >- BACEN/BTG funds-recovery identifier linking this infraction to its MED Funds Recovery process examples: - 91d65e98-97c0-4b0f-b577-73625da1f9fc type: string contactInformation: $ref: '#/components/schemas/ContactInformation' description: Contact information of the person reporting the fraud counterpartyParticipant: description: ISPB of the counterparty PSP (8 uppercase alphanumeric characters) examples: - '87654321' type: string createdAt: description: Creation timestamp (ISO 8601 UTC) examples: - '2023-11-07T05:31:56Z' format: date-time type: string fraudMarkerId: description: Unique fraud marker identifier from BACEN examples: - FM123456789 type: string id: description: Unique identifier for the infraction report (UUID) examples: - 550e8400-e29b-41d4-a716-446655440000 type: string infractionAmount: description: Monetary amount of the infraction in BRL examples: - '1500.00' type: string reason: description: Report reason type examples: - REFUND_REQUEST type: string reportDetails: description: Detailed description of the fraud incident examples: - >- Customer reported receiving a call from fake bank employee requesting PIX payment for supposed security verification type: string reporterParticipant: description: >- ISPB of the PSP reporting the infraction (8 uppercase alphanumeric characters) examples: - '12345678' type: string situationType: description: Type of fraud situation examples: - SCAM type: string status: description: Current status of the infraction report enum: - OPEN - ACKNOWLEDGED - CLOSED - CANCELLED examples: - OPEN type: string transactionDepth: description: >- Depth of the infraction's transaction in the DICT tracking graph (root = 1). Set by DICT; absent until DICT provides it. examples: - 1 format: int64 type: integer transactionId: description: PIX End-to-End transaction ID (32 alphanumeric characters) examples: - E12345678202411241430ABCDEFGHIJK type: string updatedAt: description: Last update timestamp (ISO 8601 UTC) examples: - '2023-11-07T05:31:56Z' format: date-time type: string required: - id - accountId - transactionId - reason - situationType - contactInformation - status - reporterParticipant - counterpartyParticipant - createdAt - updatedAt type: object LegacyErrorBody: additionalProperties: false properties: code: type: string fields: additionalProperties: type: string type: object headers: additionalProperties: type: string type: object message: type: string paths: additionalProperties: type: string type: object queryParams: additionalProperties: type: string type: object raw: type: string title: type: string required: - code - title - message type: object ContactInformation: additionalProperties: true properties: email: description: Email address of the customer reporting the fraud examples: - customer@example.com minLength: 1 type: string phone: description: Phone number of the customer (E.164 format recommended) examples: - '+5511999999999' minLength: 1 type: string required: - email - phone type: object securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.