> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking HitPay as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/hitpay

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](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`

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

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The HitPay connector syncs payment requests, charges, subscription plans, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

## Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

Connect your HitPay account using an API key to sync payment requests, charges, subscription plans, customers, and recurring billing. Find your key in the HitPay dashboard under **Settings** > **Payment Gateway**.

You'll be asked for:

-   **API key**
-   **Environment**: choose between Production (api.hit-pay.com) and Sandbox (api.sandbox.hit-pay.com).

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All HitPay tables are full refresh. Each sync replaces the contents of the table.

## Configuration

| Option | Description |
| --- | --- |
| `API key` **Type:** password **Required:** True |  |
| `Platform API key` **Type:** password **Required:** False | Only needed for HitPay platform accounts. Leave blank otherwise. |
| `Environment` **Type:** select **Required:** True |  |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `PaymentRequests` | A payment link a merchant creates to collect a specific amount via card, PayNow, FPX, GrabPay, or another supported method. | Full refresh | — | — |
| `Charges` | A completed attempt to collect payment, created from a payment request or another checkout flow. | Incremental, Full refresh | created\_at | — |
| `SubscriptionPlans` | A recurring billing plan template merchants can subscribe customers to. | Full refresh | — | — |
| `Customers` | A saved customer record used to associate charges, payment requests, and recurring billing. | Full refresh | — | — |
| `Payouts` | A settlement of the business's available balance to its own linked bank account. | Full refresh | — | — |
| `Invoices` | An invoice the merchant issues to a customer, with its amount, dates, and payment link. | Full refresh | — | — |
| `BalanceTransactions` | A ledger line on the Cards (by Adyen) balance, such as a credit for a charge or a debit for a payout. | Incremental, Full refresh | datetime | — |
| `RecurringBilling` | A recurring billing agreement charging a customer on a schedule, either from a subscription plan or a saved card. | Full refresh | — | — |

## Troubleshooting

-   If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
-   If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.