GoCardless to MySQL Integration

How Datrise loads GoCardless into MySQL

Datrise syncs GoCardless's payments, customers, mandates, subscriptions, payouts, and refunds 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

GoCardless: Bank debit collection and recurring payments.

MySQL: Widely used OSS relational engine (InnoDB).

How GoCardless entities map to MySQL

GoCardless entity	MySQL object	Notes
payments	`gocardless_payments`	id PK · custom fields → JSON columns
customers	`gocardless_customers`	id PK · linked to gocardless_payments
mandates	`gocardless_mandates`	id PK · linked to gocardless_payments
subscriptions	`gocardless_subscriptions`	id PK · linked to gocardless_payments

FAQ

How does Datrise handle GoCardless'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 GoCardless 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 GoCardless 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.