> ## 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

> Compare the Drop-in, Elements, Secure Fields, and API-only integration paths, and pick the one that matches your PCI scope.

## Choose the right integration approach

Payrails offers several SDKs, each with a different balance of customization and PCI scope. Pick the approach that matches how much control you need over the checkout experience and how much card data your application handles.

### What to consider

* **Customization vs. ease of integration.** For the simplest client-side setup that still uses Payrails orchestration, use the Drop-in SDK. For full control over the experience and presentation, use Elements or Secure Fields.
* **PCI compliance.** Every client-side SDK uses the Payrails PCI-compliant token vault, which minimizes your PCI scope. To collect and tokenize card data yourself, integrate with the API only.
* **Adding new payment methods.** The Drop-in SDK includes the frontend code for every payment method, so adding methods such as Apple Pay and Google Pay takes no frontend work on your side. The other approaches give you more control over where payment options appear in your checkout.

The following table compares what each approach supports. If you are unsure which one is right for you, contact your Payrails representative.

| I want to... | Drop-in | Elements | Secure fields | API only |
| :- | :- | :- | :- | :- |
| Use Payrails orchestration features such as routing and retries | ✅ | ✅ | ✅ | ✅ |
| Use the Payrails PCI-DSS certification to collect PAN data in my application | ✅ | ✅ | ✅ | ❌ |
| Tokenize payment methods with no additional frontend code | ✅ | ✅ | ❌ | ❌ |
| Add new payment methods with no additional frontend code | ✅ | ❌ | ❌ | ❌ |
| Customize the style of a Payrails SDK with my own CSS | ✅ | ✅ | ✅ | ❌ |
| Have complete control over the checkout experience: position, style, and animations | ❌ | ✅ | ✅ | ✅ |

### Next steps

After you choose an approach, start on the client-side implementation. The [SDK guide](/docs/orchestration/checkout-sdks) explains how to get started, and each SDK type has its own guide: [Drop-in](/docs/orchestration/checkout-sdks/web-v5-legacy/drop-in), [Elements](/docs/orchestration/checkout-sdks/web-v5-legacy/elements), and [Secure Fields](/docs/orchestration/checkout-sdks/web-v5-legacy/secure-fields).

If you prefer more frontend flexibility and choose not to use an SDK, refer to [accepting payments via API](/docs/orchestration/checkout-sdks/accept-payments-via-api).


## Related topics

- [Getting started](/docs/analytics-and-reporting/getting-started/index.md)
- [Getting Started](/docs/token-vault/getting-started.md)
- [How to Integrate](/docs/orchestration/checkout-sdks/react-native/how-to-integrate.md)