Skip to main content
POST
Reconcile an operation against the counterpart's settlement status

Authorizations

Authorization
string
header
required

JWT bearer token issued by the identity provider.

Path Parameters

operationId
string
required

Operation id (UUID).

Example:

"018f8a3e-4b2c-7c1a-9e5d-2f6a1b3c4d5e"

Body

application/json
participantIspb
string

ISPB (8 characters) the SLC0908 consulta is run on behalf of. A resource selector for the counterpart node, not an identity claim.

Example:

"12345678"

reason
string

Audit justification (mandatory; enforced by the domain). At most 1024 characters. This verb takes no evidence — the counterpart's answer is the evidence.

Maximum string length: 1024
Example:

"operation stuck at FORWARDED after the ASLC023 window closed"

Response

OK

action
enum<string>
required

Outcome class: IN_SYNC (the two ledgers already agreed, nothing written) or SYNCHRONIZED (the local record was advanced).

Available options:
IN_SYNC,
SYNCHRONIZED
Example:

"SYNCHRONIZED"

counterpartStatus
string
required

The counterpart's RAW SLC0908 settlement status, echoed verbatim rather than re-rendered through this service's vocabulary.

Example:

"CONFIRMED"

localState
string
required

Local state after the reconcile.

Example:

"CONFIRMED"

operationId
string
required

Operation id (UUID) that was reconciled.

Example:

"018f8a3e-4b2c-7c1a-9e5d-2f6a1b3c4d5e"

previousState
string
required

Local state before the reconcile. Equal to localState on an IN_SYNC run.

Example:

"FORWARDED"

reconciledBy
string
required

Authenticated subject who requested the reconcile, taken from the validated request identity and never from the payload.

Example:

"ops@acquirer.com"

controlNumber
string

Counterpart control number correlating the operation, when the answer carried one.

Example:

"CTRL-0042"

trigger
string

Transition trigger (always NUCLEA_RECONCILED). Absent on an IN_SYNC run, where no transition was persisted.

Example:

"NUCLEA_RECONCILED"