Skip to main content

Stripe Integration Overview

Learn how to connect Stripe to QuotaPath

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. 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 follow the steps below:

  1. Open Integrations in the Data group of the left-hand navigation (it is not under Settings). If you already have a source connected, you will land on Connected; otherwise you will see Available. Stripe is in the catalog of connectable sources.

  2. Click on Available Integrations & Apps.

  3. Optional: Click Payment to filter to Payment sources.

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

  5. 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,’ and ‘Secret Key,’ then click Submit:

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

  6. Here you will select your sync schedule and the objects/streams you would like to sync. If you select "Sync every 24 hours" you will also be able to select the Time of First Daily Sync, allowing control over when data refreshes daily.

  7. 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 on the Stripe card on the Connected view of Integrations

  8. After the source is connected, open the Stripe card and choose Manage to change settings. Sync schedule, objects, re-authentication, and disconnect live on the Manage Source tab. To pull the latest records, an Admin clicks Sync and Refresh on the card or the source page (that action is admin-only).

  9. 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, jump to How to set up for Payouts Eligibility below.

How to sync Plans to Stripe

Go to the Plans page, open the plan, then open the component you want to map. Mapping is set up in the Mapping module while you edit that component (QuotaPath calls this a component, not a 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 Integrations, open Stripe, and use the Objects tab (or Manage Source) to make sure that object is included. 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, save the mapping for this component. If the plan has additional components, repeat the steps for each one. After every component is mapped to Stripe and the members are assigned 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?