Skip to content
EXIROM

Payment analytics + Nimo AI

Find what changed.
Know where to investigate.

Understand payment performance with custom dashboards and Nimo, your AI payment analyst. Compare merchants and providers, explore cascade recovery, or ask a question and follow the evidence—all inside Exirom.

Book an Analytics demo →See Nimo in action ↓

Custom dashboards · Provider drill-downs · Nimo AI assistance

Payment KPIs and money movement in Exirom. Illustrative data throughout this page; enlarge any screenshot to inspect the product view.

What changed?

Compare volume, approval and payment mix across the same period.

Where did it happen?

Follow the result into merchants, providers, accounts and issuing segments.

What should we check?

Review the evidence and focus your team’s next investigation.

Meet Nimo

Your AI
payment analyst.

Can’t find the answer? Tired of charts and spreadsheets? Ask Nimo in your own words. It uses your dashboard view and filters to explain performance with supporting comparisons, tables and visual summaries.

  • Understand a change. Ask what happened to volume, approval or traffic.
  • Follow the evidence. Compare merchants, providers and payment methods, then ask a follow-up.
  • Find your next investigation. Request a monthly review with findings and proposed checks.

Example question

“Which merchants account for the biggest volume drops?”
See Nimo in a demo →

Inside Exirom Analytics. Findings guide investigation; Nimo does not automatically change routing.

Example 1 of 4 · Traffic & merchants

Example conversation · traffic and merchant comparison.

Fictional example data. Enlarge to read Nimo’s explanation and supporting evidence.
Read example response

Text version of the illustrated response. All names, accounts and figures are fictional.

Today’s traffic is lighter: 1,800,000 approval-eligible transactions, down 10% against the same hours yesterday. Successful volume is €86.4M, down 10%. Approval improved to 80%, up four percentage points: fewer transactions, with a higher share succeeding.

Merchant Alpha, Merchant Beta and Merchant Gamma account for the largest drops in successful volume compared with the same hours yesterday.

Illustrative daily merchant successful-volume comparison
MerchantYesterdayTodayDrop
Merchant Alpha€24M€19.2M€4.8M (20%)
Merchant Beta€20M€16M€4M (20%)
Merchant Gamma€12M€9M€3M (25%)
Merchant Delta€8M€6M€2M (25%)
Merchant Epsilon€6M€4.8M€1.2M (20%)

Suggested follow-ups: is Merchant Gamma’s drop driven by fewer payments or lower approval? Which accounts explain Merchant Alpha’s volume drop?

From overview to investigation

Follow the question into the detail.

Six ways to explore your payment performance. Open the full widget library when you want to go deeper.

What changed, and when?

Compare successful volume, approval and transaction trends across periods. Find when the change began.

Reconstructed trend with exact illustrative data, based on the product widget. Enlarge to inspect the example.

Cascade recovery breakdowns

Where does cascade recovery come from?

Break recovery down by initial decline code, PSP pair, rescuing provider or cascade depth. Compare rescued payments, rescue rates, recovered volume and volume left unsuccessful.

Illustrative cascade-recovery report. Open the full view to inspect the figures.
See recovery KPIs: rescued payments, volume and time
Illustrative recovery overview. Compare uplift, recovered volume, rescue rate, lost volume and time to rescue.

Which merchant or account changed?

Expand merchant comparisons into merchant accounts. See whether a change is broad or concentrated in one account.

Illustrative product view: Monthly merchant performance. Enlarge to inspect the detail.

Which provider or processing account?

Follow PSPs into merchants and external MIDs—the provider-side processing accounts. Compare approval, attempts and approved value.

Illustrative product view: Provider attempt drilldown. Enlarge to inspect the detail.

Which issuing segment stands out?

Explore attempt approval by issuer country, issuing bank and BIN. Find differences hidden by the overall average.

Illustrative product view: Approval by issuer country. Enlarge to inspect the detail.

What is behind the failures?

Open a decline reason to see its merchants and PSP / external MID breakdown. Locate the largest concentrations of failed attempts.

Illustrative product view: Decline analysis. Enlarge to inspect the detail.
Browse all 32 widget typesOutcomes · PSP attempts · Payouts

32 widget types

