> 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/integration-guide/payment-suite/payment-method-card/mobile.md). # Mobile Integrate secure, customizable payments into iOS and Android apps with Juspay Hyperswitch mobile SDKs for native and cross-platform frameworks. Juspay Hyperswitch SDK offers **powerful and flexible mobile SDKs** to integrate secure, customizable, and high-performance payments into your iOS and Android apps — whether you're building with native frameworks or cross-platform tools like React Native and Flutter. ### Key Features * **Native & Cross-Platform Support** – iOS, Android, React Native, and Flutter. * **Lite SDK Mode** – Minimal bundle size with full payment capabilities via web components. * **Unified Configuration** – Same `PaymentSheet.Configuration` or `PaymentSession` options across platforms: * Appearance & branding * Billing & shipping details * Payment method preferences * **Secure by Default** – PCI DSS compliant, tokenized transactions. * **Customizable UI** – Match your app's look and feel. * **Global Payment Methods** – Cards, wallets, and more. --- # 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.hyperswitch.io/integration-guide/payment-suite/payment-method-card/mobile.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.