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

# Integrations

> Connect dispute service providers to Payrails to process chargebacks, and find the setup guide for each supported dispute integration.

A dispute service integration is a company that processes electronic chargebacks for merchants. It enables customers to manage disputes.

Payrails makes it easy to work with multiple dispute integrations through a single integration. This gives you more flexibility without needing separate integrations for each.

## Connect your providers to Payrails

<Note>
  To accept chargebacks with Payrails, you must connect at least one dispute integration. You can create and configure an integration in the Payrails Portal by following the setup guides below.
</Note>

Each setup guide walks you through how to configure a dispute integration in Payrails. It includes:

* Required prerequisites
* Step-by-step instructions to create and configure the integration
* Specific credentials and webhook setup

Use these guides when adding a new dispute provider or reviewing an existing setup.


## Related topics

- [Integrations](/docs/orchestration/integrations/index.md)
- [Server-to-server Integration](/docs/use-cases/server-to-server-integration-reference-architecture.md)
- [Headless Integration using SDK](/docs/orchestration/checkout-sdks/web-v5-legacy/headless-integration-using-sdk.md)