Approval rate reporting
Issuer decisions vary by decline code, BIN, authentication result and retry timing. Authorisation approval rate reporting gives risk and treasury teams transaction-level evidence, with Cardflo capturing scheme responses and classifying soft and hard declines.
- Category
- Reporting
- Capabilities
- 8
- Available on
- All plans
Payments and finance teams need one agreed number for how much of their submitted volume is being approved, cut the same way every month. Without a consistent denominator and a fixed set of dimensions, two people looking at the same week reach different conclusions about whether acceptance is healthy.
Cardflo calculates approval rates against every authorisation submitted through the acquirer partner network and holds the result steady across acquirer, MID, card BIN, card product, currency and country. Teams can compare like with like over any period, benchmark one processing route against another and set thresholds that raise an alert when a segment moves out of pattern. Where the question turns from how many to why, the decline code reporting page carries the response-code detail.
Approval rate reporting offers an in-depth comparison of performance across various card types and currencies, highlighting the impact of scheme dynamics. This allows for targeted optimisation of the MID portfolio, boosting overall transaction success.
Approval rate reporting overview
Approval rate reporting is a measurement surface. It fixes one definition of acceptance, applies it consistently, and lets teams slice the result by the dimensions that describe how a payment was processed rather than why it failed.
The calculation runs over all submitted authorisations, so the denominator does not shift when traffic mix changes, and the same figure is available in the dashboard, in exports and over the reporting API. That consistency is what makes the number usable in a board pack or an acquirer review.
Segmentation is where the report earns its keep. Acceptance is broken out by acquiring partner and MID, by card BIN and card product, and by currency, cardholder country and merchant category, so a merchant can see whether a soft month reflects a single route, one market or a change in traffic composition.
Period comparison sits alongside every segment, with daily, weekly and monthly views and rolling baselines, so a genuine shift can be told apart from ordinary variance.
The report deliberately stops short of diagnosis. Response-code families, permitted reattempt treatment and code-level playbooks belong to decline code reporting; the behaviour of an individual issuing bank over time belongs to card issuer performance reporting; checkout behaviour before submission belongs to conversion reporting.
Approval rate reporting answers the size question and hands off cleanly to whichever of those answers the follow-up.
How approval rate reporting works
Fixing the calculation
Acceptance is computed as approved authorisations over all authorisations submitted, with the same treatment of reversals and cancellations everywhere the number appears. Holding the definition constant means the figure can be compared across months, routes and markets without anyone having to restate how it was derived.
Building the segments
Each authorisation carries the acquiring partner, MID, card BIN, card product, currency, cardholder country and merchant category it was processed under. Acceptance is aggregated along every one of those dimensions, so any combination can be opened without a bespoke query or a data request.
Baselines, trends and alerts
Every segment keeps a rolling baseline of its own recent behaviour. Daily, weekly and monthly views sit over the top for trend reading, and thresholds are set against the segment baseline so an alert reflects a real departure for that route or market rather than movement in the headline figure.
Why approval rate reporting matters
One number everybody trusts
Disputes about acceptance are usually disputes about method. Publishing a single calculation, with the same denominator in every view, removes that argument and lets payments, finance and commercial teams discuss the same trend instead of reconciling two spreadsheets before the conversation can start.
Evidence for acquirer conversations
Route-level and MID-level acceptance measured over matched periods is the material for a commercial review. It shows which partner performs on which traffic, supports a case for reweighting volume, and turns a renewal discussion into a data conversation rather than an exchange of impressions.
Regulatory notes for approval rate reporting
Scheme monitoring thresholds
Card networks watch the ratio of failed to successful authorisation traffic and operate programmes for merchants that submit excessive volumes of requests which cannot succeed.
Consistent measurement matters here because a merchant needs to know, with evidence, where it sits relative to those thresholds before an acquirer raises it.
A fixed acceptance calculation segmented by MID gives that visibility per account rather than as a blended average.
Where a single MID is dragging the portfolio towards a monitoring threshold, it can be identified and addressed before the network programme applies, and the treatment of individual response codes is governed on the decline code reporting page.
Strong Customer Authentication and measured acceptance
In the European Economic Area and the United Kingdom, in-scope electronic payments require Strong Customer Authentication unless a valid exemption applies, and the authentication path a transaction takes affects the acceptance you measure.
Because acceptance is segmented by market and card product, the effect of authentication policy in one territory can be read against comparable traffic elsewhere.
That keeps a regulatory requirement from being mistaken for a commercial problem, and vice versa, when the figure moves in a single region.
Approval rate reporting use cases
Monthly acceptance reporting pack
A payments lead reports acceptance by acquiring partner and market each month using one calculation, so trend commentary stands up without a methodology footnote.
Route comparison on matched traffic
A merchant running two acquirers compares acceptance on matched traffic over the same period, then shifts volume towards the stronger route with measured evidence.
Benchmarking a newly opened market
A retailer benchmarks acceptance in a newly opened country against its established markets to judge whether local acquiring is worth pursuing.
Card product analysis
A subscription business segments acceptance by card product and finds commercial cards trailing consumer cards, informing which credentials to prioritise for updating.
Approval rate reporting by the numbers
Acquiring partner, MID, BIN, card product, scheme, currency, cardholder country and merchant category can be combined freely over any period.
Rolling baselines per segment let a genuine movement be separated from ordinary day-to-day variance before anyone acts on it.
The acceptance calculation is fixed rather than configurable, so figures quoted in different months and by different teams remain directly comparable.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Approval rate reporting
- Apply one fixed acceptance definition across dashboards, exports and the reporting API.
- Break acceptance out by acquiring partner and by individual MID.
- Segment by card BIN, card product and scheme to see which portfolio slices lag.
- Compare markets using cardholder country, settlement currency and merchant category.
- Set rolling baselines per segment so ordinary variance does not trigger noise.
- Raise alerts when a named segment falls below its own threshold rather than a global one.
- Benchmark two processing routes over the same period and the same traffic mix.
- Publish the figure finance and payments teams both cite, from a single calculation.
A short scoping call, then a written plan for your MIDs.
Questions about Approval rate reporting
How is the approval rate calculated here?
Approved authorisations are divided by all authorisations submitted, with reversals and cancellations treated identically in every view. The definition is fixed rather than configurable, which is the point: a figure that can be redefined per report cannot be compared across months or teams.
If you need the underlying counts for your own model, both the numerator and the denominator are available in exports and over the reporting API.
Which dimensions can I segment by?
Acquiring partner, MID, card BIN, card product, scheme, settlement currency, cardholder country and merchant category, in any combination, over any period. Those dimensions describe how a payment was processed.
The dimension that describes what the issuer objected to is the response code, and that lives on the decline code reporting page so the two reports keep separate jobs.
What is a healthy approval rate?
It depends on the vertical, the market and the traffic mix, so an absolute target is rarely useful. The number that matters is your own baseline per segment.
A domestic card-present portfolio and a cross-border subscription portfolio can differ by many points while both performing normally, which is why alerts here are set against each segment's own recent behaviour instead of a single site-wide figure.
How do I compare two acquirers fairly?
Match the traffic before comparing the outcome. Filter both routes to the same period, markets, card products and ticket bands, then read acceptance on that matched set.
Comparing raw route totals usually just reflects the mix each route was sent, which is how a stronger partner can appear weaker simply because it carries the harder traffic.
Related guides.
See how Cardflo compares.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.