> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/defend/faq.md). # FAQ Frequently asked questions about DEFEND Common questions about risk management, limits, and player management. *** ## General ### What is DEFEND? DEFEND is LSports' centralized Risk Management System that gives sportsbook operators visibility and control over betting activity, financial exposure, and player behavior. ### Do I need TRADE to use DEFEND? No. DEFEND works with customers regardless of their feed data source. You can use LSports' TRADE feed or integrate your third-party odds provider via the Customer Integration API. ### What data does DEFEND require? DEFEND needs fixture metadata and market data. We recommend aligning with TRADE's message structure for compatibility, but our team can help map your existing feed format. *** ## Limits & Configuration ### What types of limits can I set? DEFEND supports multiple limit levels: * **Platform limits** — Global limits across your entire operation * **Tier limits** — Limits set per sport, by competition tier and by market * **Player limits** — Individual player restrictions ### Can I set different limits for different sports? Yes. Each sport has its own tiers. Every competition sits in a tier, and each tier has a default limit. You can override that default for any market, separately for PreMatch and InPlay. See [Tiers](/u/defend/risk-controls/tiers.md). ### How quickly do limit changes take effect? Limit changes are applied in real-time. New bets will be evaluated against updated limits immediately. ### What currency does DEFEND use? DEFEND's default currency is EUR. Currency conversion currently happens on your side: apply your fixed exchange rate before sending values to DEFEND, since DEFEND does not convert currencies itself. *** ## Player Intelligence ### How do I block a player? Navigate to Player Intelligence, find the player in the Player List, and apply a block. You can block players individually or by rule. ### Can I set individual limits for specific players? Yes. Player Platform Limits let you override your platform limits for specific players. ### How do I identify suspicious players? DEFEND provides bet slip analytics to identify unusual betting patterns. Look for: * Unusually high win rates * Stake patterns that differ from normal players * Timing correlations with market movements *** ## Integration ### How do I integrate with DEFEND? 1. Review the [Integration Guide](/u/defend/integration-guide.md) 2. Set up [Authentication](/u/defend/integration-guide/authentication.md) 3. Use the [Customer Integration API](/u/defend/api.md) to submit data 4. Use the Bet Slip API to submit player bets ### What authentication method does DEFEND use? DEFEND uses JWT token authentication. See [Authentication](/u/defend/integration-guide/authentication.md) for token generation. ### Can I use DEFEND with my existing sportsbook platform? Yes. DEFEND is designed to integrate with any sportsbook platform via REST APIs. *** ## Operations ### How do I monitor bet slips in real-time? The Operational dashboard shows all incoming bet slips with status, stake, potential win, and projected P\&L. ### What happens when a bet exceeds limits? Depending on your configuration, bets can be: * Automatically rejected * Flagged for manual review * Accepted with alerts ### Can I export data from DEFEND? Yes. Contact your CSM for data export options and formats. *** ## Support ### How do I get help with DEFEND? * **Technical issues:** [Open a ticket](https://support.lsports.eu/support/tickets/new) * **Account questions:** Contact your CSM * **Feature requests:** Submit via the support portal --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lsports.eu/u/defend/faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.