RevCent

Stop fraud before it reaches your business.

RevCent protects ecommerce businesses with Sentinel Anti-Fraud, RevCent’s free in-house fraud prevention system that evaluates visitors, customers, cards, velocity, order context, and previous fraud intelligence before risky payments reach the processor.

Sentinel Anti-Fraud

Prevent fraud before payment authorization.

Sentinel is RevCent’s in-house anti-fraud system. It runs before the payment is sent to a gateway, so high-risk attempts can be stopped before they create processing fees, gateway pressure, lost inventory, disputes, or damaged merchant history.

1
Checkout attempt
VST-88291 · Card •••• 4242 · $249.00
2
Visitor & IP
IP 198.51.100.42 · New device · Location mismatch
3
Behavior
3 attempts in 42 sec · Session velocity high
4
Payment & history
Card recently changed · No prior fraud match
5
Decision
Evaluate before gateway authorization
Sentinel reviewEvidence builds before authorization
Checkout attempt
Card•••• 4242Order total$249.00
Visitor & IP evidence
Location mismatchDetectedProxyClear
Behavior evidence
Attempt velocity3 in 42 secSession patternHigh
Payment & history evidence
Card changedRecentlyPrior fraud matchNone
Decision outcome
CleanContinue to gatewayFraudBlock before gateway
Multiple Layers

Fraud is stopped at multiple levels.

Fraud rarely shows up as one obvious signal. RevCent evaluates the request from several angles before deciding whether a payment should continue, be blocked, or be reviewed.

Checkout
Request
Bot velocity
IP · velocity · proxy · automation
Visitor
Device mismatch
device · journey · metadata
History
Prior fraud pattern
customer · card · order · fraud history
Gateway
Request levelIs this request safe to evaluate?

Sentinel inspects IP reputation, proxy use, location signals, request velocity, and automation patterns before the checkout reaches deeper payment logic.

Visitor levelDoes this attempt match the visitor?

Device consistency, session behavior, acquisition metadata, and the visitor journey are evaluated together to expose sudden or implausible changes.

History levelDoes this match what we already know?

Customer, card, order, prior decisions, and stored fraud evidence are compared with the current attempt so repeat patterns are recognized immediately.

Suspicious signals are isolated before payment is sent. Each layer catches a different class of fraud while clean attempts continue to the gateway.

Fraud Memory

RevCent remembers previous fraud.

A fraud attempt should make the business smarter. RevCent stores fraud context so previous attacks, suspicious patterns, blocked attempts, and risk signals can influence what happens next.

Every fraud decision becomes reusable context. Fraud Memory connects the evidence from previous attacks to the visitors, payments, customers, and orders involved—then makes that context available when the next attempt arrives.

01 / Evidence retained

What RevCent remembers

Every blocked attempt becomes a connected record of what happened and why. RevCent keeps the decision alongside visitor, payment, and business context, preserving the evidence behind the attack.

Identity and network
Retain visitor, IP, location, proxy, device, browser, and session details from each checkout attempt.
Behavior and timing
Capture velocity, navigation, repeated submissions, field changes, and mismatches in the order they occurred.
Payment and business
Connect card behavior, customer history, products, order value, and earlier fraud outcomes across the business.
02 / Continuous comparison

How future attempts are evaluated

Every new checkout can be compared with earlier evidence before gateway authorization. Sentinel connects visitor, payment, and business signals, revealing repeated patterns that may appear harmless when considered alone.

Recognize returning behavior
Connect new devices, cards, or IPs to visitor patterns already observed in previous fraud attempts.
Find meaningful overlap
Combine similarities across behavior, timing, and payment activity into stronger evidence of repeated fraud.
Use the complete history
Evaluate each checkout alongside earlier decisions, related records, and outcomes for a fuller risk assessment.
03 / Earlier intervention

What happens when fraud returns

When a known pattern returns, RevCent can respond with the supporting evidence already attached. High-confidence fraud can be blocked before gateway authorization, while the latest outcome enriches future decisions.

Stop before the gateway
Reduce authorization fees, processor pressure, artificial decline spikes, and gateway traffic from returning fraud attempts.
Preserve the explanation
Keep matched evidence, decision reasons, and related visitor records available for reporting, support, and review.
Improve the next decision
Attach the latest attempt, its outcome, and new relationships so future protection has richer context.
Card Testing Protection

Stop card testing before it burns your gateway.

