--- title: Fiserv API Integration on Truto slug: fiserv category: Payment Gateway canonical: "https://truto.one/integrations/detail/fiserv/" --- # Fiserv API Integration on Truto **Category:** Payment Gateway **Status:** Generally available ## MCP-ready AI tools Truto exposes 44 tools for Fiserv that AI agents can call directly. - **create_a_fiserv_payment** — Create a primary Fiserv payment transaction such as a sale, preauthorization, or credit. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, orderId, userId, transactionType, paymentToken, approvedAmount, transactionStatus, transactionResult, approvalCode, and 32 more. Required: requestType, transactionAmount. - **get_single_fiserv_payment_by_id** — Get the current state of an existing Fiserv payment transaction by id. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, orderId, userId, transactionType, paymentToken, transactionOrigin, paymentMethodDetails, transactionAmount, transactionStatus, approvalCode, transactionState, and 30 more. Required: id. - **update_a_fiserv_payment_by_id** — Update a Fiserv payment and continue processing after a redirect response, such as 3D Secure authentication. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, orderId, userId, transactionType, paymentToken, transactionStatus, transactionState, secure3dResponse, and 33 more. Required: id, authenticationType. - **fiserv_payments_void** — Perform a secondary transaction, such as a void or reversal, on an existing Fiserv payment. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, orderId, userId, transactionType, paymentToken, transactionOrigin, transactionStatus, transactionResult, approvalCode, and 32 more. Required: payment_id, requestType. - **update_a_fiserv_payments_action_by_id** — Update an existing transaction in Fiserv. Returns the transaction response including ipgTransactionId, transactionStatus, transactionAmount, approvalCode, and transactionState. Only applicable to existing preAuth transactions. Required: id, requestType. - **create_a_fiserv_payments_apm** — Perform an action on an existing Fiserv APM transaction, identified by its apm_id. Returns the transaction response including ipgTransactionId, orderId, transactionStatus, transactionResult, approvalCode, and redirectURL. Required: apm_id, requestType. - **update_a_fiserv_payments_apm_by_id** — Update an existing Fiserv APM transaction by performing an action on it. Returns the transaction response including ipgTransactionId, orderId, transactionStatus, transactionResult, and approvalCode. Required: id, requestType. - **get_single_fiserv_order_by_id** — Get the current state of an existing Fiserv order. Returns: clientRequestId, apiTraceId, responseType, type, orderId, numberOfInstallments, billing, shipping, mandate, transactions, additionalDetails. Required: id. - **create_a_fiserv_order** — Perform a secondary transaction (postAuth or return) against an existing Fiserv order, referenced by its order ID. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, orderId, userId, transactionType, paymentToken, approvedAmount, transactionStatus, approvalCode, and 33 more. Required: order_id, requestType. - **create_a_fiserv_payment_schedule** — Create a gateway-managed payment schedule in Fiserv. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, orderId, userId, state, transactionResponse. Required: requestType, startDate, frequency, transactionAmount. - **get_single_fiserv_payment_schedule_by_id** — Get details of a gateway-managed payment schedule in Fiserv by id. Returns: clientRequestId, apiTraceId, responseType, type, orderId, numberOfInstallments, billing, shipping, mandate, transactions, additionalDetails, recurringPaymentDetails, industrySpecificExtensions. Required: id. - **update_a_fiserv_payment_schedule_by_id** — Update a gateway-managed payment schedule in Fiserv by id. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, orderId, userId, state, transactionResponse. Required: id, requestType, frequency, transactionAmount. - **delete_a_fiserv_payment_schedule_by_id** — Cancel a gateway-managed payment schedule in Fiserv by id. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, orderId, userId, state, transactionResponse. Required: id. - **list_all_fiserv_payment_urls** — Get the current state of an existing Fiserv payment URL. Returns: clientRequestId, apiTraceId, responseType, type, paymentUrlDetails, industrySpecificExtensions. Required: fromDate, toDate. - **create_a_fiserv_payment_url** — Create a Fiserv payment URL to generate a payment link for a transaction. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, orderId, paymentUrl, expiration, transactionId. Required: transactionAmount, transactionType. - **fiserv_payment_urls_bulk_delete** — Delete an existing Fiserv payment URL link. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, orderId, paymentUrl, expiration, transactionId. - **create_a_fiserv_payment_token** — Create a Fiserv payment token from a payment card, payment device, or referenced order to securely store sensitive card details. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, requestTime, brand, country, paymentToken, paymentCard, networkToken, processor, tokenAlias, orderId, and 3 more. Required: requestType. - **get_single_fiserv_payment_token_by_id** — Get the payment card details associated with a Fiserv payment token by id. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, requestTime, brand, country, paymentToken, paymentCard, networkToken, processor, tokenAlias, orderId, ipgTransactionId, merchantTransactionId, additionalResponseData. Required: id. - **delete_a_fiserv_payment_token_by_id** — Delete a Fiserv payment token by id. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, requestTime, brand, country, paymentToken, paymentCard, networkToken, processor, tokenAlias, orderId, ipgTransactionId, merchantTransactionId, additionalResponseData. Required: id. - **fiserv_payment_tokens_bulk_update** — Update one or more Fiserv payment tokens in a single request. Returns: clientRequestId, apiTraceId, responseType, type, requestStatus, requestTime, errors. Required: requestType, paymentTokens. - **list_all_fiserv_installments_plans** — Get eligible installment plans for a payment in Fiserv by submitting store and payment card or token details. Returns: clientRequestId, apiTraceId, responseType, type, installmentPlans. Required: requestType, storeId, amount. Arguments are sent as the JSON body. - **fiserv_card_verifications_verify** — Verify a payment card in Fiserv. Returns the verification result including ipgTransactionId, transactionStatus, transactionResult, approvalCode, transactionAmount, and paymentToken. - **fiserv_account_verifications_verify** — Verify a payment card or payment token in Fiserv. Returns the transaction response including clientRequestId, responseType, transactionType, transactionResult, approvalCode, paymentMethodDetails, and accountVerificationResponse. Required: requestType. The body must be either a PaymentCardVerificationRequest or a PaymentTokenVerificationRequest. - **list_all_fiserv_exchange_rates** — Generate a dynamic currency conversion in Fiserv by converting a base amount to a foreign currency. Returns: clientRequestId, apiTraceId, responseType, type, ipgTransactionId, requestTime, exchangeRateDetails. Required: requestType, baseAmount. Use requestType DCCExchangeRateRequest with bin, or DynamicPricingExchangeRateRequest with foreignCurrency; arguments are sent as the JSON body. - **fiserv_card_informations_lookup** — Look up card information such as issuer country, card function, and card brand in Fiserv. Returns: clientRequestId, apiTraceId, responseType, type, cardDetails, requestStatus. Requires storeId and a paymentCard or paymentCardEncrypted payload. - **fiserv_account_informations_lookup** — Look up card-related account information in Fiserv for a payment card or payment token. Returns: clientRequestId, apiTraceId, responseType, type, cardDetails, requestStatus. Required: requestType. - **create_a_fiserv_checkout** — Create a new Fiserv checkout to initiate a payment transaction. Returns the checkout object with its checkoutId, storeId, and redirectionUrl for the hosted payment page. Required: storeId, transactionType, transactionAmount. - **get_single_fiserv_checkout_by_id** — Get a single Fiserv checkout by id. Returns: storeId, checkoutId, orderId, transactionType, approvedAmount, transactionStatus, transactionFailure, paymentMethodUsed, currencyConversion, ipgTransactionDetails, requestSent. Required: id. - **create_a_fiserv_payment_link** — Create a Fiserv payment link that can be passed to the end consumer to direct them to a checkout page. Returns: paymentLink. Required: storeId, transactionType. - **get_single_fiserv_payment_link_by_id** — Get the details of a Fiserv payment link by id — the short link identifier (e.g. dBpYUi) generated when the link was created. Returns: storeId, paymentLink, checkoutId, orderId, approvedAmount, transactionType, transactionStatus, transactionFailure, paymentMethodUsed, currencyConversion, ipgTransactionDetails, requestSent. Required: id. - **list_all_fiserv_disputes** — Search Fiserv disputes by date range, status, acquirer reference number, order ID, merchant ID, or card scheme case ID. Returns: id, status, stageCode, stageDescription, result, lastAction, posted, due, workByDate, cardScheme, cardIssuer, acquirerReferenceNumber, amount, currency, visaId, and 10 more. Status defaults to OPEN. Max 100 per page. Requires the Institution number credential field when the API key covers more than one institution. - **get_single_fiserv_dispute_by_id** — Retrieve a single Fiserv dispute by id. Returns the full dispute record including status, stageCode, reasonCode, amount, currency, and related transactions, documents, events, and notes. Required: id. Requires the Institution number credential field when the API key covers more than one institution. - **get_single_fiserv_dispute_document_by_id** — Retrieve a dispute document by id in Fiserv. Returns the raw binary document content in the requested format (PDF, image, DOCX, XML, or XML-to-JSON). Required: id, dispute_id. The document is returned only if it matches the requested Accept format. Requires the Institution number credential field when the API key covers more than one institution. - **create_a_fiserv_dispute_document** — Attach an evidence document file to a Fiserv dispute case. Returns: documentId. Required: dispute_id, evidence, templateCategoryCode, tcn, networkFormType. Only one document can be attached per API call. Requires the Institution number credential field when the API key covers more than one institution. - **create_a_fiserv_event_action** — Execute an action against a dispute event in Fiserv. Returns an empty 204 response on success. Required: dispute_id, event_id, code, tcn. Additional data fields may be required depending on the action code; retrieve them from the dispute's allowedActions requiredDataFields via GET Disputes by Id. Requires the Institution number credential field when the API key covers more than one institution. - **create_a_fiserv_action_undo** — Undo a previously taken action on a Fiserv dispute case. Returns an empty 204 response on success. Required: dispute_id, action_id, tcn. The undo is only allowed while the action has not yet been processed in the daily cycle. Requires the Institution number credential field when the API key covers more than one institution. - **create_a_fiserv_dispute_note** — Add a note to a Fiserv dispute case to provide more detail and information. Returns the created note's id, tcn, createdBy, created, and userName. Required: dispute_id, tcn, content. Notes cannot be updated once added, but additional notes can be added. Requires the Institution number credential field when the API key covers more than one institution. - **list_all_fiserv_funding_rejects** — List Fiserv funding rejects, optionally filtered by merchant, status, funding id, or posted-date range. Returns: id, reason, reprocessedDate, posted, lastUpdatedBy, status, merchant, originalPayment, account. Max 100 per page. Requires the Institution number credential field when the API key covers more than one institution. - **fiserv_funding_rejects_bulk_update** — Update the Funding Reject statuses of a batch of funding ids in Fiserv. Accepts an array of items, each with fundingId and status (3 digit status index), minimum one item. Returns an empty 204 response on success. Requires the Institution number credential field when the API key covers more than one institution. - **create_a_fiserv_post_adjustment** — Create financial adjustments in Fiserv OmniPay by submitting fees and adjustments to merchant accounts as an array, to be applied as part of the merchant payment or collection. Returns: adjustmentSlipNumber, adjustmentStatus, adjustmentCreationDate. Max 1,000 adjustments per call. OmniPay Financial Adjustments API: requires the Institution number and OmniPay environment credential fields; test keys are routed to the CAT host. - **fiserv_modify_adjustments_bulk_update** — Modify one or more previously created adjustments in Fiserv OmniPay by submitting a JSON array of modifications (up to 1,000 per call); adjustments can only be modified before processing pickup and only while their status is neither Released nor Cancelled. Returns an empty 204 response on success. OmniPay Financial Adjustments API: requires the Institution number and OmniPay environment credential fields; test keys are routed to the CAT host. - **fiserv_cancel_adjustments_bulk_delete** — Cancel one or more adjustments in Fiserv OmniPay by submitting them as an array in the request body. Returns an empty 204 response on success. Up to 1,000 adjustments can be cancelled per request, and only adjustments that have not yet been picked up for processing (status neither 'Released' nor 'Cancelled') can be cancelled. OmniPay Financial Adjustments API: requires the Institution number and OmniPay environment credential fields; test keys are routed to the CAT host. - **list_all_fiserv_get_adjustments_stageds** — List staged adjustments in Fiserv OmniPay. Returns: merchantId, adjustmentSlipNumber, adjustmentStatus, adjustmentCategory, adjustmentType, adjustmentCreationDate, accountNumber, amount, currency, date, description, feeSequence, originalTransactionArn, and 5 more. Date ranges span at most 1 month within the last 6 months; max 1000 per page. OmniPay Financial Adjustments API: requires the Institution number and OmniPay environment credential fields; test keys are routed to the CAT host. - **list_all_fiserv_reference_datas** — List reference data valid values for an institution in Fiserv OmniPay adjustments. Returns: classification, code, description. OmniPay Financial Adjustments API: requires the Institution number and OmniPay environment credential fields; test keys are routed to the CAT host. ## How it works 1. **Link your customer's Fiserv account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Fiserv.** The Proxy API is a 1-to-1 mapping of the Fiserv API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Embed Fiserv as a native payment method for your merchants** — Let your mid-market and enterprise customers connect their existing Fiserv acquiring accounts to process payments directly inside your SaaS, without you building and maintaining the gateway integration yourself. - **Power recurring billing with gateway-managed subscriptions** — Offer subscription and membership SaaS customers the ability to push recurring billing logic down to Fiserv via payment schedules, eliminating internal cron jobs and keeping card data entirely out of your PCI scope. - **Automate chargeback defense for support and risk teams** — Give support, risk, and ops teams the ability to pull open disputes, attach evidence documents, add notes, and submit defense actions to Fiserv without leaving your product. - **Streamline back-office reconciliation for finance teams** — Let ERP, accounting, and revenue-ops platforms sync funding rejects and OmniPay staged adjustments from Fiserv so finance teams can reconcile payouts against the general ledger automatically. - **Enable pay-by-link and hosted checkout for field and invoicing apps** — Help invoicing, field service, and trades platforms generate Fiserv payment links, URLs, and hosted checkouts on the fly so their customers can collect card payments by SMS or email without touching card data. ## What you can build - **Tokenized one-click checkout** — Vault customer cards via Fiserv payment tokens and run future charges with a single API call for frictionless repeat purchases. - **Auth, capture, and void flows for travel and hospitality** — Create pre-authorizations, capture them later via orders, or void holds — the exact flow needed for bookings, deposits, and gig-economy escrow. - **Dispute defense console** — Surface open Fiserv disputes inside your app, upload evidence documents, append notes, and trigger event actions or undo actions directly from the agent view. - **Pay-by-link invoice collection** — Auto-generate a Fiserv payment link or payment URL when an invoice is finalized, send it to the payer, and poll the link to flip invoice status to paid. - **Dynamic currency conversion at checkout** — Pull live Fiserv exchange rates to present buyers with their local currency at checkout and improve international conversion. - **OmniPay adjustments and funding-reject sync** — List funding rejects and staged adjustments, post new adjustments, and bulk-modify or cancel them so finance teams can resolve settlement discrepancies programmatically. ## FAQs ### How do end users authenticate their Fiserv account in our product? Truto handles the Fiserv credential exchange and token storage for you. Your users connect their Fiserv account once through a Truto-managed flow, and your app calls Fiserv endpoints via Truto without storing or rotating secrets yourself. ### Which Fiserv capabilities are available through Truto today? The current Fiserv integration covers payments (create, retrieve, update, void), orders, APMs, payment schedules, payment URLs and links, hosted checkouts, payment tokens, installments, card and account verifications and lookups, exchange rates, disputes with documents, notes, and event actions, and OmniPay funding rejects, post adjustments, modify/cancel adjustments, staged adjustments, and reference data. ### Can we keep card data entirely out of our PCI scope? Yes. You can use Fiserv hosted checkouts, payment links, and payment URLs so card entry happens on Fiserv-hosted surfaces, or use payment tokens so sensitive card data never touches your servers. ### Does the integration support recurring billing without us running a scheduler? Yes. You can create, retrieve, update, and delete Fiserv payment schedules so Fiserv itself triggers the recurring charges on the cadence you define, rather than your app managing cron jobs. ### Can we automate chargeback and dispute workflows? Yes. You can list disputes, fetch individual disputes and dispute documents, upload new evidence documents, add dispute notes, and submit event actions (and undo actions) to progress or defend a case. ### How fresh is the data we read from Fiserv? All reads are made directly against the Fiserv API at request time, so data such as payment status, dispute state, funding rejects, and staged adjustments is live rather than cached. You control polling cadence or trigger reads on demand from your application.