Fiserv Suspense Account Management mock API and live sandbox

The tenancy model. SAM scopes its data to party groups — an issuer's organizational slice of the processing system — and each envelope names the group it answered for alongside the numeric cross-reference id real requests must carry. The sandbox pinning both to one canonical group keeps that scoping visible in every parse without requiring you to provision anything, and multi-tenant client code can assert it threads the group context through each call.

Contract-by-contract, yes; as a persisted lifecycle, no. The create acknowledges with a suspense item DTO whose identifiers are placeholder ID001 values, and the clearance routes accept their requests independently — nothing links the two calls, and no item ages between them. That covers request construction and response binding for each step. The full arc — create an item, watch it on the aging report, clear it, see the clearance audit — is scenario work for a private WireMock Cloud copy, where WireMock's stateful scenarios can walk one item across those four contracts.

POSTs because report criteria — date windows, hierarchy selections, code filters — travel in the body across this whole API family; empty because the sandbox ships the report contracts without seeded rows. Each report names its result list (settlementSummaryReportList, emailNotificationsList, and so on), so response wiring is verifiable per report even before a private copy fills them with statement lines shaped like your portfolio's.

Upstream posting activity — and in this library, that upstream is the Operations Execution template, whose adjustments desk models the batch and dual adjustment intakes, per-network chargeback RPCs, and review queues whose exceptions land in suspense. The two surfaces share the same envelope conventions, so a client built against one reads naturally against the other; work the money movement there, and the accounting cleanup here.