> ## Documentation Index > Fetch the complete documentation index at: https://docs.fincle.com.br/llms.txt > Use this file to discover all available pages before exploring further. # List infractions > Lists the infractions filed against transactions of the account, with the disputed amount and the outcome of the analysis. ## OpenAPI ````yaml /openapi.yaml get /infractions openapi: 3.0.3 info: title: Fincle API version: 1.0.0 description: >- Fincle payments API: charges by Pix, credit card and boleto, subscriptions, transactions, refunds, infractions, notifications and transfers. servers: - url: https://api.fincle.com.br description: Production server security: [] tags: - name: Authentication description: Issuance of the access token from the API key. - name: Charges description: Creation of charges by Pix, credit card and boleto. - name: Subscriptions description: Recurring billing on credit card. - name: Transactions description: Retrieval and refund of transactions. - name: Refunds description: Refund requests submitted by payers. - name: Infractions and MED description: Pix infraction reports and the amounts blocked as a result. - name: Webhooks description: Registration of notification endpoints and tracking of deliveries. - name: Balance and transfers description: Balance, statement, fees and transfer of the amounts received. paths: /infractions: get: tags: - Infractions and MED summary: List infractions description: >- Lists the infractions filed against transactions of the account, with the disputed amount and the outcome of the analysis. operationId: listInfractions parameters: - schema: type: integer minimum: 1 default: 1 in: query name: page required: false description: Requested page, starting at 1. - schema: type: integer minimum: 1 maximum: 100 default: 10 in: query name: pageSize required: false description: Number of items per page (maximum 100). - schema: anyOf: - type: string enum: - OPEN - CANCELLED - ACKNOWLEDGED - DEFENDED - ANSWERED - WAITING_ADJUSTMENTS - CLOSED - WAITING_PSP - type: array items: type: string enum: - OPEN - CANCELLED - ACKNOWLEDGED - DEFENDED - ANSWERED - WAITING_ADJUSTMENTS - CLOSED - WAITING_PSP in: query name: status required: false description: >- Filters by one or more statuses; repeat the parameter to add statuses. responses: '200': description: Page of infractions filed against the account. content: application/json: schema: type: object properties: success: type: boolean description: Always `true` in a successful response. data: type: array items: type: object properties: id: type: string description: Infraction identifier. externalId: type: string description: >- Infraction identifier in the partner institution's system. status: type: string enum: - OPEN - CANCELLED - ACKNOWLEDGED - DEFENDED - ANSWERED - WAITING_ADJUSTMENTS - CLOSED - WAITING_PSP description: Status of the infraction in the analysis workflow. type: type: string enum: - FRAUD - REFUND_REQUEST - REFUND_CANCELLED description: 'Nature of the dispute: fraud or return request.' amount: type: integer description: Disputed amount in cents (R$ 199.00 = 19900). reportedBy: type: string enum: - CREDITED_PARTICIPANT - DEBITED_PARTICIPANT nullable: true description: >- Which side filed the dispute: the receiving or the paying side. reportDetails: type: string nullable: true description: Reason stated by the party that filed the dispute. analysisResults: type: string enum: - AGREED - DISAGREED nullable: true description: >- Outcome of the analysis: `AGREED` upholds the dispute, `DISAGREED` rejects it. analysisDetails: type: string nullable: true description: Grounds for the outcome of the analysis. message: type: string nullable: true description: >- Free-text message attached to the infraction by the partner institution. transactionIds: type: array items: type: string description: >- Transactions of the account affected by the disputed Pix. defenses: type: array items: type: object properties: id: type: integer description: Identifier of the defense submitted. defenseDetails: type: string description: Text of the defense submitted. fileCount: type: integer description: Number of files attached as evidence. createdAt: type: string format: date-time description: Time at which the defense was recorded. required: - id - defenseDetails - fileCount - createdAt additionalProperties: false description: Defenses already submitted, from oldest to newest. createdAt: type: string format: date-time description: Time at which the infraction reached the platform. updatedAt: type: string format: date-time description: Time of the last update to the infraction. required: - id - externalId - status - type - amount - reportedBy - reportDetails - analysisResults - analysisDetails - message - transactionIds - defenses - createdAt - updatedAt additionalProperties: false pagination: type: object properties: page: type: integer description: Page returned. pageSize: type: integer description: Items per page requested. total: type: integer description: Total number of items matching the filter. totalPages: type: integer description: Total number of pages available. required: - page - pageSize - total - totalPages additionalProperties: false required: - success - data - pagination additionalProperties: false description: Page of infractions filed against the account. example: success: true data: - id: clx9d5n6s0009qz0a3m4n5o6p externalId: INF-2026-0009123 status: OPEN type: FRAUD amount: 19700 reportedBy: DEBITED_PARTICIPANT reportDetails: The payer states that the transaction is not recognized. analysisResults: null analysisDetails: null message: Prazo de resposta de 7 dias corridos a partir da abertura. transactionIds: - clx9b3k2p0007qz0a7h8i9j0k defenses: - id: 3312 defenseDetails: >- Proof of service delivery issued on 2026-09-05, with record of the payer's acceptance. fileCount: 2 createdAt: '2026-09-11T16:20:00.000Z' createdAt: '2026-09-10T09:14:00.000Z' updatedAt: '2026-09-11T16:20:00.000Z' pagination: page: 1 pageSize: 10 total: 1 totalPages: 1 '401': description: Token missing, invalid, expired or belonging to a blocked account. content: application/json: schema: type: object properties: success: type: boolean description: Always `false` in an error response. message: type: string description: Readable message explaining the failure. required: - success - message additionalProperties: false description: >- Token missing, invalid, expired or belonging to a blocked account. example: success: false message: Token inválido ou expirado '422': description: The request did not pass schema validation. content: application/json: schema: type: object properties: success: type: boolean description: Always `false` in an error response. message: type: string description: Readable message explaining the failure. required: - success - message additionalProperties: false description: The request did not pass schema validation. example: success: false message: 'name: Nome é obrigatório' '429': description: >- Too many requests: the limit is 1000 requests per minute per source IP. Wait the number of seconds given in the `retry-after` header and retry with exponential backoff. content: application/json: schema: type: object properties: success: type: boolean description: Always `false` in an error response. message: type: string description: Readable message explaining the failure. required: - success - message additionalProperties: false description: >- Too many requests: the limit is 1000 requests per minute per source IP. Wait the number of seconds given in the `retry-after` header and retry with exponential backoff. example: success: false message: Muitas requisições. Tente novamente em breve. headers: retry-after: $ref: '#/components/headers/retry-after' x-ratelimit-limit: $ref: '#/components/headers/x-ratelimit-limit' x-ratelimit-remaining: $ref: '#/components/headers/x-ratelimit-remaining' x-ratelimit-reset: $ref: '#/components/headers/x-ratelimit-reset' '500': description: >- Internal failure while processing the request. Retry; if it persists, open a support ticket stating the time and the route. content: application/json: schema: type: object properties: success: type: boolean description: Always `false` in an error response. message: type: string description: Readable message explaining the failure. required: - success - message additionalProperties: false description: >- Internal failure while processing the request. Retry; if it persists, open a support ticket stating the time and the route. example: success: false message: Erro interno do servidor security: - bearerAuth: [] components: headers: retry-after: description: Seconds to wait before repeating the request. schema: type: integer x-ratelimit-limit: description: >- Maximum number of requests in the window (1000). Present in every response. schema: type: integer x-ratelimit-remaining: description: >- Number of requests still available in the current window. Present in every response. schema: type: integer x-ratelimit-reset: description: Seconds until the window counter resets. Present in every response. schema: type: integer securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.