Receive a PIX Automatico recipient-side authorization registration event
Receives the JDPI notifica-autorizacao-recebedor-callback push event (section 6, body section 5.2.4): an async re-delivery of the recipient-side authorization registration. It reuses the inbound 5.2.4 register use case (load + transition to Accepted/Rejected). Idempotent: a re-delivery converging on the same status is a no-op. No response body.
Authorizations
JWT bearer token issued by the identity provider.
Headers
Bearer access token (the financial-ingress gate; the handler fails closed with PIX-0082 when absent).
"Bearer eyJ..."
Event registration instant (UTC: aaaa-mm-ddTHH:mm:ss.sssZ). Mandatory per §6.1.
"2024-06-05T10:10:05.025Z"
Event name (see §6.3.1 catalog). Mandatory per §6.1; informational passthrough.
"situacao-autorizacao-callback"
Body
Authorization timestamp (UTC).
"2024-09-20T14:11:27.453Z"
Recurrence creation timestamp (UTC).
"2024-09-20T09:25:49.025Z"
First payment date (aaaa-mm-dd).
"2024-01-10"
Unique recurrence id (29-char, RR...).
"RR0435879820240920njua7shf40o"
JDPI request id (36-char GUID).
"45F763C6-7487-4363-9406-A1DE2A9636D3"
Authorization journey (2..4).
2
Contract/order identifier (35-char).
"1234567890ABC"
The recurrence pagador. The spec marks pagador.codMunIbge Sim on 5.2.4, but it is accepted-not-consumed this wave (the domain has no municipality field).
The recurrence recebedor.
Payer analysis result (true=Aceita, false=Rejeitada).
true
Retry policy (0=none, 1=up to 3 in 7 days).
1
Recurrence periodicity (0..4).
4
Free-text contract description (35-char).
"Conta de energia"
The devedor, sent only when it differs from the payer.
Last payment date (aaaa-mm-dd).
"2026-01-10"
Rejection reason code (4-char; required when resultadoAutorizacao=false).
"AP13"
Fixed payment amount in reais (a JSON number).
550
Response
No Content

