How to Integrate Stripe with PartnerPortal

Use this guide to connect Stripe to PartnerPortal, map Stripe customers to the right portal leads, and choose whether your portal should stay on the legacy commission-time lookup flow or use the newer in-app revenue ledger.

• Admin access to PartnerPortal
• A Stripe account
• Stripe customers already created for the leads you want to map, if you are using the legacy workflow

1. Open Integrations from the PartnerPortal sidebar.

2. Click Enable Stripe.

3. Sign in to Stripe and approve the connection.

If Stripe asks you to reconnect, use the Reauthorize action from the integration card instead of disconnecting and reconnecting from scratch.

Use this workflow when your portal still wants commission generation to read revenue directly from Stripe when the scheduler runs.

In the legacy workflow:

• Stripe is the source of truth for revenue lookup
• PartnerPortal reads Stripe revenue at commission-generation time
• the separate Revenue page is not the main source of truth
• lead-to-customer mapping is what tells PartnerPortal which Stripe revenue belongs to which lead

1. Click Map Leads on the Stripe integration.

2. For each lead, type to search for the matching Stripe customer.

3. Select the right Stripe customer record or records for that lead.

4. Save the mappings.

Two Stripe mapping details matter:

• one lead can have more than one saved Stripe customer ID when needed
• one Stripe customer should only be mapped to one lead at a time

When Commission Source stays on Legacy, PartnerPortal does not wait for revenue to be stored in the app first. Instead, scheduled commission generation reads the mapped Stripe revenue directly from Stripe for the period being processed.

This is the older workflow. It is still supported, but it gives your team less visibility before commissions are created because Stripe remains the main revenue source.

Use this workflow when you want Stripe charges and refunds to flow into PartnerPortal’s in-app Revenue ledger as they happen, so your team can review revenue before or while commissions are created.

In the modern workflow:

• new Stripe charges and refunds are captured into PartnerPortal
• the Revenue page becomes the main working screen for review
• PartnerPortal tries to match each record to a lead automatically
• scheduled commissions can later use the in-app revenue ledger instead of pulling directly from Stripe

When Stripe revenue is captured, PartnerPortal tries to match it in this order:

1. saved Stripe customer mapping first
2. exact customer-email match next
3. website-domain match last

Email and domain matches can still need review. Once your team confirms the right lead, PartnerPortal saves that customer mapping so future Stripe revenue from the same customer can match more directly.

Turning on capture handles new Stripe revenue. It does not automatically pull in older Stripe history that existed before capture was enabled.

If you want older Stripe revenue available inside PartnerPortal:

1. turn on capture
2. open the Revenue page
3. use the import tools there to backfill older Stripe charges and refunds

If you also want scheduled commissions to use that in-app ledger rather than the legacy Stripe pull, change Commission Source to In-App Revenue in Payment Settings.

Most Stripe revenue settings now live in Portal Setup → Payment Settings, while the Stripe integration page remains the place for lead-to-customer mappings.

Once Stripe is connected, the shared Payment Settings page is where the Stripe-specific revenue controls appear. That is where your team manages revenue capture, import status, deleting captured revenue, and the Commission Source setting that decides whether scheduled commissions use the legacy Stripe lookup or the in-app revenue ledger.

Use Capture Stripe Revenue when you want PartnerPortal to store Stripe charges and refunds inside the app.

When it is enabled:

• new Stripe charges and refunds appear on the Revenue page
• PartnerPortal stores the time capture was enabled
• the integration can show revenue-import status if a historical import is running, completed, or failed

If you need to clear the in-app Stripe revenue ledger, the destructive delete action lives under the Stripe revenue settings in Payment Settings.

This deletes captured Stripe revenue records from PartnerPortal, but it does not remove saved lead-to-customer mappings and it does not disconnect Stripe.

In Payment Settings → Commission Generation, choose which revenue source scheduled commission generation should use:

• Legacy: read revenue directly from Stripe at scheduler time using your saved mappings
• In-App Revenue: generate commissions from the revenue records already stored on PartnerPortal’s Revenue page

If your team wants a review step before commissions are generated, In-App Revenue is usually the clearer workflow. If your team still wants PartnerPortal to pull directly from Stripe at generation time, keep it on Legacy.