A WireMock simulation of U.S. Bank's REST API — covering domestic, international, and repeating wire initiation with transfer detail retrieval.
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 Submit domestic wire
curl -s -X POST 'https://mjmg3.wiremockapi.cloud/transfers/domestic' \
-H 'Content-Type: application/json' \
-d '{}'POST Submit international wire
curl -s -X POST 'https://mjmg3.wiremockapi.cloud/transfers/international' \
-H 'Content-Type: application/json' \
-d '{}'POST Submit repeat wire
curl -s -X POST 'https://mjmg3.wiremockapi.cloud/repeat-transfers/domestic' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Wire Transfers API (1.7.1) · 4 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /repeat-transfers/domestic | Initiate an immediate or scheduled Repeat Wire Transfer Request. |
| GET | /transfers/{paymentID} | Retrieve the details of a single domestic or international wire transfer transaction. |
| POST | /transfers/domestic | Initiate an immediate or scheduled Wire Transfers. |
| POST | /transfers/international | Initiate an immediate or scheduled International Wire Transfers. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
Three initiation routes — domestic, international, and the repeat variant for standing instructions — share one acknowledgment contract: a UUID paymentID minted fresh on every submission, status Scheduled, and a confirmation that the transfer entered the queue. The sandbox registers each id it hands out, and retrieval honors the registry, returning a not-found body numbered 404.1234 for ids it never issued. The detail a registered id resolves to is deliberately more foreign than the ack that produced it: a fifteen-dollar payment denominated in CAD, bound for a Jane Doe, addressed through the spec's full nesting — wireTransfers wrapping a transfers array wrapping recipient details wrapping payment details — with the sender's account block left empty and the business payment type masked to asterisks, the way wire records redact fields downstream systems aren't entitled to see.
The ack reports USD and one amount, the detail CAD and another — the two routes serve independent fixtures joined only by the id. That split rewards clients that treat the acknowledgment as receipt-of-submission and the detail route as the source of truth, and it hands currency-handling code a non-USD record to parse without any special setup.
Depth, sparsity, and redaction at once. The payment facts sit four levels down inside nested wrapper objects, the sender's account details arrive as an empty object rather than being omitted, and businessPaymentType is a string of asterisks. Each is a real wire-reporting behavior: models must survive empty-but-present blocks and masked values without treating either as an error.
Not observably — domestic, international, and repeat all mint a fresh UUID into the same Scheduled envelope regardless of the request body. The differentiation you'd build tests around (routing validation, IBAN requirements on the international leg, schedule fields on repeats) is request-side contract work for a private WireMock Cloud copy; here, what's verified is that your client addresses the right route and threads the returned id into the detail lookup.
When settlement speed is the story. Wires are scheduled, high-value, bank-hours instruments; sub-second payouts over the RTP and FedNow rails, with requests for payment and their cancellation flow, live in the Instant Payments template. And when an international wire needs a locked-in currency rate first, the Foreign Exchange template models the quote-and-accept step that precedes it.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.