Search or choose a view, then open a widget for its explanation and available screenshots.

Explore the final payment result, the processing attempts behind it and payout performance. Widget availability depends on the selected analytics view.

Showing 32 of 32 widget types

Transaction outcomes

Transaction KPI overview

How is payment performance changing?

Read successful volume, approval, transaction count and average amount together for the selected period. Compare with the selected reference period before investigating individual segments.

Product overview showing the KPI row and Money movement together. Fictional business data; enlarge to inspect the full view.

Transaction outcomes

Money movement

Where is money moving?

Review successful sales, card and APM sales, payouts and refunds with their counts, volumes and prior-period values.

Product overview showing the KPI row and Money movement together. Fictional business data; enlarge to inspect the full view.

Transaction outcomes

Volume progression

Which merchant or account changed?

Compare merchant volume across daily, weekly and monthly windows. Expand a merchant into merchant accounts; use monthly progression for volume, counts and approval together.

Compare each merchant's daily, weekly, and monthly successful volume with prior periods. Expand a merchant to see the merchant-account breakdown underneath it. Percentage changes help separate changes in the merchant's volume from changes in the overall payment mix.
See 1 more view: Monthly merchant performance

Monthly merchant performance

Track month-to-date successful volume, previous-month volume, the seven-day average, transaction count, approved count, and approval rate for each merchant. Expanded rows show account detail. A dash indicates that a value, such as a forecast, is not available in the displayed view.

Transaction outcomes

Transaction volume trend

When did the change begin?

Switch between successful volume, count and approval. Compare the timeline with the reference period and change the time granularity.

A faithful reconstruction of the product’s trend widget with exact fictional hourly data. Illustrative totals: €86.4M today versus €96M yesterday, down 10%. Blue shows today; the dashed line shows yesterday. Controls illustrate the product interface and are not interactive in this image.

Transaction outcomes

Currency exposure

Which currencies carry the volume?

Compare the currencies in your payment activity and how each performs. Keep original amounts and reporting-currency conversions distinct when reading comparisons.

Transaction outcomes

Merchant account outcomes

Is one merchant account pulling down the total?

Compare transaction outcomes across merchant accounts to locate differences within a merchant. Merchant accounts and provider-side external MIDs are separate dimensions.

Transaction outcomes

Cards vs APM transaction outcomes

Are cards and alternative methods moving differently?

Compare cards with alternative payment methods over time and inspect the gap between their transaction outcomes.

Transaction outcomes

Final MID distribution

Which external MIDs ultimately processed the payments?

Compare volume and approval by the provider-side processing account on the final transaction. Final-account distribution is separate from the accounts involved in earlier attempts.

Transaction outcomes

Routing version impact

What changed after a routing version went live?

Compare each account’s newest routing version with the previous one over equal observation windows. This is a before-and-after comparison, not an A/B test: traffic mix may also have changed.

Transaction outcomes

Merchant transaction performance

Which merchants contribute most to the total?

Rank merchants by volume and compare their approval and share of total transaction activity.

Transaction outcomes

Final PSP group distribution

How is final volume distributed across provider groups?

See how payment volume is split across the PSP groups that finally processed the transactions.

Transaction outcomes

Issuer → PSP group performance

How do final results differ by issuer and provider group?

Expand an issuer into PSP groups and compare final card-sale outcomes. A cascaded payment counts once using its final transaction.

Transaction outcomes

Transaction approval by issuer

Which issuers have weaker final payment outcomes?

Compare final card-sale approval by issuing bank and expand into BINs. Each cascaded payment counts once at its final outcome; this differs from attempt approval.

Transaction outcomes

Transaction approval by issuer country

Which issuer countries have weaker final outcomes?

Compare final card-sale approval by issuer country, then expand into issuers and BINs. Each cascaded payment counts once at its final outcome.

Transaction outcomes

Transaction decline codes

Why did payments ultimately fail?

Review final card-sale decline codes and expand into the account behind them. This view counts final failed transactions and blocked routing no-match outcomes, rather than every unsuccessful PSP attempt.

PSP attempts & routing

PSP attempt approval by issuer country

Which issuer countries need investigation?

Compare attempt approval, approved attempt value and attempt count by issuer country. Expand a country into issuing banks, then into BINs, the card-number ranges that identify issuing segments.

