Does PCI DSS apply to a dating site?
Yes, if the site takes card payments, even when it never sees a card number. The Payment Card Industry Data Security Standard (PCI DSS) is a baseline of technical and operational requirements for protecting payment account data.
The PCI Security Standards Council, which writes the standard, says it applies to entities that store, process or transmit cardholder data or sensitive authentication data, and to those that could affect the security of that environment. A dating site whose checkout page loads a payment form falls into the second group at least.
The Council does not police it. It says whether a business must comply, or prove that it complies, is decided by the organisations that run compliance schemes, such as a payment brand or an acquirer. In practice your payment processor or acquiring bank will ask you to confirm compliance each year, and its contract will normally let it act if you do not.
How much work is PCI DSS for a dating site?
It depends almost entirely on how the card details get from the member to the processor. The less your own servers and pages touch card data, the shorter the form you fill in.
Merchants below the top level confirm compliance with a Self-Assessment Questionnaire (SAQ). There are several versions. Stripe's PCI guide maps its own integration types to them, and other processors publish similar tables:
| How the member pays | Does card data touch your servers? | Form Stripe says applies |
|---|---|---|
| Hosted checkout page or embedded payment fields from the processor | No | SAQ A |
| Mobile app using the processor's official SDK components | No | SAQ A |
| Your own payment form that posts card data straight to the processor | Your page controls the form | SAQ A-EP |
| Card numbers sent to your server, then to the processor's API | Yes | SAQ D |
| Staff typing card numbers into the processor's dashboard | Staff handle the numbers | SAQ C-VT |
| Apple or Google in-app purchase | No, the store takes the payment | None for those payments |
| White label platform takes the payment | No, and you are not the merchant | The platform's own compliance |
The gap between the first row and the fourth is large. Stripe says a business that handles card data directly "might be required to meet more than 300 security controls", which can mean dedicated security software and hardware and paying external auditors.
For almost every dating brand the right answer is the first row. Use the processor's hosted page or embedded fields and never let a card number reach your own systems. Our guide to dating checkout optimisation covers the conversion side of that choice.
What changed for hosted payment pages in 2025?
SAQ A now asks you to confirm that your site cannot be attacked through scripts. The change matters to dating sites because their pages often carry many third-party scripts.
In January 2025 the PCI Security Standards Council announced an updated SAQ A for PCI DSS v4.0.1, effective from 31 March 2025. It removed three requirements from the form, including two on payment page security (6.4.3 and 11.6.1). In their place it added an eligibility test: merchants must "confirm their site is not susceptible to attacks from scripts that could affect the merchant's e-commerce system(s)". The Council said the changes do not remove or reduce the underlying requirements in the standard itself.
Stripe makes the practical point: including JavaScript from other sites makes your security depend on theirs, and it recommends keeping it to a minimum on payment pages. For a dating site that means:
- load no advertising pixels, chat widgets or A/B testing scripts on the checkout page unless you truly need them
- keep a list of every script on that page and who approved it
- set a Content Security Policy that only allows the sources you expect
- serve the page and everything on it over TLS 1.2 or above, which Stripe requires for payment pages.
What PCI merchant level is a dating site?
Most new dating brands are at the lowest level, because levels are set by how many card transactions you process in a year. Each card brand publishes its own table. Mastercard's is below.
| Mastercard level | Annual Mastercard and Maestro transactions | What Mastercard asks for |
|---|---|---|
| Level 1 | More than 6 million | Annual assessment with a Report on Compliance |
| Level 2 | More than 1 million, up to 6 million | Annual SAQ, with an approved assessor for SAQ A, A-EP or D |
| Level 3 | More than 20,000 e-commerce transactions, up to 1 million | Annual SAQ |
| Level 4 | All other merchants | Annual SAQ |
Mastercard says Level 4 merchants must comply with PCI DSS, but it does not require them to validate compliance to Mastercard itself unless a law or regulation does. Acquirers must still show Mastercard that they manage the risk across their smaller merchants. That is why your processor asks for a yearly attestation even when you are small.
Remember that a subscription business counts every renewal as a transaction. A dating brand can move up a level faster than a shop with the same number of customers.
What card data can a dating site keep?
Keep only what the processor hands back, and never the full card number. Stripe says the card type, the last four digits and the expiry date are not subject to PCI compliance, and that you can store anything its API returns. Renewals are charged against a token held by the processor, so your database never needs the card itself.
Dating sites have two leaks to watch:
- Support channels. Members sometimes type a full card number into an email, a live chat or a contact form when a payment fails. Tell staff never to ask for it, and delete or mask it when it arrives.
- Member messages and profiles. Scammers and confused members paste card details into chat. A filter that masks long card-like numbers protects members and keeps the data out of your logs.
Do not take card payments over the phone or by typing numbers into a dashboard unless you have checked what that does to your scope. It is a different SAQ.
What should a dating site do each year for PCI DSS?
Complete the right SAQ, sign the attestation and check that nothing has changed in how you take payments. A short annual routine covers it.
- Confirm which integration you use and which SAQ your processor says applies.
- List every page and app screen where a member can pay.
- Review the scripts on each payment page and remove any you do not need.
- Check that no card numbers are stored in your database, logs, support desk or backups.
- Confirm who has admin access to the site and the processor account, and that each login uses two-factor authentication.
- Ask your processor whether it needs vulnerability scans from an Approved Scanning Vendor.
- Complete the SAQ and Attestation of Compliance, and keep a copy.
- Repeat the review whenever you change processor, checkout or hosting.
If card data is ever exposed, you will have duties to your acquirer and under data protection law. Our guide to breach response for dating sites covers that, and platform security standards covers security beyond payments.
Who is responsible for PCI DSS on a white label platform?
The platform is, when it takes the payments. On a white label network the platform is the merchant, runs the checkout and deals with the acquirers, so you never handle card data and have no SAQ to file for those payments.
Dating Partners, our sister company run by the same group as this site, handles payments, refunds, chargebacks and fraud screening for its partner sites. It is for dating websites only. DatingAPI, also part of our group, runs payments as part of its platform for dating apps. See our payments and customer care page.
Ask any provider, including ours:
- Who is the merchant of record?
- Can I see your current Attestation of Compliance, and which level does it cover?
- Does any card data ever pass through pages or scripts that I control?
- What may I add to the checkout page, if anything?
If you run your own platform and merchant account, the duty is yours. Our guide to payment processors for dating sites explains approvals, reserves and dispute limits. This page is general information, not legal or security advice; check your obligations with your acquirer or a Qualified Security Assessor.
Questions
Is PCI DSS a law?
No. It is an industry standard. The PCI Security Standards Council says whether a business must comply or validate is decided by the organisations that manage compliance, such as a payment brand or an acquirer, so it reaches you through your processor's contract.
Does using Stripe or another processor make a dating site PCI compliant?
Not on its own. Stripe describes PCI compliance as a shared responsibility: it is certified as a service provider, and the business accepting payments must still do so in a compliant way and attest to that each year.
Can we store the last four digits of a member's card?
Yes. Stripe says the card type, the last four digits and the expiry date are not subject to PCI compliance, so you can keep them to show members which card is on file.
Do in-app purchases on iOS and Android fall under PCI DSS for us?
When a member pays through Apple or Google in-app purchase, the store takes the payment and your app never handles the card. Your own web checkout is still in scope.
What is a QSA?
A Qualified Security Assessor is an independent assessor approved by the PCI Security Standards Council. The largest merchants need one to complete an annual Report on Compliance.
Sources
- PCI Security Standards Council: PCI DSS, checked 21 November 2026
- PCI Security Standards Council: Important updates announced for merchants validating to Self-Assessment Questionnaire A, checked 21 November 2026
- Mastercard Site Data Protection: what merchants need to know, checked 21 November 2026
- Stripe: Integration security guide, checked 21 November 2026
- Stripe: What is PCI DSS compliance?, checked 21 November 2026
- Dating Partners partner terms, checked 21 November 2026
What changed
- : First published. Replaces our older guide on PCI DSS payment security for dating sites.