> Insights | ExpandUp — Embedded Finance Architecture

Payments Architecture

ExpandUp Insights

Architecture, monetization, rail selection, program models, and compliance design — written for practitioners building embedded finance programs.

Case Studies

AP Payments Monetization

AP Platform Recovers $1.2M in Annual VCard Economics

How a platform with $180M annual payment volume restructured its VCard program — moving from BaaS card infrastructure to a direct bank relationship — and recovered $1.2M in annual interchange.

Read case study →

Embedded Payments Launch

Vertical SaaS Platform Launches Embedded Payments Correctly

How a 2,400-customer SaaS platform designed its program before selecting a vendor — and launched at 95 basis points take rate from day one.

Read case study →

Fintech Migrates Off BaaS — $880K Annual Economics Recovery

How a fintech processing $6M monthly migrated from BaaS to a direct sponsor bank relationship over 16 months — and what the compliance and economics gaps looked like on the other side.

Read case study →

Infrastructure Strategy

BaaS Infrastructure Provider: Capability Strategy for SaaS, AP & Banks

Strategy for a BaaS infrastructure provider to better serve vertical SaaS, AP platforms, and enable banks to win more commercial payment volume from existing clients.

Read case study →

Vendor Analysis

Unit vs. Direct Sponsor Bank: Economics Compared

Interchange share, float economics, and the annual gap at $5M monthly. When Unit is the right choice — and the migration trigger that justifies moving.

Read analysis →

Payments Economics

How to Optimize Interchange When You're on Stripe

What you can do within Stripe, what Stripe cannot do for your interchange, and the migration math at your volume.

Read analysis →

Marqeta vs. Direct Card Issuing: When the Platform Fee Is Worth It

Marqeta's platform fee vs. direct processing economics — and how to evaluate whether your program needs Marqeta's capabilities at your volume.

Read analysis →

Treasury Prime Economics Breakdown

Treasury Prime was acquired by Patriot Bank in 2024. Here is what the bank-embedded model means for interchange economics and program flexibility.

Read analysis →

AI & Agentic Finance

Agentic Finance

When Your AI Agent Executes a Payment, It Becomes a Regulated Entity

The compliance obligations that attach the moment AI crosses from recommendation to execution — BSA/AML, OFAC, authorization chain, Reg E liability.

Agentic Finance

Agentic Finance: What Happens When AI Has Payment Authority

The compliance framework, authorization architecture, and sponsor bank requirements for AI systems with delegated payment execution authority.

The Compliance Architecture for AI-Initiated VCard Payments

Authorization chain design, OFAC screening in the execution loop, and spending controls as the compliance layer for AI-executed virtual card payments.

AI Payment Routing

Static Waterfall vs. Dynamic AI Routing: The Revenue Difference at Scale

A 5% improvement in VCard routing accuracy at $100M annual volume generates ~$875K in additional interchange. Here is the data infrastructure that makes it possible.

The Embedded Finance Ops Tasks AI Actually Fixes — and the Ones It Doesn't

Alert triage, reconciliation classification, KYB extraction — where AI has genuine leverage. SAR decisions, bank relationships, novel exceptions — where it doesn't.

AI-Assisted Exception Handling in AP Payment Programs

At 50,000 payments monthly and 3% exception rate, exception handling costs $240K annually. Here is the triage layer that recovers most of that cost.

What a Compliance Team Looks Like When AI Handles the First Layer

When AI handles SAR triage, OFAC review, and KYB extraction, the compliance team structure changes. Here is what it looks like and what the humans focus on.

Vertical SaaS & Payment Architecture

Vertical SaaS Payments

The Payments Decision Most Vertical SaaS Companies Get Backwards

Most SaaS companies pick a payments vendor before designing their payments program. That sequence is backwards — and it costs them years of recoverable economics.

Vertical SaaS Payments

The Vertical SaaS Payments Journey: Four Stages Most Companies Go Through

