Skip to main content
GET
Read a single transaction's full detail (receipt / dispute / audit)

Authorizations

x-api-key
string
header
required

Partner API key (platform- or merchant-scoped). Contract key-enforces context.merchant_id.

Path Parameters

integrationId
string<uuid>
required

The calling integration's id. MUST match the key's integration.

transactionId
string<uuid>
required

The transaction id.

Response

Transaction detail.

The standard response envelope that every enveloped endpoint serializes through. ok is a boolean discriminator: when ok is true, the typed result is carried in data; when ok is false, a typed error object is returned instead. The meta object is uniform across the entire API surface.

ok
boolean
required
meta
object
required

The uniform response metadata block returned on every response. data_completeness_score is computed per call and reports the completeness of the returned data. decision_trace_id is present on responses that carry decision or insight output and can be used to correlate the response with its reasoning. capabilities is an additive, response-level array of hints advertising features the caller may use, and may be extended over time without notice.

data
object

Full detail for a single transaction. Returns a flattened representation of the transaction and its related objects: line_items (the order's line items), applied_offers, and related_transactions. All monetary amounts are integers in the smallest currency unit (minor units) and are accompanied by an explicit ISO-4217 currency. The metadata object is sanitized server-side before it is returned.

error
object | null

The typed error object returned with every non-2xx response. code is a string enum (for example WALLET_PROGRAM_AMBIGUOUS, CREDENTIAL_TYPE_UNSUPPORTED, INSUFFICIENT_FUNDS, IDEMPOTENCY_KEY_REUSED, CURRENCY_NOT_SUPPORTED), never a bare HTTP status number. Inspect code for programmatic branching, not the HTTP status. Some codes echo the valid set in details so clients can present or reconcile the accepted values: for example CREDENTIAL_TYPE_UNSUPPORTED lists the supported credential types, CURRENCY_NOT_SUPPORTED lists the supported ISO-4217 currencies, and WALLET_PROGRAM_AMBIGUOUS lists the candidate wallet_program_id values that matched the request.