Card testers rotate through payment credentials to discover which cards are valid. Sentinel evaluates every attempt within its complete visitor, device, network, session, and checkout context so RevCent can identify the coordinated pattern and stop it before gateway authorization.

RevCent evaluates the testing campaign, not just the individual decline. Card testers rotate payment credentials to discover which cards are valid. Sentinel correlates the activity around those attempts, makes a pre-authorization decision, and stops high-confidence attacks before they consume gateway resources.

Detection

How the pattern is recognized

  1. 01
    Attempt velocity

    Payment attempts accelerate beyond normal customer pacing across a short, connected window.

  2. 02
    Rapid card rotation

    Card numbers change repeatedly while the surrounding checkout behavior remains substantially the same.

  3. 03
    Shared visitor context

    Visitor, device, browser, IP, session, and journey signals connect attempts that appear separate at the card level.

  4. 04
    Failure clustering

    Declines and validation failures accumulate in a pattern that is unlikely to represent independent customers.

  5. 05
    Known attack overlap

    Fraud Memory compares the activity with previous card-testing evidence and related visitor patterns.

Prevention

How RevCent responds

  1. 01
    Evaluate before authorization

    Sentinel reviews the complete attempt before RevCent sends a payment request to the configured gateway.

  2. 02
    Combine related signals

    Several weak indicators can become decisive when velocity, card rotation, failures, and visitor context point to one campaign.

  3. 03
    Block the testing path

    High-confidence card-testing activity can be stopped inside RevCent instead of becoming processor traffic.

  4. 04
    Keep legitimate buyers moving

    A single decline is not treated as an attack by itself, helping normal checkout behavior continue without unnecessary friction.

  5. 05
    Strengthen future decisions

    The evidence and outcome remain connected through Fraud Memory so returning patterns can be recognized earlier.

Continuous protection

Every attempt adds context before any payment is sent.

Protection runs throughout the checkout flow. RevCent continually connects what is happening now with what it has already learned, allowing clean activity to continue while coordinated testing is contained upstream of the processor.

01Observe the sequence

Each attempt is evaluated with the recent activity surrounding the same visitor, device, network, and checkout journey.

02Recognize the campaign

Sentinel connects velocity, rotating cards, repeated failures, and known history into one card-testing pattern.

03Intervene before the gateway

When the combined evidence is decisive, RevCent blocks the attempt before creating an authorization request.

04Retain the intelligence

The signals and decision become reusable fraud context for later attempts, even when the attacker changes a card or device.

Case Studies

Real attacks become better protection.

The value of anti-fraud is not just blocking one suspicious payment. It is reducing processing damage, preserving merchant account health, and turning attack patterns into reusable intelligence.

Case 01

2,500 stolen cards blocked in minutes.

Single card-testing event. Five-minute window. No attempts sent to the processor.

Attack context

Fraudsters rotated approximately 2,500 stolen cards through one connected checkout pattern. Velocity, card changes, shared visitor context, and repeated failures exposed the campaign.

RevCent decision

Sentinel connected the attempts, recognized high-confidence card testing, and blocked the activity before any authorization request was created.

Business protection

The processor remained untouched, unnecessary authorization fees and gateway pressure were avoided, and the attack pattern was retained in Fraud Memory.

Case 02

$360,000 in fraud prevented in one month.

Total prevented amount calculated across one client account. None sent to the processor.

Attack context

Suspicious payment attempts accumulated across the month. Request risk, visitor validation, payment context, customer history, and prior fraud evidence were evaluated together.

RevCent decision

Sentinel identified the combined risk before normal processing and stopped the suspicious payment activity before it could reach the processor.

Business protection

RevCent reduced transaction costs, chargeback exposure, fulfillment risk, and merchant account pressure while preserving the evidence behind each decision.

Protect every payment with Sentinel.

Sentinel evaluates connected request, visitor, payment, customer, order, and historical context before suspicious activity reaches the gateway—giving your business comprehensive protection without treating every decline like fraud.

Evaluate the complete contextConnect velocity, device, IP, visitor behavior, payment changes, business history, and earlier fraud evidence before making a decision.
Stop attacks before authorizationBlock high-confidence fraud and card testing before they create gateway traffic, processing costs, fulfillment risk, or merchant account pressure.
Remember every decisionRetain the evidence and outcome in Fraud Memory so later attempts can be compared with what RevCent has already learned.