A WireMock simulation of U.S. Bank's REST API — covering account ownership and account status checks for domestic U.S. accounts.
Run this template as a mock API in WireMock Cloud for a private instance you control — edit stubs, add stateful scenarios, use dynamic response templating, and inspect requests in the log.
Open in WireMock Cloud (free) →Account validation is the pre-payment question — does this account exist, is it open, and does it belong to the person I'm about to pay — asked before an ACH pull or a disbursement leaves the door. U.S. Bank answers it from EWS data, and the API's distinguishing feature is that one inquiry can come back at three depths: a detailed response exposing the full set of EWS status fields, a translated response that boils those fields down through a set of simplification rules, and a basic response for consumers that only need a verdict. The template packages that contract as an OpenAPI spec with four stubs, so client models for each response flavor can be built and exercised against a mock instead of a gated bank environment.
This is the one U.S. Bank template in the library that doesn't run a shared public instance. To work with it, launch the template into WireMock Cloud — the four stubs become a private mock under your control immediately, which for a verification API is arguably the better arrangement anyway: validation logic needs pass, fail, and every status in between, and those are variations you'll script yourself regardless.
It's a risk-appetite decision the API leaves to you. The detailed flavor hands over the raw EWS status fields and lets your compliance rules interpret them; the translated flavor applies the bank's interpretation first, trading nuance for consistency; the basic flavor reduces to essentials for flows that gate on a single answer. Mocking is most valuable on the detailed path — the field combinations are numerous, and a private copy can pin each one your rules engine must classify.
Early Warning Services — the fraud-and-verification consortium owned by the major U.S. banks, the same organization that operates the Zelle network. Sourcing from EWS means the statuses describe what the account's own institution reports, not an inference from transaction history. It also means responses fall under consortium data-use terms in production — one more reason development and CI runs belong against a mock rather than the live service.
Upstream, as the cheaper first gate. The Bank Information template checks that a routing number resolves to a real institution and reports which payment rails reach it — a structural check with no consortium lookup involved. Account validation then asks the expensive question about the specific account. Payment-intake flows commonly run the two in sequence, and the pair of templates lets you test that funnel end to end.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.
