> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/cashier-payments/overview/modular-integration.md).
# Modular Integration
Most gaming merchants already operate a substantial in-house payments stack. They’ve built a cashier UI tuned to their players. They have direct contracts with a wallet provider, a chargeback management vendor, a fraud engine, and one or two acquirers they’re not willing to give up. The case for “rip-and-replace payments platforms” rarely survives contact with these realities - and even when it does, it concentrates platform risk in a single vendor.
Juspay is built on the opposite premise. Every module - 3DS, routing, retries, vault, payouts, fraud workflows, authentication, analytics - is independently consumable. Merchants integrate the components they need and leave everything else untouched.
A few common adoption shapes for gaming operators:
* Routing-only: Keep your existing checkout, vault, and PSP relationships. Use Juspay’s Smart Router as a thin orchestration layer to distribute volume, run experiments, or add fallback connectors.
* Authentication Suite only: Adopt Juspay’s standalone 3DS server to centralize authentication across multiple acquirers and get rich authentication data, while continuing to authorize through your existing PSPs.
* Payouts module: Add Juspay’s payout engine for withdrawals without touching the deposit side. Useful for operators happy with their deposit stack but struggling with withdrawal SR or cost.
* Full Gaming Suite: End-to-end deposit, withdrawal, vault, 3DS, FRM workflows, cashier UI, and analytics.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.hyperswitch.io/integrations/cashier-payments/overview/modular-integration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.