Overview

Detect The Bet is the merchant-intelligence and control-assurance layer for gambling payments. We give you a verified, always-current list of the gambling merchants that hide behind ordinary category codes, and you check transactions against it inside your own systems. The result is a gambling control you can show works, not just one that exists. Your customer data never reaches us.

The delivery model

The feed is published to you, not connected to you. We maintain the intelligence and sign every release; you verify it against a key you hold and run the checks entirely inside your own environment. There is no integration into your systems, no service in your transaction path, and no data flowing back to us.

The problem we solve

A standard gambling block reads a merchant's category code. But the fastest-growing gambling merchants (sweepstakes casinos, pick'em apps, offshore books) bill under ordinary codes like games and retail, so a category-based block never sees them. Your control is only as good as the merchant identity beneath it. We supply that identity.

What you get

• A signed merchant feed. Each merchant carries a recommendation (block or review) and a decision record: how confident we are, the strength of the evidence, a plain-language reason, and when it was last reviewed. Enough for your compliance team to defend any decision.
• Behavioral signals (review only). Beyond matching merchants, we surface gambling-shaped spending patterns for a human to review. These never decline a transaction on their own.
• A reference client. A small, dependency-free library your engineers drop into your existing authorization step. Integration is measured in hours, not a project.
• An assurance record. Every release carries a plain-language summary of what changed and why, and your verification log accumulates into evidence a risk committee can use: what the control covered, what it caught, what you knew, and when you acted.

What you keep and control

You keep all customer data and you make every final decision. You choose which categories apply, what each recommendation maps to (block, review, allow), and which confidence levels act automatically versus queue for review. We identify and characterize the activity; you set the policy.

How a rollout goes

• 1. Free coverage assessment. Your analyst runs our signed kit on your own past transactions, on your own machines, with one command. You see exactly what your current block is missing, and nothing leaves your environment.
• 2. Shadow mode. Run the feed in log-only mode. It records what it would have caught, with zero customer impact, so you can measure the effect before enforcing anything.
• 3. Production. Turn on enforcement for the merchant feed. Behavioral signals stay review-only by design.
• 4. Continuous assurance. Stay covered and stay able to show it: release-by-release change summaries, alerts when newly discovered exposure appears, and a running evidence record for risk and product reviews.

Next

See How it works for the three-step integration: verify the signature, make one lookup per transaction, and stay current automatically.