> ## Documentation Index > Fetch the complete documentation index at: https://docs.payrails.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code. > Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it. > Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code. > Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation. > Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent. > Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format. > Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code. # Getting Started > In this section, you will learn how to use Vault as a standalone module, about our proxies, tokenization and detokenization methods. ## Introduction If you have read our [Token Vault introduction](/docs/overview/vault) page, you already know that Payrails offers multiple ways to use our Token Vault, as a standalone module or within the Payment Orchestration with Payrails. In this section, we introduce the Vault module. If you are not sure how you want to use the vault, you can navigate to the next [section](#options-to-use-payrails-token-vault) to learn your options. ## Benefits * Payrails Vault is a **PCI-DSS Level 1 compliant** vault, which you can use to minimize your PCI scope. * It is provider-agnostic that allows you to **switch between any payment service providers** at any time, without disrupting your customer experience or facing technical hurdles. Because your token vault is independent of any single payment processor, you’re not locked into any one provider—this means you can take advantage of **better rates, improved service, or new features** from other providers at any time. * Payrails Vault enables you to securely receive and send tokenized data to **a variety of third-party services—not just PSPs**—without exposing sensitive information to your systems. Whether it's fraud prevention tools, online travel agencies, channel managers, property management systems, loyalty platforms, other external token vaults, or internal systems, you can configure proxy connections to route sensitive data securely and stay out of PCI scope. * With Vault, your returning customers can use stored payment methods for a **smoother checkout experience**, use tokenized payment methods, which are the **best performing in subscription** or recurring payment scenarios (particularly when used with network tokens), and **enable users to manage** their saved cards and have control over their sensitive information. * You can unlock more benefits with additional Vault features, such as network tokenization, card lifecycle updates and BIN lookup data. You will find more information about each feature as you navigate to the next pages of the **Token Vault** section. ## Options to use Payrails Token Vault There are 2 main alternatives to use Payrails Token Vault: Getting started 1 **1. Token Vault as a standalone module:** In the case that you want to manage third-party integrations within your system, such as payment providers or your travel partners, but only use our Vault for the storage and processing of the sensitive data, you can use our Vault as a **proxy** which collects the sensitive data via our SDKs and pass the sensitive information to third parties without touching the sensitive data. Getting started 2 **2. Token Vault as part of payment orchestration:** In the case that you want one single API integration with Payrails payment orchestration platform, which in the background, will connect you to all the provider integrations for you in a PSP-agnostic way by leveraging our Vault. ### Using Token Vault with combination of other Payrails modules If you start using our Vault as a standalone module, you can always start using our other modules later, such as payment orchestration or analytics, at any moment in time. It is also possible to use both integration methods at the same time if your business needs require that. ## Related topics - [Getting started](/docs/analytics-and-reporting/getting-started/index.md) - [Getting Started](/docs/orchestration/getting-started.md) - [How to Integrate](/docs/orchestration/checkout-sdks/react-native/how-to-integrate.md)