Answers.Body: <p>Because CiviCRM is open source there is no supplier who you could ask to do this. 
  Basicly it comes down that someone develops the software to work with the new standard. </p>
  
  <p>In Open Source we have a saying that you have to scratch your own itch. Means that if your organisation is dependent on credit card payments and paypal, your organisation has to make sure it keeps working because its your organisation who would suffer.</p>
  
  <p>If you have a developer in your organisation then he or she could do the job. But If you dont have a developer you have to fund a developer to make it working for you.</p>
  
  <p>In this case, there is a likely change that other organisations are also willing to contribute (eg developer resources or funding). But you have to find them and come together. </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-16T08:01:49.783Z
Answers.LastActivityDate: 2019-01-16T08:01:49.783Z
Answers.UserDisplayName: Jaap Jansma - CiviCooP
Answers.Body: <p>Looks like we may have a solution –</p>
  
  <p><a href="https://civicrm.org/blog/eileen/announcing-paypal-checkout" rel="nofollow noreferrer">https://civicrm.org/blog/eileen/announcing-paypal-checkout</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-07-15T08:59:41.520Z
Answers.LastActivityDate: 2019-07-15T08:59:41.520Z
Answers.UserDisplayName: Anil
Body: <p>A couple of clients using PayPal have received an email regarding a new European Union directive.</p>
  
  <p>Some info from the email –</p>
  
  <blockquote>
    <p>As a business accepting card payments, your online checkout will need
    upgrading to comply with a new European Union directive requiring
    Strong Customer Authentication (SCA). The directive applies from 14
    September 2019, but card issuers are working towards SCA by April so
    that their systems are fully operational by the deadline.</p>
    
    <p>Want to know more?</p>
    
    <p>Find out more about PSD2 and check out our guide to integration - 
    <a href="https://www.paypal.com/uk/webapps/mpp/psd2" rel="noreferrer">https://www.paypal.com/uk/webapps/mpp/psd2</a></p>
  </blockquote>
  
  <p>As I understand it, no changes are required if users are redirected from your website to PayPal (hosted payment integration) but changes are required if you accept card payment on the actual website (Direct or in-line payment processors) </p>
  
  <p>PayPal is one of the core payment processors in CiviCRM and the in-line option is now also compatible with webforms so I’m guessing this will affect many.</p>
  
  <p>How do we move forward to be ready by the deadline as transactions will be declined if no action is taken?</p>
  
  <p>I’m guessing this will also affect other in-line payment processors?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-03-01T08:57:38.770Z
Comments.Text: Looks like it’s been raised on lab.civicrm - https://lab.civicrm.org/dev/financial/issues/41
Comments.UserDisplayName: Anil
Tags: <payment-processor><paypal>
Title: PayPal PSD2 - new European Union directive from 14th September 2019
ThreadText: # PayPal PSD2 - new European Union directive from 14th September 2019
  
  (Asked by: username_0 on 2019-01-15)
  
  A couple of clients using PayPal have received an email regarding a new European Union directive.
  
  Some info from the email –
  
  > As a business accepting card payments, your online checkout will need
  > upgrading to comply with a new European Union directive requiring
  > Strong Customer Authentication (SCA). The directive applies from 14
  > September 2019, but card issuers are working towards SCA by April so
  > that their systems are fully operational by the deadline.
  >
  > Want to know more?
  >
  > Find out more about PSD2 and check out our guide to integration -
  > <https://www.paypal.com/uk/webapps/mpp/psd2>
  
  As I understand it, no changes are required if users are redirected from your website to PayPal (hosted payment integration) but changes are required if you accept card payment on the actual website (Direct or in-line payment processors)
  
  PayPal is one of the core payment processors in CiviCRM and the in-line option is now also compatible with webforms so I’m guessing this will affect many.
  
  How do we move forward to be ready by the deadline as transactions will be declined if no action is taken?
  
  I’m guessing this will also affect other in-line payment processors?
  
  **Tags:** payment-processor, paypal
  
  > **Comments:**
  > **username_0**: Looks like it’s been raised on lab.civicrm - https://lab.civicrm.org/dev/financial/issues/41  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2019-01-16. Score: 1
  
  Because CiviCRM is open source there is no supplier who you could ask to do this.
  Basicly it comes down that someone develops the software to work with the new standard.
  
  In Open Source we have a saying that you have to scratch your own itch. Means that if your organisation is dependent on credit card payments and paypal, your organisation has to make sure it keeps working because its your organisation who would suffer.
  
  If you have a developer in your organisation then he or she could do the job. But If you dont have a developer you have to fund a developer to make it working for you.
  
  In this case, there is a likely change that other organisations are also willing to contribute (eg developer resources or funding). But you have to find them and come together.
  
  
  ---
  
  ### Answer by username_0 on 2019-07-15. Score: 1
  
  Looks like we may have a solution –
  
  <https://civicrm.org/blog/eileen/announcing-paypal-checkout>
  
  
  ---
  
  