API template library

Fiserv Operations Execution mock API and live sandbox

A WireMock simulation of Fiserv's REST API — covering issuer back-office ODS views and RPC updates spanning accounts, adjustments, authorizations, disputes, collections, lending, and statements.

Vendor
Fiserv
Functionality
Issuer operations data and updates
Spec version
1
Endpoints
547
Stubs
547
Protocol
REST
Validation
AI-validated Before publication, an AI agent exercised these endpoints against the real Fiserv API through WireMock's recording proxy, and the recorded traffic was used to verify each stub's request and response shapes.

Live sandbox · no signup, no API key

Fiserv Issuer Solutions - Operations Execution

A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.

Base URL
https://98o84.wiremockapi.cloud

POST ACCT_CHANGE_IN_TERMS_AUDIT ODS View

curl -s -X POST 'https://98o84.wiremockapi.cloud/account/v4/accountChangeInTermsAudit' \
  -H 'Content-Type: application/json' \
  -d '{}'

POST ACCOUNT_RELATIONSHIPS ODS View

curl -s -X POST 'https://98o84.wiremockapi.cloud/account/v4/accountRelationships' \
  -H 'Content-Type: application/json' \
  -d '{}'

POST ALPHA ODS View

curl -s -X POST 'https://98o84.wiremockapi.cloud/account/v4/alphaSearch' \
  -H 'Content-Type: application/json' \
  -d '{}'
Method Path Summary
POST /account/v4/accountChangeInTermsAudit ACCT_CHANGE_IN_TERMS_AUDIT ODS View
POST /account/v4/accountRelationships ACCOUNT_RELATIONSHIPS ODS View
POST /account/v4/alphaSearch ALPHA ODS View
POST /account/v4/applicationTranCounter APPLICATION_TRAN_COUNTER ODS View
POST /account/v4/auditHistory AUDITHISTORY ODS View
POST /account/v4/cardIssuance CARD_ISSUANCE ODS View
POST /account/v4/cardIssuancePlastic CARD_ISSUANCE_PLASTIC ODS View
POST /account/v4/combinedWarningBulletins CWBTRAN ODS View
POST /account/v4/companyAccounts COMPANY_ACCOUNTS ODS View
POST /account/v4/customerIdentification CUSTOMER_IDENTIFICATION ODS View
POST /account/v4/customers ACCOUNT_CUSTOMER ODS View
POST /account/v4/cycleToDateCombinedWarningBulletins CWBDAILY ODS View
POST /account/v4/dailyPromotionPayoff DAILY_PROMOTION_PAYOFF ODS View
POST /account/v4/dataLinkCardholderValues DATALINK_CARDHOLDER_VALUES ODS View
POST /account/v4/datalinkDataDefinition Search DATALINK_DATA_DEFINITION view
POST /account/v4/emvChipDetails CHIP_DETAIL ODS View
POST /account/v4/expandedPayoffBalance EXPANDED_PAYOFF_BALANCE ODS View
POST /account/v4/expandedPayoffBalanceWithGrace EXPANDED_PAYOFF_WITH_GRACE ODS View
POST /account/v4/feeProgramAccount FEE_PROGRAM_ACCOUNT ODS View
POST /account/v4/instantIssuanceDetail INSTANT_ISSUANCE_DETAIL ODS View
POST /account/v4/lookupMerchantAcquiringId MERCHANT_ACQUIRING_ID_LOOKUP ODS View
POST /account/v4/merchantAccountInformation MRCHMS ODS View
POST /account/v4/merchantAccountLookup MRCHAL ODS View
POST /account/v4/payoffBalance PAYOFF_BALANCE ODS View
POST /account/v4/phoneSearch PHONES ODS View
POST /account/v4/promotions TLP ODS View
POST /account/v4/scriptHistory SCRIPT_HISTORY ODS View
POST /account/v4/search CAP ODS View
POST /account/v4/securityDetails SECURITY_DETAILS ODS View
POST /account/v4/securityReport SECURITY ODS View
POST /account/v4/tokenizationTransfer NON_TRANSACTIONAL_TOKEN_XREF ODS View
POST /adjustments/v2/addBatchAdjustment ADJUSTMENT_BATCH_ADD RPC
POST /adjustments/v2/addDualAdjustment DUAL_ADJUSTMENT_ADD RPC
POST /adjustments/v2/addEnhancedBatchAdjustment ADJUSTMENT_BATCH_ENHANCED_ADD ODS RPC
POST /adjustments/v2/amexChargeBackOutgoing AMEX_CB_OUTGOING_MANUAL RPC
POST /adjustments/v2/approveAdjustment JQMTRN RPC
POST /adjustments/v2/approvedQueue JRQTRN ODS View
POST /adjustments/v2/deleteAdjustment JQMTRN RPC
POST /adjustments/v2/deleteBatchAdjustment ADJUSTMENT_BATCH_DELETE RPC
POST /adjustments/v2/feeAdjustmentReversal FEE_RECALC_ADJUSTMENT RPC
POST /adjustments/v2/mcChargeBackOutgoing MC_CB_OUTGOING_MANUAL RPC
POST /adjustments/v2/mcFeeCollectionOutgoing MC_OUTGOING_FEE_COLLECTION RPC
POST /adjustments/v2/pendingQueue JRQTRN ODS View
POST /adjustments/v2/rejectAdjustment JQMTRN RPC
POST /adjustments/v2/rejectedQueue JRQTRN ODS View
POST /adjustments/v2/visaAuthorizationIssues VISA_CB_OUTGOING_MANUAL RPC D1/I1
POST /adjustments/v2/visaCancellationsAndReturns VISA_CB_OUTGOING_MANUAL RPC D2/I2
POST /adjustments/v2/visaFraudIssues VISA_CB_OUTGOING_MANUAL RPC D3/I3
POST /adjustments/v2/visaNonReceiptGoodsServices VISA_CB_OUTGOING_MANUAL RPC D4/I4
POST /adjustments/v2/visaNonReceiptInformation VISA_CB_OUTGOING_MANUAL RPC D7/I7
POST /adjustments/v2/visaProcessingErrors VISA_CB_OUTGOING_MANUAL RPC D5/I5
POST /authorizations/v2/acsAuthorizationControls The ACS_AUTHORIZATION_CONTROLS
POST /authorizations/v2/amexCardSecurityDetail AMEX_CARD_SECURITY_DETAIL view
POST /authorizations/v2/authHistory Search ORIGINAL_AUTH_HISTORY and CARDHOLDER_AUTHORIZATIONS views
POST /authorizations/v2/authTransactionInfo The AUTH_TRANSACTION_INFO
POST /authorizations/v2/cardAuth CARDHOLDER_AUTHORIZATIONS ODS View
POST /authorizations/v2/cardVerification CARD_SECURITY_VERIFICATION ODS View
POST /authorizations/v2/companyAuthStrategyDetail COMPANY_AUTH_STRATEGY_DETAIL ODS View
POST /authorizations/v2/companyAuthStrategySummary COMPANY_AUTH_STRATEGY_SUMMARY ODS View
POST /authorizations/v2/companyAuthStrategyUpdate COMPANY_AUTH_STRATEGY_UPDATE RPC

