Linking Mono as a source
This source is currently in beta. It works end to end, but you may still hit rough edges. Let us know if you do.
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 Mono connector syncs your open banking data into PostHog, including customers, linked bank accounts, transactions, payment collections, and direct debit mandates.
Mono is an African open banking platform that lets businesses access financial data from their customers' bank accounts.
Prerequisites
Before connecting Mono to PostHog:
- You need a secret API key from your Mono app. Copy it from the Mono dashboard.
- Your customers must link their bank accounts through Mono before you can import transactions.
Adding a data source
- Go to the Data pipeline page and select the Sources tab.
- Click + New source and select Mono by clicking the Link button.
- Enter your Secret API key from the Mono dashboard.
- Enter a Transaction start date in
YYYY-MM-DDformat. This is the earliest date from which transactions are imported. It must be before today. - Click Next.
- Select the tables you want to import, set the sync method and frequency, then click Import.
The data warehouse then starts syncing your Mono data. You can see details and progress in the data pipeline sources tab.
Configuration
| Option | Type | Required |
|---|---|---|
Secret API key | password | Yes |
Transaction start date | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
customers | Customers registered with the Mono business. | Full refresh | — | — |
accounts | Bank accounts linked to the Mono business. | Full refresh | — | — |
transactions | Transactions from linked bank accounts within the selected date range. | Incremental, Full refresh | date | — |
institutions | Financial institutions that Mono supports, with their authentication methods and product scopes. | Full refresh | — | — |
payments | One-time and recurring payments collected through Mono DirectPay and Direct Debit. | Incremental, Full refresh | created_at | — |
mandates | Direct debit mandates that customers authorized for the business. | Full refresh | — | — |
mandate_debits | Debits made against direct debit mandates. | Incremental, Full refresh | date | — |
Sync modes
The transactions, payments, and mandate_debits tables support incremental syncing. All other tables use full refresh.
| Table | Sync method | Notes |
|---|---|---|
customers | Full refresh | |
accounts | Full refresh | |
transactions | Incremental or full refresh | Uses date as the cursor for incremental syncs |
institutions | Full refresh | |
payments | Incremental or full refresh | Uses created_at as the cursor for incremental syncs |
mandates | Full refresh | |
mandate_debits | Incremental or full refresh | Uses date as the cursor for incremental syncs |
Incremental syncs fetch rows with a date at or after the last synced value, with a one-day overlap to capture late-arriving data. Full refresh syncs reload all data.
Incremental syncs only pick up new rows going forward. They don't capture updates to previously synced records, such as payment refunds or status changes, outside the one-day overlap window. Use full refresh if you need the latest state of all records.
Available tables
| Table | Description |
|---|---|
customers | Customers registered with the Mono business |
accounts | Bank accounts linked to the Mono business |
transactions | Transactions from linked bank accounts within the selected date range |
institutions | Financial institutions that Mono supports, with their authentication methods and product scopes |
payments | One-time and recurring payments collected through Mono DirectPay and Direct Debit |
mandates | Direct debit mandates that customers authorized for the business |
mandate_debits | Debits made against direct debit mandates |