Payments intelligence · Built for vertical SaaS

Your payments margins moved. Flexibl tells you exactly why.

Flexibl turns the payments running through your platform into a single source of truth by unifying processor fees, interchange, merchant cohorts and contract economics into one intelligence layer your team can act on.

Book a demo →See what we surface
Connects toStripe·Adyen·Worldpay·Fiserv·Paysafe·Nuvei·+ others
DashboardAnalyzeAdviseOptimizeReconcile
FY 2026 · YTD MarTD
3 Active Findings · $284k impact
Margin leakage detected

Visa CPS Retail downgrades on commercial cards

In-scope GPV$25.6M
Margin impact−0.31%
Annualized−$80,182
Pass Level III line-item data on every PaymentIntent.
Fee schedule drift

Processor interchange++ markup deviates from contract

Affected txns184,302
Avg variance+4 bps
Recovery est.$42.8K
Captured savings

Network token coverage now 91% of in-scope GPV

Volume tokenized$19.8M
Realized+$21,800/yr
Net Margin
2.14%
▼ 0.18% vs Q4
GPV YTD
$369.0M
▲ 9.6% YoY
Effective Rate
1.99%
▼ 4 bps
Net Profit
$3.98M
▲ $284k
Why margin moved this quarter
Decomposed by driver · Q1 2026 vs Q4 2025
CostGainNet
← Decomposed from 1.59M transactions across 4 processorsOpen driver detail →
The three problems

The number gets defended.
The cause never gets fixed.

Problem 01 · Margin Explanation

Revenue looks fine. Until someone asks why it moved.

Payments margins shift month to month because fees change, card mix moves, processor behaviour drifts. Most platforms don't discover the problem until leadership asks for an explanation. By then, the answer requires days of spreadsheet work and still comes back incomplete.

"Can you put a number on why margin dropped 18 bps?"
Problem 02 · Data

Stripe calls it one thing. Adyen calls it something else.

Every processor uses different fee names, different report formats, and different settlement timings. When you're running two, five, or fourteen processors simultaneously, there's no consistent way to read across them. Teams end up manually mapping fees and rebuilding context every month.

stripe · "processing_fee"
adyen · "interchange++"
worldpay · "blended_rate"
→ same fee, three names, no shared schema
Problem 03 · Reconciliation

Manual reconciliation isn't a workflow. It's a risk.

Matching transactions to payouts to your internal ledger across processors, product lines, and time periods is one of the highest-effort, lowest-leverage activities in your payments org. One missing file, one delayed settlement, and the whole process starts over.

For most platforms, this is still a monthly manual exercise.
The reframe

Visibility isn't the same as control. And your processor doesn't want you to have either.

Processor reports are built to serve the processor. Bi tools can visualize your data but can't interpret payment-specific economics. Internal builds work until your first processor API change, your second processor, or your first acquisition. Without a neutral layer that sits outside those relationships, you're always a step behind and the explanation gap stays open.

See what a neutral payment layer looks like →
Who this is for

Three roles. One shared problem.

CEO

Payments is a growing revenue driver. When margins move, you need an explanation you can stand behind.

CFO

You're signing off on payment economics you can't fully verify. When something looks off, there's no independent source of truth.

Payments & Revenue Leaders

You're accountable for margin performance across processors and merchants but the data is split across systems that don't talk.

"No reliable, independent source of truth for payment economics."
- the shared pain
Foundation

A neutral system of record for payment economics.

Control starts with a foundation your processors can't influence. Flexibl connects your payment processors, billing systems, and internal software data into a single normalized data model.

Fragmented sources
S
StripeREST · webhooks
A
AdyenSFTP · reports
W
Worldpayfile feed
F
Fiservbatch
B
Billing systemAPI
L
GL / ledgerCSV / API
E
ERPconnector
Normalized

One consistent taxonomy.

Stripe calls it "processing fee." Adyen calls it "interchange++." Worldpay bundles it. Flexibl maps all of it to one schema so you can read across processors as if they spoke the same language.

transaction_idtxn_4F4FFF
processoradyen
card_brandvisa · commercial
interchange1.42%
scheme_fee0.13%
processor_markup0.20%
payout_idpo_91x · ledger ✓
Actionable
→ Analyze

Cross-processor explainability. Margin movement traced back to transaction-level cause.

→ Advise

Quantified, prioritized recommendations grounded in real payment expertise.

→ Optimize

Realized impact tracking that closes the loop on every change.

→ Reconcile

Continuous transaction → payout → ledger matching with auto-flagged exceptions.

Fragmented→ Normalized→ Actionable
Proof

Real platforms. Real findings.

Platforms using Flexibl have identified processor fees applied incorrectly against contracted terms in multiple cases running undetected for months. Reconciliation workflows that required manual monthly effort now run continuously.

up to 215bps

in processor fee errors recovered. Money platforms were already losing without knowing it.

Across live platforms · 2025-2026
14d

median time to first material finding after connecting processor and ledger data.

Cohort of platforms
5-35bps

in incremental savings from interchange optimization.

Per platform, post-onboarding
01 / Analyze01

Analyze.

Understand what happened and why.

A unified view of your payment data across every processor, merchant, and product that makes margin movement explainable, not just visible.

Explore Analyze →02 / Advise02

Advise.

Know what to do about it.

Guided, quantified recommendations grounded in real payment expertise and patterns observed across platforms running embedded payments at scale.

