Linking Opn Payments (formerly Omise) 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.
This source is currently in alpha. The interface and available tables may change.
The Opn Payments (formerly Omise) connector syncs charges, customers, disputes, 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.
Enter your Opn Payments (Omise) secret key to sync charges, customers, transfers, and more. Find your secret key in the Opn Payments dashboard under Keys.
You'll be asked for:
- Secret key: for example
skey_test_....
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 Opn Payments (formerly Omise) tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Secret key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Charges | A single attempt to charge a customer's card or other payment source. | Incremental, Full refresh | created_at | — |
Customers | A customer record that can store cards and be charged repeatedly. | Incremental, Full refresh | created_at | — |
Disputes | A chargeback dispute raised against one of your charges. | Incremental, Full refresh | created_at | — |
Events | A record of a change in your Opn Payments account (e.g. charge.create). | Incremental, Full refresh | created_at | — |
Recipients | A bank account recipient that transfers can be sent to. | Incremental, Full refresh | created_at | — |
Refunds | A refund of all or part of a charge back to the original payment source. | Incremental, Full refresh | created_at | — |
Transactions | A ledger entry recording money moving in or out of your Opn Payments balance. | Incremental, Full refresh | created_at | — |
Transfers | A transfer of your Opn Payments balance to a bank account. | Incremental, Full refresh | created_at | — |
Troubleshooting
- If the connection fails with an authorization error, 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.