> 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/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/token-first-model-setup.md). # Token First Model Setup Best for PCI compliant merchants who wants to store the card during initial checkout phase without charging their customers. The Payment method SDK allows you to securely collect payment information and give customers the option to save their payment details for future transactions. By vaulting these details during the initial checkout phase. #### **Key Features** * **Full Token Management** – Create, retrieve, update, and delete payment tokens directly from your server. * **PSP and Network Tokenization** – Generate both PSP tokens and network tokens through a single API. * **Secure Storage** – Store tokens safely in Hyperswitch’s Vault. * **Reduced Frontend Complexity** – Shift tokenization processes to the backend, minimizing frontend dependencies. #### Understanding Payment and Vault Flow
**Vaulting :** 1. **Collect Card Details** – Card details are entered by customer and sent to your server. 2. **Send a Tokenization Request** – Make a **/payment\_methods** API request with the card details. 3. **Token Creation & Validation** – Hyperswitch validates the request and generates a secure token in the vault. 4. **PSP & Network Tokenization (Optional)** – If configured through your Hyperswitch dashboard, we also generate PSP and/or network tokens when you pass relevant parameters as mentioned below 5. **Receive Payment Method ID** – You get a `payment_method_id`, which can be used for future payments. **Payment :** 1. **Payment using stored card :** To charge the customer you will will have to call the `/payment/create` API and pass the`payment_method_id` along with `confirm` as `true` **Integration Documentation -** * [S2S Vault Tokenization](https://docs.hyperswitch.io/~/revisions/TGn71uwTlQJmyyiYgHpt/explore-hyperswitch/payments-modules/vault/server-to-server-vault-tokenization) * [Create Payment API](https://api-reference.hyperswitch.io/v1/payments/payments--create) --- # 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/~/revisions/gkH4cp2rB1DvMiW6aktj/about-hyperswitch/payment-suite-1/token-first-model-setup.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.