---
title: "SmartCheck: historical payment signals for Smart Routing"
description: "Signals from anonymized transactional history across PSPs on the eComCharge platform, used as conditions in Smart Routing rules."
url: "https://ecomcharge.com/platform/smartcheck/"
lang: "en"
image: "https://ecomcharge.com/static/assets/img/og-default.859636851186.png"
breadcrumbs: "Home > Platform > SmartCheck"
---

SmartCheck

# Give every payment more context.

SmartCheck provides signals derived from anonymized transactional history across PSPs processing payments on the eComCharge platform. Use them as conditions in Smart Routing.

[Request a demo](https://ecomcharge.com/contacts/sales/)
[Read the documentation](https://help.ecomcharge.com/en/knowledge-base/pspbackoffice-smart-check)

Up to 365 days of history per card
Your PSP or the whole platform
Conditions in Smart Routing rules

What SmartCheck is

## Payment history from across the platform, inside every rule.

SmartCheck collects the type and final status of every card transaction and keeps them for up to 365 days. Depending on the shop settings, your rules read the history of your own PSP (Local DB) or of all PSPs on the platform (Global DB).

Anonymized transactional history
Across PSPs on the eComCharge platform

SmartCheck
Provides historical signals

Historical signals

Current transaction
Transaction data

Smart Routing
Applies your processing rules

More context

## Look beyond the current transaction.

Two payments can look similar based on current transaction data while their previous payment behaviour is different. SmartCheck brings that historical context into your processing rules.

Transaction A

Amount
:   €120

Currency
:   EUR

Issuer country
:   Germany

Transaction B

Amount
:   €120

Currency
:   EUR

Issuer country
:   Germany

SmartCheck
Adds historical context

Transaction A history
No chargebacks within the defined period

Transaction B history
Repeated payment failures

Traffic segmentation

## Separate primary traffic from established traffic.

Use SmartCheck historical signals as conditions in Smart Routing to separate primary traffic from transactions with an established payment history and route the flows through different processing channels.

Keep primary traffic separate from processing channels used for transactions with an established payment history.

Transaction

SmartCheck

Historical parameter
Number of successful transactions per card

Smart Routing
Applies your traffic segmentation rules

Primary traffic
No established payment history

Processing channel A

Secondary traffic
Established payment history

Processing channel B

**SmartCheck** provides the historical signals. **Smart Routing** defines how the traffic is segmented and where it is sent.

More ways to use SmartCheck

## Use payment history beyond traffic segmentation.

SmartCheck historical signals can also be used as conditions in Smart Routing rules to control authentication and transaction processing.

Authenticate

SmartCheck signal
No chargebacks in the defined period

Smart Routing rule

Skip 3DS

Control

SmartCheck signal
Repeated payment failures

Smart Routing rule

Reject

These are just two examples. Explore more SmartCheck parameters and rule scenarios in our Knowledge Base.

[Explore SmartCheck documentation](https://help.ecomcharge.com/en/knowledge-base/pspbackoffice-smart-check)

SmartCheck

## Bring payment history into your processing decisions.

Use SmartCheck historical signals together with Smart Routing to build processing rules around previous payment behaviour, not only the transaction in front of you.

[Request a demo](https://ecomcharge.com/contacts/sales/)
[Contact us](https://ecomcharge.com/contacts/)

Current transaction

SmartCheck
Historical signals

Smart Routing

Processing decision