From collecting payments to orchestrating them — the economics and ownership at each stage are fundamentally different. Here is the map.

Vertical SaaS Payments

What "Payments Partner" Actually Means — and What You're Giving Up

BaaS, PayFac, direct bank, ISO — each gives you different things and costs you different things. The honest breakdown before you choose.

Vertical SaaS Payments

The Bank Relationship Is a Revenue Decision, Not a Compliance Project

Every month of delay at $5M monthly costs $35,000–$45,000 in recoverable economics. Here is why the bank relationship is the most important revenue decision in payments.

Vertical SaaS Payments

Architecture First: Why Pre-Build Decisions Define Your Payments Ceiling

Five architecture decisions made before vendor selection determine what your payments program can ever become. Here is how to make them deliberately.

Vertical SaaS Payments

How Much of Your Payments Program Should You Own vs. Outsource?

What you need to own. What you can durably outsource. What you can outsource now but must plan to own. A framework for SaaS payments ownership structure.

Vertical SaaS Payments

Two SaaS Companies, Same Volume, $1.1M Different Payments Economics

Company A launched on Stripe and migrated 14 months later. Company B designed the program before vendor selection. At $8M monthly their annual economics differ by $1.1M.

Payment Architecture

How a Payment Actually Gets Sent: The Mechanics of Payment Initiation

Trigger layer, authorization gate, rail selection, instruction construction, response handling, exception path, reconciliation record — the 8 components most builds miss.

Featured

AP Payments Architecture

Building a High-Performing, High-Monetizing AP Payments Platform

The complete 8-layer architecture — program model, bank structure, orchestration platform, payment product stack, cascading routing, AR partners, AI execution, and supplier experience. The reference post for AP platform product leaders.

Read the full architecture →

Business Outcomes & Economics

Enterprise Value

Why Payment Architecture Is an Enterprise Value Decision

The program model choice determines revenue quality, margin profile, and valuation multiple. At $8M monthly the enterprise value difference between BaaS and direct bank is $15M–$25M.

Business Economics

The CFO's Guide to Embedded Finance Unit Economics

Revenue per transaction, cost per transaction, margin profile, compliance cost, and the payback period. The numbers a CFO needs before approving the embedded finance investment.

Investor Narrative

How to Build an Investor-Ready Embedded Finance Narrative

The five components of a credible embedded finance narrative — program model with rationale, economics at scale, compliance independence, bank strategy, and migration path.

For CEOs & CFOs

Building the Embedded Finance Business Case

Revenue model, cost model, compliance cost, valuation narrative, build/partner/buy framework, and the investor questions your embedded finance strategy needs to answer.

Calculators & Tools

See the numbers for your program.

AP Platform Operator

AP Platform Revenue Calculator

Virtual card interchange plus monetized electronic payments — what your program actually generates as platform revenue.

AP Customer / Finance Team

AP Customer ROI Calculator

Check elimination savings, exception reduction, and AP labor recovery — what switching to electronic payments is worth to your customers.

Embedded Payments

Payments Leakage Calculator

Interchange gap, float opportunity, and fee structure gap vs. industry benchmarks — select your segment and model.

Compliance Risk Matrix

BaaS vs. PayFac vs. MTL vs. FBO — compliance requirements compared across five program models.

Sponsor Bank Strategy

What Actually Happens During Sponsor Bank Due Diligence

Most fintechs approach sponsor bank due diligence as a sales process. Banks approach it as a risk assessment. Here is what banks actually evaluate — and what causes programs to stall.

AP & B2B Payments

The Hidden Economics of Virtual Cards in AP Programs

VCard interchange is the highest-revenue rail in AP automation — but most programs capture a fraction of what's available. Here is exactly how VCard economics work and where the money goes.

BaaS & Program Models

What BaaS Providers Don't Tell SaaS Platforms

BaaS providers are excellent at explaining what they enable. They are less forthcoming about what they capture, what they constrain, and what happens when you try to leave.

