Set up Stripe for a UK business with Payment Links or developer tools. Verify details, test in sandbox mode, and configure payouts before launch.

Stripe setup title card with payment illustrations

Create your Stripe account, verify the email Stripe sends you, then work through the Dashboard account checklist to unlock live payments. While you wait, decide whether you want a no-code route (Payment Links or Checkout) or a developer build (Checkout Sessions or Payment Intents). Test everything in sandbox mode first, add your bank details, and you’re ready to take real money.

TL;DR:

  • UK businesses may need Companies House details, incorporation or VAT records, and recent address proof; Stripe accepts extra documents through the Dashboard.
  • Stripe recommends hosted Checkout for most businesses; reserve Payment Intents with Elements for a genuinely custom embedded form that needs more control.
  • For custom integrations, keep test and live keys separate, verify webhook signatures, and fulfill orders only after confirmed webhook events.
  • Match the bank account name to legal business records exactly, or payouts may be delayed; payout schedules can be manual, daily, weekly, or monthly.
Pipelineapp
Bring Payments Into Your Job Workflow
Pipeline brings lead management, jobs, invoicing, and payments together, helping UK trades and service businesses keep customer work organized.
Get in touch about Pipeline

Table of Contents

Create a Stripe account and verify your email

Head to dashboard.stripe.com and sign up with your business email. Stripe sends a verification link straight away, and clicking it promptly matters more than it sounds: an unverified email can hold up every later step, including payouts.

Once you’re in, find your way around before you start clicking randomly:

  • Sign in and look for Account settings in the top right of the Dashboard.
  • Check Account status to see exactly what’s outstanding before you can go live.
  • Keep your contact details accurate, since Stripe uses them for verification follow-ups and payout confirmations.

Getting these basics right from day one saves you a second trip through settings later, when you’d rather be focused on taking your first payment.

Complete your business profile and meet verification requirements

This is the stage most people underestimate. Stripe needs to confirm who you are and what your business does before it lets you accept live payments, and the Dashboard checklist walks you through it: business details, a description of what you sell, and personal identity verification for anyone with significant control of the company.

For UK businesses, the documents Stripe typically asks for include:

  • Details that match your Companies House record, including named persons with significant control (PSC).
  • A certificate of incorporation or VAT registration number, where relevant to your business type.
  • A recent utility bill or bank statement to confirm your registered address.

This lines up with what Stripe itself sets out in its know your customer obligations, which lays out the checklist you’ll complete in the Dashboard before live payments switch on. If Stripe comes back asking for more, upload documents directly through the Dashboard rather than replying by email: that’s where the review team expects to find them, and it keeps your verification moving.

Accept your first payment: no-code or developer path

Before you touch any code, decide how hands-on you want to be. Both paths get you paid; they just suit different setups.

  1. Go no-code if you want speed. Create a Product in the Dashboard, then generate a Payment Link or use Stripe Checkout for a hosted payment page. No development required, and it’s secure by default.
  2. Go developer if you need control. Use Checkout Sessions for a hosted flow you trigger from your own code, or Payment Intents with Elements when you want an embedded form on your own site.
  3. Build the product and price first. Every payment, whichever route you take, starts from a Product and Price object in Stripe.
  4. Create your link or session, then send a real test transaction through it using Stripe’s test cards before anyone outside your business sees it.

Stripe’s own comparison between these two approaches is worth reading if you’re torn: it recommends hosted Checkout for most businesses, because it offloads a lot of the security and compliance work that a custom-built form would otherwise put on you. Payment Intents and Elements exist for when you genuinely need a bespoke checkout experience, not as the default choice.

If you run a trades or service business and want payment links tied directly to specific jobs rather than generic products, it’s worth looking at how payment links fit into job workflows before you commit to a structure.

Use the sandbox to test webhooks and failure paths

Illustrated sandbox webhook test with failure branch

Test mode exists so your mistakes happen before launch, not after. Switch between test and live mode using the toggle in the Dashboard, and grab your test API keys from the same Developers section you’ll use for live keys later.

Run through more than the obvious success case:

  • Trigger a failed card payment and confirm your app handles the decline gracefully.
  • Simulate a dispute to see how that status flows through your records.
  • Test what happens if verification is incomplete when a payment attempt comes in.
  • Set up a webhook endpoint in test mode and use the Dashboard’s webhook tester to confirm events arrive and signatures verify correctly.

Stripe’s own testing documentation covers test cards and sandbox behaviour in detail, and working through it properly now avoids a support backlog later.

Pro Tip: Test your webhook signature verification deliberately with a wrong secret once, so you know what a genuine failure looks like before it happens in production.

