Stripe Connector for FreeScout

Works with Stripe ↗

Stripe Connector puts customer payment and subscription context beside a FreeScout conversation. It uses a restricted, read-only Stripe API key, so it can look up information without changing anything in Stripe.

What the connector shows

When a FreeScout conversation has a customer email address, the connector searches Stripe for matching customer and recent payment records. Depending on what it finds, the sidebar can show:

• Customer identity, with the name linked to the Stripe customer, plus the email and customer-since date.
• Subscriptions showing a link icon that opens the subscription in Stripe, the period, a coloured status dot, the unit price of the first item with its billing interval such as €49/m or €120/y, and the product name (falling back to the price nickname, then a generic label). Columns such as Cancels, Trial end, or Discount appear only when a plan has them.
• Payments in an order-style table: a link icon that opens the payment in Stripe, the date, a status dot with any Radar risk and card-check icons, the total, and a trimmed list of the items bought.
• Refunds and disputes shown as details on the payment row they belong to. The Details column appears only when at least one row has something to show.
• Failed payments with an available decline reason, shown in the same Details column.
• Amounts with a currency symbol where one exists, for example €61 or $12.50, otherwise the currency code; dates render compactly, such as Sep 24 '26.
• Captured, Refunds, and Net totals for the loaded payments.
• Email linking (Pro): when a customer writes from a different address than the one in Stripe, link a Stripe email to the thread and the panel shows that customer's payments.
• A saved payment method's brand, last four digits, and expiry.

When the connector can only see part of the payment history, a single note under the totals says that the totals cover loaded payments only. It does not repeat on every total.

The connector limits each lookup and checks only records connected to that customer. It does not scan the entire Stripe account for disputes or payment history. An empty or partial result does not prove that no other record exists in Stripe.

Prerequisites

Before you start, make sure you have:

• A working FreeScout installation.
• Stripe dashboard access that allows you to create a restricted API key.
• An active ReplyRabbit Pro or Team licence, or a standalone Stripe Connector Pro licence. The standalone licence is 18 EUR as a one-time purchase per FreeScout installation.
• ReplyRabbit installed only if you want the optional, explicitly enabled AI commerce context for drafts.

Sign in to your ReplyRabbit dashboard. An active ReplyRabbit Pro or Team plan includes the connector download. If you do not have either plan, buy the standalone licence there, then download the connector and keep its licence key in the dashboard.

Create a restricted Stripe API key

The connector needs a Stripe restricted key, not a secret key. Create a new restricted key in the Stripe dashboard. Set Customers, Subscriptions, Invoices, Charges, PaymentIntents, PaymentMethods, and Disputes to Read, and set Products to Read to show subscription plan names. Without Products read, subscriptions fall back to the price nickname or a generic label. Leave every unrelated permission set to None.

Copy the restricted key when Stripe displays it. Treat it like a password. The connector encrypts it when saved and never shows the complete value again.

Install the connector

1. Download Stripe Connector

   Sign in at app.replyrabbit.app. Download the connector through your active ReplyRabbit Pro or Team plan, or purchase the standalone Stripe Connector Pro licence first.

2. Upload it to FreeScout

   In FreeScout, open Modules, use the upload control to select the ZIP, and install it.

3. Activate the module

   Activate Stripe Connector from the FreeScout Modules list.

Configure a mailbox

1. Open Stripe Connector settings

   Open the FreeScout mailbox that should show Stripe payment context, then choose Stripe Connector from its settings menu.

2. Paste the restricted key

   Enable the connector and paste the restricted read-only Stripe key. If you bought the standalone connector licence, also paste its licence key from your ReplyRabbit account. An installed ReplyRabbit Pro or Team licence unlocks Stripe Connector Pro automatically. Save the settings.

3. Test the saved key

   Use Test saved key to confirm that Stripe accepts the key and its customer read permission.

4. Check a matching conversation

   Open a conversation whose customer email exists in Stripe and confirm the Stripe panel appears in the sidebar.

Each FreeScout mailbox stores its own encrypted Stripe key. You can connect different Stripe accounts to different mailboxes.

Match a customer who writes from a different email (Pro)

Stripe matches on the conversation's email address. When a colleague writes in, or the customer uses a different address than the one on their Stripe customer, link the right email to the thread:

1. Find the Stripe panel

   Open the conversation and find the Stripe panel in the sidebar.

2. Link another email

   Choose Link another email, then pick an address from the thread or type the billing address used in Stripe.

3. Check the panel

   The panel now shows that customer's payments, notes the Linked to address, and offers Remove link. The connector settings list every saved link with a Remove action per address.

Linking maps every non-mailbox address in the thread, the sender, To, and Cc, to the Stripe email you choose. Those links are stored for the mailbox, so future conversations from any of them resolve to the same Stripe customer. Linking is a Pro feature; Free keeps the standard email lookup. The connector still only reads Stripe data.

Optional ReplyRabbit draft context

The sidebar works without ReplyRabbit. ReplyRabbit is only needed if you want recent Stripe details available when generating AI drafts.

To opt in, set both REPLYRABBIT_COMMERCE_CONTEXT_ENABLED=true and STRIPEINTEGRATION_COMMERCE_CONTEXT_ENABLED=true in the FreeScout environment, then enable the connector for the mailbox. Both settings default to off. After changing them, run php artisan config:clear from the FreeScout directory so FreeScout picks up the new values instead of a cached configuration.

Stripe must be the only active full-context provider for that mailbox. If Shopify is also supplying full commerce context, ReplyRabbit leaves commerce data out of drafts until only one remains enabled. Magento and WooCommerce entitlement lookups do not conflict. The Stripe sidebar stays available to the support agent.

Data handling and limits

The connector sends the conversation email to Stripe over HTTPS to find matching customer-scoped records. It stores the restricted key encrypted. It does not cache full card numbers, raw Stripe payloads, billing addresses, metadata, payment intent secrets, or receipt URLs.

Stripe requests use the pinned 2026-02-25.clover API version. When no Customer record matches, the connector inspects no more than 200 recent charges from the last 90 days and exact-matches the email locally. This guest-payment fallback is intentionally incomplete.

The limited lookup keeps the sidebar responsive and reduces unnecessary data access. A single note under the totals explains when they cover only the payments the connector loaded. For a complete account-wide audit, use the Stripe dashboard.

Troubleshooting

Next steps

• Read How to set up ReplyRabbit if the mailbox still needs AI provider or draft settings.
• See the Shopify connector, WooCommerce connector, or Magento connector guides for other commerce platforms.

FAQ