Compare issuer countries by approval, approved attempt value, and attempts. Expand a country into issuing banks and then BINs to find the issuing ranges behind the result. The colored bars visualize the approval-rate bands shown in the legend.

PSP attempts & routing

PSP attempt approval by issuer

Which bank or BIN is behind the result?

Rank issuing banks by attempt approval, approved value or attempt count. Expand a bank into its BINs to see differences hidden by the issuer average.

Compare issuing banks by attempt approval, approved value, and attempt count. Expand an issuer to inspect BIN-level performance and its country labels. Sorting and CSV controls support closer review of the displayed breakdown.

PSP attempts & routing

Cascade recovery

What did eligible retries recover?

Review rescued payments, recovered payment volume, rescue rate, approval uplift and time to rescue. Rescue rate excludes unresolved cascades; recovered volume is payment volume, not profit.

Measure the results of retrying eligible payments: approval uplift, recovered payment volume, rescue rate, lost volume, and average time to rescue. The chart shows when recovered volume occurred. In this example, 6,000 recoveries out of 24,000 cascaded transactions give a 25% rescue rate. Six illustrative time buckets each contain €80,000 recovered, totaling €480,000.

PSP attempts & routing

Cascade recovery breakdowns

Where is recovery coming from?

Break recovery down by initial decline code, PSP pair, rescuing provider or depth. Compare rescued counts, rescue rates, recovered volume and volume left unsuccessful. A PSP pair links the immediately preceding failed provider to the rescuing provider.

Break recovered and unsuccessful cascades down by initial decline reason, PSP pair, rescuing provider, or cascade depth. Cascaded counts the transactions entering recovery; rescued counts those approved later. Compare rescue rate and gross recovered volume with the volume left unsuccessful.

PSP attempts & routing

Attempt decline codes

Which failure reasons are most frequent?

Compare decline counts and shares. Expand a code into merchants, then into the combined PSP / external MID rows behind those failed attempts. Share is relative to the displayed level.

See which decline reasons account for unsuccessful attempts, then expand a reason into merchants, then combined PSP / external MID rows. Counts show frequency; share bars show the proportion within the displayed level. Decline-code identifiers remain product labels while all business data is illustrative.

PSP attempts & routing

PSP attempt outcomes by geo consistency

Do outcomes differ when country signals disagree?

Compare attempts where BIN, billing and IP countries match or differ. Inspect succeeded, failed and other outcome counts alongside approval and approved value.

Compare attempt outcomes for matching or differing BIN, billing, and IP countries. Each row shows its share of attempts, succeeded and failed counts, other outcome categories, approval, and approved value. This makes differences between geographic groups visible in one table.

PSP attempts & routing

Issuer → PSP → external MID performance

Does an issuer perform differently across providers?

Expand an issuing bank into the PSPs and external MIDs that handled its card attempts. Compare approval with approved and failed attempt counts.

Follow an issuing bank into the PSPs and external MIDs (provider-side processing accounts) that handled its card attempts. Compare approved and failed attempts with approval rates and prior-period changes. This helps identify whether an issuer's results differ by provider or processing account.
See 1 more view: Issuer performance drilldown

Issuer performance drilldown

Expand the issuer-to-PSP hierarchy to inspect individual provider-side accounts. Account aliases such as DEMO-EUR-001 identify fictional processing configurations. Use the approval and failed-attempt columns together to investigate the source of an issuer-level change.

PSP attempts & routing

Attempted MID health

Has a processing account deteriorated recently?

Compare first-attempt approval and attempt count for each external MID: the recent four hours against the same clock hours over the prior seven days. Read percentage-point change, z-score and top decline code together.

Compare each provider-side processing account's recent approval rate and transaction count with its seven-day baseline. The percentage-point delta shows the approval change, the z-score provides a standardized comparison, and top decline identifies the leading decline code. Read these together when investigating account degradation.

PSP attempts & routing

PSP attempt performance

Is the change concentrated in one provider or external MID?

Compare approval, attempts, unique transactions and attempted or approved value. Switch between PSP → merchant, merchant → PSP and PSP → MID views, then expand the hierarchy. Retries can count the same payment more than once.

