Answers.Body: <p>The Stripe development team has upgraded the code of the extension to support the new API that is PCI compliant.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-29T18:39:43.583Z
Answers.LastActivityDate: 2020-02-29T18:39:43.583Z
Answers.UserDisplayName: Scott Pulver
Body: <p>I am using the latest version of the Stripe extension (5.2) and have CiviCRM up-to-date and Drupal. I'm getting this error in my Stripe portal, I only use Stripe with CiviCRM. Can anyone provide some insight? Was not sure if i should post this here or at <a href="https://lab.civicrm.org/extensions/stripe/issues" rel="noreferrer">https://lab.civicrm.org/extensions/stripe/issues</a></p>
  
  <p><a href="https://i.sstatic.net/zSmAJ.png" rel="noreferrer"><img src="https://i.sstatic.net/zSmAJ.png" alt="enter image description here"></a></p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-01-07T23:50:00.067Z
Comments.Text: Has Stripe changed its policy recently? [Previously it stated](http://web.archive.org/web/20170120013605/https://stripe.com/docs/security) that "As long as you serve your payment pages over TLS, and use either Checkout or Stripe.js as the only way of handling card information, Stripe automatically creates a prefilled SAQ A questionnaire for you, and you won’t need to undergo a PCI audit". But now that page states for Stripe.js v2 (which the extension uses) it states "Requirement: SAQ A-EP" (unless using Elements with Stripe.js).
Comments.UserDisplayName: Andrew Thompson
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-01-08T00:17:41.710Z
Comments.Text: See also https://www.drupal.org/project/uc_stripe/issues/2959726
Comments.UserDisplayName: Andrew Thompson
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-03-01T19:36:51.393Z
Comments.Text: You say "I am using the latest version of the Stripe extension (5.2)" but the latest Release is 6.3.2 - can you clarify in your Question
Comments.UserDisplayName: petednz - fuzion
Tags: <drupal><civicontribute><payment-processor><stripe>
Title: CiviCRM Stripe PCI Compliance
ThreadText: # CiviCRM Stripe PCI Compliance
  
  (Asked by: username_0 on 2018-12-28)
  
  I am using the latest version of the Stripe extension (5.2) and have CiviCRM up-to-date and Drupal. I'm getting this error in my Stripe portal, I only use Stripe with CiviCRM. Can anyone provide some insight? Was not sure if i should post this here or at <https://lab.civicrm.org/extensions/stripe/issues>
  
  [![enter image description here](https://i.sstatic.net/zSmAJ.png)](https://i.sstatic.net/zSmAJ.png)
  
  **Tags:** drupal, civicontribute, payment-processor, stripe
  
  > **Comments:**
  > **username_1**: Has Stripe changed its policy recently? [Previously it stated](http://web.archive.org/web/20170120013605/https://stripe.com/docs/security) that "As long as you serve your payment pages over TLS, and use either Checkout or Stripe.js as the only way of handling card information, Stripe automatically creates a prefilled SAQ A questionnaire for you, and you won’t need to undergo a PCI audit". But now that page states for Stripe.js v2 (which the extension uses) it states "Requirement: SAQ A-EP" (unless using Elements with Stripe.js).  
  > **username_1**: See also https://www.drupal.org/project/uc_stripe/issues/2959726  
  > **username_2**: You say "I am using the latest version of the Stripe extension (5.2)" but the latest Release is 6.3.2 - can you clarify in your Question  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2020-02-29. Score: 1 | Accepted answer
  
  The Stripe development team has upgraded the code of the extension to support the new API that is PCI compliant.
  
  
  ---
  
  