Linking Flutterwave 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.
Contents
The Flutterwave connector syncs transactions, settlements, refunds, 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
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- 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.
New Flutterwave sources use API v4 by default and authenticate with OAuth2 client credentials. Existing sources connected with v3 credentials continue to work.
You can find your API keys under Settings > API Keys in the Flutterwave dashboard. If the page shows a public key, secret key, and encryption key, you are on v3 keys — click Switch to v4 live API keys to see your client ID and client secret.
You'll be asked for:
- Client ID: your v4 OAuth2 client ID.
- Client secret: your v4 OAuth2 client secret.
- Secret key (v3 only): only needed for sources connected with v3 keys (for example
FLWSECK-...).
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_attimestamp). 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 for a full explanation of how each mode works and how to choose between them.
All Flutterwave tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
Client IDType: text Required: False | |
Client secretType: password Required: False | |
Secret key (v3 only)Type: password Required: False | Only needed for sources connected with v3 keys. |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
transactions | A payment collected on the Flutterwave account, one row per charge attempt across every payment method (card, bank transfer, mobile money, USSD). | Full refresh | — | — |
settlements | A payout of collected funds from the Flutterwave balance to the merchant's settlement bank account. | Full refresh | — | — |
refunds | Money returned to a customer against a previously successful transaction. | Full refresh | — | — |
transfers | An outbound payout initiated by the merchant to a bank account, mobile money wallet, or Flutterwave balance. | Full refresh | — | — |
chargebacks | A payment dispute raised by a customer or their bank against a transaction. | Full refresh | — | — |
beneficiaries | A saved payout recipient that transfers can be sent to without re-entering their bank details. | Full refresh | — | — |
Note: The tables
payment_plans,subscriptions, andsubaccountsare only available on API v3. They are not synced for v4 sources.
Troubleshooting
- If the connection fails with an authorization error on v4, your client ID or client secret is incorrect. Copy your current v4 API keys from your Flutterwave dashboard, then reconnect the source.
- If the connection fails with an authorization error on v3, the secret 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. If that doesn't help, contact support – we're happy to help.