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

# Connections

> Find the setup guide for each provider Payrails connects to: payment service providers, payment methods, fraud tools, dispute providers and data sources.

Each catalog below lists the supported providers, with a setup guide for each one.

## Accept payments

**account-tree**

Payment service providers

Connect a PSP or acquirer and route payments through it.

[Open](/docs/orchestration/integrations)

**credit-card**

Payment methods

Check which methods you can offer, in which countries and through which providers.

[Open](/docs/orchestration/payment-methods)

## Protect revenue

**shield-person**

Fraud prevention

Screen payments with a fraud provider in your workflow before authorization.

[Open](/docs/orchestration/fraud-integrations)

**warning**

Disputes

Connect dispute service providers to process chargebacks in Payrails.

[Open](/docs/chargebacks/integrations)

## Report and reconcile

**bar-chart**

Data sources

Add your payment providers as data sources to power analytics, reporting and fee monitoring.

[Open](/docs/analytics-and-reporting/getting-started/connect-your-data-sources)


## Related topics

- [Workflows](/docs/overview/workflows.md)
- [Receive notifications](/docs/orchestration/payment-acceptance/receive-notifications.md)
- [Payrails Checkout SDKs](/docs/orchestration/checkout-sdks.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.