AP & B2B Payments

Why Most AP Payment Monetization Programs Stall

AP monetization looks straightforward. Most programs that try it generate a fraction of projected revenue. Here is why — and what the structural fix looks like.

Payment Economics

Why Payment Revenue Underperforms Forecast — and What to Do About It

Payment revenue forecasts almost always miss to the downside. The reasons are structural and predictable. Here is why the gap happens and how to close it.

Payments Strategy

Stripe Is Not Your Payments Strategy

Stripe is a legitimate starting point. It becomes a strategic constraint when you need interchange capture, card issuing, disbursements, or float economics. Here is how to know when you have outgrown it.

Payment Economics

Why Your Processor Owns More of Your Payment Economics Than You Think

Most platforms assume their payment processor is a vendor. At scale it is a business partner capturing a significant share of your transaction economics — silently, by default.

Payment Economics

How Mature SaaS Platforms Recover Payment Margin

SaaS platforms that launched on Stripe or BaaS and now process meaningful volume are sitting on recoverable payment margin. Here is the recovery sequence that works — and what to avoid.

Team & Operations

Your First Embedded Finance Hire: What the Role Actually Requires

Most platforms hire a payments PM or compliance officer as their first embedded finance hire. Neither role covers what early-stage embedded finance programs actually need.

Embedded Lending

Before You Add Lending to Your Platform: Five Architecture Decisions That Determine Your Economics

Most platforms evaluate providers before defining their lending model. The five architecture decisions that determine economics, flexibility, and long-term margin need to come first.

Embedded Lending

Why Embedded Lending Programs Underperform — and What's Actually Causing It

Low referral fees, constrained product flexibility, limited customer ownership. Most embedded lending programs that underperform share the same root causes. Here is what they are.

When AI Workflows Hit Money Movement: What Changes and Why It Matters

AI founders think moving money is an API call. The moment funds flow, compliance, sponsor bank requirements, and transaction architecture obligations arrive simultaneously. Here's what changes — and why it matters before you scale.

Launch Architecture

Before You Talk to Stripe or Marqeta: What to Decide First

The decisions that determine your payment program economics need to be made before your first vendor conversation. Here are the five that matter most — and what happens when you skip them.

The 5 Reasons BaaS Unit Economics Collapse

BaaS works at $5M in monthly volume. It breaks at $50M. Here are the five structural reasons why — and what to do about them before scale makes them permanent.

SaaS Monetization

How Vertical SaaS Companies Actually Make Money on Payments

The real economics of embedded payments — interchange, float, fee design, and why most SaaS platforms capture a fraction of available revenue. Written by operators who have done it.

Infrastructure Strategy

BaaS vs. PayFac vs. Sponsor Bank: A Real Operator Comparison

The three primary embedded payments models compared by an operator who has run all of them. Economics, compliance, timeline, scaling limits, and what founders consistently get wrong.

AP & B2B Payments

The Payment Waterfall: Why Getting Money Out the Door Is Harder Than It Looks

Every AP company says they have a payment waterfall. Very few have true payment orchestration — automated exception handling, economics-aware routing, and a waterfall that doesn't stop when things go wrong.

Payment Speed as a Revenue Line

Most programs treat speed as a cost. The programs generating real payments revenue treat it as a product. The spread between delivery cost and delivery value is margin — and most programs never capture it.

Monetization · BaaS Architecture

Float and Settlement Are Revenue Architecture — Not Operations

The bank keeps float revenue by default. Every BaaS program that didn't negotiate float economics in the bank relationship is giving away revenue it could be capturing from day one.

Monetization Strategy

Five Monetization Levers for Payments + AP Platforms

Workflow value, vendor graph monetization, settlement velocity pricing, embedded credit, and capital flow partnerships — the five levers that determine whether a payments platform is a revenue engine or a commodity.

Monetization Strategy

Three Underused Revenue Levers for Embedded Finance Platforms

