← Back to blog

PCI DSS for Mobile Apps: What UK Businesses Must Know

November 16, 2026
PCI DSS for Mobile Apps: What UK Businesses Must Know

If your mobile app takes card payments, PCI DSS applies to your business, even when a payment provider handles every transaction. How much work it brings depends on one early design decision: whether card data ever touches your app or your servers. Keep it out, and validation can be a short self-assessment. Let it in, and you face the full questionnaire and a much larger bill. We build apps with that decision made at the start, in discovery, not after launch.

Pocketapp
pocketapp.co.uk
Plan Payment Security Into Your App
Pocket App develops tailored mobile apps, with strategic discovery that can help address payment architecture decisions before development begins.
Visit

TL;DR

  • PCI DSS (the Payment Card Industry Data Security Standard) covers any business that stores, processes or transmits cardholder data, including when payments are outsourced.
  • PCI DSS v4.0.1 is the standard in force, and its future-dated requirements became mandatory on 31 March 2025.
  • Using a provider's prebuilt payment components or hosted pages usually means the short SAQ A. Collecting raw card numbers in your own screens means SAQ D, the full assessment.
  • UK costs vary hugely: a properly run SAQ A can come in under £5,000, while a full audit typically costs £18,000 to £85,000.
  • The cheapest route to compliance is an architecture decision made before design starts.

Table of Contents

When PCI DSS applies to your app

PCI DSS is the security standard set by the PCI Security Standards Council, the body formed by the major card brands. It is not a law. It is a contractual requirement that your acquirer (the bank or provider that lets you accept cards) passes on to you.

The Council's own FAQ is clear that the standard applies to any entity that stores, processes or transmits cardholder data, even when all payment processing is outsourced to a third party. Outsourcing changes what you have to prove, not whether you have to prove it. The FAQ says you must still:

  • make sure the provider is PCI DSS compliant;
  • hold a written agreement acknowledging the provider's responsibilities (Requirement 12.8.2);
  • monitor the provider's compliance at least annually (Requirement 12.8.4);
  • validate your own compliance, typically through SAQ A.

So a retailer with a shopping app, a charity taking donations in-app, or a brand selling memberships all sit inside the standard. The question is how big a piece of it they carry.

What changed recently, and what is in force now

Three dates matter for anyone commissioning an app now.

  1. PCI DSS v3.2.1 was retired on 31 March 2024, making v4.0 the only active version.
  2. The 51 requirements that v4.0 had marked as future-dated became mandatory on 31 March 2025, according to the same Council podcast. They include e-commerce requirements 6.4.3 and 11.6.1, which had been best practice only until then.
  3. The Council's 15 October 2024 bulletin announced the self-assessment questionnaires for v4.0.1. It clarified eligibility criteria in SAQs A, A-EP and C-VT and added a requirement to SAQ A. The v4.0 questionnaires stayed usable only until v4.0 was retired on 31 December 2024.

The practical effect is that any app built or updated now is judged against v4.0.1. Check the Council's document library for the current version before you sign off a specification, because the standard is revised from time to time.

The decision that sets your scope: where card data lives

PCI scope is about where card data travels. Every system that touches it, and every system connected to those systems, is in scope. There are three broad ways to build payments into an app.

Option 1: Hosted page or redirect

The app opens a payment page hosted by your payment provider, in a secure web view or browser, and the customer types their card details there. Your app never sees the number.

Option 2: The provider's native components

The provider supplies a prebuilt payment screen or library that you embed. The card fields belong to the provider's code, and the data goes straight to them. Adyen's documentation says that for its Drop-in and Components native libraries the required validation document is SAQ A under PCI DSS v4.0.1, covering requirements 2, 6, 8, 11 and 12.

Option 3: Your own card form

You design the screen, receive raw card data in the app and send it onward yourself. The same Adyen guide states that a business building its own UI and using only the provider's APIs, with card data sent over TLS 1.2, must complete SAQ D, the full self-assessment for entities that handle cardholder data.

The brand case for option 3 is usually a fully custom checkout. In practice, a well-designed native component can be styled to sit naturally inside your app, so the trade is smaller than it looks. That is the kind of question we work through in discovery, with a prototype in front of you, before anyone writes production code.

