CiviCRM Community > CiviCRM Jobs

LinkPoint / First Data Global Gateway Support

(1/6) > >>

Scott M. Stolz:
We have a non-profit that needs support for the First Data Global Gateway (formerly called LinkPoint).

They specifically need support for the Global Gateway API (also known as the LinkPoint API).

http://www.firstdata.com/linkpoint/
http://www.firstdata.com/support/manuals_and_guides/global_gateway.htm

I am willing to pay for someone to develop the module if the price is reasonable.

A couple things to keep in mind include:


* This module is needed for a 501(c)(3) non-profit organization to accept donations through CivCRM's CiviDonate module.
* The module will be donated to the entire CiviCRM community.
* It should be built to such a standard that CiviCRM Developers would consider adding this module to CiviCRM core (like PayPal and Google Checkout and Authorize.NET, etc.).
.
Please send me a private message and/or post here so I may respond.  Thank you.

Scott M. Stolz:
If anyone would like to chip in and help get this module created, it would be greatly appreciated.

Eileen:
I've worked on a payment processor for civicrm so I'll take a look later today if I get the chance and see how much is involved. In my experience getting the developer account organised can be a big hassle with payment processors at times

Eileen:
I've taken a poke around their site and there is a fair range of methods & options available with that processor. The simplest secure option is Connect - them hosting the payments page which means it doesn't matter whether the civicrm site has an SSL cert. Basic transaction data is transmitted by un-encrypted http but not credit card data (this is similar to Paypal Express in functionality & security but hopefully better in terms of customer experience). This option works for single & recurring transactions but only for credit cards as far as I can see.  They actually seem to allow you to collect credit card data with this method and post it unencrypted to them - this might look better to the customer but is not adequately secure in my mind

The other main option is the API which means you can collect credit card data on the civi site & send it encrypted to their site. If you don't want the customer to be redirected to the processor this is the way to go. The virtual check (bank account debit) functionality only works in conjunction with the API method

The documentation they provide is pretty hard going.

So, the time required (and hence cost) would depend a bit on

* whether you wanted the credit card data to be collected on the civiCRM site & sent to the processor (more complex & requires an SSL cert).
* Whether you wanted virtual check functionality
* Whether you wanted recurring contribution functionality
I assume by civiDonate you mean civiContribute?

Eileen:
Ah - just read that you specify the API.

The questions about recurring payments and virtual check still remain though

Navigation

[0] Message Index

[#] Next page