Refresh DICT infraction from BACEN
Fetches the infraction’s current record from BACEN (getInfractionReport) and projects the counterparty-determined outcome onto the local row verbatim: no computation, no interpretation. No scheduler runs this — the operator triggers it explicitly.
Autorizaciones
JWT bearer token issued by the identity provider.
Encabezados
Required key used to prevent replaying the mutation.
Parámetros de ruta
BACEN-assigned infraction resource UUID; a local record UUID never resolves here
Respuesta
OK
Persisted local DICT infraction record
Record creation timestamp (RFC 3339, UTC)
"2026-06-14T12:00:00Z"
BACEN end-to-end identifier (E2E ID) of the disputed PIX transaction
"E12345678202607101200D3E4F5A6B7C"
BACEN-assigned infraction resource UUID — the public, canonical identity of this record
"550e8400-e29b-41d4-a716-446655440000"
BACEN infraction notification reason: REFUND_REQUEST or REFUND_CANCELLED
"REFUND_REQUEST"
BACEN report delivery state. Always SENT at rest (a resource row is persisted only once BACEN has confirmed it; a rejected or ambiguous attempt creates no row).
"SENT"
ISPB (8 numeric digits) of the participant that reported the infraction
"12345678"
Situation that gave rise to the infraction: SCAM, ACCOUNT_TAKEOVER, COERCION, FRAUDULENT_ACCESS, OTHER, or UNKNOWN
"SCAM"
Local infraction lifecycle state: OPEN, ACKNOWLEDGED, CLOSED, or CANCELLED
"OPEN"
Last update timestamp (RFC 3339, UTC)
"2026-06-14T12:00:00Z"
When a human acknowledged the notification (RFC 3339, UTC) — the local evidence that a person, not a scheduler, declared it received. Absent while status is OPEN.
"2026-06-20T10:00:00Z"
When the DICT 8.4 §20.3 seven-day analysis window closes (RFC 3339, UTC), counted from bacenCreationTime. Absent while BACEN's creation instant has not been observed — an unknown anchor is not a deadline, and a local clock would put the deadline later than the one BACEN counts.
"2026-06-21T12:00:00Z"
Free-text analysis details accompanying analysisResult; omitted until close (ours or the counterparty's, via refresh)
closeInfractionReport analysis outcome: AGREED or DISAGREED; omitted until close (ours or the counterparty's, via refresh)
AGREED, DISAGREED "AGREED"
BACEN's own operational envelope for its most recent interaction on this infraction, including its LastModified version; omitted when no BACEN interaction has ever landed on it.
When BACEN created this infraction notification (RFC 3339, UTC); distinct from createdAt
"2026-06-14T12:00:00Z"
BACEN-echoed regulator-facing contact
BACEN-assigned counterparty participant ISPB (ExtendedInfractionReport.CounterpartyParticipant)
"87654321"
When THIS deployment first observed a notification created elsewhere (RFC 3339, UTC). Read against analysisDeadlineAt it separates an operator who did not act on a notification held for six days from a rail that discovered it minutes ago already six days old — a blocked feed or a deployment that was down. Absent for a notification this rail itself reported.
"2026-06-20T09:00:00Z"
BACEN-assigned fraud marker id, present only after an AGREED close
"550e8400-e29b-41d4-a716-446655440002"
BACEN-assigned funds-recovery id this infraction is linked to (MED 2.0); omitted for a standalone infraction
"550e8400-e29b-41d4-a716-446655440003"
BACEN-reported blockable amount, exact decimal (ExtendedInfractionReport.InfractionAmount); absent when BACEN's response omitted it
1500
Durable operation-intent id that produced this snapshot's current state, when known
"01930000-0000-7000-8000-000000000000"
Detail supplied for the counterparty PSP's analysis; present when the situation carries one
BACEN-assigned reporter (payer) participant ISPB (ExtendedInfractionReport.ReporterParticipant)
"12345678"
MED tracking-graph layer of the disputed transaction (DICT 8.5 TransactionDepth): 1 for the root transaction, 2 for the second layer, and so on. Absent when BACEN has not stated a layer — notably for notifications answered before the 2026-10-26 vigencia.
x >= 11

