Real Time Monitoring & Blocking

Real Time Monitoring and Blocking helps you detect and block fraud in real time as an easy, no-code solution. Once enabled, Real Time Monitoring & Blocking (RTM) monitors every transaction as it happens, helping stop fraud attempts while keeping payments smooth for your customers.

RTM is built directly into the TabaPay platform, giving you strong protection without the cost or complexity of separate systems.

TabaPay also offers the most accurate and secure card-level controls in the industry. Our technology links every version of a card across tokens, wallets, and reissues so your rules stay consistent and reliable. This is powered by Payment Account Reference (PAR), a network-standard identifier that provides full card-level visibility without exposing sensitive data.

Request to enable at TabaPay Support or [email protected].

Use Cases

  • Decrease fraudulent Chargebacks: Block transactions that from chargeback or fraudulent risk signals
  • Help Avoid Account Funding Scams: Monitor card velocity, card limits, and transaction limits leading to load funds into accounts with a rapid cash-out.
  • Block brute force attacks or low-value fraud: Stop fraudsters from testing stolen cards, or detect fraud designed to blend in over time.

Why RTM?

  • Leverage risk signals from tens of millions of cards and >2MM daily transactions to expand detection and mitigation. If a card is new to you, we have likely seen it before and can help stop fraud before it starts.
  • Use PAR for precise and secure card-level controls to ensure unique identification without exposing sensitive data.
  • Use templatized rules based on velocities and limits so you can operate within your risk tolerances.
  • Fast and seamless integration captures data in days, not months.
  • Designed to scale with you as we grow together.

How RTM Works

TabaPay provides multiple layers of protection that combine your business knowledge with the strength of TabaPay’s global fraud intelligence network.

Sources of Data

The RTM layered system protects against fraud at three levels, each powered by different sources of data:

  • Client Proprietary Data: You configure protection based on your own knowledge. This includes unique, non-payment data such as internal customer risk scores, loyalty status, or user IDs that help inform transaction decisions.
  • Client Transactional Data: TabaPay analyzes your transaction data to identify risk patterns unique to your business.
  • TabaPay Global Intelligence: Our global network insights leverage data patterns observed across millions of transactions to detect and stop fraud before it reaches you.

RTM Data Flow

RTM works seamlessly within the TabaPay platform and does not require any additional API calls. Once you enable RTM, transaction data automatically flows into TabaPay’s built-in real-time system, which makes block or flag decisions instantly without adding latency.

  1. Customer initiates a payment.
  2. You send a Create Transaction API request to TabaPay.
  3. Real-time decisioning and monitoring: ACCEPTED, REJECTED, or IN_REVIEW (shadow mode only)
  4. If Rejected Transaction is blocked. If Accepted, transaction is sent to the network.
  5. Network returns with a network success, or error.
  6. TabaPay returns the API response.
  7. You display the relevant confirmation to the customer.

Optionally, you can include your proprietary data (such as internal customer risk scores, loyalty status, or user IDs) in the Create Transaction API. RTM will use this information to apply your configured rules and make more informed and precise decisions.

Out-of-the-Box Rules

TabaPay provides ready-to-use rules that you can enable and configure directly. Use the following table to understand which rules you can control, the data they rely on, and how they protect you.

Configurable Controls

You configure the risk controls based on your business knowledge, transaction patterns, and risk tolerance.

Rule NameRule LogicClient ControlActionExample
Card VelocityBlock/flag transactions when a card exceeds an allowed number of transactions within a set timeframe.Define number and time window (1/3/7/30 days).Block/FlagBlock if > 3 pushes in 1 day
Card LimitBlock/flag transactions when a card exceeds a set daily or weekly total amount.Set total amount and time window (1/3/7/30 days).Block/FlagBlock if total daily pulls > $1,000
Per-Transaction LimitBlock/flag any single transaction above a defined amount.Define per-transaction maximum.Block/FlagBlock if amount > $3,000
Client-Level LimitBlock/flag activity when total transactions across all cards exceed a set limit.Set total amount and time window (1/3/7/30 days).Block/FlagBlock if daily total amount > $100K
Card ListBlock/flag transactions from cards in the uploaded list.Upload or edit list of cards (PARs).Block/FlagBlock Card (PAR) 1xd23kxkans32903
BIN ListBlock/flag transactions from BINs in the uploaded list.Upload or edit list of BINs.Block/FlagBlock BIN 123456
Velocity, limits based on your data.Block or flag transactions based on velocity, limit, or list rules, but use your own proprietary data (such as user ID, device ID, etc.).Upload custom propriety list of cards, BINs, etc..Block/FlagBlock if a client user ID has > 3 pushes in 1 day

Client Intelligence Rules

Rules powered by TabaPay’s analytics on your own transaction data, identifying risk patterns within your ecosystem.

Rule NameRule TriggerClient ControlActionExample
Excessive RetriesBlock/flag transactions from cards that repeatedly fail or are declined and the number of retries exceeds network requirements.Toggle on/offBlock/FlagBlock if card has more than 10 declines with MasterCard within a calendar day.
Same Card, Multiple NamesBlock/flag transactions from cards used under multiple customer names within a set period.Adjust name thresholdBlock/FlagFlag if card used by > 3 names in 30 days.
AVS MismatchBlock/flag transactions from cards that have previously received a negative AVS mismatchToggle on/offBlock/FlagBlock if AVS code = N(address mismatch).

More details about excessive retries rules: Excessive Retry Rules.

Global Intelligence Rules

The most powerful layer: powered by TabaPay’s global network data across all merchants. These rules block known fraud before it reaches you.

Rule NameRule TriggerClient ControlActionExample
Global Chargeback SignalsBlock/flag transactions from cards that previously caused fraud chargebacks with any TabaPay merchant.Toggle on/offBlock/FlagCard automatically blocked after prior chargeback
Global Fraud SignalsBlock/flag transactions from cards reported as fraudulent by other merchants or networks.Toggle on/offBlock/FlagCard automatically blocked after fraud report
Smarter Card Identification with PAR

Identifying cards accurately is critical for fraud prevention. However, using full card numbers creates security and compliance risk, while using only partial digits can’t uniquely identify a card when tokens or reissued cards are involved.

TabaPay solves this with Payment Account Reference (PAR), a secure, persistent identifier that links all versions of a card across networks and tokens. PAR ties back to the PAN and all its associated tokens, whether the transaction was made via the original card number or via a token (Apple Pay, Google Pay, network token, etc.). This means:

  • You can apply rules at the “card level” (velocity, limits, block lists) using PAR, without needing to store the actual PAN.

  • You preserve uniqueness across tokens. Even if a user switches from using a token to a physical card or vice versa, the PAR remains the same.

  • You minimize PCI/PII risk. You never expose or store raw PANs, but still maintain full card-level visibility.

TabaPay is the first in the industry to offer this capability, delivering the most accurate and secure card-level controls available today.