DatriseAI-first ETL

Braintree Yellowfin

AI-first ETL from Braintree into Yellowfin. Governed entities, incremental sync, typed landing tables.

How Datrise loads Braintree into Yellowfin

Datrise syncs Braintree's transactions, customers, disputes, and settlement records into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

Braintree: PayPal-owned payment gateway for card and wallet transactions.

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How Braintree entities map to Yellowfin

Braintree entityYellowfin objectNotes
transactionsbraintree_transactionsid PK · custom fields → flattened columns
customersbraintree_customersid PK · linked to braintree_transactions
disputesbraintree_disputesid PK · linked to braintree_transactions
settlement recordsbraintree_settlement_recordsid PK · linked to braintree_transactions

FAQ

How does Datrise handle Braintree's custom fields in Yellowfin?

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

How does the Braintree to Yellowfin sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Braintree to Yellowfin 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.