This flow is a suggested reading of the BACEN manuals for Pix. The manuals prevail over this page. Your institution, as the participant, validates the flow and implements it on the Lerian APIs. See how to read the diagrams.
Participants
- Your institution. The Pix participant of the paying customer. It opens the recovery and follows it.
- Pix Lerian. Keeps the recovery and publishes each change.
- Lerian SPI. Exchanges the recovery with DICT and reads its changes from DICT.
- DICT. The BACEN directory. It traces the funds and runs the recovery with the receiving participants.
Before you start
- The Pix left an account of your institution in the last 80 days. Keep its end-to-end ID.
- Your systems receive the Pix Lerian events. See Pix Lerian events.
Diagram
Open the recovery
Request the refund
Rules
situationTypeis one ofSCAM,ACCOUNT_TAKEOVER,COERCION,FRAUDULENT_ACCESS,OTHERorUNKNOWN. WithOTHER, describe the case inreportDetails.- A Pix takes one recovery. A cancelled recovery also counts.
- A recovery is a case at DICT. Its status alone does not show that funds came back.
- To stop a recovery, cancel it with
POST /dict/funds-recoveries/{id}/cancel.
How you know it finished
Pix Lerian publishes
funds_recovery.updated, and GET /dict/funds-recoveries/{id} shows the recovery in COMPLETED.
What can go wrong
The Pix Lerian error list describes each code.