+487 more endpoints in the full spec.

Unauthenticated WireMock Cloud demo sandbox for Fiserv — not an official Fiserv sandbox, and it returns simulated example data only.

What's inside the Operations Execution template

Operations Execution is the widest surface in Fiserv's Issuer Solutions line — the REST face of the card processor's back office, where every route is either an ODS view reading the operational data store or an RPC executing a host transaction. This template mocks 547 of them across nineteen families: account servicing and cardholder search, the adjustments queues with their approve-and-reject verbs and per-network chargeback intakes, authorization history and strategy controls, then disputes, collections, commercial card, insurance, lending, merchant views, statements, and the OnDot card-controls bridge. Every route answers the same way: HTTP 200 wrapping the envelope this API family shares — a processorInfo header naming system, cycle, tor, and mode, followed by the collection that view returns, empty. Views yield their named arrays (authorizations, customers, adjustmentReviewQueueList); RPCs yield the messages and messageMap blocks a host response carries. It is the entire endpoint map of an issuer back office, reachable without VPN paperwork or processor credentials.

  • Account and customer views — the account/v4 family's servicing reads, from alpha search to EMV chip detail
  • Adjustments desk — pending, approved, and rejected queues plus batch intakes and network chargeback RPCs
  • Authorizations — auth history, card verification, and company-level strategy views and updates
  • Risk and recovery — the disputes, collections, insurance, and lending families
  • Merchant and statements — merchant account views, statement detail reads, and the OnDot integration routes

Frequently asked questions

Structure, not data. Every field the envelope promises is present — the processorInfo header renders each slot as the literal string VALUE, and each view's collection arrives as an empty array. That makes the template a routing and contract fixture: clients verify they're addressing the right path with the right method and can deserialize the envelope, while assertions about record content wait for a private WireMock Cloud copy where you fill the arrays with portfolio-shaped rows. Nothing you post is echoed back, so request payloads are free-form during wiring work.

They're the API's two verbs of being. An ODS View is a read against the operational data store — the endpoint name maps to a named view like CARDHOLDER_AUTHORIZATIONS, and its response is that view's row set. An RPC executes a host transaction — an adjustment add, a strategy update — and reports outcome messages instead of rows. The mock keeps the distinction visible in the response shapes, which is worth preserving in your client's abstractions: reads paginate and filter, RPCs succeed or fail.

The surface is POST-only, views included — criteria travel in the request body, as they do against the real gateway. A GET falls through to WireMock's not-matched diagnostic rather than an API error, which is also your signal for typoed paths: the diagnostic names the closest stub, a practical way to explore family naming (it's how you'd discover that memos live at both /memos/v1 and /cisMemos/v1, or that merchant views sit under /merchantViews/v4).

It's the operational trunk the specialized surfaces branch from, and the family resemblance is visible in the shared processorInfo envelope. The Loyalty & Rewards template dresses the same grammar differently — its collections come back populated with sample records, so it's the better fixture for field-level model binding — while the SAM template covers the suspense-accounting desk this API's adjustments feed into. Wiring tests start here, where the whole map is one base URL.

Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.