Fiserv and Adyen Integration for Fintech Products

Published: Nov 8, 2026 Author: Itexus Team Read 13 min
Have a project in mind? Let’s turn it into a working product
Discuss Your Project

Fintech products rarely talk to one payment company. A lending app may collect card payments through Adyen, a merchant platform may sit on Fiserv acquiring, and a bank may run both. Each provider has its own developer portal, its own credentials, its own test environment and its own rules for going live. The work is less about calling one endpoint and more about getting through onboarding, handling asynchronous events and keeping the money records straight.

This guide is for product and engineering teams that need to connect a fintech product to Fiserv, Adyen or both. It covers what data moves between your system and each provider, the ways to integrate, the setup steps both companies document, the problems teams run into, what is and is not published about cost, and when a custom build is worth it.

What a Fiserv and Adyen Integration Syncs

A payment integration is a two-way conversation. Your product sends payment instructions out, and the provider sends results and events back. The objects differ in name between the two companies, but the flows are similar.

Adyen

Adyen's online payments documentation describes an integration in three parts:

  • Payments server. Your backend makes requests to the Checkout API endpoints and receives the responses. Adyen recommends using its API libraries for this.
  • Client website or app. The front end collects payment details from the shopper and passes them to your server. Adyen recommends its Drop-in and Components UI tools here.
  • Webhook server. An endpoint you run that receives webhooks from Adyen about payment statuses and other payment activity.

So the outbound data is mostly payment requests: amounts, currencies, payment method details collected by Drop-in or Components, and references you use to match them later. The inbound data arrives as webhooks. Adyen lists what they cover: payment results for asynchronous methods such as iDEAL, disputes and chargebacks, notices that a report is ready, onboarding verification results, account holder and balance updates for Adyen for Platforms, and relayed authorisation for Issuing.

Adyen states that you can "process all payment methods using a single API", which matters for a fintech product that wants cards, wallets and local methods without separate builds. The same docs list 3D Secure 2 authentication, risk management and recurring payments through tokenization as features of the online payments integration.

Fiserv

Fiserv's developer portal organizes access around API keys tied to your merchant setup. When you create a production key with the Online Payments setup, the portal preselects three APIs: Payments, Payment Links and Checkouts. Each key is linked to a Store ID (or a hierarchy ID) and works with identifiers your processing partner gives you, including your Merchant ID.

In practice that means your product sends payment, checkout and payment link requests to Fiserv, and keeps a mapping between its own customers or merchants and the Fiserv Store and Merchant IDs that those requests belong to.

If your product runs on Clover, the data set is wider. Clover's developer docs say the REST API lets web apps make authorized calls to manage merchant data, the Android SDK gives apps on Clover devices access to merchant business data and device hardware, and the Ecommerce API connects merchants with ecommerce services.

Integration Options

There are three ways to connect a fintech product to these providers. Most teams combine them.

Provider tools and hosted options. Adyen offers Drop-in and Components for the client side and Pay by Link for payment links. Fiserv's portal exposes Payment Links and Checkouts APIs alongside the core Payments API. These shorten the build and keep sensitive card entry inside provider-built UI.

Platform apps. On Clover, you can publish an app to the Clover App Market, where merchants look for tools for their businesses. This is a distribution channel as much as an integration method.

Custom integration through the APIs. Your own backend calls Adyen's Checkout API or Fiserv's Payments API directly, runs its own webhook handling, and writes results into your ledger, core system or accounting stack. This is the path when payments are part of the product rather than a checkout add-on.

Option Best for Limits Cost basis
Adyen Drop-in or Components, Pay by Link Fast online checkout with many payment methods UI and flow follow Adyen's tools; backend and webhook work still needed Adyen processing terms; build effort
Fiserv Payments, Checkouts, Payment Links APIs Products processing through a Fiserv partner or acquirer Production key needs an agreement and Fiserv review Terms set through your processing agreement; build effort
Clover app (REST API, Android SDK, Ecommerce API) Software sold to merchants on Clover Tied to the Clover platform and App Market Clover says developers receive 70% of net subscription revenue
Custom API integration (one or both providers) Ledgers, multi-provider routing, reconciliation, platform models You own uptime, retries, security and upgrades Engineering cost and maintenance

How to Set Up a Fiserv or Adyen Integration

The steps below follow what each provider documents for getting from a test account to live traffic.

Set up Adyen credentials

Adyen authenticates server requests with an API credential. Each credential has a username in the format tnuoccAynapmoCruoY.ynapmoC@654321_sw, an API key, and one or more roles. A credential must have at least one enabled role, and roles are switched on under Permissions in the Customer Area.

A few details from Adyen's credential docs save time later:

  • When you generate a new API key it is active immediately, and the previous key stays valid for 24 hours so you can roll it out.
  • You cannot copy the API key again after you leave the page, so store it in your secrets manager at once.
  • Adyen recommends separate credentials to limit access, for example one per sales channel.
  • You can restrict a credential to an allowed IP range.
  • Credentials cannot be deleted, but you can set them to Inactive, which takes effect immediately.

