Create a funds recovery
Opens a MED 2.0 funds recovery. A successful creation returns HTTP 201 with status CREATED. When BACEN has not resolved the creation yet, the recovery is stored as PENDING with an empty bacenFundsRecoveryId and returned with HTTP 202: keep its id and use it for every later operation. A PENDING recovery resolves when it is next read or operated on, or when the provider reports on it: it then reads as CREATED with its bacenFundsRecoveryId or, when BACEN never applied the creation, it is withdrawn and reads as 404 / PIX-0110, which frees the root transaction for a new creation. While it is PENDING, cancel, refund, and patch return 409 / PIX-0114, the tracking graph returns 404 / PIX-0110, and the linked lists are empty. Resending the same request under an X-Idempotency header within one hour returns the original 201 or 202 response, status included, with the header X-Idempotency-Replayed: true; a resend while the first request still runs answers 412 / PIX-0112 with Retry-After: 1; a failed creation is not cached, so repeating it runs the creation again. A duplicate recovery is rejected with 409 / PIX-0113. If the timestamp in rootTransactionId is outside the applicable MED contestation window, the request is rejected with 422 / PIX-0117. The window is determined by the funds recovery creation time: pacs.008 uses 80 calendar days; pacs.004 uses 30 calendar days before 2026-09-01T00:00:00Z and 80 calendar days from that instant onward. This timestamp validation does not confirm that the referenced transaction exists. The participant is determined by the authenticated tenant. participantId, reporterParticipant, rootTransactionType, and idempotencyKey are rejected when included in the body. If an earlier request for the same operation is still in progress at the provider, the request is rejected with 409 / PIX-0035 and nothing changes: retry after a short wait.
Autorizações
JWT bearer token issued by the identity provider.
Cabeçalhos
Idempotency key (at most 64 bytes); required on create. Enforced by the replay middleware, not the handler.
"a1b2c3d4-0000-0000-0000-000000000001"
Corpo
"550e8400-e29b-41d4-a716-446655440000"
"E12345678202605171530aB3xK9mWq2z"
SCAM, ACCOUNT_TAKEOVER, COERCION, FRAUDULENT_ACCESS, OTHER, UNKNOWN "SCAM"
The time the paying user's complaint was registered in your service channel, in RFC 3339. Required. A time later than the moment the recovery opens is refused with 422 (PIX-0100). Pix Lerian does not send it to BACEN; it relays it to the provider and stores it with the recovery.
"2026-05-17T13:15:00Z"
"Victim of a WhatsApp scam"
Resposta
Created
"550e8400-e29b-41d4-a716-446655440000"
Recovery id the provider assigned. Empty while status is PENDING.
"9f3a8b7e-2c1d-4e5a-8b6f-1a2b3c4d5e6f"
"2026-05-17T13:30:00Z"
"018f8c1d-1234-7abc-9def-000000000001"
"12345678"
"12345678"
"E12345678202605171530aB3xK9mWq2z"
SCAM, ACCOUNT_TAKEOVER, COERCION, FRAUDULENT_ACCESS, OTHER, UNKNOWN "SCAM"
PENDING, CREATED, TRACKED, AWAITING_ANALYSIS, ANALYSED, REFUNDING, COMPLETED, CANCELLED "CREATED"
"2026-05-17T13:30:00Z"
"7c9e6679742540de944be07fc1f90ae7"
"Victim of a WhatsApp scam"

