FAQs

❓ What is the sCCF API?

The Suggested Customer Confidence Factor (sCCF) API provides machine-generated confidence scores for customers, shops, and terminals based on behavioural patterns observed in betting data. These scores help operators identify trustworthy profiles, optimise liability limits, and reduce risk exposure in an automated, scalable way.

❓ How does the sCCF model work?

The sCCF model uses historical betting behaviour to generate a confidence score between 0.00 and 10.00. It evaluates behavioural signals such as transaction frequency, volatility, betting patterns, and more to assess risk. These scores act as advisory recommendations to help operators make informed liability management decisions.

❓ What’s the difference between sCCF and CCF?

• sCCF is a machine-learning generated score that provides an independent, suggested confidence level.

• CCF is a manually or rule-based assigned value used in MTS for ticket validation.

Operators can compare the two values to assess whether a manual update or auto-adjustment is needed.

❓ What entities are supported?

The API returns scores for:

• Customers (individual player accounts)

• Shops (retail branches)

• Terminals (self-service betting stations)

❓ How often are sCCF scores updated?

sCCF is evaluated daily for active entities. It updates automatically based on real-time transactional data, ensuring the latest behaviours are reflected.

❓ What input data is required to use the sCCF API?

Each API request must include:

• bookmaker: Your assigned Insight Tech / MTS bookmaker ID

• sub-bookmaker: The sub-entity under your bookmaker (or * to target all)

• One of:

  • customer IDs

  • shop IDs

  • terminal IDs

Endpoints support range filtering and pagination using startKey or lastEvaluatedKey.

❓ What does a high or low sCCF value mean?

Score Range	Meaning
≥ 3.00	Very high confidence – likely trustworthy
1.02 – 3.00	Above average – low risk
0.61 – 1.01	Moderate risk or unverified behaviour
< 0.60	High potential risk – may require review

Note: These thresholds are indicative only. Operators should define their own thresholds based on internal workflows and risk tolerance.

❓ What happens if an entity doesn’t have an sCCF score?

Entities may not have a score if:

• They are new or inactive

• There’s insufficient behavioural data

• They haven’t triggered the model’s evaluation criteria

❓ Can I use sCCF to auto-adjust limits?

Yes. While sCCF is advisory, it is designed to support automated workflows. You can:

• Feed sCCF into auto-CCF logic

• Apply dynamic liability limits

• Flag high-risk profiles for manual intervention

❓ What are the API rate limits?

Limit Type	Value
Requests/second	10
Daily quota	200,000 requests
Minute quota	500 requests

Exceeding limits results in a 429 Too Many Requests response. Use exponential backoff for retries.

❓ Is sCCF real-time?

No. The model runs once daily, but results are always available via API for on-demand access. For real-time adaptations, operators should incorporate daily pulls into their workflows or delay ticket processing until the score is retrieved.

❓ Who should I contact for support?

For access issues, integration help, or data questions, contact:

• Your OAM

• Your assigned CI engineer

• Or submit a ticket via Sportradar support.