Record what was established about an unresolved cancellation repasse
Records the outcome an operator ESTABLISHED for ASLC063/067 repasses whose delivery this service could not determine on its own. RBAC: connectivity:admin. It is the ONLY way to clear an unresolved repasse intention, and each clearing is one-way. CONFIRMED means you established the file DID reach Núclea: the repasse’s duty is discharged and the (operationId, aslcType) pair STAYS blocked, because relaying again would duplicate a regulatory notification to the acquirer. ABANDONED means you established it NEVER reached Núclea: the pair is returned to a relayable state, while the burnt control number and the attempt count survive on the row so the attempt budget still sees what this repasse has spent. IN_FLIGHT is REFUSED as an outcome with 400 — that state belongs to the relay itself, which writes it alongside a fresh control number and a charged attempt, so re-arming a repasse through this verb would unblock a submission whose outcome is unknown and charge nothing for it. reason is ALWAYS required and is logged at ERROR with the targets: it is the audit record of a human overriding an automated refusal on a regulatory rail. There is no scope-wide form: each intention records a finding about a DIFFERENT file at Núclea, and only the caller knows which ones they checked — the same posture POST /v1/connectivity/unpark takes. Enumerate the targets with GET /v1/connectivity/cancellation-relay-intents. Idempotent: re-running reports the already-recorded intentions as not_in_flight and rewrites nothing, so a repeat can never overturn a finding. Per-target results are resolved / not_in_flight / not_found. It transmits nothing, drives no operation transition and emits no business event.
Autorizaciones
JWT bearer token issued by the identity provider.
Cuerpo
The intentions to resolve, enumerated with GET /v1/connectivity/cancellation-relay-intents. 1..500 entries; repeats of the same (operationId, aslcType) pair are collapsed.
1 - 500 elementsThe finding, one of CONFIRMED or ABANDONED. CONFIRMED = you established the file DID reach Núclea: the repasse's duty is discharged and the pair stays blocked, because relaying again would duplicate a regulatory notification. ABANDONED = you established it NEVER reached Núclea: the pair is returned to a relayable state, and the burnt control number plus the attempt count survive on the row.
CONFIRMED, ABANDONED "ABANDONED"
How the finding was established. ALWAYS required: this is the audit record of a human overriding an automated refusal on a regulatory rail, and both findings are consequential — a wrong CONFIRMED drops the acquirer's notification for good, a wrong ABANDONED lets a second one be submitted. It is logged at ERROR with the targets.
1 - 500"Núclea support ticket 48210: control number 2026052800019 was never received."
Respuesta
OK
Admin action that was executed.
"resolve-cancellation-relay-intent"
Per-target detail, in the request's (deduplicated) order.
The finding that was recorded.
CONFIRMED, ABANDONED "ABANDONED"
Distinct (operationId, aslcType) pairs named in the request.
3
Intentions whose guarded UPDATE actually matched; these now carry the finding.
2
Pairs with no intention, or whose intention was no longer unresolved.
1