Explore Advise →03 / Optimize03

Optimize.

Confirm that it worked.

Realized impact tracking that closes the loop so your team can validate decisions, not just make them.

Explore Optimize →
01 · Analyze

Fragmented data becomes explainable economics.

Flexibl turns fragmented payment data into explainable economics not just charts, but causation. When margins move, this is where you establish the scope and sequence so your investigation starts with facts, not guesswork.

  • Transaction TrendsWhat changed, and when?

    Unified view of volume, refunds, disputes, and mix shifts across all processors in one timeline.

  • Per-Merchant AnalyticsWhere is the impact concentrated?

    Profitability, product adoption, and attachment at the merchant level see which merchants are compressing margins.

  • Margin & Cost BreakdownsWhat's driving movement?

    True revenue, fees, and margins across transactions, processors, and products with full traceability.

  • ReconciliationDoes the money add up?

    Automated transaction → payout → ledger matching across all processors. Exceptions surface automatically.

Per-merchant margin distribution
2,000 merchants · GPV vs payment margin · YTD 2026
+ margin− margin
4.5%2.1%−1.5%$0$180k GPV$340kavg 2.14%mid-410 · soccer SaaS$322k GPV · 1.20% margin
Click any merchant → open driver detail↓ 47 below avg margin
Issue Detectedfinding · F-0042 · auto-detected 4h ago

Misapplied Interchange Qualification

Commercial cards on MCC 7372 are qualifying at standard CNP rates instead of Level III. Pattern detected across 4 sub-levers on Visa + Mastercard.

Impacted Volume
$4.2M
Margin Impact
−0.38%
Annualized Impact
−$160K
Confidence
High
Recommended Action

Review qualification mapping for MCC 7372 across card program V-COM-04. Pass Level III line-item data on every PaymentIntent via Stripe's payment_line_items API. One dev pass covers all 4 sub-levers.

02 · Advise

Turn analysis into clear next steps.

Once payments are explainable, the question is what to do about it. Flexibl's Advice layer is built on real payment expertise and patterns observed across platforms processing billions in volume specific, quantified, and grounded in your actual data.

  • Processor Fee ValidationAre you being charged correctly?

    Validate whether processors are charging against contracted terms. Misapplied fees, pinpointed.

  • Card Plan QualificationAre transactions qualifying at the right tier?

    Identify downgrade patterns, quantify the savings opportunity, define the actions required to realize it.

  • Intelligence LayerPattern detection at scale.

    A trained model on top of normalized payment data anomalies, emerging patterns, prioritized opportunities.

Find out what's going undetected →
03 · Optimize

Optimization isn't making changes. It's knowing they worked.

Making a change to your payment stack is easy. Knowing whether it actually worked is harder than it should be. Flexibl tracks realized outcomes against expected improvements so your team can validate decisions, not just make them.

  • Realized Savings TrackingDid the change deliver?

    After a fee correction, pricing adjustment, or routing change, track actual margin impact against the baseline.

  • Processor Migration ValidationWas the migration worth it?

    Margin performance before, during, and after. Get a defensible answer to the question your CFO will eventually ask.

  • Ongoing Margin HealthIs performance staying where you set it?

    Continuous monitoring against your targets. Deviations surface before they show up in a quarterly review.

● Change verified · monitoring
Card Plan Qualification Correction Adyen
3.9%→4.4%+0.5% · +$284k/yr
Affected volume$5.8M
Implementation dateFeb 14, 2026
Variance vs expected−0.02% (within band)
StatusStable · 9 weeks
Margin · weeklybaseline → realized
change applied
Start now

Know what's driving your payment margins. Starting now.

Flexibl connects to your processors and internal systems and starts returning answers. See what your payment economics actually look like, and what's been going undetected.

Request a demo →Or see a walkthrough first
What you'll get in your demo
  • 01A live walkthrough on a sandbox dataset modeled on your processor mix
  • 02Three sample findings sized to a platform of your scale
  • 03A scoped onboarding plan with a 14-day path to first finding
FAQ

Common questions, directly from buyers.

We already get reporting from our processor. Why isn't that enough?+

Processor reports serve the processor. Fee names are inconsistent, settlements are batched to obscure true cost, and there's no cross-processor view. They tell you what happened in their system not what it means for your margins.

We have a BI tool. Can't we just build this internally?+

BI tools can visualize data but can't interpret payment-specific economics interchange qualification, card plan tiering, fee normalization across processor formats. Building and maintaining the payment data model that makes those things queryable is the full-time job Flexibl was built to do.

How does data get into Flexibl?+

Flexibl connects directly to processor APIs and ingests settlement reports, transaction data, and fee files. For internal systems billing, ledger, ERP we support file-based and API ingestion. Most platforms are seeing normalized data within days of onboarding.

How long before we see value?+

Most platforms surface a meaningful finding a fee anomaly, a reconciliation exception, or an unexplained margin movement within the first two weeks of connecting their data.

We're mid-migration to a new processor. Is now a good time?+

It's the best time. Migrations are where the most assumptions go unvalidated and where margin gains most often get lost. Flexibl establishes a pre-migration baseline and tracks whether the new processor actually delivers what you projected.

Which processors do you support?+

Flexibl is processor-agnostic by design. If you're running multiple processors or evaluating a move between them that's exactly the use case we're built for.