Sync UniBank to PostgreSQL

BankSync may support connections to UniBank accounts through third-party open banking providers, then route the supported account data shown below to PostgreSQL. Set up takes under 10 minutes and requires no code.

AustraliaBank SyncAvailable

Get Started Free Learn more about our PostgreSQL Integration

How to sync UniBank to PostgreSQL

Mapping UniBank fields into PostgreSQL — map your columns once

Search for UniBank in BankSync

Sign up for BankSync and, if UniBank is available, link your account through a provider-hosted or bank-hosted authorization flow. BankSync does not store your online banking credentials.

Authorize PostgreSQL

Authorise BankSync to write data to your PostgreSQL workspace. Select the database, table, or sheet where the supported account data should land.

Configure field mappings

Map the supported UniBank fields supplied by the provider to columns in PostgreSQL.

Set your sync schedule

Choose hourly, daily, or weekly automatic syncs based on your plan, or run a manual sync at any time.

What gets synced from UniBank to PostgreSQL

Transactions

Sync available UniBank transaction history and provider-supplied fields such as dates, amounts, descriptions, merchants, and categories.

Balances

Sync current and available balances for supported UniBank accounts.

Account Details

Use provider-supplied account names, masked identifiers, and types to organise data in PostgreSQL.

Custom Field Mappings

Map any UniBank field to any column in PostgreSQL — fully configurable.

Sync Schedules

Choose hourly, daily, or weekly automatic syncs based on your plan, or run a manual sync at any time.

Ready to sync UniBank with PostgreSQL?

Start your 14-day free trial. Connect your bank, configure your sync, and have data flowing into PostgreSQL in minutes.

Get Started Free

UniBank Details|PostgreSQL Details|View Pricing

Sync UniBank somewhere else

The same UniBank connection can feed any of these destinations.