Frequently asked questions

Short answers to the questions we hear most. For anything not here, reach us at alex@detecthebet.com.

Is it an API?

No. We do not connect to your systems and you give us no access. You receive a signed file you verify and check against inside your own environment. There is no service to call during authorization, and if we went offline your block keeps working on the last release you verified.

Do you see our customers' data?

No. In normal operation the feed flows one way and no transaction, personal, or cardholder data reaches us. The free assessment runs inside your environment by default, so we see nothing there either. The only exception is the optional extract path, where you may send an anonymized export that is processed locally and where personal data is refused and deleted at intake.

Do we have to send you anything to see the gap?

No. The default is the assessment kit: your analyst runs one command on your own machines against your own export. A bundled dry run proves the pipeline in about a minute, the feed signature is verified before every load, and you choose what, if anything, to share back. The aggregate summary is enough for the follow-up conversation.

How is this different from the merchant controls we already have?

Your control is only as good as the merchant identity beneath it. A standard block reads a category code, and disguised gambling is coded under the wrong one. We are the layer that identifies who the merchant really is, so your existing control catches what it is missing.

What does it cost?

The coverage assessment is free. The subscription covers the signed feed plus continuous assurance: coverage monitoring, alerts when newly discovered exposure appears, and release-by-release evidence for risk and product reviews. It is priced per active protected account; we discuss the specifics directly. You see the gap on your own data before there is any commitment.

How often is it updated?

On a regular cadence. New releases are data, not code, so applying an update is a verify-and-load step with nothing to redeploy. Each release comes with a plain-language summary of what changed.

What languages does it support?

The feed is plain, signed JSON, so you can match against it in any language. We provide a dependency-free reference client and can supply a port or a thin local component if you prefer.

Is it secure?

Yes, and in a low-surface way: we never receive your data, the feed is verified on your side and fails closed, and the software has no third-party dependencies. See Security and ask for the diligence pack under NDA.

Do you name banks publicly?

No. Anything we find about a specific institution stays private so it can be addressed quietly. Public attention points at gambling operators, never at the banks we work with.

Who is it for?

Any bank or card program that offers a gambling block, starting with teen and family programs where the promise of safe spending is loudest and the gap is most provable.

How long does integration take?

Hours, not a project. It is one lookup added to the authorization step you already run, plus a refresh you wire once. See How it works.