Volver a publicaciones
Traducción en curso. Mostrando la versión en inglés.

Build vs Buy vs Partner: A2A Decision Framework for Banks

• 15 min de lectura
Build vs Buy vs Partner: A2A Decision Framework for Banks

Build vs Buy vs Partner: A2A Decision Framework for Banks

Based on aggregated data from payware partner deployments. Names and identifying details have been changed.

Banks can see A2A payments eating into card interchange. The responses fall into three camps: build the infrastructure yourself, buy a company that already has it, or partner with a platform that runs it. Each comes with its own price, its own clock and its own strategic consequences. This guide puts numbers on all three.

The Strategic Context

Why Banks Must Act

Card revenue is shrinking. European interchange caps have already cut what a bank earns per card transaction, A2A adoption is growing as merchants look for cheaper ways to get paid, and every payment that leaves the bank’s rails takes a customer touchpoint with it.

Competitors are moving. Klarna, Mollie and Stripe have launched A2A offerings, other banks are entering, and the early movers tend to lock in merchant relationships before the rest arrive.

Regulation pushes the same way. PSD2 mandates open banking access (EUR-Lex: Directive 2015/2366). SEPA Instant Credit Transfer became mandatory for euro-area banks in 2025, receiving from January and sending from October; Bulgarian banks follow in January 2027, and payment institutions, e-money institutions and banks in non-euro EU countries during 2027 (EUR-Lex: Regulation 2024/886). The rails a bank needs for A2A are becoming a legal obligation rather than a project.

And merchants are asking for it. B2B buyers in particular prefer a bank transfer for larger purchases.

For most banks the question is no longer whether to enable A2A. It is how.

Option 1: Build Proprietary A2A Infrastructure

What “Build” Means

An in-house A2A platform. That means a payment initiation service (with PISP authorization if the bank wants to initiate payments from accounts held at other banks), a connectivity layer to those banks, merchant APIs and SDKs, support for several initiation methods (QR codes, NFC, payment links and so on), a merchant dashboard with reporting, compliance infrastructure for AML, KYC and transaction monitoring, a security layer for fraud detection and authentication, and settlement infrastructure to manage the funds flows.

Timeline Estimate

Planning and regulatory work take 6 to 8 months: the business case, the license application where one is needed, vendor selection and hiring. Core development takes 12 to 15 months: the initiation engine, bank connectivity, APIs, security and compliance. Testing and launch take another 6 to 7 months: UAT with pilot merchants, security audits, onboarding systems and go-to-market preparation.

Total: 24 to 30 months. Twenty-four is the optimistic case. Thirty is the realistic one, and the usual overruns push it past that.

Cost Breakdown

Based on payware market analysis, for a mid-to-large bank in Western Europe, with salaries expressed as annual cost spread over the active months.

Development:

  • Engineering team, 15-20 people for 30 months at €85K a year: €3.2-4.3M
  • Product management, 3-4 people for 30 months at €90K: €680-900K
  • Security and compliance, 4-5 people for 30 months at €85K: €850K-1.1M
  • Infrastructure (cloud, licenses, tools): €300-500K
  • Subtotal: €5-6.8M

Regulatory and legal:

  • PISP license application: €100-300K
  • Legal counsel: €200-400K
  • Compliance setup: €150-300K
  • Subtotal: €450K-1M

Third-party integrations:

  • Bank connectivity middleware: €500K-1M
  • Fraud detection tools: €200-500K
  • Monitoring and analytics: €100-300K
  • Subtotal: €800K-1.8M

Sales and go-to-market:

  • Merchant education: €500K-1M
  • Sales team: €400-800K
  • Marketing: €300-600K
  • Subtotal: €1.2-2.4M

Total upfront: €7.5-12M, call it €8-12M for a bank of typical size and scope.

Then every year: €1-1.5M for the engineering team that maintains and extends the platform, €400-600K for operations and support, €300-400K for infrastructure and €300-500K for compliance and security. Total: €2-3M a year.

Advantages of Building

You own the roadmap. Features get prioritized by the bank’s strategy, not a vendor’s. Proprietary features are unavailable to competitors on shared platforms, and there is a first-mover advantage to be had. There is no revenue share, so the economics improve as volume grows. And the bank has full access to its transaction data for customer insight and cross-selling.

