PayPal Transactions to Neon Integration

How Datrise loads PayPal Transactions into Neon

Datrise syncs PayPal Transactions's transactions, payers, balances, fees, refunds, and currency conversions into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

PayPal Transactions: PayPal transaction history and settlement detail.

Neon: Serverless Postgres destination with branching and autoscaling.

How PayPal Transactions entities map to Neon

PayPal Transactions entity	Neon object	Notes
transactions	`paypal_transaction_transactions`	id PK · custom fields → jsonb columns
payers	`paypal_transaction_payers`	id PK · linked to paypal_transaction_transactions
balances	`paypal_transaction_balances`	id PK · linked to paypal_transaction_transactions
fees	`paypal_transaction_fees`	id PK · linked to paypal_transaction_transactions

FAQ

How does Datrise handle PayPal Transactions's custom fields in Neon?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Neon types.

How does the PayPal Transactions to Neon sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect PayPal Transactions to Neon 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.