Connect Stripe for billing context

Connecting Stripe enriches every ticket with the customer's real billing context — their subscriptions, invoices and revenue — pulled in automatically. Agents stop tab-hopping, and your AI-drafted replies become billing-aware. This guide walks you through it end to end in about five minutes.

What you get

Once Stripe is connected, Lunadesk quietly attaches billing data to the customer on each ticket:

• A “Stripe billing” card in the ticket sidebar — lifetime value, MRR, subscription status, a “Payment overdue” flag when the customer is delinquent, and each subscription with its recent invoices.
• Billing-aware AI drafts — the assistant reads that same context, so suggested replies already know whether the customer is on the Pro plan or has an unpaid invoice.
• A full integration workspace — Overview, Customers, Subscriptions, Invoices and Catalog tabs, with a one-click Resync.

Before you begin

• You're a Lunadesk admin (Settings → Integrations is admin-only).
• You have access to your company's Stripe Dashboard with permission to create API keys.
• You'll create a restricted API key — a scoped, least-privilege key. Never paste a full secret key (sk_live_…); a restricted key (rk_live_…) is safer and all Lunadesk needs.

Step 1 — Create a restricted key in Stripe

In your Stripe Dashboard, head to the API keys page and mint a new restricted key. Here's the exact path:

1. Open Developers → API keys — in the Stripe Dashboard, click Developers (bottom-left), then API keys.
2. Create restricted key — under Restricted keys, click Create restricted key.
3. Name it — give it a descriptive name so you recognise it later, e.g. lunadesk-billing.
4. Set the permissions — set each resource below to Read (or Write for the actions mode). Every other resource stays None.
5. Create the key & verify — click Create key and complete Stripe's two-factor verification if asked.
6. Copy it now — Stripe shows the key (rk_live_…) only once. Copy it — you'll paste it into Lunadesk next.

Permissions to grant

Set these resources on the key. This is the exact set Lunadesk needs to read your billing context (plus permission to register its sync webhook):

Step 2 — Connect it in Lunadesk

Back in Lunadesk, go to Settings → Integrations, click Add an integration, and choose Stripe. You'll land on the Connect Stripe screen.

Pick a connection mode

Choose how much access Lunadesk has. Read-only is the default and right for most teams.

Paste your key and connect

Paste the rk_live_… key you copied from Stripe and click Connect Stripe.

What happens after you connect

Lunadesk immediately backfills your customers, subscriptions, invoices, products and prices, then keeps them fresh via webhooks. On the integration's detail page you can:

• Browse synced data across the Overview, Customers, Subscriptions, Invoices and Catalog tabs — the Overview shows customer count, subscriptions by status, MRR, and paid/open invoices.
• Hit Resync any time to pull the latest from Stripe on demand.
• Disconnect to remove the stored credentials — billing context simply stops appearing on tickets.

Read-only vs Read + actions

Keep your key secure

• Least privilege. Grant only the resources listed above — nothing more. A restricted key can't create charges or move money it wasn't given access to.
• Shown once. Stripe reveals the key a single time. Store it in a password manager if you need a copy; otherwise just create a new one.
• One key per tool. Use a dedicated key for Lunadesk so you can revoke it independently of your other integrations.
• Rotate & revoke. If a key is ever exposed, roll it in Stripe and reconnect. Lunadesk stores your key encrypted and never exposes it back to you or over the API.

Troubleshooting