Disadvantages of Building

It is the slowest route: 24 to 30 months from decision to production, during which the market window can close. It is the most expensive and the riskiest: €8-12M upfront, €2-3M a year after that, and if the project fails the money is spent anyway. Payment infrastructure is hard, the security and compliance burden is heavy, and A2A engineering talent is scarce. Merchant adoption is not guaranteed, because network effects favor the established players and winning merchants away from incumbents takes sustained effort. And the work never ends: security threats, regulatory changes and technology shifts all demand continuous engineering investment.

Best For

Large banks with substantial technology resources (100 or more engineers), high transaction volume (typically above €1B a year, to justify the investment), unusual integration requirements, a 5 to 10 year strategic commitment and the stomach for execution risk.

Option 2: Acquire Existing A2A Provider

What “Buy” Means

Acquire an A2A payment provider outright. The usual targets are licensed payment institutions that offer A2A, fintech startups with established merchant relationships, or smaller banks that have already built the capability.

Timeline Estimate

Finding a target and doing due diligence takes 3 to 6 months. Closing, with the purchase agreement, merger clearance and completion, takes another 3 to 6. Integrating the technology, operations and brand and moving the merchants across takes 6 to 12 months.

Total: 12 to 24 months. Twelve is optimistic. Eighteen to 24 is what usually happens.

Cost Breakdown

Purchase price: €10-50M depending on the target’s size and traction. A typical mid-market A2A provider sits at €15-30M.

Due diligence:

  • Legal counsel: €200-500K
  • Financial advisors: €300-600K
  • Technical audits: €150-300K
  • Subtotal: €650K-1.4M

Integration:

  • Technical integration, 8-12 people for 12 months: €800K-1.4M
  • Operational integration: €400-700K
  • Rebranding and marketing: €500K-1M
  • Subtotal: €1.7-3.1M

Total acquisition investment: €12-35M. The range is wide for a reason.

Then every year: €1.5-2.5M to retain the acquired team, €500K-1M for infrastructure maintenance and €300-500K in integration overhead. Total: €2.3-4M a year.

Advantages of Acquiring

It is faster than building, 12 to 24 months against 24 to 30, because the development phase has already happened. The technology has been validated in production with real merchants and known transaction economics. The merchants come with it, with cross-sell potential from day one. The acquired team brings operational A2A knowledge that is very hard to hire from scratch. And the bank owns the result outright, with no revenue share.

Disadvantages of Acquiring

€12-35M competes with every other investment the bank wants to make. Integration is demanding: the systems work is hard, the cultural friction between a startup and a bank is common, and key people tend to leave once the deal closes. Merger clearance can be delayed or refused. In a frothy market the bank can overpay, integration costs regularly exceed the estimate, and goodwill impairment is a real possibility. And the technology bought may need substantial refactoring before it meets bank-grade standards.

Best For

Large banks with an active M&A function and a record of integrating what they buy, a strong balance sheet, the willingness to absorb integration risk and a 5 to 10 year commitment.

Option 3: Partner with Infrastructure Provider

What “Partner” Means

Integrate with an A2A infrastructure platform that already exists, payware being one. The bank uses a white-labeled or co-branded platform, the provider supplies the technology layer, the bank concentrates on merchant relationships and distribution, and the transaction fees are shared.

Timeline Estimate

Partnership agreement and planning take 2 to 3 months: terms, commercial agreement, technical scoping and regulatory coordination. Technical integration takes 3 to 4 months: API integration, white-label branding, the merchant onboarding flow and UAT. Pilot and launch take 2 to 3 months.

Total: 7 to 10 months. Seven is optimistic. Nine to 10 is realistic.

Cost Breakdown

Based on payware deployment data, assuming a 4 to 6 person integration team with annual salaries spread over the active months.

Integration:

  • Integration team, 4-6 people for 6 months at €75K a year: €150-225K
  • Partner onboarding fee: €100-300K, depending on the partner
  • Testing and QA: €50-100K
  • Subtotal: €300-625K

