---
title: "Create funds recovery [beta]"
method: POST
path: "/v1/pix/funds-recoveries"
tags: ["Funds recovery"]
---

# Create funds recovery [beta]

`POST /v1/pix/funds-recoveries`

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 original fraudulent transaction.

**Automated flow**

   DICT manages the entire process automatically. You only define the initial parameters and the system executes tracking, prioritization, and blocking.
   **Use for**: Standard cases, high volume of recoveries, or when you trust DICT's default algorithm.

**Notes:**

  * Fraudulent transactions must have occurred less than **80 days** ago
  * Only the **debtor participant** (payer) can create funds recovery
  * 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**

Thie endpoint generates a [Pix funds recovery status changed](https://developers.pismo.io/events/docs/pix-dict-funds-recoveries-status-change-1) event.

For more information refer to [Pix funds recovery](https://developers.pismo.io/pismo-docs/docs/pix-funds-recovery).

## Request body

- CreateFundsRecoveryRequest — Create funds recovery request
  - `root_transaction_id` string, required — Fraudulent transaction end-to-end-id
  - `situation_type` 'SCAM' | 'ACCOUNT_TAKEOVER' | 'COERCION' | 'FRAUDULENT_ACCESS' | 'OTHER' | 'UNKNOWN', required — Situation type: * `SCAM` - Scam/fraud through social engineering * `ACCOUNT_TAKEOVER` - Unauthorized transaction without digital authentication * `COERCION` - Coercion crime (kidnapping, extortion) * `FRAUDULENT_ACCESS` - Fraudulent access and authorization (phishing, stolen password) | * `OTHER` - Other cases. This option **REQUIRES** you pass `report_details`. * `UNKNOWN` - Unknown state
  - `contact_information` ContactInformation, required
    - `phone` string, required — Contact phone number
    - `email` string, required — Contact email
  - `report_details` string — Details about report
  - `tracking_graph_parameters` TrackingGraphParameters — Graph parameters. Higher values for `min_transaction_amount` and lower values for `max_transactions`,`max_hops`, and `hop_window` generate smaller and faster graphs. The opposite generates larger and more complete graphs.
    - `min_transaction_amount` number, required — Minimum amount in Brazilian reals to include transaction in tracking.
    - `max_transactions` integer, required — Maximum number of transactions to track
    - `hop_window` string, required — The window duration between transactions * `PT30M` - 30 minutes * `PT45M` - 45 minutes * `PT1H` - 1 hour * `PT2H` - 2 hours
    - `max_hops` integer, required — Maxium tracking depth (1-10 layers)

## Response `201`

Created - synchronous success

- CreateFundsRecoveryResponse — Create funds recovery request
  - `id` string — Funds recovery identifier. Returned from the [Create funds recovery](https://developers.pismo.io/pismo-docs/reference/post-create-funds-recovery) endpoint.
  - `status` 'CREATED' | 'AWAITING_ANALYSIS' | 'TRACKED' | 'ANALYSED' | 'REFUNDING' | 'COMPLETED' | 'CANCELLED' — Funds recovery status: * `CREATED` - For `INTERACTIVE` * `AWAITING_ANALYSIS` - For `AUTOMATED` when processed synchronously * `CREATED` - Recovery created, awaiting next action. Both flows. * `TRACKED` - Tracking graph created. `INTERACTIVE` only * `AWAITING_ANALYSIS` - Awaiting analysis from receiver PSPs (deadline: 7 days). Both flows. * `ANALYSED` - Analysis completed, ready for refund. Both flows * `REFUNDING` - Refund process in progress. Both flows. * `COMPLETED` - Recovery successfully completed. Both flows. * `CANCELLED` - Recovery cancelled. Both flows.
  - `root_transaction_id` string — Fraudulent transaction end-to-end-id
  - `situation_type` 'SCAM' | 'ACCOUNT_TAKEOVER' | 'COERCION' | 'FRAUDULENT_ACCESS' | 'OTHER' | 'UNKNOWN' — Situation type: * `SCAM` - Scam/fraud through social engineering * `ACCOUNT_TAKEOVER` - Unauthorized transaction without digital authentication * `COERCION` - Coercion crime (kidnapping, extortion) * `FRAUDULENT_ACCESS` - Fraudulent access and authorization (phishing, stolen password) | * `OTHER` - Other cases. This option **REQUIRES** you pass `report_details`. * `UNKNOWN` - Unknown state
  - `reporter_participant` string — Reporter participant ID
  - `contact_information` ContactInformation
    - `phone` string, required — Contact phone number
    - `email` string, required — Contact email
  - `report_details` string — Details about report
  - `created_at` string, date-time — Creation datetime. A RFC 3339 date-time value. For example - `2023-04-12T23:20:50.52Z`.
  - `updated_at` string, date-time — Updated datetime. A RFC 3339 date-time value. For example - `2023-04-12T23:20:50.52Z`.

## Other responses

- `202` — Funds recovery creation continues asynchronously
- `400` — Invalid request data
- `403` — Not authorized to create funds recovery for this transaction
- `404` — Transaction not found
- `409` — Recovery already exists
- `504` — Timeout

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)
