Square to Postgres integration for a queryable payments replica

The Square to Postgres integration from Adapters syncs payments, orders, refunds, customers, and payouts from the Square API into your own Postgres tables on an incremental schedule, so reporting and app features query transaction data with plain SQL instead of paging the Square API live. Field mapping takes about a minute and no code is required.

Try it in the live demo

Input

Output

Field mapping auto-plugged · tap a port to rewire

5 sample records ready

Last updated July 2026

What running Square to Postgres by hand costs you

Square reports cannot join to your product, inventory, or accounting tables, so cross-location margin and cohort questions get answered by exporting CSVs.
The Square API pages with cursors and returns money as integer cents in a nested money object, so a hand-rolled export mishandles multi-location and currency every time.
Payments get refunded and disputed after they settle, and a one-time export into Postgres is stale before the next payout reconciliation.

The field mapping, out of the box

These cables are pre-wired when you pick the pair. Rewire any of them, or add your own, in the same visual data mapping tool you use for every adapter.

Input / SQUARE

Output / POSTGRES

payment.id

square_payment.id

order.total_money

square_payment.total_cents

buyer.email_address

square_payment.buyer_email

payment.location_id

square_payment.location_id

payment.status

square_payment.status

payment.updated_at

square_payment.updated_at

Transforms included

Incremental loads walk the Square cursor and filter on the updated-at range so only changed payments come back; the nested total_money object flattens to an integer cents column plus a currency code, buyer and location ids land as foreign keys, the RFC 3339 timestamps parse to TIMESTAMPTZ in UTC, and writes upsert with ON CONFLICT on the Square payment id so a retried or overlapping window never double-inserts a row.

How it goes live

Three steps, minutes end to end, covered by flat data integration pricing from $49 a month.

STEP 01

Pick the pair

Connect Square and Postgres with scoped credentials. About a minute each.

STEP 02

Confirm the mapping

The cables above are pre-wired. Adjust any field, preview the transform on sample records, done.

STEP 03

Schedule the sync

Hourly down to every minute, with retries, alerting, and a full log on every run.

Try it in the live demo Preloads SQUARE → POSTGRES with sample records

Square to Postgres sync: common questions

How does the Square to Postgres sync work?

How much does the Square Postgres integration cost?

Pricing is flat and monthly: Starter at $49, Growth at $149, Scale at $399. Every plan includes this pair, visual field mapping, and per-record logs. There are no per-task or per-row fees, so the bill stays the same as volume grows.

How often can Adapters sync Square to Postgres?

Hourly on Starter, every 5 minutes on Growth, and down to every minute on Scale. Failed records retry automatically with backoff, and alerting plus a full per-record log come standard on every run.

Do I need to write code to connect Square and Postgres?

No. Fields are auto-mapped the moment you pick the pair, and you can rewire any mapping visually before the first sync. Incremental loads walk the Square cursor and filter on the updated-at range so only changed payments come back; the nested total_money object flattens to an integer cents column plus a currency code, buyer and location ids land as foreign keys, the RFC 3339 timestamps parse to TIMESTAMPTZ in UTC, and writes upsert with ON CONFLICT on the Square payment id so a retried or overlapping window never double-inserts a row.

More pairs from the API connector library

Browse the full api connector library, or request a pair you do not see.

Square and Postgres, finally in agreement

Map the pair once and let it sync on schedule. Flat price from $49 a month, no per-task fees.

Try the live demo

No credit card required.