> ## 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.
# Stripe
> Configure a Stripe Disputes integration, with or without Stripe Connect, so Payrails processes your chargebacks.
**Who should use this guide**
This guide is intended for merchants who:
* Use **Payrails** as a chargeback
* Use **Stripe Disputes** (with or without Stripe Connect)
***
## Create and configure a Stripe integration in Payrails
1. Log in to the **Payrails** portal.
2. Go to **Settings** → **Integrations**.
3. Select **Add instance** to create a new Stripe integration configuration.
4. Select the **workspaces** where this integration should be available.
**About workspaces**
Workspaces determine where this integration is available. They let you isolate provider setups by region or business line, or share the same configuration across multiple workspaces.
***
## Step 1: Choose the integration type
* Select **Dispute** and continue to the next step.
## Step 2: Choose the provider
* Select **Stripe** and continue to the next step.
***
## Step 3: Configure your Stripe integration
**What you’ll need from Stripe**
Before you begin, make sure you have access to:
* (Optional) Service / platform account ID (Stripe Connect only)
* Stripe account ID
* Publishable API key
* Restricted secret API key
* Webhook signing secret
[Log in](https://dashboard.stripe.com/login) to your Stripe dashboard to complete this step.
### Integration instance name
**In Payrails**
* Enter an **Instance name** for your integration.
***
### Service account (Stripe Connect only)
Skip this section if you process disputes directly on your own Stripe account.
**In Stripe**
* Go to **Settings** → **Account details**.
* Copy the **Service account ID** (also called the platform account ID).
**In Payrails**
* Paste the value into the **Service account** field.
***
### Merchant Stripe account ID
**In Stripe**
* Go to **Settings** → **Business**.
* On the **Account details** tab, copy the **account ID** (`acct_` followed by a 16-character alphanumeric string).
**In Payrails**
* Paste the value into the **Merchant Stripe account ID** field.
***
### Secret API key
Use a restricted API key to limit access scope and reduce blast radius if the
key is compromised.
**In Stripe**
1. In **Developers**, locate **Restricted keys** and select **Create restricted key**.
2. Choose **Providing this key to another website**.
3. Grant the minimum required permissions:
* Charges (read/write)
* Disputes (read/write)
* Files (read/write)
* Payment Intents (read/write)
* Refunds (read/write)
* Webhooks (read)
4. Name the key and add `https://www.payrails.com` as the destination URL.
5. Copy the generated API key.
**In Payrails**
* Paste the value into the **Secret API key** field.
***
### HMAC key (webhook signing secret)
Payrails uses Stripe webhooks to receive asynchronous chargeback status
updates.
If you are using Stripe Connect, skip this part.
Create the webhook in the same mode (test or live) as your Payrails
integration.
**In Stripe**
1. Go to **Developers** → **Webhooks**.
2. Select **Add destination**.
3. Choose **Your account**, then **Selected events**, and enable only the following events:
4. Select **Webhook endpoint** and continue.
**In Payrails**
* Copy the **Notification URL** from the **Account configuration** section.
In **Stripe**
1. Configure the destination:
1. Give the destination a descriptive name.
2. Paste the Payrails **Notification URL** and
3. Select **Create destination**.
2. Copy the **Signing secret**.
In **Payrails**
* Paste the **Signing secret** into the **HMAC key** field.
***
## Enable the integration
**In Payrails**
* Select **Save account** to enable the integration.
The **Enabled** status indicates that the Stripe integration is active.
Your Stripe integration is now ready to process chargebacks.
***
## Next steps
1. Run a test payment triggering a chargeback using a Stripe [test card](https://docs.stripe.com/testing#disputes).
2. Verify that:
* The dispute appears in Stripe.
* The chargeback status updates correctly in Payrails.
3. Once verified in test mode, repeat the setup in live mode.
## Related topics
- [Stripe](/docs/orchestration/integrations/stripe.md)
- [Payrails Web Fraud SDK](/docs/orchestration/checkout-sdks/payrails-web-fraud-sdk.md)
- [iDEAL](/docs/orchestration/payment-methods/ideal.md)