Fiserv Omnichannel mock API and live sandbox

Everything except the finale. Applications and all six sub-resource types keep real records — creates echo and register, PATCH merges survive re-reads, deletes are confirmed-gone 204s, and unknown UUIDs 404 — so a boarding client can run its entire data-entry sequence against live state. Submission is the cutoff: the 202 always reports order 732691 and the stored application stays OPEN, meaning status-progression handling (SUBMITTED, approved, declined) is scenario work for a private WireMock Cloud copy. The shared store also implies neighbors: list responses can contain other users' probe records, so filter by ids you minted.

The route does. The four upload paths stamp their documents IDENTIFICATION, FINANCIAL, CONTRACT, or OTHER respectively; the body just needs the metadata you want kept, and the response adds the id, an OPEN state, and created/modified stamps from the moment of upload. No binary content is stored or validated, so keep test fixtures light. Since the listing accumulates whatever anyone uploads, deletion is polite probe hygiene — and the 204-then-404 sequence it produces is itself worth asserting.

It answers one, fully formed. Whatever SaleToPOI request you post, the response is a complete payment approval — message header with POI and sale ids, MasterCard chip entry, a masked PAN, Result Success with authorized amounts — which exercises the deep parsing nexo's nested structure demands. What it doesn't do is vary by request type: reversals, refusals, and loyalty messages all draw the same payment response. Terminal-flow branching belongs in a private copy with one stub per MessageCategory.

It's the data-model-forward one. The Corporate Onboarding template models onboarding as an opaque intake — one deep application document in, a minted id and a status to poll — while Omnichannel decomposes the merchant into addressable resources you build up call by call and can still edit mid-flight. Integrations composing an application UI over granular records rehearse here; ones submitting a finished package and tracking its progress belong there. For what happens after boarding — the merchant taking card-not-present payments — the Online Payments template picks up the story.