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.

Built on Smart Routing PSPs · Acquiring banks · Compliance teams Configured by the eComCharge team
Inside Smart Routing

Referer Control on one screen

Referer ControlDeclared domainsRules
Incoming transaction
Referer check
Merchant
Casino A
Referer
casino-a.com
Declared
casino-a.com
Amount
€120.00
casino-a-bonus.net€85.00 · DE lucky-spins.io€300.00 · PL
Rules: evaluated in order
  • In declared listProcess
  • Mirror patternFlag for review
  • UndeclaredAlert PSP
Action
Processed Referer matches a declared domain
Flagged for review Tagged for the compliance team
Alert sent PSP and account manager notified
Checking the referring domain…
What you can do
AlertFlag & tagBlockRoute elsewhere
Captured at checkout The browser records where the customer came from · available in Smart Routing rules in real time
Works with
Smart Routing
For
PSPs · Acquiring banks · Compliance teams
Setup
Configured by the eComCharge team
Feature Smart Routing The gap most platforms miss
Standard approachPSP trusts what the merchant declares at onboarding, no way to verify actual traffic sources at the transaction level
With Referer ControlEvery transaction carries the referring domain, visible in Smart Routing rules, actionable in real time
Why this matters

One declared domain. Several real ones.

When a customer opens a checkout page, the browser records where they came from: the domain that sent them there. The platform captures this and makes it available inside Smart Routing rules.

PSPs and banks can verify in real time whether transactions come from the domains their merchants declared, and act on any mismatch automatically.

Traffic by referring domain

Without referer tracking, the mismatch only surfaces during an audit, or when an acquirer raises a question.

The gap most platforms miss
With Referer ControlEvery transaction carries the referring domain, visible in Smart Routing rules and actionable in real time.
Undisclosed storefronts

A merchant registers one domain

In practice they may run subdomains, mirror sites or parallel storefronts that were never disclosed.

Not always fraud

Regional versions nobody registered

Some are honest expansions. Others route traffic that would not pass a compliance check: grey-market products, unlicensed services, look-alike mirrors.

No visibility

The mismatch surfaces at the audit

Neither the PSP nor the bank sees it: transactions arrive and get processed. With Referer Control it surfaces per transaction, immediately.

How it works

Captured at checkout, compared in real time.

When a customer arrives at the payment page, the platform captures the referring domain. Smart Routing then compares it against the domains registered for that merchant.

Step 1

Customer opens checkout

The browser records where the customer came from.

Step 2

Platform captures domain

Recorded per transaction and available in Smart Routing.

Step 3

Compared to declared

Does the domain match what the merchant registered?

Step 4

Rule triggered

Mismatch detected, the configured action fires automatically.

What you can do

Four responses, configured per merchant.

Rules and alerts are configured by the eComCharge team based on the PSP’s or bank’s compliance requirements. One merchant can be set to Alert, another to Block.

Alert

Notify, don’t block

The transaction is processed, the PSP and account manager are informed.

Flag

Process and tag for review

Visibility for compliance without blocking legitimate traffic.

Block

Reject specific domains

Rejected at the routing layer, no manual step per transaction.

Monitor

Track volume by domain

Patterns of undeclared traffic surface over time, for proactive merchant conversations.

A real example

Three domains nobody declared.

During traffic analysis on the platform, a merchant registered under one domain was generating transactions from three additional subdomains and regional variants of its site. The merchant was not blocked, but the PSP now had visibility it didn’t have before, and could talk to the merchant about its actual traffic setup.

1 Declared domain, registered at onboarding.
+3 Undeclared variants: subdomains and regional versions found in traffic.
0 Blocked. Visibility first, a conversation with the merchant second.
Who uses this and how

Banks, PSPs and compliance teams.

Referer data comes from browser sessions and reflects the domain visible at checkout. It is not a fraud prevention system and can be circumvented by sophisticated actors. Its value is transparency and early detection of undeclared traffic sources.

Banks

Portfolio-wide monitoring

Declared domains are registered at onboarding. Traffic from outside the declaration triggers an alert.

PSPs

Transparency with acquirers

Acquirers increasingly ask how PSPs validate traffic sources. This is a concrete, demonstrable answer.

Compliance teams

One more review signal

Supports merchant reviews alongside transaction data, not as a standalone audit tool.

In practice

Portfolio monitoring

Periodic checks find merchants whose traffic sources differ from onboarding.

In practice

Acquirer due diligence

Domain-level visibility shown when applying for new acquiring relationships.

In practice

Incident response

A documented transaction-level trail when a merchant account is flagged.

In practice

Ongoing verification

New merchants watched for 30 to 90 days before risk limits are raised.

When to enable Referer Control
Merchants with multiple storefronts Acquirers require traffic source transparency Domain compliance in the onboarding agreement Grey-market or mirror-site risk in the vertical

Referer Control: FAQ

No. Referer Control works at the platform level. Merchants don't need to integrate or configure anything. You see the data. You decide what to do with it.

Yes. Rules are configured at the merchant or shop level. One merchant can be set to Alert, another to Block, depending on their risk profile and your relationship with their acquirer.

You can whitelist known domains per merchant. Referer Control only flags domains that aren't in the declared list, so legitimate multi-domain merchants won't generate false alerts once their domains are registered.

Referer Control captures the referring domain from the browser at checkout. It applies to card payments processed through the eComCharge checkout, where the browser initiates the session.

Referer Control

See it on your own traffic.

We configure the rules with you in Smart Routing. Tell us about your merchants and acquirers.