DatriseAI-first ETL

Paystack to Azure Synapse Integration

AI-first ETL from Paystack into Azure Synapse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Paystack into Azure Synapse

Datrise syncs Paystack's transactions, customers, plans, subscriptions, settlements, and refunds into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

Paystack: Online payment collection for African markets.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Paystack entities map to Azure Synapse

Paystack entityAzure Synapse objectNotes
transactionspaystack_transactionsid PK · custom fields → NVARCHAR(MAX) JSON columns
customerspaystack_customersid PK · linked to paystack_transactions
planspaystack_plansid PK · linked to paystack_transactions
subscriptionspaystack_subscriptionsid PK · linked to paystack_transactions

FAQ

How does Datrise handle Paystack's custom fields in Azure Synapse?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the Paystack to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect Paystack to Azure Synapse the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.