PCI DSS Responsibility Matrix

Last updated: October 31, 2026

1. Purpose

PCI DSS requirement 12.8 requires every merchant to manage its third-party service providers (TPSPs), and 12.9 requires providers to acknowledge their responsibilities in writing. This matrix is Darkstar's written acknowledgment. It is designed to drop into an acquirer, ISO, or processor underwriting file alongside the connected processor's own AOC.

Roles: D = Darkstar (checkout and CRM platform). P = connected processor / gateway (Whop, Stripe, or an NMI-based merchant account). M = the merchant. "N/A (SAQ A)" = requirement does not apply to a fully hosted, fully outsourced card flow, which is the standard Darkstar configuration.

2. Matrix

Build and maintain secure networks and systems

Req.RequirementPDM
1.1/1.2Network controls and secure configuration (processor and hosting environments)YesYes (Railway managed)N/A (SAQ A)
1.3/1.5Firewall / network segmentation for the CDEYesYes (Railway isolation)N/A (SAQ A)
2.xSecure configurations for system componentsYesYesN/A (SAQ A)
2.4Inventory of in-scope componentsYesYesN/A (SAQ A)
2.5Bash/crypto management of non-user accountsYesYesN/A (SAQ A)

Protect account data

Req.RequirementPDM
3.1Data retention and disposal policy for cardholder dataYesYes (tokens kept while subscribed; merchant-gateway card data kept while a business need exists)Aware (policy reference)
3.2PAN rendered unreadable / not storedYes (vaulted)Yes (tokens only on processor paths; PAN encrypted at rest on merchant-gateway stores)N/A (SAQ A on processor paths)
3.3/3.4Sensitive authentication data (magnetic stripe, PIN) - not applicable to a card-not-present web checkoutYes (validated at authorization)Not applicable (no magnetic stripe or PIN can exist on a web checkout)N/A (SAQ A on processor paths)
3.5Encryption keys for stored account dataYesHosting provider (managed DB) / Darkstar for merchant-gateway stored card dataN/A (SAQ A on processor paths)

Vulnerability management

Req.RequirementPDM
5.xMalware protection on systems in the CDEYesYes (managed hosting)Own endpoint devices
5.3.6Cryptographic software and libraries kept currentYesYes (patched Node runtime and TLS stack)N/A (SAQ A)
6.xSecure development and change controlYesYes (reviewed deploys)N/A (SAQ A)
6.4.3Payment page script authorization and integrityYes (their scripts)Yes (checkout scripts SRI/nonce-controlled)Storefront scripts: M
11.6.1Payment page change (header/script) detectionYesYes (checkout controlled, external monitors)N/A (SAQ A)
11.xScanning and pen testing of the CDEYes (ASV scans)Yes (application layer)N/A (SAQ A)

Access control and authentication

Req.RequirementPDM
7/8.xRole-based access, unique IDs, MFA on CDE accessYesYes (dashboard roles, 2FA available)Own dashboard users
8.3.xPasswords, lockout, session controlYesYes (bcrypt, rate limiting, httpOnly cookies)Own credentials
9.xPhysical security of systemsYesYes (cloud, no card data on premises)Own devices and premises

Testing and governance

Req.RequirementPDM
10.xLogging and monitoring of access to account dataYesYes (audit trail)N/A (SAQ A)
12.8TPSP management (list, due diligence, AOCs)Yes (provides AOC)Yes (provides this matrix)Yes (primary owner)
12.9TPSP written acknowledgment of responsibilitiesYesYes (this page)Collect from P and D
12.10Incident response planYesYesNotify customers if affected
A1Multi-tenant provider requirements (if applicable)YesYesN/A

For merchants using a manual merchant-gateway (NMI) path where the card passes through the checkout server and is stored encrypted as the merchant's service provider, rows marked "N/A (SAQ A)" become "Applies" to the Darkstar checkout CDE, and Darkstar provides the evidence (encryption, access controls, export logging). Your QSA should validate that path as SAQ A-EP / SAQ D territory or accept the token-first variant we offer.

3. Evidence Darkstar provides

  • This responsibility matrix (this page, dated).
  • Architecture description: checkout pages fully hosted on Darkstar pay domains, card fields rendered by processor components on processor paths; merchant-gateway stores store PAN encrypted at rest with Darkstar as service provider.
  • Current AOC / attestation for each connected processor (from the processor, on request).
  • SAQ A eligibility statement per store, in writing, on request.
  • Security control summary on the Security page.

Request any of these from compliance@darkstarpay.com.