Sales and go-to-market:

  • Sales enablement: €200-400K
  • Merchant education: €150-300K
  • Marketing: €200-400K
  • Subtotal: €550K-1.1M

Total upfront: €850K-1.7M.

Then every year: €180-270K for two or three account managers, €200-400K for marketing and merchant support, plus the revenue share, which varies by partner and volume. Total: €380-670K a year plus the share.

As an illustration only: with a merchant fee of 0.50% per transaction and a partner taking a third of it, the bank keeps about 0.33%. The margin per transaction is lower, and the infrastructure cost is close to zero.

Advantages of Partnering

It is the fastest route to market, 7 to 10 months with no development phase. It is the cheapest upfront, €850K-1.7M against €8-12M to build or €12-35M to buy, which makes the capital approval easier. The infrastructure is already proven in production with known performance. The bank spends its energy on merchant acquisition and relationships rather than engineering. The cost structure is variable: the revenue share scales with volume, so there is no fixed infrastructure cost to carry before the volume arrives. And the provider keeps adding features for all its customers without the bank paying for each one.

Disadvantages of Partnering

The margin per transaction is lower, and at very high volume the share starts to look expensive. Reliability, roadmap priorities and pricing sit outside the bank’s direct control, and switching has a cost. It is a shared platform: white-label branding is possible but the core features are the same for everyone. Competitors may use the same platform, which makes claims of technology leadership harder to sustain. And over the long term, a partner being acquired, changing its prices or discontinuing the service could force a disruptive transition.

Best For

Mid-sized banks, and large banks that want speed, when there is competitive urgency, capital is constrained or committed elsewhere, strong merchant relationships are already in place to distribute through, the investment needs to be controlled and reversible, or the bank wants to validate demand before committing to a build or an acquisition.

Decision Matrix

FactorBuildBuy/AcquirePartner
Time to Market24-30 months12-24 months7-10 months
Upfront Cost€8-12M€12-35M€0.9-1.7M
Annual Cost€2-3M€2.3-4M€0.4-0.7M + revenue share
ControlCompleteHighShared
CustomizationUnlimitedHigh (post-integration)Limited
Execution RiskHigh (project failure)Medium (integration failure)Low (proven infrastructure)
DifferentiationHigh (proprietary)Medium (acquired brand)Low (white-label)
MaintenanceInternal teamInternal team (acquired)Partner-managed
RegulatoryNew license where neededAcquired licenseBank’s existing license
Merchant AdoptionUncertainExisting base includedPartner’s ecosystem
Exit FlexibilityLow (sunk cost)Low (acquired asset)High (contract termination)
Strategic ValueHighest (own asset)High (own asset)Lower (dependency)

Case Studies

Based on aggregated data from payware partner deployments. Names and identifying details have been changed.

Scenario 1: Large Bank Builds

A large bank built its own A2A infrastructure. It had a large merchant base to activate, engineering capacity in house, board-level commitment and a clear differentiation goal.

Development took 30 months and €10M all in. The bank launched with a pilot cohort of merchants, and adoption ran slower than projected; it took sustained market education to move.

The lessons: time to market runs longer than the plan, a launch does not produce adoption on its own, and the investment is justified only at very high transaction volume.

Scenario 2: Mid-Sized Bank Acquires

A mid-sized bank acquired a fintech A2A provider to accelerate its digital roadmap, pick up merchant relationships and gain A2A expertise quickly.

It took 18 months from letter of intent to completed integration, €20M for the acquisition and another €2M for integration. The merchant relationships were retained and cross-sold. Key people left after the deal, and the technology carried debt that had to be refactored.

The lessons: cultural integration between a startup and a bank is consistently harder than the technical kind, acquired technology often carries debt that surfaces in due diligence or after close, and the merchant relationships are usually the most durable asset in the deal.

Scenario 3: Mid-Sized Bank Partners

A mid-sized bank partnered with payware. Its priorities were speed, a limited capital budget and distribution over technology ownership.

It went from agreement to production in 9 months for €1.2M, onboarded merchants in the first year, and negotiated a revenue share with the right to renegotiate at volume thresholds.

