Referer Control: know where your payment traffic actually comes from
Most PSPs trust what merchants declare. eComCharge checks what actually arrives.
Smart Routing / Referer Control
Merchant A
Declared domain: casino-a.com| Referring domain | Response |
|---|---|
| casino-a.com | Processed |
| casino-a-bonus.net | Flag & tag |
| lucky-spins.io | Alert |
Referer Control on one screen
- In declared listProcess
- Mirror patternFlag for review
- UndeclaredAlert PSP
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.
Referer Control / Casino A
| Referring domain | Declared | Rule |
|---|---|---|
| casino-a.com | Yes | Process |
| casino-a-bonus.net | No | Flag for review |
| lucky-spins.io | No | Alert PSP |
Without referer tracking, the mismatch only surfaces during an audit, or when an acquirer raises a question.
The gap most platforms missA merchant registers one domain
In practice they may run subdomains, mirror sites or parallel storefronts that were never disclosed.
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.
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.
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.
Customer opens checkout
The browser records where the customer came from.
Platform captures domain
Recorded per transaction and available in Smart Routing.
Compared to declared
Does the domain match what the merchant registered?
Rule triggered
Mismatch detected, the configured action fires automatically.
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.
Referer Control / Settings
Declared domainsNotify, don’t block
The transaction is processed, the PSP and account manager are informed.
Process and tag for review
Visibility for compliance without blocking legitimate traffic.
Reject specific domains
Rejected at the routing layer, no manual step per transaction.
Track volume by domain
Patterns of undeclared traffic surface over time, for proactive merchant conversations.
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.
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.
Portfolio-wide monitoring
Declared domains are registered at onboarding. Traffic from outside the declaration triggers an alert.
Transparency with acquirers
Acquirers increasingly ask how PSPs validate traffic sources. This is a concrete, demonstrable answer.
One more review signal
Supports merchant reviews alongside transaction data, not as a standalone audit tool.
Portfolio monitoring
Periodic checks find merchants whose traffic sources differ from onboarding.
Acquirer due diligence
Domain-level visibility shown when applying for new acquiring relationships.
Incident response
A documented transaction-level trail when a merchant account is flagged.
Ongoing verification
New merchants watched for 30 to 90 days before risk limits are raised.
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.
Where it’s used
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 rate0 New MIDs added Read the case studySee it on your own traffic.
We configure the rules with you in Smart Routing. Tell us about your merchants and acquirers.