EcomCharge
Get started Get started
Case studies

How a PSP Avoided Payment Network Penalties by Controlling Retry Logic in Smart Routing

Subscription · Recurring · Compliance · Smart Routing • April 2026
0 Network penalties Retry mandates enforced automatically
↑ Approval rate Fewer unnecessary declines, better retry timing
0 Merchant-side changes Configured at the platform level
At a glance
Client
A PSP working with subscription and recurring payment models, including merchants that rely on MIT for billing
Challenge
Automated retries hit the same cards hundreds of times a day; most systems count total failures, not consecutive ones — the gap that leads to network fines
Solution
Smart Routing retry rules with consecutive failed attempt counting
Result
Zero network penalty violations · improved approval rates · no merchant-side changes required
Segment
Recurring payments PSP
Applies to
Subscriptions · MIT · iGaming · Forex
Network rule
Max 10 retries per card in 14 days
Solution used
Smart Routing
Case study 05 · names protected by NDA
Case study 05

Challenge

When a recurring payment fails, the natural response is to try again. But how often, and when?

Without controlled retry logic, automated systems were retrying failed transactions too frequently — sometimes hundreds of times per day on the same card. This created three compounding problems
Problem 1

Approval rates collapsed

Each retry counted as a new failed transaction, dragging down approval rates — even though the underlying issue was a single unpaid charge.

Problem 2

Network rules violated

Visa mandates no more than 10 retry attempts within a 14-day window per card. Exceeding this triggers penalties for the acquiring bank.

Problem 3

No one could count correctly

Counting consecutive failed attempts on the same card within a rolling window is technically complex. Most systems simply don't do it.

The PSP needed a way to track sequential retry behaviour and enforce limits automatically — without rebuilding merchant-side logic.

Case study 05

Solution

The platform enabled the PSP to implement controlled retry logic using Smart Routing rules — including strictly sequential failed attempt counting. This included
Tracking the exact number of consecutive failed attempts per card
Enforcing retry frequency limits in line with Visa and Mastercard mandates
Delaying subsequent attempts until the card exits the restricted window
Sending automated alerts when a rule approached its limit — giving the team time to act before a limit was hit

The configuration was set up by the eComCharge team based on the PSP's retry strategy and the payment network requirements their merchants were subject to.

How Smart Routing controls retry behaviour

Each retry attempt is evaluated in context — not just counted in total

Without Smart Routing rules Uncontrolled retries — violation in progress
Retry attempts on this card14 attempts · limit is 10
System retried the same card 14 times in 12 days. Visa limit exceeded. Acquiring bank exposed to penalty. Merchant unaware.
Alert threshold reached Smart Routing fires alert at 70% of limit
Retry attempts on this card7 of 10 · alert sent
Team notified before the limit is hit. Time to coordinate with the merchant or pause retries — no penalty triggered.
With Smart Routing rules Compliant retry — within network limits
Retry attempts on this card6 of 10 · within limit
Consecutive attempts tracked per card within a rolling 14-day window. Next retry delayed until the window permits. Zero violations.
Checks Consecutive failures per card Not total failures — consecutive ones, in sequence, within a rolling window. Exactly as Visa requires.
Enforces Retry frequency limits Delays the next attempt until the card exits the restricted window. No manual intervention needed. Visa & Mastercard compliant
Alerts Before limits are hit Automated alert when a card or merchant approaches the retry cap — time to act before a violation occurs. No merchant-side changes
Case study 05

What changed

Instead of retrying blindly, the system evaluated each attempt in context
How many consecutive failures had already occurred on this card
How recently the last attempt was made
Whether another retry was permitted under network rules

Retry attempts dropped dramatically. The ones that remained were well-timed and compliant.

Case study 05

Result

Eliminated retry attempts that violated Visa/Mastercard retry mandates
Reduced unnecessary declined transactions — approval rates improved
Protected the acquiring bank from payment network penalties
Merchants no longer needed to build or maintain complex retry logic themselves
Case study 05

When this matters

Retry control is critical for any PSP working with
Subscription billing and recurring charges
Merchant-initiated transactions (MIT) after card-on-file setup
High volumes of failed payment attempts
Merchants who rely on automated retry robots without built-in frequency limits

This applies equally to low-risk PSPs (SaaS subscriptions, streaming, utilities) and high-risk (microloans, iGaming deposits, forex).

In practice

How PSPs use this in practice

PSPs configure Smart Routing rules to
Cap the number of retry attempts within a defined time window (e.g. max 3 attempts per 7 days)
Delay retries until the card exits the restricted window
Receive alerts when a card or merchant approaches a retry limit
Automatically add cards with extreme retry patterns to a blacklist

This allows PSPs to recover failed payments systematically — while staying compliant with network rules and protecting long-term approval performance.

Results

Recurring payments PSP · Smart Routing retry rules · Visa & Mastercard compliance

Zero
Network penalty violations

Retry mandates enforced automatically across all merchants

↑ Approval
Approval rates improved

Unnecessary declines removed — fewer retries, better timing, higher success rate

✓ Protected
Acquiring bank protected

No exposure to Visa or Mastercard penalties from retry violations

0 changes
No merchant-side work

Configured at the platform level — merchants needed no integration changes

Most systems can count total failed transactions. Smart Routing tracks strictly sequential consecutive failures per card within a rolling window — exactly what payment network rules require. Acquiring banks in regulated markets rely on this to stay penalty-free.

Want to discuss a similar setup for your platform?

Talk to us

More case studies

  1. 01 3× volume growth without adding infrastructure iGaming · High-risk · Smart Routing · SmartCheck 3× in 12 months
  2. 02 95% of tokens migrated in one week — acquirer switch with zero customer impact High-risk · Recurring · Token migration 95% tokens · 1 week
  3. 03 Acquirer failure contained in seconds — before a single merchant noticed Low-risk · Platform stability · Proactive monitoring Resolved in seconds

Set up your payment processing system

in 7 days, not a year
Request demo