> ## 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. # Close an Infraction Report > **DEPRECATED:** This endpoint is deprecated and will be removed in a future release due to MED 2.0 changes. MED 2.0 manages infraction report updates through the Funds Recovery lifecycle. Use this endpoint to submit the closure analysis for an infraction report received. This endpoint must be used to respond to infractions reported to your PSP, meaning when the account was the receiver of the transaction reported as fraud, within 7 days with the analysis result. **Notes:** - Closing a report sets its status to CLOSED and records the analysis result - Once closed, the report cannot be modified - For `REFUND_REQUEST` infractions, the report must be closed by the payee's PSP - For `REFUND_CANCELLED` infractions, the report must be closed by the payer's PSP ## OpenAPI ````yaml /pt/openapi/v3-current/indirect-pix.yaml post /v1/dict/infraction-reports/{infraction_id}/close openapi: 3.1.0 info: 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. title: Pix BTG API version: 1.12.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/{infraction_id}/close: post: tags: - Infraction Reports summary: Close an Infraction Report description: >- **DEPRECATED:** This endpoint is deprecated and will be removed in a future release due to MED 2.0 changes. MED 2.0 manages infraction report updates through the Funds Recovery lifecycle. Use this endpoint to submit the closure analysis for an infraction report received. This endpoint must be used to respond to infractions reported to your PSP, meaning when the account was the receiver of the transaction reported as fraud, within 7 days with the analysis result. **Notes:** - Closing a report sets its status to CLOSED and records the analysis result - Once closed, the report cannot be modified - For `REFUND_REQUEST` infractions, the report must be closed by the payee's PSP - For `REFUND_CANCELLED` infractions, the report must be closed by the payer's PSP operationId: dict-close-infraction-report parameters: - description: Unique identifier of the infraction report (UUID format) in: path name: infraction_id required: true schema: description: Unique identifier of the infraction report (UUID format) format: uuid type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/CloseInfractionReportInput' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/CloseInfractionReportOutput' description: OK '400': content: application/json: schema: $ref: '#/components/schemas/LegacyErrorBody' description: Bad Request '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: CloseInfractionReportInput: additionalProperties: false properties: analysisDetails: description: >- Detailed analysis notes. Max 2000 characters. Required if fraudType is OTHER examples: - Fraud pattern confirmed through transaction history analysis maxLength: 2000 type: string analysisResult: description: 'Analysis result: AGREED or DISAGREED' enum: - AGREED - DISAGREED examples: - AGREED minLength: 1 type: string fraudType: description: Type of fraud detected. Required if analysisResult is AGREED enum: - APPLICATION_FRAUD - MULE_ACCOUNT - SCAMMER_ACCOUNT - OTHER - UNKNOWN - '' examples: - SCAMMER_ACCOUNT type: string required: - analysisResult type: object CloseInfractionReportOutput: additionalProperties: false properties: accountId: description: Account ID (UUID) examples: - 550e8400-e29b-41d4-a716-446655440000 type: string analysisDetails: description: Detailed analysis from counterparty examples: - Analysis confirms fraudulent activity pattern type: string analysisResult: description: Analysis result from counterparty 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 involved in the transaction examples: - '87654321' type: string createdAt: description: Timestamp when the report was created (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 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: - CLOSED 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: Timestamp when the report was last updated (ISO 8601 UTC) examples: - '2023-11-07T06:45:30Z' format: date-time type: string required: - id - accountId - transactionId - reason - situationType - contactInformation - status - reporterParticipant - counterpartyParticipant - createdAt - updatedAt type: object LegacyErrorBody: additionalProperties: false properties: 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 code: 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.