Action Rules: automate what you used to miss
Stop monitoring dashboards. Set the conditions. Let Smart Routing do the rest.
Smart Routing / Action Rules
Action Rules
Merchant and shop level| When | Then |
|---|---|
| Monthly cap reaches 70% | Alert PSP and account manager |
| Fraudulent credentials detected | Add to blacklist |
| Volume spike on one shop | Limit traffic |
Action Rules on one screen
- Cap ≥ 70%Alert PSP
- Fraud patternBlacklist
- Chargebacks > 1%Limit traffic
Conditions in, automated responses out.
Smart Routing is not just about where to send a transaction. It also controls what happens when specific conditions are met.
Action Rules let PSPs and banks define triggers and attach automated responses to them: alerts, blacklists, rejections. Instead of monitoring payment flows and reacting after something goes wrong, the system acts on their behalf. Each PSP, merchant or shop can have its own thresholds.
Smart Routing / Action Rules
| Condition | Action | Active |
|---|---|---|
| Acquirer cap ≥ 70% | Alert | |
| Known fraud pattern | Blacklist | |
| Chargebacks > 1% | Limit traffic | |
| Decline spike | Reject |
Alert
Automatic notification to the PSP, the account manager or both when a threshold is crossed.
Block credentials
Payment credentials blacklisted instantly, the transaction stopped before it reaches the bank.
Decline at routing
Declined at the Smart Routing layer, with no manual step per transaction.
Any action
The action layer is extensible: new action types built on demand by the eComCharge team.
Don’t let a promotion kill your traffic.
Some acquiring partners set hard monthly limits, for example no more than €100,000 a month. When the limit is reached, traffic stops automatically.
For most PSPs this limit is invisible until it’s too late. A flash sale, a long billing month or a spike in volume, and transactions are suddenly declined.
“Rule X is approaching its limit, please take action.”
The alert at 70% of the cap, sent to the PSP and the account managerStop fraud before the fine arrives.
Payment networks monitor the quality of traffic that acquiring banks send them. When a bank submits transactions with obviously fraudulent data (stolen cards, known fraud patterns, flagged credentials), the network issues a warning or a fine.
This is not a fraud prevention system in the traditional sense. It is a precise, configurable response to a known pattern.
- Signal from the network
- Pattern identified, team notified
- More violations meanwhile, a fine is likely
- Condition: the transaction matches the pattern
- Credentials added to the blacklist automatically
- Next attempt stopped before the bank
Three moments where waiting costs money.
Instead of monitoring dashboards and reacting, the system acts at the moment a condition is met, not hours later. Banks in regulated markets use this for fraud pattern responses where manual reaction is too slow to avoid MPS penalties.
Limit spikes
Limits are often set conservatively. A promotion or a seasonal peak hits them without warning; an alert at 70% gives a window to act.
Response speed
Pattern detected, warning issued, fine if not resolved. The blacklist fires at the moment of detection, not after someone reviews a report.
Many risk profiles
Dozens of merchants cannot be monitored manually. Rules run per merchant or shop, each with its own thresholds, managed centrally.
Four ways the rules earn their keep.
Every triggered action is logged with the transaction that caused it, so the rules double as an audit trail.
Limit management
Separate alert thresholds per acquirer, so the PSP knows which channel is approaching capacity before traffic is disrupted.
Fraud containment
When a card or IP matches a known pattern, the blacklist fires before the transaction reaches the acquiring bank.
Merchant-level risk
Thresholds per merchant, based on its volume, risk profile and acquirer relationship.
Compliance automation
Where transaction types require monitoring, every triggered action is logged with its transaction.
Action Rules: FAQ
Yes. Action Rules are configured at the PSP, merchant, or shop level. Each account can have its own thresholds, triggers, and response actions, all managed centrally from the back-office.
Immediately: at the moment the transaction is evaluated by Smart Routing. There is no delay between the condition being met and the action being executed.
No. The eComCharge team configures Action Rules based on your business logic; you describe what you need, we build it. No self-service configuration required, no development work on your side.
Smart Routing rules determine where a transaction goes, which acquirer, which channel. Action Rules determine what happens when a condition is met: alert, blacklist, reject. Both run inside the same Smart Routing engine and can be combined.
Where it’s used
See it on your own traffic.
We configure the rules with you in Smart Routing. Tell us about your merchants and acquirers.