> 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/cashier-payments-suite.md).

# Cashier Payments Suite

Each row below maps a cashier-payment constraint to the feature that solves it, and to the operational outcome the merchant gets.

| Constraint                                  | Feature                                          | Outcome                                                                                                                                                    |
| ------------------------------------------- | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Friction-sensitive deposit conversion**   | 3DS Intelligence Engine + 3DS Cascading          | Challenge applied surgically to fresh cards; COF traffic stays frictionless; processor-side declines retry silently across PSPs                            |
| **High-risk BIN exposure**                  | Card Eligibility Engine                          | BIN, issuer, country, and card-type restrictions enforced at point of entry, before the player ever submits                                                |
| **Credit-card prohibitions (UK / IE / AU)** | Credit-card blocking                             | Single dashboard toggle blocks credit cards, including credit-card-backed wallet tokens                                                                    |
| **Closed-loop withdrawals (AML)**           | Closed-loop validator + Smart Router for Payouts | Eligibility enforced per leg; merchant-controlled split routed via configurable payout rules; retriable failures cascade across connectors                 |
| **Player-name verification (DE / CA)**      | Name-verification workflows                      | Player name relayed to APMs (Klarna Debit Risk, Sofort, Trustly, Rapid Transfer) and Interac; verification status delivered via webhook                    |
| **Withdrawal SR, cost, and speed**          | Smart Router for Payouts + Smart Retries         | Per-rail SR, settlement-time, and cost surfaced in analytics; routing optimized within AML constraints                                                     |
| **Cashier conversion**                      | Customizable Cashier SDK                         | Themed checkout with payment-method ordering, promotion, grouping, and one-click last-used checkout, across Web / iOS / Android / RN / Capacitor / Flutter |
| **Credential storage and reuse**            | PCI-compliant Vault                              | Processor-independent card and bank credential storage; saved-method API powers one-click COF deposits                                                     |
| **Roadmap and stack control**               | Self-hostable, open-source                       | Operator retains existing wallet, fraud, vault, and acquirer relationships; deploys Juspay components selectively in its own VPC                           |

The suite ships with 120+ pre-built connector integrations — including Stripe, Adyen, Worldpay, Checkout.com, Cybersource, Nuvei, Trustly, Skrill, Neteller, PayPal, and iGaming-specific PSPs — so adding or swapping providers is configuration, not engineering work.

A high-level view of how these fit together:

<figure><img src="/files/qqX9GeZzXh1C6F4lEuHh" alt=""><figcaption></figcaption></figure>

See [Features](/integrations/cashier-payments/features.md) Section for additional details


---

# 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/cashier-payments-suite.md?ask=<question>&goal=<endgoal>
```

`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.