Test credentials live in the test Customer Area. When you move to live, you generate a new API key in the live Customer Area. Plan for this in your configuration: the live key is a separate secret, not a flag on the test one.

Build the Adyen payment flow and webhooks

Pick the client side first. Drop-in gives you a ready payment form; Components let you place individual payment method fields in your own layout. Adyen's docs list two server flows, the Sessions flow and the Advanced flow, and SDKs for web, iOS, Android, React Native and Flutter.

Then build the webhook endpoint. Adyen sends webhooks as HTTP POST calls to an endpoint you define, and your endpoint must accept them with a 2xx status code, store the message, and then process its contents. Keep acceptance and processing separate, so a slow database write never causes a delivery failure. Adyen also documents HMAC signature verification for webhooks; check signatures before you trust a payload.

Before launch, work through Adyen's Go-live checklist. Points that catch fintech teams:

  • Adyen does not copy settings from the test Customer Area to live, so users, notifications and payment methods are set up again.
  • Generate a live API key, check its permissions and switch to live endpoints.
  • Set up live webhooks, return a success status such as 202, and subscribe to every event type you need.
  • Add payout bank details, set up automatic reports, and use the Settlement details report for reconciliation.
  • Set up fraud and chargeback notifications and confirm PCI DSS compliance.
  • Run real payments, refused payments, refunds and partial refunds. Adyen notes that payments with real details incur fees.

Get Fiserv developer access

Fiserv's developer portal starts with a standard sign-up: register, verify your email, complete multi-factor authentication and log in. The API Keys page already has a pre-generated Test Sandbox Key with a dummy Store ID, which Fiserv describes as having "access to all APIs". You can start calling sandbox endpoints straight away, or create your own sandbox key with the same steps you will later use for production.

Every request carries the key in the API-Key header.

Request a Fiserv production key

Production access has a business precondition. Fiserv's getting started page says "your organisation must have an agreement with a Fiserv payment processing partner or acquirer". That partner supplies your Merchant ID and Store ID.

The production steps in the portal are:

  1. Open the API Keys page and select Create new key.
  2. Choose Production, then a setup option. Online Payments preselects Payments, Payment Links and Checkouts; Advanced Setup preselects nothing, so you choose permissions yourself.
  3. Review the API permissions.
  4. Enter the key details: name, company, alliance, and the Store ID or Hierarchy ID.
  5. Submit from the Summary screen.

Fiserv then reviews the request. Its docs say "our team will review and validate your Production API key request before activating it", and you may get an email asking for more information. If you use a gateway hierarchy or node, confirm the right Store or Hierarchy ID with your relationship manager or support team before you submit, because a wrong value delays the review.

Build for Clover, if it applies

For software aimed at Clover merchants, start with a Clover sandbox account, then choose the REST API for web apps or the Android SDK for apps that run on Clover devices. If you plan to sell through the App Market, factor the 70% net subscription revenue share into your pricing.

Common Problems and Limits

Separate test and live secrets. Adyen requires a new API key in the live Customer Area, and Fiserv issues production keys separately from sandbox keys after review. Teams that hardcode test settings, or share one secret across environments, hit failures on launch day.

Key rotation windows. Adyen keeps the old key valid for 24 hours after you generate a new one. If your deployment takes longer than that across all services, some calls will fail. Rotate through a central secrets store, not per service.

Webhook handling. Adyen expects a 2xx response, then processing. Endpoints that do heavy work before responding, or that reject messages they cannot parse yet, create delivery problems. Adyen provides Customer Area tools to find and resolve webhook delivery failures, but your code still needs idempotent processing so a repeated event does not post a payment twice.

Asynchronous outcomes. Some payment methods, iDEAL among them, finish after the initial API response. A product that marks a payment final on the first response will show wrong balances. Treat the webhook as the source of truth for final status.

Merchant identifiers on Fiserv. Production keys are bound to a Store ID or Hierarchy ID that your processing partner provides. Products serving many merchants need a clean mapping between their own accounts and those IDs, or payments land under the wrong store.

Production gating. Fiserv's review before key activation, and the need for a partner or acquirer agreement, add calendar time that has nothing to do with code. Start the commercial side early.

Disputes and reconciliation. Adyen sends dispute and chargeback events and report availability notices by webhook. If nothing in your stack consumes them, chargebacks surface late and reports pile up unread. Decide upfront where these events land: your ledger, your support tooling, or your accounting system.

Costs

The developer documentation used for this guide does not publish processing prices for either provider. On the Fiserv side, production access requires an agreement with a Fiserv payment processing partner or acquirer, so pricing comes through that relationship. Ask both for written fee schedules before you build pricing into your product.

The one published figure in this area is Clover's: developers who sell apps through the Clover App Market receive 70% of the net subscription revenue.

Build cost depends on scope. For reference, the Itexus fintech development page says discovery and prototyping engagements "start from around $30,000", and enterprise fintech projects "often range from $150,000 to $1,000,000+". A single checkout on one provider sits at the low end of that range; multi-provider routing with a ledger and reconciliation sits much higher.