Set up payouts and add your bank details

Payouts won’t start until you’ve added a bank account in Payout settings, and the account name needs to match your legal business records exactly. A mismatch here is one of the more common causes of delayed payouts, so it’s worth double-checking before you move on.

From there:

  • Choose a payout schedule: manual, daily, weekly or monthly, depending on how you manage cash flow.
  • Expect standard settlement timing to follow Stripe’s documented schedule for your account type and region.
  • Consider Instant Payouts if you need same-day access to funds on eligible UK debit cards, noting that instant payouts carry a small fee and have per-payout limits, so they won’t suit every transaction.

Full detail on schedules and settlement timing sits in Stripe’s payouts documentation, which is worth bookmarking if your cash flow planning depends on predictable timing.

Developer quickstarts: API keys, SDKs and your deployment checklist

If you’re building your own integration rather than using Payment Links, a few things need to happen in order.

  1. Grab your API keys from the Developers section of the Dashboard, keeping test and live keys clearly separated, and never commit live secret keys to a public repository.
  2. Install an official SDK for your language, or follow one of Stripe’s quickstarts to scaffold a Checkout Session or Payment Intent in minutes rather than hours.
  3. Use the Stripe CLI for local development, since it lets you forward webhook events to your machine without deploying anything first.
  4. Create webhook endpoints for the events you actually need, commonly checkout.session.completed and payment_intent.succeeded, and verify every signature before trusting the payload.
  5. Reconcile and fulfil orders based on confirmed webhook events rather than the response from your frontend, since that’s the only signal you can fully trust.

Stripe’s get started documentation covers SDKs and quickstarts for the main languages, and if you want a ready-made template for the receipt emails that follow a successful payment, this guide to payment receipt emails and signed webhooks is a useful reference for getting that part right the first time.

Security and final pre-launch checks

Before flipping the switch to live mode, lock down the basics. Turn on two-step authentication for every team member with Dashboard access, and set permissions so only the people who need financial controls actually have them, which our security practices overview covers in more depth.

Confirm your statement descriptor will make sense on a customer’s bank statement, check your receipt and refund templates read the way you want them to, and run one final end-to-end test: verification complete, webhooks firing, success and cancel pages behaving as expected.

How Stripe setup fits into your wider job and invoicing workflow

A Stripe account that works in isolation only solves half the problem. The real friction for trades and service businesses shows up when payments, invoices and job records live in different places: you chase a payment, then separately update a spreadsheet, then separately mark the job done.

Connecting payments directly to the job they belong to is what actually speeds up cash collection and keeps reconciliation simple, rather than money quietly going missing between systems. We built our invoicing feature inside Pipeline on that same logic: invoices and payments tied to the job, not sitting apart from it.

— Chris

See how Pipeline brings payments and job management together

Getting Stripe live is one job done. Keeping it connected to quotes, jobs and invoices as your business grows is the part that saves you hours every week. We built Pipeline so UK trades and service businesses can manage leads, schedule jobs, send quotes, raise invoices and collect payments through Stripe, all from one place, on flat monthly pricing with no per-user fees to budget around.

Our Starter plan runs £38 a month, with Solo available from £12 a month for sole traders who want the same tools at a smaller scale. If you want to see how it works for your specific trade, our tools for UK trades page has free CIS, VAT and pricing calculators worth trying first. When you’re ready, book a look at how Pipeline handles your jobs and payments together.

FAQ

What is needed to set up Stripe?

You need a business email, basic business details and, before you can accept live payments, completed identity verification through the Dashboard checklist. This covers business information, a description of what you sell, and personal ID for anyone with significant control of the company, as set out in Stripe’s know your customer obligations.

Is Stripe linked to HMRC?

No, Stripe is not connected to HMRC’s internal systems, and merchants remain responsible for keeping their own tax records and filing returns. Under Making Tax Digital, digital record-keeping rules require approved software to submit returns, and payment data from Stripe alone doesn’t meet that requirement on its own.

How do I set up Stripe for a UK business?

Sign up at dashboard.stripe.com, verify your email, then complete the Dashboard checklist with your business details and the UK-specific documents Stripe requests, such as Companies House alignment and VAT registration where relevant. Once verification clears, add your bank details in Payout settings and choose whether to launch with a no-code Payment Link or a developer-built Checkout flow.

Do I need a registered business to set up Stripe?

You can set up Stripe as a sole trader or a registered company, since both are accepted account types. What matters is that the details you provide, including your legal name and address, match official records exactly, which avoids delays during verification.

Sources

Recommended