Get started with a free trial today
Already have an account? Sign in
Stitch’s Braintree integration replicates data using theBraintree API. Refer to theSchema section for a list of objects available for replication.
A high-level look at Stitch's Braintree (v1) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status | Released on March 1, 2017 | Supported by | |
| Stitch plan | Standard | API availability | Available |
| Singer GitHub repository | |||
| REPLICATION SETTINGS | |||
| Anchor Scheduling | Supported | Advanced Scheduling | Supported |
| Table-level reset | Unsupported | Configurable Replication Methods | Unsupported |
| DATA SELECTION | |||
| Table selection | Unsupported | Column selection | Unsupported |
| Select all | Unsupported | ||
| TRANSPARENCY | |||
| Extraction Logs | Supported | Loading Reports | Supported |
To set up Braintree in Stitch, you need:
Access to a Production Braintree account. Stitch does not currently support connecting to Sandbox accounts.
Super Admin and API Access permissions in Braintree. This is required to create the API access token in Braintree.You can find info on Braintree user roles and permissions here.
Additionally, Stitch’s Braintree integration will only replicate transactions for thedefault merchant account in your Braintree instance. You can verify the merchant account set as the default by going toSettings > Processing > Merchant Accounts when signed into Braintree.
This step may not be required.
This step is only required if yourestrict IP access to your Braintree account.
If you don’t use this feature,skip to the next section.
The IP addresses you’ll whitelist depend on theData pipeline region your account is in.
Locate the list of IP addresses for your region:
This will display theClient Library Key page, which contains your Braintree API credentials:

Leave the Braintree Client Library Key page open for now - you’ll need thePublic Key,Private Key, andMerchant ID to complete the setup in Stitch.
On the Stitch Dashboard page, click theAdd Integration button.
Click theBraintree icon.
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Braintree” would create a schema calledstitch_braintree in the destination.Note: Schema names cannot be changed after you save the integration.
The Sync Historical Data setting defines the starting date for your Braintree integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Braintree’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.
In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Braintree integrations support the following replication scheduling methods:
Advanced Scheduling using Cron (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.
After you finish setting up Braintree, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to theAnchor Scheduling documentation for more information.
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is forversion 1 of this integration.
This is the latest version of the Braintree integration.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs >customers), while case is maintained in PostgreSQL destinations (CusTomERs >CusTomERs). Refer to theLoading Guide for your destination for more info.
Thetransactions table contains info about the transactions in your Braintree account, including the transaction’s status.
Note: Our Braintree integration will only replicate transactions for thedefault merchant account in your Braintree instance. You can verify the merchant account set as the default by going toSettings > Processing > Merchant Accounts when signed into Braintree.
Key-based Incremental | |
Primary Key | id |
Replication Key | created_at |
| Useful links |
amount NUMBER | ||
created_at DATE-TIME | ||
credit_card_details OBJECT
| ||
currency_iso_code STRING | ||
customer_details OBJECT
| ||
disbursement_details OBJECT | ||
gateway_rejection_reason STRING | ||
id STRING | ||
merchant_account_id STRING | ||
order_id STRING | ||
payment_instrument_type STRING | ||
paypal_details OBJECT | ||
plan_id STRING | ||
processor_authorization_code STRING | ||
processor_response_code STRING | ||
processor_response_text STRING | ||
recurring BOOLEAN | ||
refunded_transaction_id STRING | ||
service_fee_amount NUMBER | ||
settlement_batch_id STRING | ||
status STRING | ||
subscription_details OBJECT
| ||
subscription_id STRING | ||
type STRING | ||
updated_at DATE-TIME |
| Related | Troubleshooting |
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.