<i>Most organizations utilize third parties to handle credit card info so they don&#x27;t have to be PCI compliant.</i><p>That&#x27;s not true.  If you enable payment by credit card <i>at all</i>, you&#x27;re subject to PCI.  Even a SAQ A[1] category merchant (payment page entirely hosted and managed by a PCI-compliant, third-party payment processor) are required to formally confirm that their processor is currently PCI compliance, have written rules of engagement with the processor and obey the PCI data handling and retention requirements.  And if you embed your payment page in your own page (technically, if any part of the payment page is served from your site and not the processors site) then you&#x27;re a SAQ-AP merchant[2], and you&#x27;ll be expected to conform to a lot more of the standard.<p>[1] <a href="https:&#x2F;&#x2F;www.pcisecuritystandards.org&#x2F;documents&#x2F;Understanding_SAQs_PCI_DSS_v3.pdf" rel="nofollow">https:&#x2F;&#x2F;www.pcisecuritystandards.org&#x2F;documents&#x2F;Understanding...</a>
[2] <a href="https:&#x2F;&#x2F;www.clerkendweller.uk&#x2F;2014&#x2F;3&#x2F;7&#x2F;PCIDSS-SAQ-AEP-and-SAQ-A-Comparison-of-Questions" rel="nofollow">https:&#x2F;&#x2F;www.clerkendweller.uk&#x2F;2014&#x2F;3&#x2F;7&#x2F;PCIDSS-SAQ-AEP-and-SA...</a>