Source connector

Braintree connector

Braintree integration for databases, warehouses and BI tools

PayPal-owned payment gateway for card and wallet transactions. Datrise captures Braintree entities such as transactions, customers, disputes, and settlement records, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Braintree GraphQL API (dated versioning) / Server SDKs over the legacy REST gateway authenticates with API key, OAuth 2.0, incremental runs key on createdAt.

Of the 4 objects, 3 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `braintree_transactions`) with a schema derived from the Braintree API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Braintree pipeline page, and join the waitlist to get the Braintree connector (ERP) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Braintree data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
transactions	braintree_transactions	Append-only, incremental by timestamp
customers	braintree_customers	Upsert by primary key, incremental on updated-at
disputes	braintree_disputes	Upsert by primary key, incremental on updated-at
settlement records	braintree_settlement_records	Upsert by primary key, incremental on updated-at

Braintree API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Braintree GraphQL API (dated versioning) / Server SDKs over the legacy REST gateway
Authentication	API key, OAuth 2.0 — Requests carry a Base64-encoded public/private API Key pair (or a tokenization key / client-token fingerprint for restricted client-side calls) in the `Authorization` header; Braintree Auth adds OAuth access tokens and is closed beta.
Pagination	cursor — The GraphQL API implements Relay Cursor Connections (`pageInfo.hasNextPage`, `startCursor`/`endCursor`); the legacy REST/SDK Transaction Search instead streams a `ResourceCollection` you iterate without an explicit page size you control.
Rate limit	Not published
Incremental cursor	createdAt — Transaction Search exposes range operators on `createdAt` (and other lifecycle timestamps such as `settledAt`/`disbursementDate`), but there is no single `updatedAt` field, so a status change without a matching lifecycle timestamp will not surface via a createdAt-only poll.
Webhooks	Yes — Webhooks (Transaction, Dispute, Subscription, Disbursement, and other kinds)
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating Braintree

Every GraphQL request requires a `Braintree-Version` header in `YYYY-MM-DD` format; omitting it or reusing a stale date from a copy-pasted example can silently opt a request into different (or deprecated) field behavior.
Braintree does not publish a rate-limit number; the only signal is an HTTP 429 with no rate-limit headers or `Retry-After`, so a connector must infer backoff empirically rather than budget against a documented ceiling.
Transactions are never hard-deleted and there is no deleted-records feed; a voided transaction keeps its record with `status: voided`, so "delete detection" for this source really means watching the `status` field, not polling for absence.
Refunds are only possible once a transaction reaches `Settling`/`Settled`; a transaction still `Authorized` or `Submitted for Settlement` must instead be voided, which produces a different terminal status (`voided`) that a naive status-diff sync can miss if it only expects `settled`/`refunded`.

Compare this against every other documented API

Popular destinations for Braintree

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Braintree connector FAQ

What Braintree data does the connector extract?: 4 objects: transactions, customers, disputes and settlement records. Each lands in its own table with types preserved; history-style objects (1: transactions) load as append-only streams.
Is the Braintree integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Braintree data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Braintree → destination pair has its own page with the object-to-table mapping.

Related ERP sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Braintree pipeline with guided onboarding

Join the waitlist to get priority access for Braintree integrations with guided setup, schema-aware mapping, and production-grade incremental sync.