---
title: "Use Cases"
description: "Platform capabilities in real scenarios: Referer Control and Action Rules inside Smart Routing, with real examples from PSPs and banks on the eComCharge platform."
url: "https://ecomcharge.com/use-cases/"
lang: "en"
image: "https://ecomcharge.com/static/assets/img/og-default.859636851186.png"
breadcrumbs: "Home > Use Cases"
---

Use cases

# Platform capabilities in real scenarios.

One capability per page: what it checks, how the rule is set up and the situations PSPs and banks use it for, with examples from the platform.

[Request a demo](https://ecomcharge.com/contacts/sales/)

Inside Smart Routing
Per PSP, merchant and shop
Configured with our team

All use cases

## Built on Smart Routing, configured with our team.

Each page covers one capability: what it checks, how the rule is set up and the situations PSPs and banks use it for.

[Use case 01 · Smart Routing · Referer Control: know where your payment traffic actually comes from · Most PSPs trust what merchants declare. eComCharge checks what actually arrives. · For PSPs · Acquiring banks · Compliance teams · Explore Referer Control](https://ecomcharge.com/use-cases/referer-control/)

[Use case 02 · Smart Routing · Action Rules: automate what you used to miss · Stop monitoring dashboards. Set the conditions. Let Smart Routing do the rest. · For PSPs · Acquiring banks · Explore Action Rules](https://ecomcharge.com/use-cases/action-rules/)

How it gets set up

## From your policy to working rules.

You describe the policy, the eComCharge team turns it into Smart Routing conditions and actions, and the platform enforces it on live traffic.

**0** Development work on your side. The eComCharge team configures the rules.

**3** Levels a rule can apply to: PSP, merchant and shop.

Step 1

### Describe the policy

Which domains a merchant may use, which limits an acquirer sets, which credentials you want stopped.

Step 2

### We configure the rules

The eComCharge team turns it into Smart Routing conditions and actions, per PSP, merchant or shop.

Step 3

### The platform acts

Alerts, flags, blacklists and limits fire on live traffic, without anyone watching a dashboard.

Case studies

## Want the whole story?

[All case studies](https://ecomcharge.com/case-studies/)

[Case study 01 · iGaming · High-risk · Smart Routing · 3× volume growth without adding infrastructure · A European PSP processing high volumes of recurring traffic had no reliable way to separate primary from secondary traffic. Routing decisions were based on limited data, sensitive MIDs … · 3× · Transaction volume · ↑ · Approval rate · 0 · New MIDs added · Read the case study](https://ecomcharge.com/case-studies/3x-volume-growth/)

[Case study 02 · High-risk · Recurring · Token migration · 95% of tokens migrated in one week, acquirer switch with zero customer impact · A high-risk PSP lost access to their acquiring partner overnight. The question wasn't whether to find a new acquirer. It was whether they could keep their entire recurring … · 95% · Tokens migrated · ~1 week · Full migration · 0 · Payment interruptions · Read the case study](https://ecomcharge.com/case-studies/token-migration-one-week/)

[Case study 03 · Low-risk · Platform stability · Proactive monitoring · Acquirer failure contained in seconds, before a single merchant noticed · eComCharge support spotted an acquirer slowing to 30-second responses on platform monitors and isolated it through the interface in seconds, no outage, no client ticket. · Seconds · Time to isolate · 0 · Downtime · 0 · Merchants affected · Read the case study](https://ecomcharge.com/case-studies/acquirer-failure-contained/)

Use cases

## Have a scenario we have not covered?

Tell us what you need to detect or stop. We will show you how it maps to Smart Routing.

[Talk to us](https://ecomcharge.com/contacts/sales/)
