> ## 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.
# Checkout
> Configure a Checkout.com Disputes integration so Payrails processes your chargebacks, covering account details and credentials.
**Who should use this guide**
This guide is intended for merchants who:
* Use **Payrails** as a chargeback
* Use **Checkout.com Disputes**
*We use a server-to-server integration with Checkout.com, so your account must be enabled to process dispute. If this isn’t enabled, chargebacks won’t work in production. Please contact your Checkout.com account manager or support team to activate it.*
## Create and configure a Checkout.com integration in Payrails
1. Log in to the **Payrails** portal.
2. Go to **Settings** → **Integrations**.
3. Select **Add instance** to create a new Checkout.com 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**.
* Continue to the next step.
***
## Step 2: Choose the provider
* Select **Checkout.com**.
* Continue to the next step.
***
## Step 3: Configure your Checkout.com integration
**What you’ll need from Checkout.com**
Before you begin, make sure you have access to:
* Processing Channel ID (`pc_XXX`)
* Checkout.com **Access Key ID**
* Checkout.com **Access Key Secret**
* Webhook signature key
[Sign in](https://dashboard.checkout.com) to your Checkout.com dashboard to complete this step.
***
### Integration instance name
**In Payrails**
* Enter an **Instance name** for your integration.
***
### Account details
**In Checkout.com**
1. [Sign in](https://dashboard.checkout.com) to the **Checkout.com Dashboard**.
2. Locate your **Processing Channel ID** in the account or processing channel settings.
3. Copy the Processing Channel ID (`pc_XXXX`).
**In Payrails**
* Paste the value into the **Processing Channel ID** field.
***
### API credentials
**In Checkout.com**
1. Go to **Developers**.
2. Select **Create new key**.
3. In **Key details**, select **Access key pair**.
4. Add a **Description** to help identify the key.
5. Under **Scopes** → **Customise** → **Custom scopes**, enable:
* `disputes:accept`
* `disputes:provide-evidence`
* `disputes:view`
* `files`
* `gateway`
* `payments:search`
* `issuing:disputes-read`
* `issuing:disputes-write`
* `issuing:transactions-read`
* `issuing:transactions-write`
6. Select **Allow any processing channel** (or restrict if required).
7. If needed, locate your Processing Channel ID here (`pc_XXX`).
8. Select **Create new key**.
9. Copy the **Access Key ID** and **Access Key Secret**.
**In Payrails**
* Paste the credentials into the corresponding fields.
***
### Webhooks (notifications)
Payrails uses Checkout.com webhooks to receive asynchronous chargeback status updates.
Create the webhook in the same mode (test or live) as your Payrails integration.
**In Checkout.com**
1. Go to **Developers** → **Webhooks**.
2. Select **New webhook**.
3. Enter a name for the webhook.
4. Paste the **Notification URL** from Payrails.
5. Generate a **Signature key**.
6. Select:
7. Save the webhook.
**In Payrails**
* Paste the **Signature key** into the **HMAC key** field.
***
## Enable the integration
**In Payrails**
* Select **Save account** to enable the integration.
The **Enabled** status indicates that the Checkout.com integration is active.
Your Checkout.com integration is now ready to process chargebacks.
***
## Next steps
1. Run a test payment triggering a chargeback using a supported Checkout.com [test card](https://www.checkout.com/docs/developer-resources/testing/disputes-testing).
2. Verify that:
* The dispute appears in Checkout.com.
* The chargeback status updates correctly in Payrails.
3. Once verified in test mode, repeat the setup in live mode.
## Related topics
- [Checkout](/docs/overview/checkout.md)
- [Checkout.com](/docs/orchestration/integrations/checkout-com.md)
- [Update Checkout Amount](/docs/orchestration/checkout-sdks/android/update-checkout-amount.md)