PCI DSS Scope
A factual description of how card payments are handled by this platform, and what that means for PCI DSS scope. This is written from the actual payment code, not from a general statement of intent.
1. How card data is actually handled
The platform never receives a card number, CVV, or expiry date. When a customer pays, they are sent to a payment page hosted entirely by Stripe. That page is created by a request from our server to Stripe's API, Stripe returns a URL, and the customer's browser is redirected to it in full. Card details are typed directly into Stripe's own page and go straight to Stripe. They never pass through, or get logged by, our servers, our database, or our application code at any point.
This is true for every payment flow in the system:
- A new customer subscribing to a plan.
- An existing customer changing plans through the customer portal.
- A one-time payment collected from a qualified lead by the Payment Bot.
2. What is stored in our database
The following Stripe-related identifiers are stored, none of which are card data:
| Field | What it is |
|---|---|
| Stripe Customer ID | An opaque reference to the customer record inside Stripe. |
| Stripe Subscription ID | An opaque reference to the active subscription inside Stripe. |
| Stripe Checkout Session ID | An opaque reference to a completed checkout session. |
| Stripe Payment Intent ID | An opaque reference to a specific payment attempt. |
None of these identifiers can be used outside of our own Stripe account to retrieve a card number. No card brand, last-four digits, expiry date, cardholder name, or card fingerprint is stored anywhere in the database.
3. Webhook authenticity
Stripe notifies the platform of events (a successful payment, a subscription change, a dispute) through a webhook. Every webhook request's signature is verified against the raw request body using the shared webhook signing secret before the event is trusted. A request with an invalid or missing signature is rejected outright.
4. What this means for PCI DSS scope
Because card data is never received, transmitted, or stored by this platform's servers, application code, or database, at any point, the applicable self-assessment path for a merchant using this architecture is typically SAQ A, the shortest questionnaire, reserved for merchants who have fully outsourced all cardholder-data handling to a redirect-based, PCI-validated third party.
- This platform's own infrastructure is not in scope for the cardholder-data-environment requirements that apply to a merchant handling card numbers directly.
- The actual SAQ type, and whether SAQ A specifically applies to your account, is confirmed by your acquiring bank or payment processor based on your merchant configuration, not by this document.
- If your business later adds a card-entry method that is not a redirect to Stripe (an embedded card form, a phone/manual-entry flow, a stored-card feature), that change would move this determination and would need to be reassessed before launch.
5. Related documentation
- SOC 2 Overview: the broader security-controls picture this scope determination sits inside.
- Billing: how the Checkout session and subscription lifecycle work end to end.
- Compliance: data handling, KYC/AML, and the remaining legal/compliance items.
Was this page helpful?