PCI DSS Compliance

Last updated: October 31, 2026

1. Overview

The Payment Card Industry Data Security Standard (PCI DSS) is a global standard owned by the card brands (Visa, Mastercard, American Express, Discover, JCB). Any business that accepts card payments must comply with it, and so must every service provider it uses. Darkstar is designed so that our merchants validate at the lowest possible scope: SAQ A.

Darkstar is not a bank and is not a payment processor. We are a CRM and checkout platform that routes each charge to the processor a merchant connects (Whop, Stripe, or an NMI-based merchant account). On processor-hosted paths, cardholder data is captured, vaulted, and charged by those PCI DSS validated providers and Darkstar stores only tokens and display metadata. On the merchant-gateway path, Darkstar acts as the merchant's service provider: card data is submitted through our hosted checkout, stored encrypted, and vaulted with the merchant's own gateway to support rebills, renewals, recovery, and processor migration.

In PCI DSS terms, Darkstar is a service provider to its merchants (and, for merchant-gateway stores, a card-data-storage service provider). Acquiring, authorization, and settlement sit with the connected processors, their sponsor banks, and the card networks. Darkstar does not acquire transactions, is not an acquiring bank, and is not itself a payment processor or payment facilitator.

2. Card data by processing path

PCI DSS distinguishes cardholder data (PAN, cardholder name, expiration, service code) and sensitive authentication data (full magnetic stripe, PIN or PIN block). On a card-not-present web checkout, magnetic stripe and PIN data cannot exist; what the checkout collects is entered by the buyer into the payment fields.

DataWhere it livesDarkstar access
Full card number (PAN)Processor vault (Whop, Stripe, NMI); on merchant-gateway stores, also stored encrypted by Darkstar as service providerStored encrypted for merchant-gateway stores; tokens otherwise
Card tokenProcessor vault; token ID mirrored in DarkstarToken ID only
Brand, last 4 digits, expiryDarkstar database (display and routing)Yes, non-sensitive metadata
Buyer name, address, order dataDarkstar databaseYes

On the hosted checkout, card fields render inside processor-controlled components (Whop card fields, Stripe Elements, Whop Elements express wallets for Apple Pay and Google Pay). The browser posts the card to the processor first; Darkstar receives a token. On the merchant-gateway (NMI) path, the card is charged and vaulted in the NMI Customer Vault in the same transaction; Darkstar stores the resulting customer_vault_id token.

3. Shared responsibilities

Using Darkstar does not remove a merchant's own PCI obligations. It reduces them. The matrix below follows the same structure NMI and other gateways publish for their partners.

Control areaDarkstarMerchant
Checkout page hostingResponsible (pay domain, TLS, headers)Provide the domain and DNS
Payment fields and iframe securityProcessor (Whop / Stripe / NMI)Confirm processor compliance annually
Token vault and card storage (processor paths)ProcessorChoose connected processors
Stored card data (merchant-gateway path)Darkstar as service provider (encrypted, access-controlled, logged)Owner of the data; may request export
SAQ completion and attestationSupport with evidenceResponsible (SAQ A on processor paths; higher on merchant-gateway paths - we confirm per store)
Storefront page and its scriptsMerchantResponsible
Physical security of systemsDarkstar and its hosting providersOwn devices and credentials

4. Your PCI scope as a Darkstar merchant

SAQ A eligibility

Merchants using the Darkstar hosted checkout on processor-hosted paths (Whop, Stripe) validate with SAQ A when all of the following hold:

  • All processing of account data is entirely outsourced to PCI DSS compliant third-party providers.
  • The merchant does not electronically store, process, or transmit account data on its own systems.
  • All elements of the payment page delivered to the consumer's browser originate from a PCI DSS compliant provider (the checkout is fully hosted on the Darkstar pay domain, and card fields come from the processor).
  • The merchant has confirmed the processor's compliance (see section 5).

If your storefront collects card data on its own pages before handing off to Darkstar, or your integration receives card numbers on your server, your scope rises (SAQ A-EP or SAQ D). Ask us and your QSA before building it that way.

Higher-scope paths we support

The Darkstar merchant-gateway (NMI) path sends the card from the checkout to the gateway and stores it encrypted with Darkstar as your service provider; merchants on this path typically validate at SAQ A-EP or SAQ D, and Darkstar supports the assessment with evidence of encryption, access controls, and logging. Where your acquirer or QSA requires it, a lighter integration (token-first via the processor collection library) keeps you in SAQ A. We will tell you which path a store uses, in writing, so your attestation is accurate.

5. Connected processors and their validation

Darkstar routes payments only to processors a merchant connects under Connections. Each provider below is responsible for its own PCI DSS validation as a service provider. Presence on the Visa Global Registry of Service Providers or the Mastercard Compliant Service Provider List is the baseline a merchant should confirm annually.

