DatriseAI-first ETL

Braintree MySQL

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

How Datrise loads Braintree into MySQL

Datrise syncs Braintree's transactions, customers, disputes, and settlement records into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

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

MySQL: Widely used OSS relational engine (InnoDB).

How Braintree entities map to MySQL

Braintree entityMySQL objectNotes
transactionsbraintree_transactionsid PK · custom fields → JSON 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 MySQL?

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

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

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

Related pipelines

Early access

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