Compare PSP processing attempts and follow the same view down into merchants and external MIDs. Attempts can exceed unique transactions because a payment may have more than one processing attempt. Continued and recovered counts show the cascade activity associated with the displayed provider.
See 2 more views: Provider attempt drilldown · Merchant attempt performance

Provider attempt drilldown

Start with a PSP, then expand its merchants and provider-side processing accounts, labelled EXTERNAL MID. Compare approval, attempts, unique transactions, attempted and approved value, and cascade continuation and recovery. Every account alias in these examples is fictional.

Merchant attempt performance

Start with a merchant, expand its PSPs, and inspect the provider-side account used for processing. Compare attempted and approved value with approval, attempts, and unique transactions. This view helps locate whether a performance change is broad or concentrated in one provider account.

PSP attempts & routing

PSP volume progression

How has provider volume changed across periods?

Compare daily, weekly and monthly successful provider volume, with Overall, Cards and APM views. Expanded rows show processing-account detail; monthly progression adds month-to-date comparisons.

Compare provider volume across daily, weekly, and monthly periods. Overall, Cards, and APMs separate the payment mix, while expanded rows reveal account detail. Keep the same currency and period when comparing providers.
See 1 more view: Monthly provider performance

Monthly provider performance

Review month-to-date volume against the previous month and the seven-day average, with separate card and APM totals. Count, approved count, and approval are shown where applicable. Expanded rows expose downstream processing accounts; dashes indicate unavailable values.

PSP attempts & routing

PSP attempt approval heatmap

Which issuer and PSP combinations stand out?

Compare issuer-versus-PSP combinations in a grid colored by attempt approval. Use it to identify combinations for closer investigation.

PSP attempts & routing

Cascade funnel

What happens at each cascade position?

See how many attempts reach each cascade position and how many succeed there. A position is a processing-attempt stage, not a separate customer payment.

PSP attempts & routing

Attempt approval by hour

Are there hours with weaker attempt approval?

Compare approval by hour of day to find time windows that warrant closer review.

Payouts

Final payout approval heatmap

Which issuer and provider combinations have weaker payouts?

Compare issuers against PSPs in a grid colored by final payout approval.

Payouts

Final payout approval by issuer country

How does payout approval differ by issuer country?

Compare final payout approval by issuer country and expand into issuing segments down to individual BINs.

Payouts

Final payout approval by issuer

Which issuing banks have weaker payout approval?

Compare final payout approval by issuing bank and expand into individual BINs.

Payouts

Payout KPI overview

How are payouts performing?

Review payout volume, count, approval rate and average amount for the selected period.

More screenshots: Nimo, filters and boards
Nimo AI · 6 viewsAsk a question. Follow the answer.

See the conversation from opening Ask AI through traffic analysis, monthly comparisons and proposed investigations.

Open Ask AI

Launch Nimo from the Ask AI control inside the analytics dashboard. Keep the current view and filters as the starting point for a question.

Ask in plain language

Start with a suggested question or write your own. Nimo carries the current dashboard view and applied filters into the question, including the traffic, approval, PSP, merchant, or decline segment you are investigating.

Follow the change into the merchants

Ask how traffic compares with the previous period, then follow up on the merchants behind the change. Nimo combines a written explanation, a merchant comparison table, and suggested follow-up questions in the same conversation.

Get a monthly review

Ask for a broad performance review with highlights and visual summaries. Nimo organizes the answer into a period comparison, key metrics, and a visual volume breakdown so you can follow the supporting data. The transaction row shows the approval-eligible population; blocked and unfinished payments are excluded from that denominator.

Compare methods and merchants

Explore which payment methods and merchants contributed to a change. The answer pairs comparison tables with an explanation of volume and approval differences, helping focus the next question.

Turn findings into investigations

Ask what to improve and where to start. Nimo presents priorities, supporting evidence, and proposed investigations across accounts, merchant conversion, routing, cascading, and payment methods. Findings and suggested actions remain distinguishable in the response.
Overview · 2 viewsUnderstand the final payment result.

Review successful volume, approval, money movement and change over time before investigating the processing path.

Transaction outcomes

