Linking Checkout.com as a source
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
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Checkout.com.
- Create an access key in the Checkout.com dashboard under Settings > Access keys with the
disputesscope. Note whether your key is for the production or sandbox environment. - Back in PostHog, select the Environment that matches your access key (Production or Sandbox).
- Enter your Access key ID and Access key secret, then click Next.
- 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 | — |