ProcessorRoleMerchant verification
WhopCard fields, express wallets, vaulting, acquiring on managed accountsAnnual AOC / registry listing
StripeStripe Elements tokenization and acquiringAnnual AOC / registry listing
NMI and NMI-based merchant accountsGateway, Customer Vault tokenizationAnnual AOC / registry listing
Darkstar gateway (partner MIDs)Routing only; vault stays on the underlying processorUnderlying processor AOC

NMI maintains PCI DSS Level 1 certification as a service provider and publishes a PCI DSS responsibility matrix for partners and merchants. Stripe and Whop likewise validate annually as Level 1 service providers. When you connect a different gateway, request its AOC and add it to your own TPSP list (PCI DSS requirement 12.8).

6. How Darkstar secures the checkout

Darkstar is built to the PCI DSS principles even where the requirement formally sits with the processor, because the pay domain is ours to run:

  • HTTPS everywhere with TLS 1.2+; HSTS with preload on every public page.
  • Strict Transport Security, X-Content-Type-Options nosniff, Referrer-Policy strict-origin-when-cross-origin, and a Permissions-Policy that disables camera, microphone, and geolocation on checkout.
  • Nonce-based Content-Security-Policy with strict-dynamic on operator surfaces; API responses ship a deny-all CSP and X-Frame-Options DENY.
  • Checkout pages are served no-store so no card-entry page is ever cached.
  • On processor-hosted paths, card fields are processor components; on merchant-gateway paths the card is posted once from the hosted checkout over TLS.
  • JWT session cookies are httpOnly, Secure, and SameSite=Lax; passwords are bcrypt hashed.
  • Login rate limiting, role-based access per store, and audit logs in the CRM.
  • Database credentials and processor keys live in environment variables; processor secrets are never rendered to the browser.

7. Tokenization and portability

Every card that can be rebilled is vaulted by the processor and referenced by a token. Tokens Darkstar stores are processor references (for example an NMI customer_vault_id or a Whop payment id), not PANs, so a token in the CRM cannot be used to derive the card number. On merchant-gateway stores, Darkstar additionally stores the card number and expiration date encrypted, as the merchant's service provider, to run rebills and to move the store's cards between its own connected processors on request.

Tokens belong to the merchant. On request, and at termination, we export the vault data (brand, last 4, expiry, billing address, and the vault reference the receiving processor needs), and for merchant-gateway stores the stored card data itself (card number and expiration date), to a processor or vault you choose, at no additional cost. See the Terms of Service for the contractual guarantee.

8. Vulnerability management and monitoring

  • Dependencies are patched continuously; security releases are deployed on disclosure.
  • Hosting on Railway provides infrastructure-level patching, isolation, and encrypted Postgres.
  • Checkout uptime and latency are measured from outside the platform and published on the SLA page.
  • Authentication events, permission changes, and payout-relevant actions are logged in the CRM audit trail.
  • An annual internal review walks the PCI DSS v4.x principles against the current architecture.

9. Incident response

If account data could be affected, we notify affected merchants within 72 hours of confirming an incident, with what happened, what data, and what we did. For stores on processor-hosted paths, the blast radius of a CRM-only incident is metadata (order, buyer, token reference), not card numbers; for merchant-gateway stores, stored card data is encrypted at rest and access is logged.

Incidents at a connected processor are the processor's to report under their own program; we will relay what we know and help you reconcile affected orders.

10. Questions underwriters ask

QuestionAnswer
Is Darkstar a bank or a payment processor?No. Darkstar is a CRM and checkout platform (software). Acquiring, authorization, settlement, and payouts are performed by the processors and merchant accounts each merchant connects - Whop, Stripe, or an NMI-based gateway - and their sponsor banks. Darkstar routes charges to those processors on the merchant's instructions.
Is Darkstar PCI DSS Level 1 certified?The card-handling components Darkstar uses are Level 1 validated providers (Whop, Stripe, NMI). Darkstar itself operates as the checkout and CRM layer; on merchant-gateway stores it additionally acts as the merchant's card-storage service provider with encryption, access controls, and logging.
Do you store card numbers?On processor-hosted paths (Whop, Stripe), no - only processor tokens and display metadata (brand, last 4, expiry). On merchant-gateway (NMI) stores, yes - stored encrypted, as the merchant's service provider, for rebills, recovery, and processor migration.
What is our SAQ?SAQ A for fully hosted checkout on processor paths; SAQ A-EP or SAQ D on merchant-gateway paths. We confirm the path per store in writing.
Can you sign our PCI questionnaire?We complete the service-provider sections and provide evidence on request.
Are you on the Visa / Mastercard registries?The processors we route to are. Registry status for a specific gateway should be confirmed at onboarding and annually.