All Collections
Integrations
Stripe Integration Overview
Stripe Integration Overview

Learn how to connect Stripe to QuotaPath

Updated over a week ago

Contents


Integration Requirements

  • Here are the Stripe objects currently supported by QuotaPath:

    • Accounts

    • Balance Transactions

    • Bank Accounts

    • Charges

    • Checkout Sessions

    • Checkout Sessions Line Items

    • Coupons

    • Customer Balance Transactions

    • Customers

    • Disputes

    • Events

    • Invoice Items

    • Invoice Line Items

    • Invoices (Recommended)

    • Payment Intents

    • Payouts

    • Plans

    • Products

    • Promotion Codes

    • Refunds

    • Subscription Items

    • Subscriptions

    • Subscription Schedule

    • Transfers

    • External Bank Accounts

    • External Account Cards

    • Setup Intents


Before Getting Started

Before integrating Stripe, it's helpful to have the below questions answered to streamline the implementation process.

  • Do you currently have your CRM integrated with Stripe?

    • Without an existing integration between your CRM and Stripe, there will not be an existing ID that can referenced when using Stripe for Payouts Eligibility. This will need to be implemented, which can increase implementation time.

  • Do you currently have a field that can be used for the Payout Eligibility rules (either a Date or Amount field)?

    • If using Stripe for Payouts Eligibility, it is required to have either a Date or Amount field to inform the rules.

  • Will your Deal Create to Payout Eligibility relationship be 1:1 or 1:many?

    • If the relationship is 1:many, the QuotaPath support team will need to roll-up the records, which can increase the implementation time.

Stripe's API sends date and amount fields in the form of seconds and cents, so the QuotaPath support team will need to convert these fields to use within QuotaPath. These fields are applicable to both Deal Create and Payouts Eligibility use cases.


How to connect Stripe

In this article, we'll walk you through the steps to connect your Stripe account to QuotaPath. Please refer back to these steps and tips as needed.

Before connecting, this is the information you will need to ensure you can properly connect your Stripe account:

  1. Account ID:

    1. normally starts with ‘acct_’

  2. Start Date:

    1. During the connection process you will need to input the earliest possible date for data you would like flowing into QuotaPath. (i.e. if you want records from 5/10/2022 flowing into QuotaPath, use a start date of 5/9/2022)

  3. Secret Key:

      1. normally starts with ‘sk_live_’

    1. You can either create a new secret key or use one that has been previously created

If you are unable to view your Account ID or your Secret Key within your Stripe account, please reach out to your organization’s Stripe admin and request the ID and Key from them.

Now that you have all the information needed, you are ready to connect. You can view the following video, or follow the steps below:

  1. Navigate to the integrations page. Click on ‘Settings’ within the left hand nav bar and then ‘Integrations’.

  2. Find the Stripe integration card and click ‘Connect’.

  3. You will be prompted a source form to complete your authentication. Here is where you will need all the information from the first section above.

    1. Fill in the ‘Account ID,’ ‘Start Date,’ and ‘Secret Key,’ then click Submit:

  4. Now that you are successfully authenticated, click ‘Next’ within the modal to move onto the next stage of completing your integration.

  5. Here you will select your sync schedule and the objects/streams you would like to sync.

  6. Once you select ‘Sync Now’ your data will start flowing into QuotaPath:

    1. This could take a few minutes so feel free to close the modal and navigate to Home to complete any outstanding onboarding tasks. We will send you an email once your integration is ready to use.

    2. You will also be able to see your sync status across the top of the integration card under the “Connected Integrations section”

  7. At any point you can click “Edit Settings” or “Resync Now”

    1. “Edit Settings” will allow you to update your sync schedule or any of the streams/objects you have connected.

    2. “Resync now” will allow you to kick off a manual sync, ahead of your next scheduled sync time.

  8. Once Stripe is connected, navigate to Home or Plans to sync data to a compensation plan in QuotaPath.


How to set up for Deal Create only

To set up Stripe to use for Deal Create use cases only, you can proceed to the next section to learn how to sync your plans to Stripe after authentication. For more information on the definition of Deal Create, please visit this article.

If you will be using Stripe as the Payouts Eligibility source, please jump to this section.

How to sync Plans to Stripe

Go to the Plans page in your QuotaPath workspace, navigate to the plan you'd like to sync, and click the path to expand it. From there, click "Sync to CRM" to sync data for this path.

Source: Select to connect to Stripe on the first step in the pop-up modal.

Record: Choose the object in Stripe to use as the deal create source. If you are not seeing the object, go back to Settings then Integrations and edit the integration settings for Stripe and ensure you've synced the object. The most common object to use is Invoices.

Fields: Align the fields to be used for the Deal Name, Deal Amount, Deal Date and Deal Owner.

Note: Stripe does not have a standard field that can be used to match data for the Deal Owner. You will need to create a custom string field containing the rep's email.

Stages: Select the field and value to define each of the 3 deal stages for closed won, pipeline and closed lost. It is only required to define the criteria for closed won.

Review: Add additional filters as needed. The mapped field for the Deal Owner will automatically appear as a filter in order to filter the records based on who's assigned to the plan.

When finished, click 'Sync' to finish setting up the data sync for this path. If there are additional paths in the plan, repeat the above steps to sync every path in the plan. After every path is synced to Stripe and you've assigned QuotaPath workspace members to the plan, head to the Earnings page to start managing commissions!


How to set up for Payouts Eligibility

After having connected Stripe to QuotaPath and setting up your Deal Create source, you can also set up Stripe for Payouts Eligibility. You'll need to start by identifying the connecting ID and whether the relationship will be 1:1 or 1:many.

Identify Connecting ID

Here are few examples of the connecting IDs:

  • Salesforce <> Stripe (either 1:1 or 1:many)

    • Salesforce Deal Create Source: Opportunity

    • Stripe Payouts Eligibility Source: Invoice

    • Connecting ID: Account ID from Salesforce

    • Here is a helpful article on connecting Salesforce to Stripe.

  • HubSpot <> Stripe (either 1:1 or 1:many)

    • HubSpot Deal Create Source: Deal

    • Stripe Payout Eligibility Source: Invoice

    • Connecting ID: Company ID from HubSpot

    • Here is a helpful article on connecting HubSpot to Stripe.

Combine Data

After identifying the connecting ID that will connect the deal create record to the payout eligibility record(s), the data will need to be combined by the QuotaPath support team. Please reach out to the support team to complete this step.

Set Payouts Eligibility Rules

After the data has been combined, you can proceed to the Plans page to start syncing data. The first step is to sync the data that will be used for Deal Create, and then after, you'll define the Payout Eligibility rules.

For more information on the types of Payout Eligibility rules, please review this article.

Here are a few examples of common Payout Eligibility rules for Stripe:

  • Eligibility by Invoice: 'Amount Paid'

  • Eligibility by Invoice: 'Paid At'

If you are having any troubles, please feel free to reach out to our support team, support@quotapath.com, or start a chat from the icon on the lower right hand corner of your page.

Did this answer your question?