Read the final business result: successful payment volume, approval rate, transaction count, and average ticket. Money movement separates card and APM sales, payouts, and refunds, with previous-period comparisons. These are transaction outcomes; provider attempts are explored separately. In this fictional fixture, Eligible transactions means approved plus declined sales, excluding filtered and unfinished payments; average payment is per successful sale. Comparisons use matching elapsed periods.

Transaction volume trend

A faithful reconstruction of the product’s trend widget with exact fictional hourly data. Illustrative totals: €86.4M today versus €96M yesterday, down 10%. Blue shows today; the dashed line shows yesterday. Controls illustrate the product interface and are not interactive in this image.
Read the exact hourly example

The reconstructed chart and this table share one source of fictional hourly values: €86.4M today versus €96M yesterday, a 10% decrease. Both periods cover the same hours.

Fictional successful volume by hourly bucket, amounts in EUR
HourTodayYesterday
02:00€6.0M€7.0M
03:00€5.0M€6.0M
04:00€4.0M€5.0M
05:00€3.0M€4.0M
06:00€2.0M€3.0M
07:00€2.0M€3.0M
08:00€3.0M€4.0M
09:00€4.0M€5.0M
10:00€5.0M€5.0M
11:00€4.0M€4.0M
12:00€5.0M€5.0M
13:00€6.0M€6.0M
14:00€7.0M€7.0M
15:00€8.0M€8.0M
16:00€9.0M€9.0M
17:00€8.0M€8.0M
18:00€5.4M€7.0M
Total€86.4M€96.0M
Merchants · 3 viewsFind which business changed.

Compare merchant volumes and approval, then expand into merchant accounts or follow the attempt view into providers and external MIDs to locate the affected segment.

Merchant volume progression

Compare each merchant's daily, weekly, and monthly successful volume with prior periods. Expand a merchant to see the merchant-account breakdown underneath it. Percentage changes help separate changes in the merchant's volume from changes in the overall payment mix.

Monthly merchant performance

Track month-to-date successful volume, previous-month volume, the seven-day average, transaction count, approved count, and approval rate for each merchant. Expanded rows show account detail. A dash indicates that a value, such as a forecast, is not available in the displayed view.

Merchant attempt performance

Start with a merchant, expand its PSPs, and inspect the provider-side account used for processing. Compare attempted and approved value with approval, attempts, and unique transactions. This view helps locate whether a performance change is broad or concentrated in one provider account.
Routing · 7 viewsFollow every provider attempt.

Compare first attempts and later attempts, inspect external MID health and measure eligible cascade recovery.

Provider attempt drilldown

Start with a PSP, then expand its merchants and provider-side processing accounts, labelled EXTERNAL MID. Compare approval, attempts, unique transactions, attempted and approved value, and cascade continuation and recovery. Every account alias in these examples is fictional.

Cascade recovery

Measure the results of retrying eligible payments: approval uplift, recovered payment volume, rescue rate, lost volume, and average time to rescue. The chart shows when recovered volume occurred. In this example, 6,000 recoveries out of 24,000 cascaded transactions give a 25% rescue rate. Six illustrative time buckets each contain €80,000 recovered, totaling €480,000.

Provider attempt performance

Compare PSP processing attempts and follow the same view down into merchants and external MIDs. Attempts can exceed unique transactions because a payment may have more than one processing attempt. Continued and recovered counts show the cascade activity associated with the displayed provider.

Provider volume progression

Compare provider volume across daily, weekly, and monthly periods. Overall, Cards, and APMs separate the payment mix, while expanded rows reveal account detail. Keep the same currency and period when comparing providers.

Monthly provider performance

Review month-to-date volume against the previous month and the seven-day average, with separate card and APM totals. Count, approved count, and approval are shown where applicable. Expanded rows expose downstream processing accounts; dashes indicate unavailable values.

External MID health

Compare each provider-side processing account's recent approval rate and transaction count with its seven-day baseline. The percentage-point delta shows the approval change, the z-score provides a standardized comparison, and top decline identifies the leading decline code. Read these together when investigating account degradation.

Recovery breakdowns

Break recovered and unsuccessful cascades down by initial decline reason, PSP pair, rescuing provider, or cascade depth. Cascaded counts the transactions entering recovery; rescued counts those approved later. Compare rescue rate and gross recovered volume with the volume left unsuccessful.
Issuers & declines · 6 viewsFind patterns behind unsuccessful payments.

