# PCI compliance for Stripe Terminal

PCI validation for in-person payments works differently than online payments. For in-person payments like those collected through Stripe Terminal, you must validate using the SAQ C template.
If you integrate with Stripe using additional e-commerce methods, you also need to validate your PCI compliance against these transaction types. See the [guide to PCI compliance](https://stripe.com/guides/pci-compliance).
You can also view your PCI requirements at any time in the Dashboard under [Compliance Settings](https://dashboard.stripe.com/settings/compliance).
## End-to-end encryption (E2EE)
Stripe Terminal provides E2EE by default.
If you're a PCI Level 2 to 4 user, a pre-filled SAQ C document for Terminal transactions is available in your [Dashboard](https://dashboard.stripe.com/settings/compliance) under **Compliance Settings**.
## Point-to-point encryption (P2PE)
If you're a PCI Level 2 to 4 user who's signed up for Stripe Terminal P2PE, Stripe provides a pre-filled SAQ P2PE document for Terminal transactions is available in your Dashboard under **Compliance Settings**.
Read more about P2PE.
## Validation requirements based on transaction volume
PCI requirements apply to you depending on the number of transactions, both online and in-person, that you process annually per card brand.
If you process more than 6 million Visa or Mastercard transactions, or more than 2.5 million Amex transactions, or are otherwise classified as Level 1 by any of the card networks, you must go through a more detailed PCI compliance process.
Stripe monitors your transaction volume and notifies you before reaching the 6 million Level 1 threshold so you have time to prepare for full PCI DSS validation. For Level 1 merchants, Stripe provides a PCI packet that helps reduce PCI validation time from months to days. If you need a PCI Qualified Security Assessor (QSA), Stripe can connect you with auditors who are familiar with Stripe’s integration methods.