← Use cases
Success and approval rates

One missing tax field. Thousands of transactions downgraded. Who noticed?

Bicycle checks every merchant's settlement and interchange rate every day, explains each spike and ranks it by what it costs.

Book a demo Start for free

No credit card required

Before

A rate spike for one merchant hides among thousands. The cause is usually a qualification gap, such as missing data or a configuration change, and finding it by hand takes days.

With Bicycle

Each spike is explained and ranked by financial impact the day it happens, with the transactions where fixing it saves the most.

What happens when a KPI moves.

  1. 01

    Detect

    A merchant's settlement or interchange rate spikes against its baseline.

  2. 02

    Explain

    The qualification gap is named: a failed address check, missing Level 2 or Level 3 data, the wrong card level, or a merchant or network rule change.

  3. 03

    Act

    Bicycle recommends the fix: a development ticket, a case with the processor, a call to the merchant, or a merchant category code (MCC) correction.

  4. 04

    Learn

    Analyst feedback on each alert tunes detection, and known custom rates are excluded.

85%

faster investigation, from 2–3 days to under 4 hours

Seen at: Billtrust. Read the case study

Everyone can ask. Data & Analytics controls what gets trusted, published, and acted on.

Runs on
  • Settlement data
  • Transaction data
  • Merchant configuration
Used by
  • Payment operations
  • Payment analysts
  • Merchant success

Common questions

How do I find out why a merchant's interchange rate suddenly went up?
When a merchant's rate spikes, Bicycle tests many possible root causes at once: tax amount validation gaps, merchant category code restrictions, large-ticket qualification issues, custom rate code violations and government-card processing rules among them. Bicycle scores each transaction against your interchange compliance guide and surfaces the specific qualification gap behind the downgrade, so your analysts do not investigate from zero.
What data do you need to spot interchange downgrades every day?
Bicycle reads the daily settlement data from your warehouse and your processor feeds, and tracks each merchant's effective interchange rate against its own historical baseline as soon as the settlement data lands. Bicycle treats merchant, card type, interchange code and time as first-class dimensions, along with card hierarchy logic and the interchange qualification rules.
Who decides what to do about an interchange downgrade?
Your operations team decides. Bicycle sends a daily email report with the top transactions by potential savings, merchant-level impact summaries and drill-down links, and operations chooses the intervention. Analysts mark each alert true positive, false positive or not actionable. Customer-success teams view merchant-specific insights themselves, within the permissions your data team sets, without waiting on an analyst.

More on success and approval rates

See it on your own KPI.

Bring one revenue-critical KPI. We'll show how Bicycle detects the movement, explains the cause, and recommends the next step.

Book a demo