Linking Mollie as a source
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.
The Mollie connector syncs your Mollie payments data into PostHog. The following tables are supported:
| Table | Description |
|---|---|
| payments | Payment transactions |
| refunds | Refund records |
| chargebacks | Chargeback records |
| customers | Customer records |
| subscriptions | Subscription records |
| settlements | Settlement records |
| payment_links | Payment link records |
| balances | Balance accounts |
| balance_transactions | Balance transaction records |
| profiles | Payment profile records |
| mandates | Customer mandate records |
Adding a data source
- Go to the Data pipeline page and the Sources tab in PostHog.
- Click + New source and select Mollie.
- Enter your Mollie API key. You can find this in the Mollie dashboard under Developers > API keys. Use a live key (
live_...) for production data — test keys only return test-mode data. To sync organization-level tables (balances, balance transactions, settlements, and profiles), use an organization access token (access_...) instead. - Select the tables you want to sync.
- Optional: Add a prefix to your table names.
- Click Next.
The data warehouse then starts syncing your Mollie data. You can see details and progress in the data pipeline sources tab.
Sync mode
Mollie only supports full refresh syncs. Incremental syncs aren't available because the Mollie v2 API doesn't support filtering by created or updated date, and mutable objects like payments, refunds, and chargebacks continue to change status after creation. A full refresh ensures you always have accurate, up-to-date data.
Authentication
Most Mollie tables work with a regular API key (live_... or test_...). However, the following tables are organization-level resources that Mollie only serves to an organization access token (access_...):
balancesbalance_transactionssettlementsprofiles
To sync these tables, connect an access token that is scoped to your payment profile and has read permissions for those resources. Regular API keys cannot access these endpoints.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
payments | A single attempt to collect money from a customer through Mollie. | Full refresh | — | — |
refunds | A refund of all or part of a Mollie payment back to the customer. | Full refresh | — | — |
chargebacks | A reversed payment initiated by the customer's bank or card issuer. | Full refresh | — | — |
customers | A customer stored in Mollie, used to link payments, mandates, and subscriptions. | Full refresh | — | — |
subscriptions | A recurring payment arrangement that charges a customer on a fixed interval. | Full refresh | — | — |
settlements | A payout of collected funds from Mollie to your bank account. | Full refresh | — | — |
payment_links | A shareable URL that lets a customer pay a set amount through Mollie. | Full refresh | — | — |
balances | A Mollie balance account. Payments, refunds, fees and payouts are booked to a balance. | Full refresh | — | — |
balance_transactions | A single movement of funds on a Mollie balance, such as a payment, refund, chargeback, fee or settlement. | Full refresh | — | — |
profiles | A Mollie payment profile (website or app) that payments, payment links and payment methods belong to. | Full refresh | — | — |
mandates | A customer's authorization (mandate) that lets you charge their account or card for recurring payments. | Full refresh | — | — |