Which questionnaire you will complete

A self-assessment questionnaire (SAQ) is the form a smaller merchant completes to validate compliance. The UK-focused guide from MerchantHQ says small UK merchants complete an SAQ annually through their acquirer. The three you are likely to meet:

QuestionnaireWhen it appliesRough size
SAQ AThe full payment flow is on a third party and card data never touches your serversAbout 22 questions
SAQ A-EPYour own site or app environment renders or influences the payment pageLarger than SAQ A
SAQ DYou store, process or transmit card data yourselfAbout 330 questions

The question counts come from the MerchantHQ guide. The final step in all cases is an Attestation of Compliance, which you submit to whoever requires it, usually your acquirer. The standard itself describes the sequence: confirm scope, assess, complete the report, complete the attestation in full, submit it with any requested evidence such as vulnerability scan reports, and remediate if needed (PCI DSS v4.0.1).

Tap to Pay on iPhone and similar features sit in the lightest category. MerchantHQ explains that certification is held at platform level: Apple's Secure Element handles the card data and the acquirer's SDK is validated. UK businesses using it typically complete an SAQ A or SAQ A-EP.

Your acquirer decides the exact questionnaire and any extra evidence. Ask them early, ideally before design is signed off, so the app's payment approach is confirmed against what they will accept.

What the standard expects from the app itself

Even when card data stays with a provider, your app and the systems around it still have duties. Developer guidance from Clover summarises the scope around three ideas: minimise data storage, handle data securely, and protect against vulnerabilities. In practice, that translates into build decisions.

Do not store what you do not need

Card numbers, security codes and magnetic-stripe data should never land in local storage, logs, crash reports, analytics events or screenshots the operating system caches. A common source of accidental scope is a debug log that captures a request body. Build reviews should check for it.

Encrypt in transit and at rest

The Clover guidance recommends HTTPS with TLS v1.2 or higher for secure connections. Weak TLS settings and missing certificate checks are among the gaps that creep in during development. Our own piece on catching TLS and key gaps in CI shows how to catch them automatically before release.

Protect the data-entry channel

The Council's Mobile Payment Acceptance Security Guidelines for developers (v2.0, September 2017) say account data should be encrypted before it enters the device or protected by a trusted path, such as a trusted execution environment. The entry channel must also be secured against client-side injection, including buffer overflows and malicious apps. This guidance is aimed mainly at apps that accept payments on a merchant's own device, but its principles are a useful yardstick for any payment screen.

Scan and patch

Adyen's guide notes that external vulnerability scans every three months are a new requirement in v4.0.1 for SAQ A merchants using its integration. It also lists mitigations such as unique user IDs and passwords of at least 12 characters. Its documentation describes mobile in-app risk as considerably low for these integrations, since the app runs on individual devices rather than a public website. It adds that attackers can still target device-specific vulnerabilities, which is why the mitigations remain.

Watch the web side of your payments

Many apps open a web view for checkout, or share a back end with a website. Requirement 11.6.1 calls for a mechanism that alerts staff to unauthorised changes to HTTP headers and payment-page content as received by the browser. It is evaluated at least every seven days, or at a frequency justified by a targeted risk analysis under Requirement 12.3.1 (compliance guide, 11 August 2026).

There is a nuance worth knowing. In January 2025 the Council revised SAQ A, removing requirements 6.4.3, 11.6.1 and 12.3.1 and replacing them with an eligibility criterion. You confirm that your site is not susceptible to script-based attacks and that every payment-page element reaching the customer comes only and directly from a compliant third party, through full redirects or embedded iframes (Cianaatech, 22 July 2026). If you validate on SAQ A and meet that criterion, those controls fall away for you. That is one more reason to keep the payment page entirely in the provider's hands.

Watch the web side of your payments

What UK businesses should budget

Costs are where the architecture decision pays back. Paytia's UK breakdown, published in May 2026, puts a typical UK PCI audit between £18,000 and £85,000. That covers assessor fees, scans, penetration testing, internal hours and remediation, with the assessor's invoice making up 35 to 50% of it. A properly run SAQ A, by contrast, can stay under £5,000:

