Read a single transaction's full detail (receipt / dispute / audit)
Returns the full detail of a single transaction, suitable for rendering a receipt, handling a dispute, or producing an audit record. The response presents a stable, flattened shape: the related wallet, program, branch, brand, and enterprise are inlined rather than nested. line_items are reconstructed from the linked order’s line items (or from the session basket when one is present), and applied_offers breaks out the incentives and promotional grants that touched this charge.
All monetary values are integer minor units paired with an explicit ISO-4217 currency. Metadata is sanitized server-side so redemption secrets are never returned.
The response includes related_transactions, which links refunds, the original deposit, and sibling rows that share a multi_transaction_id, so you can render the complete money lineage of an order.
Access is scoped to the calling integration. A transaction owned by another integration resolves to 403 with error code FORBIDDEN, never 404. Transaction state is returned as-is and is status-discriminated: PENDING and REFUNDED transactions are returned with their current status rather than omitted or transformed.
This endpoint is read-only.
Authorizations
Partner API key (platform- or merchant-scoped). Contract key-enforces context.merchant_id.
Path Parameters
The calling integration's id. MUST match the key's integration.
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.
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.
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.
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.