EcomCharge
Get started Get started
Smart Routing

Control the payment decision, not just the route.

Route transactions, configure antifraud logic and control 3DS from one rules engine built into your payment processing flow. Apply different rules across your PSP, merchants and shops.

Request a demo Explore documentation
Transaction
€120 EUR Visa Germany Merchant A
eComCharge
Smart Routing
Rule inputs Transaction data Payment history Processing conditions
RouteWhere should it go?
Choose the processing connection.
ProtectShould it proceed?
Apply antifraud rules and actions.
AuthenticateDoes it need 3DS?
Force or skip 3DS according to your rules.
Rule inputs Transaction data Payment history Processing conditions
One engine

One transaction. Three decisions.

Routing is only one part of the processing logic. Smart Routing can determine where a transaction goes, how it is assessed and whether it requires 3DS.

Its rules can use current transaction data, merchant context, payment history and processing conditions.

One rules layer. Multiple processing decisions.

Transaction
eComCharge
Smart Routing
RoutingProcessing connection
Gateway
AntifraudTransaction assessment
Allow / Review / Reject
3DSAuthentication decision
Force / Skip
What can inform the rule
Transaction data
Merchant context
Payment history / SmartCheck
Processing conditions
Your rules

Turn your processing policy into rules.

Start with a simple routing condition or combine transaction data, merchant context, risk signals and payment history into more specific processing logic.

Routing
IF
  • MerchantMerchant A
  • CurrencyEUR
  • Issuer countryGermany
THEN
Route to Gateway A
Antifraud
IF
  • Repeated payment failures detected
THEN
Reject
Authentication
IF
  • No chargebacks within the defined period
THEN
Skip 3DS
Processing control
IF
  • Weekly processing reaches 85% of the defined limit
THEN
Notify

The rule can be simple. The processing logic does not have to be.

Antifraud

Build your antifraud logic into payment processing.

Smart Routing brings transaction assessment and antifraud rules into the same processing logic used for routing and authentication.

Define the conditions that trigger an antifraud rule and the action to take when those conditions are met.

SmartCheck history can also be used as a condition, bringing previous chargebacks and failed transactions into the decision.

Example conditions
  • Repeated payment failures
  • Bank response codes
  • Transaction conditions
  • Referer URI (Payment Widget)
  • SmartCheck history
Antifraud
rule
Rule actions
  • Allow
  • Review
  • Reject
  • Notify
Example scenario: bank response code
Specified bank response codes
Add to Black List
Example scenario: unapproved Referer URI
Unapproved Referer URI (Payment Widget)
Notify or block
Portfolio-level control

One platform does not mean one processing policy.

Different merchants and shops can have different acquiring relationships, risk requirements and processing conditions. Configure Smart Routing logic at PSP, merchant or individual shop level.

Keep one processing infrastructure without forcing every merchant to follow the same rules.

PSP
Merchant A
Shop A1
Route to Gateway ASkip 3DS
Merchant B
Shop B1
Route to Gateway BReview
One processing infrastructure | Different processing logic
More context for every rule

Look beyond the transaction in front of you.

Not every processing decision should depend only on the current payment. Smart Routing can use historical payment behaviour and accumulated processing data as part of its rules.

Use previous payment behaviour

Bring SmartCheck signals such as chargeback and failed-transaction history into Smart Routing conditions.

Repeated payment failures
SmartCheck history
Smart Routing rule
Reject
No chargebacks within the defined period
SmartCheck history
Smart Routing rule
Skip 3DS

Use accumulated processing data

Create rules around accumulated processing volumes and trigger notifications at defined thresholds.

Gateway A Weekly processing limit€10,000 Processed€8,500
85% threshold reached
Notify

Control traffic distribution

Use weights to control how eligible transactions are distributed between available processing connections.

Eligible traffic
Weighted distribution
Gateway A
Gateway B
Gateway C
Rule configuration

Change the rule, not the integration.

A new merchant. A different routing condition. A new antifraud rule. A change in 3DS logic or processing limits.

Update the processing logic centrally in Smart Routing instead of hard-coding it into individual merchant integrations.

Explore Smart Routing documentation
Smart Routing rule editor in the eComCharge Back Office: a pattern, four conditions and the Reject action
Rule configuration in the Back Office · from the Smart Routing guides
Smart Routing capabilities

Go deeper into the rules engine.

Explore additional Smart Routing controls and processing scenarios for more specific requirements.

Antifraud & risk

Processing control

Authentication

Operations & analysis

Works alongside
SmartCheck
Cascading
3DS Server & MPI

Your traffic.
Your rules.

Your merchants, acquiring relationships, risk policies and processing constraints are specific to your business. Your processing logic should be too.

Bring us your routing, antifraud or processing challenge. We will show you how it can be handled with Smart Routing.

Request a demo
Your traffic
Your rules
Smart Routing