Stripe is a simple way to accept payments online. Stripe handles everything, including storing cards, subscriptions, and direct payouts to your bank account.
We recommend setting up a one-way sync from Stripe → to the app you want to keep it in sync with, with the following reasoning in mind: You might not want any updates made in your CRM/Marketing tool/... to be synced to Stripe. E.g. When you change the contact's email address in your CRM in a 2-way sync, this change will sync to the contact in Stripe, allowing sensitive information (receipts, payment information) to be sent to this new email address. For many use cases, Stripe will be your source of truth. Bear in mind, in the configuration it's set to 2-way by default, you'll need to adjust this manually.
1. CHOOSE YOUR APPS
2. AUTHORIZE YOUR APPS
We need permission to access both your accounts, this is necessary to keep your accounts in sync. To Authorize your Stripe account, we need your 'Live Secret Key', to be found in the API section of your Stripe account.
3. CONFIGURE YOUR SYNC
Choose the filter for each app to define the subset of contacts you want to keep in sync. Setting up more than one rule is available from the Medium plan onward. For Stripe, you can choose/filter your contacts to a subset as follows:
- All your contacts at once
- Contact with a subscription
- Contact with a subscription to a particular plan
In between your filters you are able to choose the direction of your sync in the drop-down menu. Choose to sync two-way or one-way in either direction.
3.3 AVOID DUPLICATES
Only syncing contacts with an email address, as this is the field we use to match your contacts. This feature is optional when configuring 'older' connections, you'll be able to tick or untick the box. For newer ones, this is mandatory, just to make sure you're always protected from duplicates (don't we all hate them!). If you do wish to turn off this feature, just give us a shout at email@example.com. Don't worry, we will always advise first on how best to proceed!
The availability of these features is app and connection dependent. If the boxes are not there to tick, the features are simply not available. We need to be able to detect deletions and/or unsubscribes on one side and at the same time be able to create a tag/group/list/... named 'PieSync Trash' or 'PieSync Unsubscribes' on the other side. When available, we always explain how and in which direction this feature works for that particular connection.
Syncing Unsubscribes or Syncing Deletions is not available in all connections.
We need you to choose the 'winning app' in case PieSync detects conflicting changes. PieSync detects changes on a field level: Chances of having a conflict are very small; only when two people are updating the same field of the same contact, in different applications at the same time, with conflicting information, there is a conflict (phew, we hope you survived that sentence as well)! On the rare occasion, when a conflict does occur, PieSync will take the value of the master application.
During the initial sync, when we match your databases based on the email address field, we will also use your Master App choice when there's a difference on another field level. Don't worry, when your master app has empty fields, we won't delete any field information in the other app.
When you have a connection setup with Google Contacts, you can additionally sync your contacts to the Google Contacts group 'My Contacts’. This feature is especially useful for iPhone users, as your iPhone contacts get synced to 'my contacts' in Google by default.
This Feature is only available in connections with Google Contacts.
This part in the configuration shows you the default fields we currently keep in sync and how we map them between the two apps you have connected.
This feature allows you to create custom mappings, defining which contact fields should be kept in sync between your applications, including standard and custom fields (app dependent). Find out here how to set up custom fields (metadata) in Stripe.
The customizable field mapping is set up and shown in the white part below the default field mapping in the configuration. You can add an unlimited amount of mappings and remove, enable/disable them anytime.
- Find more information about Customizable Field Mapping here and don't forget to read our blog post!
- Why is my connection not showing the option to create customizable field mappings?
4. START SYNCING!
Make sure no other integrations are running next to PieSync for the accounts you have connected in PieSync. Other integrations will have access to your data and have the ability to manipulate as well. For this reason, we kindly ask you to use PieSync and nothing else to keep your data in sync. Other integrations running in parallel with PieSync are a no-go!
In case you have a lot of contacts in your applications, the initial sync will take some time, even if you configured PieSync only to sync a subset of your contacts. During the initial scan, we need to process all of your contacts (also the contacts outside the chosen subset) to avoid duplicates during the sync. After the initial sync, it should never take much longer than five minutes for updates to show.
Thanks to the feedback we have already received, we created a list of popular apps that we’re going to work on very soon. By voting them up in our pipeline, YOU decide which connectors we’ll release first. If you don’t see your app on the list or need any further help, drop us a line - firstname.lastname@example.org.
Don't forget to read our blog for the latest in productivity, apps, and technology!