Break results down by issuer, country, BIN, decline reason and geographic consistency.

Issuer to provider performance

Follow an issuing bank into the PSPs and external MIDs (provider-side processing accounts) that handled its card attempts. Compare approved and failed attempts with approval rates and prior-period changes. This helps identify whether an issuer's results differ by provider or processing account.

Issuer performance drilldown

Expand the issuer-to-PSP hierarchy to inspect individual provider-side accounts. Account aliases such as DEMO-EUR-001 identify fictional processing configurations. Use the approval and failed-attempt columns together to investigate the source of an issuer-level change.

Approval by issuer country

Compare issuer countries by approval, approved attempt value, and attempts. Expand a country into issuing banks and then BINs to find the issuing ranges behind the result. The colored bars visualize the approval-rate bands shown in the legend.

Approval by issuer

Compare issuing banks by attempt approval, approved value, and attempt count. Expand an issuer to inspect BIN-level performance and its country labels. Sorting and CSV controls support closer review of the displayed breakdown.

Decline analysis

See which decline reasons account for unsuccessful attempts, then expand a reason into merchants, then combined PSP / external MID rows. Counts show frequency; share bars show the proportion within the displayed level. Decline-code identifiers remain product labels while all business data is illustrative.

Geographic consistency

Compare attempt outcomes for matching or differing BIN, billing, and IP countries. Each row shows its share of attempts, succeeded and failed counts, other outcome categories, approval, and approved value. This makes differences between geographic groups visible in one table.
Custom dashboards · 4 viewsBuild the view your team needs.

Start with a preset, create a named board and choose available widgets. Apply filters for the transaction outcome or processing attempts you want to study.

Attempt filters

Narrow attempt analysis by merchant group, merchant, merchant account, card brand, and issuer country. Additional filters include attempted PSP groups, PSPs, external MIDs, technology providers, issuers, attempt position, routing version, decline codes, and BIN. Apply the selection to compare a specific segment and period.

Board presets

Start with the All preset for the available attempt widgets, Routing for PSP and cascade performance, or Declines for attempt failures and recovery. My Boards lists the custom dashboards available in this analytics view. Use a preset as a starting point for the questions your team needs to answer.

Create your own board

Give a new dashboard a name, then use Edit board to choose its widgets. Build different boards for transaction outcomes, routing, or decline investigation. The pictured Payment Operations board is a fictional example; its background figures also use illustrative data.

Transaction outcome filters

Filter final transaction outcomes by merchant, account, card brand, issuer country, and status. Additional filters include final PSP groups, PSPs, external MIDs, APM methods, routing version, decline codes, and final cascade depth. Final-provider filters describe where the transaction ended; attempted-provider filters describe the processing path.

Your analytics workspace

Your questions.
Your widgets. Your board.

Create a named board for the views your team uses. Choose, arrange and resize widgets, then set the period, comparison and filters for your investigation.

  • Start with a preset or create your own board.
  • Focus on merchants, providers or processing accounts.
  • Export supported tables as CSV for closer review.
The dashboard’s board controls and KPI view. Create Board and Edit board provide access to customisation; example data is fictional.
Definitions and measurement: transactions, attempts and recovery

Read the payment journey

One transaction. Every attempt explained.

A customer payment and a processing attempt measure different things. Looking at both shows the final business result and the provider decisions behind it.

Transaction outcomes

See the payment's final result: successful volume, approval rate, transaction count, and average amount. Money movement separates card sales, alternative payment methods, payouts, and refunds.

Use this view to answer: How much business did we process? How does it compare with the previous period? Which merchants and payment methods contributed?

PSP attempts & routing

Inspect each processing attempt across providers and their external MIDs (provider-side processing accounts). A cascaded payment can create several attempts before it reaches one final transaction outcome.

Compare all attempts with first attempts to distinguish initial routing performance from later recovery. Unique TX counts distinct transactions in the view; attempt counts can be higher.

