When your SaaS adds payments, it becomes a service provider
By Sam Rivera, Founder, SentinelPanda · October 20, 2026 · 3 min read · PCI DSS
Payfac-as-a-service made it easy to add payments to a product. It did not make the compliance obligation that arrives with them any smaller.
The change that happens quietly
A vertical SaaS product adds payments because customers want to be paid inside the tool they already use. The commercial logic is excellent and the integration is now straightforward — payfac-as-a-service providers have made it a matter of weeks rather than a licensing project.
What changes at the same time is what the company is, as far as PCI DSS is concerned. Before, it sold software. After, it handles or can affect the security of card data on behalf of other businesses, which is the definition of a service provider.
Merchant and service provider are different roles
A merchant accepts cards for its own sales. A service provider handles card data on behalf of others, or could affect its security. The questionnaires are different, the validation thresholds are different, and the audience for the resulting document is different.
A merchant produces an attestation for its acquirer, once a year, and mostly nobody else reads it. A service provider produces one for every customer who asks, and the asking is continuous, because each customer has their own assessor and their own renewal cycle.
Levels are counted in transactions, not dollars
This is the detail platforms most often get wrong, because the number every platform tracks is gross payment volume. Visa sets its Level 1 service provider threshold at more than 300,000 Visa transactions a year; Mastercard's corresponding figure is higher, and where a business accepts both, the stricter rule applies.
A platform processing a few hundred million dollars in small retail baskets is comfortably past that line, while one processing the same amount in large B2B invoices may not be. Level 1 means an annual on-site assessment by a qualified security assessor rather than a self-assessment, which is a different order of cost and lead time — and it is worth knowing which side you are on well before a customer asks.
What your customers will ask for
- A current attestation of compliance, dated within the last twelve months.
- A shared-responsibility document saying which requirements you cover and which remain theirs.
- Confirmation of what your scope covers — particularly if you have more than one payment path, because a second processor added later is often outside the assessed environment.
The second payment path problem
Platforms rarely stay on one integration. A marketplace gets added, an acquisition arrives with its own processor, a large customer requires a specific gateway. Each of those is a payment path, and an attestation describes the environment that was assessed — not the one you have now.
The practical failure is a platform holding a genuine, current attestation that covers its original product and not the module built last year. It is found during a customer security review, at the worst possible moment in a renewal.
Where to start
Establish which role you hold and at what level, before a customer forces the question. The answer depends on facts you already have: how the card data flows, how many transactions a year go through it, and how many distinct payment paths exist.
If you are also pursuing SOC 2, the overlap is worth knowing — the evidence gathering is largely shared, and the card questionnaire is usually the cheaper half to complete first.