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. | Requirement | P | D | M |
|---|---|---|---|---|
| 1.1/1.2 | Network controls and secure configuration (processor and hosting environments) | Yes | Yes (Railway managed) | N/A (SAQ A) |
| 1.3/1.5 | Firewall / network segmentation for the CDE | Yes | Yes (Railway isolation) | N/A (SAQ A) |
| 2.x | Secure configurations for system components | Yes | Yes | N/A (SAQ A) |
| 2.4 | Inventory of in-scope components | Yes | Yes | N/A (SAQ A) |
| 2.5 | Bash/crypto management of non-user accounts | Yes | Yes | N/A (SAQ A) |
Protect account data
| Req. | Requirement | P | D | M |
|---|---|---|---|---|
| 3.1 | Data retention and disposal policy for cardholder data | Yes | Yes (tokens kept while subscribed; merchant-gateway card data kept while a business need exists) | Aware (policy reference) |
| 3.2 | PAN rendered unreadable / not stored | Yes (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.4 | Sensitive authentication data (magnetic stripe, PIN) - not applicable to a card-not-present web checkout | Yes (validated at authorization) | Not applicable (no magnetic stripe or PIN can exist on a web checkout) | N/A (SAQ A on processor paths) |
| 3.5 | Encryption keys for stored account data | Yes | Hosting provider (managed DB) / Darkstar for merchant-gateway stored card data | N/A (SAQ A on processor paths) |
Vulnerability management
| Req. | Requirement | P | D | M |
|---|---|---|---|---|
| 5.x | Malware protection on systems in the CDE | Yes | Yes (managed hosting) | Own endpoint devices |
| 5.3.6 | Cryptographic software and libraries kept current | Yes | Yes (patched Node runtime and TLS stack) | N/A (SAQ A) |
| 6.x | Secure development and change control | Yes | Yes (reviewed deploys) | N/A (SAQ A) |
| 6.4.3 | Payment page script authorization and integrity | Yes (their scripts) | Yes (checkout scripts SRI/nonce-controlled) | Storefront scripts: M |
| 11.6.1 | Payment page change (header/script) detection | Yes | Yes (checkout controlled, external monitors) | N/A (SAQ A) |
| 11.x | Scanning and pen testing of the CDE | Yes (ASV scans) | Yes (application layer) | N/A (SAQ A) |
Access control and authentication
| Req. | Requirement | P | D | M |
|---|---|---|---|---|
| 7/8.x | Role-based access, unique IDs, MFA on CDE access | Yes | Yes (dashboard roles, 2FA available) | Own dashboard users |
| 8.3.x | Passwords, lockout, session control | Yes | Yes (bcrypt, rate limiting, httpOnly cookies) | Own credentials |
| 9.x | Physical security of systems | Yes | Yes (cloud, no card data on premises) | Own devices and premises |
Testing and governance
| Req. | Requirement | P | D | M |
|---|---|---|---|---|
| 10.x | Logging and monitoring of access to account data | Yes | Yes (audit trail) | N/A (SAQ A) |
| 12.8 | TPSP management (list, due diligence, AOCs) | Yes (provides AOC) | Yes (provides this matrix) | Yes (primary owner) |
| 12.9 | TPSP written acknowledgment of responsibilities | Yes | Yes (this page) | Collect from P and D |
| 12.10 | Incident response plan | Yes | Yes | Notify customers if affected |
| A1 | Multi-tenant provider requirements (if applicable) | Yes | Yes | N/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.