White Label
Automate High-Risk Onboarding: Streamline Risky Processes
Learn the best practices to automate high-risk onboarding, reduce security risks, and ensure a smooth, compliant onboarding experience.
-
Solutions
European BanksWhite-label payment infrastructure for acquiring banks
Low-Risk PSPsWhite-label payment gateway for low-risk PSPs
iGaming & Forex PSPsBuilt for high-risk PSPs — full control over your channels
-
Resources
Set up your payment processing system
Platform capability 02
Action Rules: automate what you used to miss
Stop monitoring dashboards. Set the conditions. Let Smart Routing do the rest.
Action RulesConditionsActions
live
Event
Acquirer B cap
Fraud patterncard 4115
Chargeback ratioShop 2 · 1.2%
Rules — evaluated in order
- Cap ≥ 70%Alert PSP
- Fraud patternBlacklist
- Chargebacks > 1%Limit traffic
Action
Alert sent
PSP and account manager, before traffic stops
Credentials blacklisted
Instantly, no manual step
Traffic limited
Shop routed to a capped channel
Watching conditions…
Conditions you can watch
Acquirer capsFraud patternsChargeback ratioDecline spikes
Set once
Rules run at the platform level · no dashboards to watch, no code on the merchant side
Feature
Smart Routing
Example rule
IfProcessing limit reaches 70% of the monthly cap with an acquirer
ThenAutomatic alert to PSP and account manager — time to act before traffic stops
What are Action Rules
Conditions in, automated responses out
Action Rules turn your processing logic into automated responses — alerts, blacklists, rejections — triggered the moment a condition is met. Instead of reacting after something goes wrong, the system acts on your behalf.
Smart Routing is not just about where to send a transaction. It also controls what happens when specific conditions are met.
Action Rules allow PSPs and banks to define triggers — and attach automated responses to them. Instead of monitoring payment flows manually and reacting after something goes wrong, the system acts on their behalf.
Configured at PSP, merchant, or shop level — each account can have its own thresholds.
Available actions
NotifyAlertAutomatic notification to PSP, account manager, or both when a threshold is crossed
BlacklistBlock credentialsPayment credentials added to blacklist instantly — transaction stopped before reaching the bank
RejectDecline at routingTransaction declined at the Smart Routing layer — no manual intervention per transaction
CustomAny actionThe action layer is extensible — new action types built on demand by the eComCharge team
Scenario 1 · Limit alerts
Don’t let a promotion kill your traffic
Some acquiring partners set hard monthly limits — for example, no more than €100,000 processed per month. When the limit is reached, traffic stops automatically.
LimitsAcquirersAlerts
live
Acquirer B · monthly cap €100,000
Alert at 70%
€71,000 processedthreshold 70%€100,000
For most PSPs, this limit is invisible until it’s too late. A flash sale, a long billing month, or an unexpected spike in volume — and suddenly transactions are being declined. By the time the team notices, revenue has already been lost.
The fix is not complicated. But it requires knowing the limit is about to be hit before it happens — not after.
With a Smart Routing action rule, the PSP sets a notification threshold at, say, 70% of the limit. When that threshold is crossed, an automatic alert goes to the PSP and their account manager: “Rule X is approaching its limit — please take action.” Raising the limit in the system takes seconds. Getting approval from the acquiring bank takes longer — which is exactly why early warning matters.
Who uses this: PSPs and banks operating under hard monthly volume limits set by acquiring partners — especially relevant during promotional periods or high-traffic months.
Scenario 2 · Auto blacklist
Stop 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 fine.
BlacklistPatternsLog
live
Pattern match · card 4115
Blacklisted
Banks don’t always have the tools to catch this automatically. They receive the signal from the payment network, identify the pattern, and then need a way to act on it — fast, and without manual intervention for every transaction.
Manual response takes time — pattern identified, team notified, action taken. By then, more violations have occurred and a fine is likely.
With a Smart Routing action rule, the bank defines the condition: if a transaction matches this pattern, automatically add the payment data to the blacklist. From that point, any transaction with those credentials is stopped before it reaches the bank — and before it generates another network penalty. This is not a fraud prevention system in the traditional sense. It is a precise, configurable response to a known pattern.
Who uses this: banks that have received warnings from Visa or Mastercard for processing transactions with fraudulent data, and need an automated way to enforce exclusions going forward.
When Action Rules become critical
Three moments where waiting costs money
1 · End of month
Limit spikes
Monthly processing limits are often set conservatively. When volume unexpectedly accelerates — a promotion, a seasonal peak — limits get hit without warning. The PSP finds out when traffic stops. An alert at 70% gives a window to act.
2 · Fraud patterns
Response speed
MPS penalty frameworks work on a timeline: pattern detected → warning issued → fine if not resolved. Manual monitoring rarely catches the pattern before the warning. Action Rules close that gap — the blacklist fires at the moment of detection, not after someone reviews a report.
3 · Many merchants
Many risk profiles
A PSP managing dozens of merchants cannot monitor each one manually. Action Rules run at the merchant or shop level — each account can have its own thresholds and triggers, managed centrally.
How PSPs use this in practice
Four ways the rules earn their keep
- Limit management
- PSPs with multiple acquiring relationships set separate alert thresholds per acquirer — so they always know which channel is approaching capacity before traffic is disrupted.
- Fraud containment
- Banks use Action Rules to respond to fraud patterns faster than any manual process allows. When a card or IP matches a known pattern, the blacklist fires immediately — before the transaction reaches the acquiring bank.
- Merchant-level risk
- PSPs with varied merchant portfolios configure Action Rules at the individual merchant level — each with its own thresholds based on that merchant’s volume, risk profile, and acquirer relationship.
- Compliance automation
- In markets where specific transaction types require monitoring, Action Rules provide an automated audit trail — every triggered action is logged with the transaction that caused it.
Why this matters for you
Instead of monitoring dashboards and reacting, the system acts on your behalf — at the moment a condition is met, not hours later. Banks in regulated markets use this specifically for fraud pattern responses where manual reaction is too slow to avoid MPS penalties.
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.