How to read approval, counts and comparisons
Approval needs a denominator
Divide successful payments by the eligible population in that view. The illustrated Nimo review excludes blocked and unfinished payments from approval. An all-status count can therefore be different from the approval denominator.
Attempts are processing events
A payment approved on a second route is one successful transaction and two attempts. Compare first-attempt approval with final outcomes to understand the contribution of later routes.
Compare the same scope
Keep the currency, filters and elapsed period consistent. Approval moving from 75% to 80% is a five-percentage-point improvement. A change in volume is a relative percentage change.

Cascading & recovery

See what happens after a decline.

Cascading gives an eligible failed payment another processing route. Your routing rules and decline handling determine whether another provider or account should be tried, and when the cascade stops.

  1. 1

    Select the first route

    The payment is sent to the provider and processing account selected by your configured routing rules.

  2. 2

    Evaluate the response

    An approval completes the payment. An eligible decline can move to the next configured route. A non-retryable failure stops the cascade.

  3. 3

    Record the final result

    A later approval is a recovery. If the eligible routes or configured cascade depth are exhausted without success, the payment remains unsuccessful.

Illustrative payment journey

Provider Alpha · DEMO-EUR-001

First attempt: eligible decline

Provider Beta · DEMO-EUR-002

Second attempt: approved

One transaction · two attempts · one recovered payment.

Illustrative recovery view: 24,000 cascaded payments, 6,000 rescued, €480,000 recovered and €1.44M left unsuccessful. This recovery example has its own population and period.
Approval uplift
The improvement in transaction approval from successful later attempts, expressed in percentage points. Use it to see how cascading changes the final outcome.
Gross recovered
The payment volume successfully recovered through cascading. This is recovered payment volume, before fees and other adjustments.
Rescue rate
Rescued payments divided by rescued plus exhausted payments; unresolved cascades are excluded. In this example there are no unresolved cascades: 6,000 rescued out of 24,000 completed cascades gives 25%.
Lost volume
Payment volume left unsuccessful after the cascade is exhausted. Read it alongside the exhausted and unresolved counts to distinguish completed failures from unfinished processing.
Average time to rescue
Time from the first attempt to the first succeeding attempt. Compare it with rescue rate and recovered volume to understand the customer experience.

Recovery breakdowns let you compare initial decline codes, PSP pairs, rescuing providers, and cascade depth. Use them to see which retry paths recover payments and which finish without success. Decline rules matter: every failure is not a candidate for another attempt.

Read more about routing and cascading →

From merchant to processing account.

Start with a business result, then follow the provider, account, issuer, or decline reason behind it. These are the terms used throughout the screenshots.

Merchant, PSP, external MID, issuer and other terms
Merchant
The business accepting the payment. Merchant views help compare businesses, brands, and their payment activity.
PSP
A payment service provider that processes a payment attempt. One transaction can pass through more than one PSP when cascading applies.
Merchant account
A merchant-side account used to organize and compare payment activity within a merchant. Merchant-account outcomes and merchant volume progression help locate differences between these accounts.
External MID
The provider-side processing account used at a PSP. Its alias can distinguish a currency or processing configuration. This is separate from a merchant account. Example aliases such as DEMO-EUR-001 are fictional.
Issuer and BIN
The issuer is the bank that issued the customer's card. A BIN identifies the card's issuing range. Issuer, country, and BIN views help locate differences in approval performance.
Cards and APMs
Cards are card payments. APMs are alternative payment methods. Their volumes and outcomes can be viewed separately so a change in payment mix is easier to understand.
Payouts and refunds
Payouts are outgoing payments; refunds return money from a sale. The money movement widget displays their transaction counts and volumes separately from successful sales.
MTD and comparison periods
MTD means month to date. Previous-period comparisons show changes in volume, count, and approval. A change in approval is measured in percentage points; a relative change in volume is shown as a percentage.

Choose the filter that matches your question.

Where did the payment finish?

Use Transaction Outcomes with final PSP and final external MID filters. These describe the provider and processing account associated with the final result.

Which route handled an attempt?

Use PSP Attempts & Routing with attempted PSP, attempted external MID, attempt position, routing version and decline-code filters. These describe the processing path, including eligible fallback attempts.

Bring your hardest payment question.

See how Exirom Analytics helps your team compare performance, locate changes and investigate the evidence.

Book an Analytics demo