The lessons: partnership consistently delivers the fastest launch, merchant adoption benefits from mature technology, and the revenue share should be modeled at projected scale before signing.

Strategic Considerations

Competitive landscape. If no direct competitor has launched A2A, building or buying can create durable differentiation. If competitors are already live, partner for speed and differentiate on distribution and merchant experience.

Merchant relationships. With strong relationships, build or partner, because the distribution already exists and an acquisition’s merchant book adds less. With weak relationships, acquire a merchant base or partner into the provider’s ecosystem.

Technical capability. A strong engineering culture makes building realistic and lowers the execution risk. A weak one argues for partnering or acquiring, so that technology risk is not compounded by an organizational gap.

Risk tolerance. High tolerance makes build or buy viable bets. Low tolerance points to partnering, with a controlled investment and a defined exit.

Time horizon. Ten years or more: build or acquire, and own the asset whose economics compound. Three to five years: partner, and test demand before committing larger capital. Under three years: partnering is the only path with a realistic launch date.

Hybrid Approaches

Partner now, build later. Partner for fast entry and build in parallel or afterwards. The bank is in the market immediately, real transaction data shapes the build, and merchants move across when the proprietary platform is ready. The risks are merchant friction during the transition, tension with the partner during the parallel build and duplicated effort. Suits a large bank that wants speed now and ownership later.

Partner and acquire. Partner for the infrastructure and acquire a company for its merchant book rather than its technology. The bank gets fast infrastructure, a faster-growing merchant base, and acquisition capital spent on commercial assets instead of technology. The risks are two parallel workstreams, integration complexity and a higher total cost. Suits a bank whose gap is merchants, not technology.

Build the core, partner for the methods. Build the processing and settlement core and partner for the customer-facing initiation methods (QR, NFC and the rest). The bank owns the strategic core and gets the partner’s UX innovation. The risks sit at the boundary: integration complexity, coordination overhead and unclear ownership at the interface. Suits a bank that wants control of the core while accepting that the partner is better at initiation methods.

The Recommendation Framework

For Most Banks: Start with Partnership

Partnership is usually the best risk-adjusted route to market. It launches fastest with the least capital at risk, and it keeps the option to build or acquire open until demand is proven.

The sequence: partner with an established provider, put the internal effort into merchant acquisition and enablement, watch adoption and volume closely, and revisit the build or buy case after 12 to 18 months of live data. A sensible trigger for that review is the point where A2A is a material share of payment volume and the revenue share costs more than owning a proprietary platform would.

For Large Banks with Resources: Consider Build

Build when the bank has strong engineering capacity, can commit 24 to 30 months and €8-12M upfront, and has a clear view of the differentiated features that justify the premium over a partnered solution.

For Banks with M&A Capability: Consider Acquisition

Acquire when the bank has proven it can integrate what it buys, capital is available, and the target brings a validated merchant base or expertise that would take years to grow organically.

Conclusion

The right path depends on what the bank values most (speed, control or differentiation), what it has (capital, engineering depth, management bandwidth), how much risk it will carry, whether it is first or catching up, and whether it is validating a market or buying an asset for the next decade.

The common mistake is defaulting to build because of not-invented-here culture, or to partner because of budget pressure, without putting the trade-offs against the bank’s actual strategy.

For most banks, partnership is the most defensible place to start. For a bank with the resources and conviction to own A2A infrastructure for the long term, building or acquiring can create durable value, provided it can actually execute.


Want to discuss the partnership approach for your bank?

payware provides white-labeled A2A infrastructure enabling banks to launch in 7-10 months with proven technology and flexible commercial terms.

Learn more: payware.eu
Contact: Get in touch


About payware

payware is the neutral transaction resolution network for instant account-to-account (A2A) payments. Banks query payware to resolve transactions - receiving merchant name, amount, currency, and the optimal merchant bank account. Payment institutions retain full control of authentication, accounts, and funds movement. ISVs integrate payware to onboard merchants to the ecosystem. With 7 payment initiation methods - QR code, NFC, BLE, soundbite, text, link, and barcode - payware offers fees as low as 0.5% and near-instant settlement.

Compartir esta publicación:

Publicaciones relacionadas