Written by: JJ Tan, Founder, Jelly | Last updated: 23 June 2026
Key Takeaways for UK Lightspeed and Stripe
- The Lightspeed Stripe integration sends real-time payment data into margin reporting for UK multi-site operators across eCom, Retail and Restaurant product lines.
- Setup steps differ by Lightspeed product. eCom uses direct OAuth in Payments settings. Retail needs payment type configuration. Restaurant focuses on online ordering integration.
- UK Stripe payouts follow rolling schedules, usually a few working days. Eligible accounts can use Instant Payouts for a 1% fee.
- Webhook configuration sends Lightspeed immediate notifications for payments, refunds and payouts. This setup cuts weekly reconciliation time to under 30 minutes.
- Jelly connects natively with Lightspeed Restaurant to turn live Stripe data into automated dish costing and daily GP alerts — book a demo to see it in action.
Before You Begin Your Lightspeed Stripe Setup
- Lightspeed admin access: You must hold Owner or Administrator permissions in your Lightspeed back office. Standard staff logins cannot authorise third-party payment connections.
- Stripe UK account: Create or log in to a Stripe account registered in the United Kingdom. Verify your business details, VAT number and bank account before you start.
- UK bank account: Stripe needs a UK sort code and account number for GBP payouts. Standard payouts usually settle within a few working days. Eligible accounts can use Instant Payouts for faster access to funds.
- Process owner: Assign one person, typically the Finance Manager or Operations Manager, to own the setup. This single-owner approach prevents webhook conflicts that appear when several users authenticate the same integration from different sessions.
- Lightspeed product confirmed: Identify whether you run Lightspeed eCom, Lightspeed Retail (X-Series) or Lightspeed Restaurant (R-Series) before you proceed. Knowing your product line is essential because each follows a different setup path, from eCom OAuth in payment settings to Retail payment type configuration and Restaurant online ordering integration.
Why Real-Time Stripe Data Matters for Operators
Real-time payment data gives you faster supplier negotiations and accurate GP visibility. When Stripe settlement figures arrive the same day as sales, your Finance Manager can compare revenue against invoice costs without waiting for a monthly accountant report. For multi-site operators, that daily clarity means you react to a margin drop within 24 hours instead of discovering it six weeks later.
Before diving into setup, you need to understand which Lightspeed products support Stripe and how that support differs across product lines.
Lightspeed Products That Work With Stripe
Lightspeed supports Lightspeed with Stripe as a payment provider for its eCom (C-Series) product line. Lightspeed does not support Stripe for in-store transactions on Retail POS (X-Series), where third-party processors must be set up as non-integrated payment types. Lightspeed eCom supports Stripe as an optional third-party integrated payment provider for online checkout after separate account registration and configuration per the setup guide. Support for Lightspeed Restaurant (R-Series) varies by product variant and region and should be confirmed with current documentation. Always check your specific Lightspeed plan and region settings, because payment provider availability can differ.
Using Stripe for In-Store and Online Payments
Stripe’s in-store capability depends on the Lightspeed product you use. For Lightspeed eCom, Stripe handles online payments only, while in-store payments need a separate terminal setup. For Lightspeed Retail (X-Series), Stripe Terminal can be configured for card-present transactions using compatible readers. For Lightspeed Restaurant (R-Series), in-venue card payments usually route through Lightspeed Payments, and Stripe is more commonly used for the online ordering layer. Confirm your hardware compatibility with both Lightspeed and Stripe support before you buy terminals.
Lightspeed eCom Stripe Setup Steps
- Log in to Lightspeed eCom back office using your Owner or Administrator credentials.
- Go to Settings → Payments. Select “Add payment method” and choose Stripe from the provider list.
- Authorise the Stripe connection. You are redirected to Stripe’s OAuth flow. Log in to your UK Stripe account and grant Lightspeed the requested permissions.
- Configure currency. Confirm GBP is set as the primary currency. Mismatched currency settings create settlement errors.
- Enable Apple Pay and Google Pay in the Stripe Dashboard under Settings → Payment Methods. Activate these methods separately, because they do not enable automatically.
- Place a test order for £0.01 or use Stripe’s test card (4242 4242 4242 4242) to confirm the payment flow completes and appears in both Lightspeed and your Stripe Dashboard.
Success indicator: A completed test transaction appears in Lightspeed eCom orders and in Stripe’s Payments tab within two minutes.
Lightspeed Retail (X-Series) Stripe Setup Steps
- Open Lightspeed Retail back office and go to Settings → Payment Types.
- Add a new payment type and select Stripe or Stripe Terminal as the provider, depending on whether you need online or card-present payments.
- Connect your Stripe account through the OAuth prompt. Use the same UK Stripe account across all sites so payouts stay consolidated.
- Assign the payment type to your registers. Enable the Stripe payment type for each register individually under Register Settings.
- Pair your Stripe Terminal reader if you use card-present payments. Follow the Stripe Terminal pairing instructions and enter the pairing code displayed on the reader.
- Run a test transaction on the register to confirm the payment type appears at checkout and settles correctly.
Success indicator: The test sale appears in Lightspeed Retail reports and in the Stripe Dashboard under the correct connected account.
Lightspeed Restaurant (R-Series) Stripe Setup Steps
- Log in to the Lightspeed Restaurant back office web portal with Owner permissions.
- Go to Settings → Online Ordering → Payment Settings.
- Select Stripe as the payment provider and complete the OAuth connection to your UK Stripe account.
- Map your menu categories so food and beverage items are correctly tagged. Jelly uses this mapping to pull item-level sales data for dish costing.
- Enable digital wallets such as Apple Pay and Google Pay in your Stripe Dashboard under Settings → Payment Methods → Wallets. Return to Lightspeed and confirm the methods appear in your online ordering checkout preview.
- Submit a test order through your online ordering page and verify it appears in both Lightspeed’s order management screen and Stripe’s Payments tab.
Success indicator: Item-level order data is visible in Lightspeed back office reports within five minutes of the test order completing.
UK Stripe Payout Timelines
UK Stripe accounts operate on a standard rolling payout schedule. The table below summarises typical timelines for GBP accounts.
| Payout Type | Timeline | Minimum Amount | Notes |
|---|---|---|---|
| Standard | Typically within a few working days | No minimum | Varies by account, see Stripe payout documentation |
| Instant Payout | Within 30 minutes | £1.00 | Requires eligible UK debit card or bank, 1% fee applies, see Stripe Instant Payouts |
| Custom Schedule | Daily, weekly or monthly | No minimum | Configurable in Stripe Dashboard → Settings → Payouts |
New Stripe accounts may have an initial payout delay of 7 to 14 days while Stripe completes identity verification. This delay is standard and lifts automatically once verification is complete.
Lightspeed Stripe Webhook Setup Checklist
Webhooks send Lightspeed real-time event notifications from Stripe, such as payment succeeded or refund issued. Use the checklist below.
| Step | Action | Where |
|---|---|---|
| 1 | Go to Developers → Webhooks in your Stripe Dashboard | Stripe Dashboard |
| 2 | Click “Add endpoint” and paste the Lightspeed webhook URL from your Lightspeed integration settings | Stripe Dashboard |
| 3 | Select events: payment_intent.succeeded, charge.refunded, payout.paid |
Stripe Dashboard |
| 4 | Copy the Webhook Signing Secret and paste it into Lightspeed’s payment settings | Lightspeed back office |
| 5 | Send a test webhook event and confirm Lightspeed logs it without error | Both platforms |
Common Lightspeed Stripe Issues and Fixes
- Admin permission errors: This issue appears most often. If the OAuth connection fails, confirm the Lightspeed account used holds Owner-level permissions, not Manager or Staff.
- Webhook endpoint mismatch: Copying the wrong URL from Lightspeed, such as a staging URL instead of production, causes silent failures. Check the endpoint URL character by character.
- Apple Pay or Google Pay not appearing: These methods need domain verification in the Stripe Dashboard. Follow Stripe’s domain registration steps and ensure your Lightspeed eCom domain is listed.
- Currency mismatch: If your Stripe account is set to EUR but your Lightspeed account operates in GBP, payouts fail. Align currencies before you go live.
- Multi-site connected accounts: Each site should connect to a Stripe connected account under one Stripe platform account. Mixing standalone accounts across sites makes consolidated reporting impossible.
How to Measure Integration Success
Once webhooks are live, the first measurable improvement is reduced weekly admin hours. Reconciliation between Lightspeed and Stripe should take under 30 minutes per week. That time saving comes from same-day margin alerts, because payment data arrives in real time and your GP report reflects today’s sales instead of last week’s figures. This daily accuracy then reduces invoice discrepancies, as Stripe settlement figures match Lightspeed sales totals each day and invoice queries drop. Finally, track digital wallet adoption in Stripe Dashboard → Reports → Payment Methods to confirm Apple Pay and Google Pay enablement is working and supporting faster checkouts.
Advanced Jelly Use With Lightspeed Stripe Data
The Lightspeed and Stripe connection delivers clean transaction data. The next step uses that data automatically. Jelly integrates natively with Lightspeed Restaurant (R-Series) through a real-time API and pulls item-level sales the moment a transaction completes. Combined with Jelly’s automated invoice scanning, every sale is weighed against live ingredient costs with no spreadsheets and no manual entry.
Operators using Jelly with Lightspeed see their Flash Report update daily with GP margin by dish. They receive Price Alerts the moment a supplier increases an ingredient cost and can build a fully costed delivery menu that includes commission overheads. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue. Amber restaurant saves £3,000 to £4,000 per month through tighter invoice controls and faster supplier negotiations supported by Jelly’s price change alerts.
The setup takes under five minutes, and you see your first Flash Report update the same day. Book a demo to walk through the connection process with the Jelly team.
Frequently Asked Questions
Rolling Out Lightspeed Stripe Across Multiple Sites
You can roll out the Lightspeed Stripe integration across multiple sites, but each site should follow a separate setup. In Stripe, use connected accounts under a single platform account so payouts and reporting stay consolidated at group level. In Lightspeed, each location’s back office needs its own payment type configuration and webhook endpoint. Complete one site fully, confirm it works, then replicate the process. Jelly supports multi-site operators and can pull item-level sales from each Lightspeed location independently, giving you a single GP dashboard across all sites.
Handling Delivery Platform Commissions With Stripe
Delivery commissions from platforms such as Deliveroo or Uber Eats sit outside your Stripe settlement. Those platforms collect payment directly and remit net revenue to you after deducting their commission, usually through their own payout schedule. Stripe only processes payments taken through your own Lightspeed online ordering or in-venue setup. Inside Jelly, you can build a separate delivery menu that includes commission percentages in dish costs, so GP for delivery items stays accurate regardless of the payment route.
How Stripe Refunds Flow Into Lightspeed and GP
When a refund is issued in Stripe, the charge.refunded webhook event fires and Lightspeed updates the relevant order record. The refund reduces your net revenue figure in Lightspeed’s sales reports. In Jelly, the Flash Report calculates GP from net sales pulled through the Lightspeed API, so refunds appear automatically with no manual adjustment. If a refund relates to a supplier credit note, such as a rejected delivery, that credit note should also be scanned into Jelly so both the cost and revenue sides of the transaction are captured correctly.
Using Jelly With Lightspeed Retail (X-Series)
Jelly’s native Lightspeed integration focuses on Lightspeed Restaurant (R-Series), which UK restaurants, pubs and hotels use most often. Lightspeed Retail (X-Series) operators can still use Jelly for invoice scanning, dish costing and supplier price alerts, but the real-time POS sales feed currently connects through the Restaurant product. If you run X-Series and evaluate Jelly, speak to the Jelly team directly, because the product roadmap is shaped by operator demand.
Changing Your UK Bank Account in Stripe
Updating your bank account in Stripe does not affect the Lightspeed connection. Log in to your Stripe Dashboard, go to Settings → Bank Accounts and Scheduling, and add the new account. Stripe sends a small verification deposit to confirm ownership. Once verified, set the new account as the default payout destination. Lightspeed continues to send transaction data to Stripe during this process, and only the payout destination changes.
Conclusion: Turning Lightspeed Stripe Data Into Control
A properly configured Lightspeed Stripe integration gives UK restaurant, pub and hotel operators clean, real-time payment data across eCom, Retail and Restaurant product lines. With UK payout timelines understood, webhooks configured correctly and digital wallets enabled, you have a solid operational foundation. The next layer, which covers live dish costs, automated invoice matching and daily GP alerts, is where Jelly removes the remaining manual work. Jelly is listed on the Lightspeed marketplace, which makes it easy to add to your existing setup without switching platforms.
Ready to gain clarity and control over every payment? Book a demo to see Jelly in action.