# Linking Checkout.com as a source - Docs

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

[Learn more](/wizard.md)

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

The Checkout.com connector syncs your disputes data into the PostHog data warehouse. Checkout.com has no list-all-payments endpoint — bulk payment data only exists via report files — so this source currently syncs disputes.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Checkout.com.
3.  Create an access key in the [Checkout.com dashboard](https://dashboard.checkout.com/) under **Settings > Access keys** with the `disputes` scope. Note whether your key is for the production or sandbox environment.
4.  Back in PostHog, select the **Environment** that matches your access key (Production or Sandbox).
5.  Enter your **Access key ID** and **Access key secret**, then click **Next**.
6.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using Checkout.com data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| disputes | Payment disputes and chargebacks | Incremental |

**Incremental** tables sync only new or updated records on each run using the `last_update` cursor field.

## Sync limitations

Only the disputes endpoint is available. Bulk payment data (charges, payouts, etc.) is delivered by Checkout.com as generated report files, which aren't supported by this source yet.

Incremental syncs use the `last_update` field as a cursor. Disputes are fetched newest-first, so the watermark is committed at the end of each sync run.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| Environment | select | Yes |
| Access key ID | text | Yes |
| Access key secret | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| disputes | A dispute (chargeback) raised by a cardholder against a Checkout.com payment. | Incremental, Full refresh | last_update | — |

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better