A WireMock simulation of U.S. Bank's REST API — covering virtual account rosters, balances, transaction reporting, and non-replicated transaction repair.
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 Retrieve virtual accounts for a physical DDA
curl -s -X POST 'https://jykgy.wiremockapi.cloud/virtual-accounts' \
-H 'Content-Type: application/json' \
-d '{}'POST Retrieve balances on a virtual account
curl -s -X POST 'https://jykgy.wiremockapi.cloud/virtual-accounts-balances' \
-H 'Content-Type: application/json' \
-d '{}'POST Retrieve transactions on a virtual account
curl -s -X POST 'https://jykgy.wiremockapi.cloud/virtual-accounts-transactions' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Virtual Account Reporting (1.4.0) · 5 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /fix-virtual-accounts-non-replicated-transactions | Fix non-replicated transactions by linking them to the right Virtual Accounts. |
| POST | /virtual-accounts | Retreive Virtual Accounts for a given physical DDA. |
| POST | /virtual-accounts-balances | Retrieve balances and account details on Virtual Accounts. |
| POST | /virtual-accounts-non-replicated-transactions | Retrieve non-replicated transactions on Virtual Accounts. |
| POST | /virtual-accounts-transactions | Retrieve transactions on Virtual Accounts. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
Virtual accounts are bookkeeping subdivisions of one physical DDA, and the template models the reporting layer that keeps them honest. The roster answers with three virtual accounts in three different statuses — active, closed, and a third state — so status-filtering logic gets its branches immediately. The balances route reports a booked balance of $3.4 million against a cleared balance of $12,345, a gap that forces clients to decide which number a given screen should show. Transaction reporting returns a deliberately mixed pair — an ACH tax payment carrying its full company block and SEC code beside an RTP credit with debtor-and-creditor detail from the TCH network — because each rail decorates a transaction differently and parsers must handle both shapes from one array. The repair workflow is the template's distinctive loop, covered in the FAQ.
It's money that landed on the physical account without a rule to route it into a virtual account — the feed serves an incoming wire, complete with SWIFT-style originator detail and a note saying no virtual account is linked. The fix route completes the story: it reports that same wire's transaction id as replicated. Exception-queue code can therefore rehearse its whole cycle — detect the orphan, submit the fix, confirm the status flip — against ids the two fixtures share.
The fixture makes the question unavoidable: booked and value-dated agree at $3,456,789 while cleared sits at $12,345. Treasury products typically show booked for position and cleared for availability, and a client that picks one figure "because they're usually the same" renders misleading numbers here — the divergence is the test.
They reuse the account numbers of the vendor's corporate banking persona — the same 1036765614xx series that appears as physical accounts elsewhere in the U.S. Bank fixtures — while the transaction feeds introduce separate 7000000144xx virtual accounts and a 295-prefixed physical DDA. Join logic should key on the fields within each response rather than assuming one number space spans the template.
Not here — this API only watches them. Opening virtual accounts, including the KYC-gated flow that ends in an account number, is modeled in the Corporate Onboarding template; the two sandboxes bracket a virtual account's life, one provisioning it and this one reporting on what it does. Note the paging metadata here signals completion with a last-set flag ("IsLastSet": "Y") rather than page counts — pagination code needs to read the flag, not compute.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.