Cost line (Paytia, May 2026 UK figures)Range
Quarterly external vulnerability scans, annual total£450 to £1,200
Optional assessor review of the attestation£1,500 to £4,000
Internal staff time£1,500 to £4,200
Policy updates£500 to £1,500

MerchantHQ's 2026 guide adds that for most UK small and medium businesses an SAQ A can be done in an afternoon and costs nothing in itself, while SAQ D is a multi-day project. Paytia says hosted iframes and tokenised storage can often move a merchant from SAQ D to SAQ A and cut annual compliance costs by 60 to 90%. These are the publishers' own figures for their period and market, so treat them as a guide to scale and get a quote for your own situation.

The lesson for a project budget is simple. A few extra days of design and engineering to keep card data away from the app can remove tens of thousands of pounds from the compliance bill, year after year.

What UK businesses should budget

A practical checklist before you brief an app developer

Use this list to shape the brief. Each point is a decision, not a technical detail.

  1. Name your payment provider and acquirer. Ask the acquirer which SAQ they expect for the integration you plan.
  2. Choose hosted or native components over a custom card form, unless you have a clear commercial reason and a budget for SAQ D.
  3. List every system the payment touches: app, web view, back end, analytics, customer support tools. Each one is a candidate for scope.
  4. Decide what is stored. For most businesses the answer should be a provider token, never a card number.
  5. Agree who handles scanning, patching and monitoring after launch. Compliance is annual, and the app changes with every release.
  6. Keep the written agreement and annual provider check that Requirements 12.8.2 and 12.8.4 call for in your compliance file.
  7. Plan the Attestation of Compliance as a project milestone, not an afterthought.

Security practice around the payment screen matters just as much as the payment architecture. Our guides on mobile app security best practices for UK businesses and what to consider before launching a secure app cover the wider checks. If you are weighing where payments in apps are heading, mobile payment trends is a useful companion.

Our perspective

Most PCI problems we hear about in apps were not security failures in the end. They were scoping failures, decided in a first meeting that nobody treated as a compliance meeting.

That is why we bring payments into discovery. In our strategic discovery workshops we make technical recommendations and choose the platform that suits the project, rather than pushing one technology. For a payment feature, that means working out with you, early, which flow keeps card data out of your app, and showing it in an interactive prototype before the build begins.

Our agile build cycles then keep the payment screen separate from the rest of the app, so a design refresh or a new feature does not quietly pull card data back into scope. After launch, server monitoring and ongoing maintenance help you keep up with the annual cycle of scans, updates and attestations.

Our advice is simple: decide your payment architecture before you decide your screens. It is the cheapest compliance decision you will make.

Paul

Plan the payment flow with us

We have delivered more than 300 projects for brands across retail, charity, healthcare and more. Our Discover, Design, Develop and Deploy process is built around settling the important decisions first, and payment architecture is one of them. If you have an existing app and want a second opinion on its payment flow before your next assessment, our Mobile App Clinics are the place to start.

Pocketapp

To discuss a new build, see our mobile app development work or get in touch through pocketapp.co.uk.

FAQ

Does PCI DSS apply if a third party processes all my app's payments?

Yes. The PCI Security Standards Council states that the standard applies to anyone who stores, processes or transmits cardholder data, even with outsourcing. Your job becomes confirming your provider is compliant, keeping a written agreement, monitoring their status yearly and completing the right self-assessment, usually SAQ A.

Which PCI DSS version should my app be built to?

PCI DSS v4.0.1 is the version assessed against now. v3.2.1 was retired on 31 March 2024, and v4.0's future-dated requirements became mandatory on 31 March 2025. Confirm the current version on the PCI Security Standards Council site before you finalise your specification.

Can I achieve PCI compliance for free?

The SAQ A form itself costs nothing, and MerchantHQ says most UK small businesses can complete it in an afternoon. Supporting items such as quarterly scans, internal time and policy updates still carry costs, which Paytia puts at under £5,000 in total for a properly run SAQ A in 2026.

What happens if my app collects card details in its own form?

You are handling cardholder data directly, which points to SAQ D, the full self-assessment of around 330 questions. Your acquirer may ask for further evidence, and the cost and effort rise sharply. Using a provider's hosted page or native components avoids this for most businesses.

Sources