Most platforms monetize transaction fees and interchange. The programs at the top of the revenue curve are also capturing network monetization, data products, and embedded working capital revenue simultaneously.

The Integration Layer Nobody Is Charging For

ERP connectors and API integrations are products — not implementation work. Every program builds them. Almost none charge for them. Here's the revenue model for turning integration into a recurring revenue line.

Payments Architecture · Monetization

The Profitability Gap: How Poor Data Model Design Kills Payments Revenue

Programs with poor data models can't verify interchange rates, can't measure Level 2/3 data transmission, and can't reconcile FBO balances. They know total revenue but can't optimize it because they can't see it.

B2B Payments · Monetization

Remittance Data Is Worth More Than the Payment

Structured remittance data eliminates manual reconciliation that costs more per transaction than the payment itself. Most programs give it away because their infrastructure can't carry it. That's a rail selection problem.

B2B Payments · Monetization

When the Payer Won't Pay

Some counterparties will never accept payment fees. The solution is to stop trying to monetize the payer — and start monetizing the receiver's problem instead. Three receiver-side revenue models that work.

B2B Payments · Monetization

Dynamic Discounting at the Payment Layer

Dynamic discounting turns early payment into a revenue product. The discount is the revenue. The working capital benefit is the value proposition. Most programs never get upstream enough in the AP workflow to offer either.

BaaS & Program Model

The FinTech Payments Model Decoded: PayFac vs. Banking Sponsorship

PayFac and BaaS/banking sponsorship have fundamentally different margin structures, compliance exposures, and flexibility ceilings. Most fintechs make this choice implicitly — by talking to a vendor first.

Payments Architecture · Infrastructure

Buy vs. Build vs. Partner: The Payment Infrastructure Decision Framework

The decision to buy, build, or partner shapes cost structure, competitive differentiation, and flexibility for years. Most programs make it reactively. Here's the framework for making it deliberately.

Payments Architecture · B2B

Beyond ACH — The Complete Payment Rail Guide

ACH is the default. It's also the lowest-revenue, slowest, most data-constrained option available. A complete guide to multi-rail architecture: ACH, RTP, FedNow, Push-to-Debit, VCC, stablecoin, and eLockbox.

Payments Architecture

Building a Future-Proof Payments Platform: Ledgers, Orchestration, and Business Rules

Three foundational components determine scale: ledger design, the orchestration layer, and the business rules engine. Programs that get all three right at launch scale cleanly. Deferring them is expensive.

Payments Architecture · B2B Payments

Launching an ACH Program: What You Need to Define Before You Build

ACH is deceptively simple. Return rate management, settlement model design, remittance format, and ODFI compliance all surface after launch for programs that didn't define them first.

Compliance & Regulation

Bank-Grade Compliance for Embedded Payments: What It Actually Requires

"Bank-grade" appears in every BaaS pitch deck and is rarely defined. What a sponsor bank examination actually requires — BSA/AML, transaction monitoring, OFAC, KYC/KYB — is different from the marketing language.

Monetization · Payments Architecture

Why Your Interchange Is Lower Than You Projected

BIN structure, card type, Level 2/3 data transmission, and revenue sharing terms all determine interchange — and all default to vendor configuration if not designed explicitly. Here's where the gap comes from.

How to Design a Fee Structure That Captures Real Value

Payment programs consistently undercharge because fees are copied from competitors or inherited from vendor rate sheets. Fee design starts with value quantification — not market benchmarking. Here's the methodology.

BaaS & Program Model · Monetization

The BaaS Scale Problem: When Your Vendor Economics Break

BaaS economics work at $10M in processing volume. They often don't at $100M. The crossover point is predictable — but only if you model it before you commit to the structure. What migration looks like and when to plan it.

No posts in this category yet.

Architecture first. Revenue second.

The programs that capture payments revenue are the ones that designed for it. We help you define the architecture before the infrastructure constrains what's possible.

Talk with us See the monetization framework