> ## 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.

# Infractions and MED

> Effects of Pix infraction reports on the transaction and the balance.

The Special Return Mechanism (Mecanismo Especial de Devolução, MED) is the procedure of the Pix scheme for returning amounts in cases of well-founded suspicion of fraud or of operational failure. It was established by BCB Resolution No. 103 of 8 June 2021, which amended the Regulation annexed to BCB Resolution No. 1 of 12 August 2020.

## How it works

The procedure begins with the dispute raised by the payer with the institution where they hold an account. That institution files an infraction report addressed to the payee's institution, which blocks the corresponding funds in the payee's account while the analysis is carried out. Once the analysis is concluded, the funds are returned to the payer, if the dispute is upheld, or released to the payee otherwise.

The Pix Regulation sets the time limits for the payer to raise the dispute and for the institutions to conclude the analysis. Those time limits and the other conditions of the procedure must be consulted in the text of the Regulation in force.

## Effects of the infraction report

The filing of an infraction against a Pix transaction produces three simultaneous effects.

| Effect | Description |
| - | - |
| Transaction status | The transaction moves from the `paid` status to the `infraction` status. |
| Precautionary block | The disputed amount is blocked in the account balance and ceases to be available for transfer. |
| Notification | The `infraction` event is sent to the registered endpoints. |

## Outcome

The outcome follows from the final status of the infraction (`status`) and the result of the analysis (`analysisResults`).

| Final status | Result of the analysis | Effect |
| - | - | - |
| `CLOSED` | `DISAGREED` | Infraction rejected. The block is lifted, and the transaction returns to the `paid` status. |
| `CANCELLED` | Not applicable | Infraction cancelled. The block is lifted, and the transaction returns to the `paid` status. |
| `CLOSED` | `AGREED` | Infraction upheld. The amount is returned to the payer, the transaction moves to the `refund` status, and the block is closed. |

## Retrieving infractions

The `GET /infractions` operation lists the infractions of the account, in descending order of last update.

| Field | Description |
| - | - |
| `id` | Infraction identifier. |
| `externalId` | Infraction identifier in the partner institution's system. |
| `type` | Nature of the infraction: `FRAUD` (suspected fraud), `REFUND_REQUEST` (return request) or `REFUND_CANCELLED` (cancellation of a return). |
| `status` | Status in the analysis workflow: `OPEN`, `ACKNOWLEDGED`, `WAITING_PSP`, `WAITING_ADJUSTMENTS`, `DEFENDED`, `ANSWERED`, `CLOSED` or `CANCELLED`. |
| `amount` | Disputed amount, in cents. |
| `reportedBy` | Participant that filed the infraction: `DEBITED_PARTICIPANT` (payer's institution) or `CREDITED_PARTICIPANT` (payee's institution). |
| `reportDetails` | Reason stated when the infraction was filed. |
| `analysisResults` | Result of the analysis: `AGREED` (upheld) or `DISAGREED` (rejected). |
| `analysisDetails` | Grounds for the result. |
| `transactionIds` | Transactions covered by the infraction. |
| `defenses` | Defenses submitted. |

## Blocked amounts

The `GET /blocked-amounts` operation lists the amounts held on the account, with the reason for the block and, in the `infractionId` field, the infraction that gave rise to it. The operation makes it possible to reconcile the difference between the amount received and the amount available for transfer.

## Notification structure

The `infraction` event contains the data of the infraction and of the transaction covered. The end-to-end identifier (`endToEndId`) is the same as that of the original payment, which makes it possible to locate the transaction in the integrator's records.

```json theme={null}
{
  "id": "0d6e13bf-d348-4282-aebd-769f142ebcee",
  "type": "infraction",
  "event": "infraction",
  "scope": "user",
  "infraction": {
    "id": "cmdf2k1p0000a1yjn3c9x7q2b",
    "amount": 125000,
    "status": "WAITING_PSP",
    "pix": { "endToEndId": "E18236120202611121410s12e9976c00" }
  },
  "transaction": {
    "id": "cmddiqpxo09zf1yju2kqkhgga",
    "amount": 125000,
    "status": "infraction",
    "pix": { "endToEndId": "E18236120202611121410s12e9976c00", "payerInfo": null }
  }
}
```

## Recommended conduct

Upon receipt of an infraction notification, it is recommended that the integrator:

* suspend the delivery of goods or the provision of services linked to the transaction, where not yet performed
* gather the evidence that demonstrates the regularity of the operation, including proof of delivery or of service provision and the records of the payer's acceptance
* monitor the status of the infraction through `GET /infractions` until the outcome
* treat the blocked amount as unavailable in its cash planning until the block is lifted


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.