Create funds recovery [beta]
Creates and establishes a new funds recovery to track and block diverted funds in Pix fraud cases.
The tracking follows the chain of subsequent transactions starting from the contested transaction.
DICT manages the entire process. You define the initial tracking_graph_parameters and DICT executes tracking, prioritization, and blocking, then opens the infraction notifications that the receiving PSPs analyze.
Notes:
- The contested transaction must have occurred less than 80 days ago. This limit is the same for an original transaction and for a reversal transaction.
- Only the payer of the contested transaction can create funds recovery. When contesting a reversal, the payer is the participant that sent the reversal — that is, the PSP of the party who received the original transaction.
- root_transaction_id takes the end-to-end ID of the original transaction, or the reversal end-to-end ID when contesting a reversal.
- A reversal issued to settle an operational flaw cannot be contested. If the refund behind the reversal had refund_reason of OPERATIONAL_FLAW, DICT rejects the funds recovery as ineligible. This is the only restriction on contesting a reversal.
- When contesting a reversal, situation_type must be OTHER, which makes report_details mandatory.
- Recipient PSPs have 7 calendar days to analyze infraction notifications
- Refund must be initiated within 72 hours after analysis completion
- Once refunding starts, the process cannot be cancelled
Terminology: the DICT operating manual refers to an original transaction as pacs.008 and to a reversal transaction as pacs.004.
Thie endpoint generates a Pix funds recovery status changed event.
For more information refer to Pix funds recovery.
Request
- Base URLhttps://sandbox.pismolabs.io/pix-dict
- URLhttps://sandbox.pismolabs.io/pix-dict/v1/pix/funds-recoveries
- AuthHTTP bearer
Request body
Example request
{
"root_transaction_id": "E1234567890123456789012345678901",
"contact_information": {
"phone": "551154874551",
"email": "polly_ester@email.com"
},
"report_details": "Details that can help the receiving participant to analyze the suspected violation",
"tracking_graph_parameters": {
"hop_window": "PT2H",
"max_hops": 5
}
}Response
Created - synchronous success
Example response
{
"id": "53D0F66A-BAB0-49D7-B7DC-807B82AABD8D",
"status": "CREATED",
"root_transaction_id": "E1234567890123456789012345678901",
"reporter_participant": "12345678",
"contact_information": {
"phone": "551154874551",
"email": "polly_ester@email.com"
},
"report_details": "Details that can help the receiving participant to analyze the suspected violation",
"created_at": "2020-08-13T13:49:03Z",
"updated_at": "2020-08-13T13:49:03Z"
}Changes
No recorded changes to this operation across all 1 revision of this API.