When a Custom Integration Makes Sense

You run payments for other businesses. Platforms and marketplaces need onboarding, balances and payouts per account. Adyen's webhooks for Adyen for Platforms account holders and balances, or Fiserv Store and Merchant ID mappings, have to be wired into your own data model. No hosted checkout does that for you.

You use more than one processor. Products that route between Adyen and Fiserv, or move volume from one to the other, need a common payment model on top of both APIs, with one set of statuses, references and reports.

You need your own ledger. Lending, wallets and banking products keep balances that must match provider events exactly. That means idempotent webhook processing, matching of captures, refunds and chargebacks, and a full audit trail.

Compliance shapes the design. Keeping card entry inside Drop-in, Components or hosted Checkouts limits how much card data your systems touch. Getting that boundary right, while still collecting what your compliance team needs, is a design task, not a setting.

Reconciliation has to close every day. If finance needs payments, fees, refunds and disputes matched to the bank and the books, you need a reconciliation layer that reads provider reports and events and posts to your accounting system. Our accounting software integration guide covers that side.

How Itexus Can Help

Itexus lists "120+ integrations delivered for neobanks, payment providers, robo-advisors, and trading systems" and integrates products "with Plaid, Yodlee, Stripe, Adyen, Bloomberg and 50+ fintech APIs". Itexus takes on Fiserv and Adyen integration projects; we have not published a Fiserv or Adyen case, and the closest work is payments and billing.

  • Payment API integration. Server flows, client components and webhook handling built for your product.
  • Multi-provider payments. One payment model over several processors, with shared statuses and references.
  • Ledger and reconciliation. Matching captures, refunds, fees and chargebacks to your books.
  • Legacy connectors. Custom connectors or middleware when an older system has no API.

For an example of payments work, see the B2B billing and payments platform, which integrates with payment processors for payment collection and real-time reconciliation. To discuss your project, contact us.

Itexus is a trusted partner

40+ reviews on
4.9
Become a client

Frequently Asked Questions

What does a Fiserv integration involve?

You register on Fiserv's developer portal, test with the pre-generated sandbox key, and then request a production key. Production requires an agreement with a Fiserv payment processing partner or acquirer, which gives you your Merchant ID and Store ID. Fiserv reviews and validates the request before activating the key.

Does Fiserv require certification before going live?

Fiserv's developer portal getting started guide describes a review of each production API key request rather than a named certification program. Your processing partner or acquirer may set further requirements, so confirm them with your relationship manager.

How does an Adyen integration work?

An Adyen integration has a payments server that calls the Checkout API, a client website or app that collects payment details (usually with Drop-in or Components), and a webhook server that receives payment status and other events. You authenticate with an API credential made of a username, an API key and roles.

What is the difference between Adyen test and live?

Test credentials are managed in the test Customer Area. To go live you generate a new API key in the live Customer Area and work through Adyen's go-live checklist. Your code should treat the live key and endpoints as separate configuration.

Can one product use both Fiserv and Adyen?

Yes. Each provider is integrated through its own API and credentials. The extra work is on your side: a common payment model, one set of references, and reconciliation that reads events and reports from both.

How much does a Fiserv or Adyen integration cost?

The developer docs do not publish processing fees; ask Adyen, and your Fiserv processing partner or acquirer, for written fee schedules. Build cost depends on scope; Itexus publishes that discovery and prototyping start from around $30,000 and enterprise fintech projects often range from $150,000 to $1,000,000+.


Free expert consultation
Get a free architect consultation or system audit.
Consult with Our FinTech Experts
Sergey Privalov
Co-founder and CTO Itexus

Selected projects

Digital Wallet and App Ecosystem for Coinstar – a $2.2B Global Fintech Firm

A digital wallet app ecosystem for Coinstar, a $2.2B global fintech company — including mobile digital wallet apps, ePOS kiosk software, web applications, and a cloud API server enabling cryptocurrency and digital asset trading, bank account linking, crypto-fiat-cash conversions, and online payments.

  • iOS
  • React.js
  • Kotlin
  • .Net Core
  • DevOps
Read More

Retail Brokerage Platform with Mobile Trading, KYC, and Operations Console

A retail brokerage platform with a mobile trading app and a web console for compliance and operations teams, supporting automated KYC, investor onboarding, account funding and withdrawals, AI-powered market analysis, stock and ETF trading, fractional shares, Auto-Invest through regulated brokerage infrastructure.

  • React.js
  • Kotlin
  • JavaScript
  • Swift
  • Google Cloud
  • DevOps
Read More

Legacy WealthTech Platform Modernization for an SEC-Registered Investment Adviser Serving 450K+ Investors

Modernization of an inherited digital advisory platform combining model portfolio subscriptions, research, alerts, education, and SEC/RIA recordkeeping across mobile, web, and messaging channels.

  • React.js
  • Node.js
  • Flutter
  • NestJS / TypeScript
Read More