AML Compliance
Customer and payment screening, transaction monitoring and investigation workflows.
Supplier popularity85%By Flagright
Flagright Transaction Monitoring
Configurable transaction and activity rules with historical tests, live shadow feeds and risk-based thresholds.
The offering
What Flagright Transaction Monitoring does
Flagright Transaction Monitoring applies configurable rules and ML anomaly detection to supplied events. Teams can create logic in the interface or generate a reviewable starting rule from a natural-language description. The documented testing sequence includes historical backtesting, live shadow mode and a controlled move into production. Real-time, post-processing and scheduled batch modes serve different operational flows.
For gambling, define how deposits, withdrawals, betting and gameplay map to players and products. Example monitoring patterns include minimal play before withdrawal, structuring across products and sudden behavioural changes. Set market, currency and risk-band thresholds, then review alerts with their source evidence. A rule or model can surface suspicious activity; AML conclusions, player-protection interpretation and permission to block a transaction remain part of the operator’s policy and integrated workflow.
Who should explore it?
Operator compliance teams testing and maintaining event-based AML scenarios across cashier and gambling activity.
- Test a minimal-play deposit/withdrawal scenario before production
- Investigate activity split across casino and sportsbook products
Documented capabilities
- No-code and assisted rule creation
- Historical simulations and live shadow mode
- Real-time, batch and post-processing modes
- Risk-band threshold selection
- Rule versions and rollback
Reported in the linked public sources. We have not independently tested these capabilities.
Product details
- Monitoring job
- Transaction/activity detection rules and anomaly alerts for financial-crime review.Source
- Gaming evidence
- Deposits, withdrawals, stakes and casino activity; rules may differ by market, currency and product.Source
- Rule controls
- Configured logic plus ML anomaly detectors; current risk scores can select the threshold assigned to a risk band.Source
- Processing modes
- Real-time events, post-processing, scheduled batches and historical transaction reprocessing.Source
- Testing and release
- Historical backtesting and private live shadow alerts precede production; versions and rollback support change control.Source
Delivery & commercial details
- Delivery & integration
- Supply the required player and transaction/activity events, map them to the monitoring schema and define alert or control responses. Use simulations and shadow mode to validate the configured rules before activation.Source
- Pricing
- Request a scoped proposal covering event volume, monitoring modes, environments, implementation, case workflows and any separately enabled AI or filing functionality.
Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.
Buyer questions, answered
What is the difference between shadow mode and production?
A shadow rule observes live transactions and generates a private alert feed outside the analyst queue. The team can assess its effect before deliberately moving it into production.
SourceCan the same rule use different customer-risk thresholds?
The product describes reading the customer’s current risk score and applying the configured threshold for that risk band. Define how the score is supplied and approve the bands before enabling the rule.
Source