--- title: "Close infraction report" method: POST path: "/v2/pix/infraction-reports/{id}/close" tags: ["Infraction reports"] --- # Close infraction report `POST /v2/pix/infraction-reports/{id}/close` ## Request - Base URL: `https://sandbox.pismolabs.io/pix-dict` - URL: `https://sandbox.pismolabs.io/pix-dict/v2/pix/infraction-reports/{id}/close` - Auth: HTTP bearer Closes an infraction report. Only the counterparty participant can close an infraction report. The operation is idempotent. If you try to close the report again with the same parameters, you will get the same response as the first time. On PSP timeout, a `202 Accepted` response is returned and the process continues asynchronously, eventually emitting a success or failure event. This endpoint generates a Pix infraction status changed event. ## Path parameters - `id` string, uuid, required ## Headers - `Authorization` string, required ## Request body - InfractionCloseRequest - `analysis_result` 'AGREED' | 'DISAGREED', required: Infraction analysis result - `fraud_type` 'APPLICATION_FRAUD' | 'MULE_ACCOUNT' | 'SCAMMER_ACCOUNT' | 'OTHER': Verified fraud type. **REQUIRED** if `analysis_result` = `AGREED`. - `analysis_details` string: Infraction's analysis details, which can guide the payer to next steps. ## Response `200` OK - PresenterInfractionReportResponse - `creation_date` string, date-time, required: Creation datetime. A RFC 3339 date-time value. For example - `2023-04-12T23:20:50.52Z`. - `credited_participant` string, required: Credited participant's ISPB (Identifcador do Sistema de Pagamento Brazil) number - the Brazilian Payment System identifier, an 8-digit value. - `debited_participant` string, required: Debited participant's ISPB (Identifcador do Sistema de Pagamento Brazil) number - the Brazilian Payment System identifier, an 8-digit value. - `end_to_end_id` string, required: This field is a Brazil Central Bank (BCB) requirement to track all steps of Pix transactions. Basically, there are two steps to a Pix transaction: 1. Initialize a transaction 2. Confirm a transaction The end_to_end_id is sent to the BCB in both steps in order to identify all transaction information. - `infraction_report_id` string, uuid, required: Infraction report ID (UUID) - `infraction_type` 'FRAUD' | 'REFUND_REQUEST' | 'REFUND_CANCELLED', required: Infraction type: * `FRAUD` - Payer or payee requested. * `REFUND_REQUEST` - Initiated only by payer's payment service provider (PSP). Used to mark a key as fraudulent and asks for a refund. * `REFUND_CANCELLED` - Initiated only by payee's PSP. To indicate that a refund done thru an infraction process was a fraud and needs to be returned, - `last_modified` string, date-time, required: Last modified datetime. A RFC 3339 date-time value. For example - `2023-04-12T23:20:50.52Z`. - `reported_by` 'DEBITED_PARTICIPANT' | 'CREDITED_PARTICIPANT', required: Who filed the infraction report - `status` 'OPEN' | 'ACKNOWLEDGED' | 'CLOSED' | 'CANCELLED', required: Infraction status - `transaction_id` string, required: Transaction ID - `analysis_details` string: Analysis details - `analysis_result` 'AGREED' | 'DISAGREED' | 'PARTIALLY_ACCEPTED' | 'TOTALLY_ACCEPTED' | 'REJECTED': Analysis results - `bacen_response_time` string, date-time: Banco Central do Brasil (Central Bank of Brazil) response datetime. A RFC 3339 date-time value. For example - `2023-04-12T23:20:50.52Z`. - `correlation_id` string, uuid: The correlation identifier is used to link related API requests and events. The Pismo engineering team can use this to track everything related to a call. If one is not passed, it is automatically generated and returned to the client in a response header. - `infraction_data` PresenterInfractionData - `credited_participant` string, required: Credited participant's ISPB (Identifcador do Sistema de Pagamento Brazil) number - the Brazilian Payment System identifier, an 8-digit value. - `debited_participant` string, required: Debited participant's ISPB (Identifcador do Sistema de Pagamento Brazil) number - the Brazilian Payment System identifier, an 8-digit value. - `infracting_account_data` PresenterInfractingAccountData, required - `account_number` string, required: Account number. - `branch` string: Bank-assigned branch ID or ISPB (Identifcador do Sistema de Pagamento Brazil) number - the Brazilian Payment System identifier, an 8-digit value. - `reported_by` 'DEBITED_PARTICIPANT' | 'CREDITED_PARTICIPANT', required: Who filed the infraction report - `tax_id_number` string, required: A government document number, such as a Social Security number (US) or Cadastro de Pessoas Físicas number (Brazil). Must be numeric with 11-14 digits. - `transaction_date` string, date-time, required: Transaction date time. RFC 3339 date-time value. For example - `2023-04-12T23:20:50.52Z`. - `key` string: Value, based on a key's type, used to encrypt Pix key. - `report_details` string: Details about report - `transaction_result` 'SETTLED' | 'REJECTED_PAYEE' | 'REJECTED_PAYER': Transaction result - `transaction_type` 'SPI' | 'INTERNAL': Transaction type: * `SPI` - Transaction was created in the Central Bank system. * `INTERNAL` - Transaction was created internally in the Pismo system. - `contact_information` ContactInformation - `phone` string, required: Contact phone number - `email` string, required: Contact email ## Other responses - `202`: Accepted - `400`: Bad Request - `401`: Unauthorized - `403`: Forbidden - `404`: Resource Not Found - `429`: Too many requests - `500`: Internal Server Error - `502`: Bad Gateway - `503`: Service Unavailable - `504`: Gateway Timeout --- [API](https://skmtc.dev/pismo/apis/instant-payments-pix-management.md) - [All operations](https://skmtc.dev/pismo/apis/instant-payments-pix-management/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/instant-payments-pix-management/revisions/eb540c289547?raw)