Answers.Body: <p>It might not be too hard to implement the omnipay version, there's a contributed plugin for that here: <a href="https://packagist.org/packages/ryanthompson/omnipay-square" rel="nofollow noreferrer">https://packagist.org/packages/ryanthompson/omnipay-square</a></p>
  
  <p>If you want to take this route, here's how it might look [thanks petednz for the prod].</p>
  
  <ol>
  <li><p>Read my old wiki entry here: <a href="https://wiki.civicrm.org/confluence/display/CRMDOC/Omnipay" rel="nofollow noreferrer">https://wiki.civicrm.org/confluence/display/CRMDOC/Omnipay</a>
  as a general introduction to what omnipay is.</p></li>
  <li><p>Get a copy of the omnipay payment processor extension. The extension home is here: <a href="https://civicrm.org/extensions/omnipay-multiprocessor-extension" rel="nofollow noreferrer">https://civicrm.org/extensions/omnipay-multiprocessor-extension</a>
  But you'll want to clone it from the repo here:
  <a href="https://github.com/eileenmcnaughton/nz.co.fuzion.omnipaymultiprocessor" rel="nofollow noreferrer">https://github.com/eileenmcnaughton/nz.co.fuzion.omnipaymultiprocessor</a></p></li>
  <li><p>Add the omnipay-square plugin to the omnipay payment processor exentsion. Yes, this is the hard part. There is a simple note here:
  <a href="https://github.com/eileenmcnaughton/nz.co.fuzion.omnipaymultiprocessor/blob/master/README.md" rel="nofollow noreferrer">https://github.com/eileenmcnaughton/nz.co.fuzion.omnipaymultiprocessor/blob/master/README.md</a>
  I found that it was most instructive to look at some examples.</p></li>
  </ol>
  
  <p>A few things I found helpful were:</p>
  
  <p>a. Learn about composer if you don't already know about it. Don't skip this step or you'll get confused.</p>
  
  <p>b. You have two routes if the omnipay plugin doesn't just work out of the box - either contribute your modifications back to the original project and keep it as the source of the plugin (possibly from your forked repo), or you can fork the original and create it as a separate project. The first one is usually the right answer, particularly if the existing plugin looks like it's going to be maintained. There are some confusing bits in terms of the vendor paths and git sources in the composer file that you'll have to figure out to sort this out.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-11-01T18:58:36.013Z
Answers.Text: Good suggestion. Would the answer benefit from having a bit more info adding about omnipay eg https://wiki.civicrm.org/confluence/display/CRMDOC/Omnipay and the extension at https://civicrm.org/extensions/omnipay-multiprocessor-extension
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-06-14T20:26:35.827Z
Answers.Text: The omnipay-square plugin seems to be taken down. It no longer exists on Packagist nor Github. Has it been moved, or taken down completely?
Answers.UserDisplayName: Demonslay335
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-11-01T18:16:05.320Z
Answers.LastActivityDate: 2016-11-04T14:04:34.067Z
Answers.LastEditDate: 2016-11-04T14:04:34.067Z
Answers.UserDisplayName: Alan Dixon
Body: <p>Is anyone developing the interface needed for using <a href="https://squareup.com" rel="nofollow">Square</a> as a payment processor?</p>
  
Tags: <civicontribute><payment-processor>
Title: Is there a CiviCRM payment processor extension to support Square?
ThreadText: # Is there a CiviCRM payment processor extension to support Square?
  
  (Asked by: username_0 on 2016-10-31)
  
  Is anyone developing the interface needed for using [Square](https://squareup.com) as a payment processor?
  
  **Tags:** civicontribute, payment-processor
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-11-01. Score: 3
  
  It might not be too hard to implement the omnipay version, there's a contributed plugin for that here: <https://packagist.org/packages/ryanthompson/omnipay-square>
  
  If you want to take this route, here's how it might look [thanks petednz for the prod].
  
  1. Read my old wiki entry here: <https://wiki.civicrm.org/confluence/display/CRMDOC/Omnipay>
     as a general introduction to what omnipay is.
  2. Get a copy of the omnipay payment processor extension. The extension home is here: <https://civicrm.org/extensions/omnipay-multiprocessor-extension>
     But you'll want to clone it from the repo here:
     <https://github.com/eileenmcnaughton/nz.co.fuzion.omnipaymultiprocessor>
  3. Add the omnipay-square plugin to the omnipay payment processor exentsion. Yes, this is the hard part. There is a simple note here:
     <https://github.com/eileenmcnaughton/nz.co.fuzion.omnipaymultiprocessor/blob/master/README.md>
     I found that it was most instructive to look at some examples.
  
  A few things I found helpful were:
  
  a. Learn about composer if you don't already know about it. Don't skip this step or you'll get confused.
  
  b. You have two routes if the omnipay plugin doesn't just work out of the box - either contribute your modifications back to the original project and keep it as the source of the plugin (possibly from your forked repo), or you can fork the original and create it as a separate project. The first one is usually the right answer, particularly if the existing plugin looks like it's going to be maintained. There are some confusing bits in terms of the vendor paths and git sources in the composer file that you'll have to figure out to sort this out.
  
  > **Comments:**
  > **username_2**: Good suggestion. Would the answer benefit from having a bit more info adding about omnipay eg https://wiki.civicrm.org/confluence/display/CRMDOC/Omnipay and the extension at https://civicrm.org/extensions/omnipay-multiprocessor-extension  
  > **username_3**: The omnipay-square plugin seems to be taken down. It no longer exists on Packagist nor Github. Has it been moved, or taken down completely?  
  
  ---
  
  