A WireMock simulation of U.S. Bank's REST API — covering physical check issuance, updates, deletion, retrieval, and criteria search.
A shared instance of this template runs on a public endpoint — call it right now from curl, an SDK, or an AI agent. Responses are fixed examples and behavior can't be changed; rate limits apply.
Jump to the endpoints ↓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) →Live sandbox · no signup, no API key
A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.
Endpoints
POST Create check payable
curl -s -X POST 'https://emlj4.wiremockapi.cloud/payments' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Check Payables (2.2.0) · 5 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /payments | Initiate the issuance of physical checks. |
| DELETE | /payments/{transactionID} | Delete details of an individual check issuance. |
| GET | /payments/{transactionID} | Retrieve details of an individual check issuance. |
| PUT | /payments/{transactionID} | Update a previously issued check. |
| POST | /payments/search | Retrieve details of all checks matching the request criteria for upto 12 months into the past from the current date. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
Issuing a check mints a transaction id built from the letters CHK, the submission date, and a six-character suffix, and files a record behind it with status INITIATED. From there the template runs a proper lifecycle. Updates aimed at an issued id succeed and their fields fold into the stored record — send an amount in a PUT and the next retrieval reports it. Deletion is the interesting verb: rather than removing the record, it rewrites status to DELETED and leaves the check readable, which is how a payments system of record actually behaves — voided instruments remain queryable for audit. All three id-addressed verbs are gated the same way, answering the numbered 404.0648 body for any transaction id the sandbox never issued, so wrong-id handling gets exercised on reads, updates, and deletes alike.
It voids rather than erases. The DELETE response reports status DELETED, and a later GET on the same id still answers — same record, new status, any previously merged fields intact. Client code that treats delete-then-404 as the only valid pattern will misread this API; the test worth writing is delete-then-read-shows-DELETED, which is also the contract the production service documents for stopped checks.
The acknowledgment template projects those two fields from a request location that issuance submissions don't populate, so they render as empty strings no matter how the request is shaped. Read the minted transactionID and the INITIATED status — those are reliable — and treat the empty pair as cosmetic. Round-tripping your own reference numbers works through PUT, whose fields genuinely persist onto the record.
Yes, which is what makes the failure notable: the response walks the real store, emitting one entry per check ever issued in the sandbox, but each entry's template leaves two numeric fields valueless and the assembled body stops being JSON. No request criteria avoid it. Point search-driven features at a private WireMock Cloud copy with a working search stub, and lean on by-id retrieval against the public sandbox.
The store is shared, so checks issued by anyone accumulate in it until it resets — one more reason the broken search matters little in practice. Key every assertion on ids your own tests minted. Once issued checks need reconciling against what the bank was actually presented — mismatched amounts, pay-or-return deadlines — that downstream workflow is the Positive Pay template's territory.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.