Braintree is currently in Open Beta. The info in this article is subject to change.
Connecting Stitch to Braintree is a four (sometimes five)-step process:
* This step is only required if you restrict IP access to your Braintree account.
To successfully complete the setup in Stitch, you must have:
Additionally, our Braintree integration will only replicate transactions for the default merchant account in your Braintree instance. You can verify the merchant account set as the default by going to Settings > Processing > Merchant Accounts when signed into Braintree.
This step is only required if you restrict IP access to your Braintree account. If you don’t use this feature, skip to the next section.
If you use Braintree’s IP restriction feature, you’ll need to whitelist Stitch’s IP addresses before you can successfully connect Braintree to Stitch.
Leave the Braintree Client Library Key page open for now - you’ll need the Public Key, Private Key, and Merchant ID to complete the setup in Stitch.
stitch_braintreein the data warehouse. This schema is where all the tables for this integration will be stored.
The Sync Historical Data setting will define the starting date for your Braintree integration. This means that data equal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to sync data beyond Braintree’s default setting of 1 year. For a detailed look at historical syncs, check out the Syncing Historical SaaS Data article.
The Replication Frequency controls how often Stitch will attempt to replicate data from your Braintree integration. By default the frequency is set to 30 minutes, but you can change it to better suit your needs.
Note that the more often Braintree is set to replicate, the higher your row count will be. Even if all the tables in your Braintree integration use Incremental Replication, replicating data frequently will increase your usage.
Stitch & Replicating Braintree Data
Before setting the Replication Frequency, we recommend checking out the structure & Replication Methods for this integration’s tables. Tables that contain nested structures and/or use Full Table Replication will lead to a higher number of replicated rows.<
To help prevent overages, we recommend setting the Replication Frequency to something less frequent - like 6 hours instead of 30 minutes.
For more tips on reducing your row count, check out the Reducing Your Row Count article.
After setting the Replication Frequency, click Save Integration to wrap things up.