> ## 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. > Payrails is designed to simplify and streamline the process of offering multiple payment methods in your online checkout. With Payrails, you can provide your customers with a variety of payment options, making it more convenient for them to complete their purchases and improving your conversion rates. # Set up payment methods ## Types of payment methods available with Payrails Payrails supports several different types of payment methods, ensuring you can cater to the diverse preferences and needs of your customers. The main categories of payment methods available through Payrails include: * **Cards**: This includes popular credit and debit cards such as Visa, Mastercard, American Express, and Discover. Card payments are widely accepted globally and provide a familiar and convenient option for customers. * **Digital Wallets**: These are electronic wallet services that enable customers to store their payment information and complete transactions with just a few clicks or taps. Examples of digital wallets include Apple Pay, Google Pay, and PayPal. * **Alternative Payment Methods**: This category encompasses various region-specific or niche payment methods that may be preferred by certain customer segments. Examples include bank transfers, direct debit, installment payments, and local payment solutions like iDEAL, Sofort, and Alipay. ## Payment Method Availability: PSPs vs. Direct Integrations Some payment methods are only available through integration with a payment service provider (PSP), while others can be directly integrated into your checkout process. PSPs often support various payment methods, making it easier to offer multiple options without managing numerous individual integrations. Direct integrations, on the other hand, involve connecting your checkout process directly to the payment method provider. This option may offer more control and flexibility but can require more effort to manage and maintain. Payrails simplifies the process of integrating with both PSPs and direct payment method providers, making it easier to offer a diverse range of payment options for your customers. ## Integration Options: SDKs and Server-to-Server Payrails provides multiple ways to integrate payment methods into your checkout process. The two primary integration options are: * **SDKs (Software Development Kits)**: Payrails offers SDKs for popular programming languages and platforms, making it easy to integrate payment methods into your web or mobile applications. Using our SDKs, you can quickly implement payment processing with minimal coding, and benefit from built-in security and compliance features. * **Server-to-Server**: This integration option involves sending transaction details directly from your server to Payrails' API. Server-to-server integrations can offer more control over the payment process and are ideal for merchants with custom or complex checkout flows. However, they may require more technical expertise to implement and maintain. The choice between SDK and server-to-server integration will depend on your specific requirements, technical capabilities, and the payment methods you wish to support. Payrails provides comprehensive documentation and support to help you choose the best integration option for your needs and ensure a seamless payment experience for your customers. ## Enable payment methods With a click of a button, you can enable various Payment methods with Payrails. To enable payment methods, complete these simple steps: 1. Establish connections to providers in the Payrails Portal as described [here](/docs/orchestration/integrations/provider-accounts). 2. Integrate with a [Payrails SDK](/docs/orchestration/checkout-sdks/index) or establish a [server-to-server integration](/docs/orchestration/checkout-sdks/accept-payments-via-api). 3. Enable payment methods per processor connection in the Payrails Portal. ## Related topics - [Checkout](/docs/overview/checkout.md) - [Set up your Payrails account and environment](/docs/account-setup/index.md) - [Workspaces](/docs/account-setup/workspaces.md)