Audit and parked transactions

A parked transaction comes back as a normal 200. It just won't move again until an operator steps in. The full audit history lives in the admin console.

Spotting a parked transaction

Stop polling when data.terminal is true. A parked transaction shows lifecycleStatus: "failed", parked: true and terminal: true. Look at details.reason and the saga steps to see what happened. The response is a regular success envelope, so please handle it that way.

An issuer FAILED, or silence past the issuer's SLA, parks the transaction. An issuer REJECTED before anything moves unwinds automatically. See Rejection and failure are different.

Where the audit trail lives

The integrator APIs return the transaction resource. The full operator audit log, covering who applied an override, who armed a sandbox outcome and the compliance agent history, sits in the authenticated admin console and is filtered by capability. Your sandbox API key can't reach it. Ask your Nuvanté account team for supervisory access.

In this version, when a participant checks its own transaction through the API, it sees:

the saga steps, with their status and timestamps
the on-chain transaction hash for each step
the settlement parties
its own balances

Per-step audit entries are only visible to admins. Each step's calls array is currently empty for everyone, because recorded chain calls aren't linked to their transaction yet. You can use the on-chain hashes to check each chain leg in a block explorer. There's no /transactions/{id}/external-calls endpoint.