[ic] Payflow setup

[Zac Reilly]

Are Dave Totten's directions, (below), current for ic 4.8.3? I examined the
payflow pro sdk and all the files still appear to retain the same names.
Thanks to whoever put the link up a few says ago.

>You are in luck. I have updated my previous attempt at documenting how
>to set this up in interchange 4.6.5, so that it describes how to set it
>up in interchange 4.8.2. I hope it helps.
>
Any feedback on this file is more than welcome.
>Dave Totten
>--
>___________________________________________________________________
>GnuPG uid: 0x887B864C
>Key fingerprint: 749E E8A9 E905 7372 163B  2D19 E8D6 4BA9 887B 864C
>For more information about GnuPG, visit http://www.gnupg.org
>
--=-ZvIUpehq+30iawJuligE
>Content-Type: text/plain
>Content-Disposition: attachment; filename=signio_482.txt
>Content-ID: <1001529657.10696.5.camel@pred>
>Content-Transfer-Encoding: 7bit
>
How to configure interchange 4.8.2 to use VeriSign/Signio's Payflow Pro
version
>3.0 as your default payment gateway.
>
Introduction:
>      The aim of this document is to explain what was necessary for me
>   to get VeriSign/Signo set up as my payment gateway. At the time
>   of this writing, I was using interchange 4.8.2 and the Payflow
>   Pro SDK version 3.00
>
Assumptions:
>      In order to procede with this document, you must be able to browse
both
>   the customer and admin interfaces of your interchange store.
>
Definitions:
>      In order to facilitate my instructions a little bit, I am going to
>   define a few variables that I will use in this document.
>
   $VENDROOT is a variable that defines where the makecat and interchange
>   binaries are located. In my installation (from the tarball) it is
located
>   at /home/interch/interchange.
>
   $SRCROOT is the directory where I uncompress the interchange tarball. In
>   my situation it is ~/home/interch/src/interchange-4.8.2.
>
   $CATROOT is the directory where my catalog is stored. In my installation,
>   it is ~/home/interch/catalogs/ic_482/
>
>Getting The Payflo Pro SDK
>      After getting your Payflo Pro account set up, log in to your account
>   at https://manager.verisign.com. Remember what you had to use here for
the
>   Partner, Login, and Password fields. They will be needed later in this
>   document. Once logged in, click the link towards the top of your screen
that
>   says download.
>      Under the section labeled Payflow Pro Software Development Kit (SDK),
>   will be a link for your operating system. I used the Linux version.
>      Once you have downloaded the software, uncompress it. I uncompressed
>   the file in my interchange users directory /home/interch/.  You should
>   now have a new subdirectory named verisign.
>      I changed directories to /home/interch/verisign/payflowpro/linux/lib.
>   The file libpfpro.so needs to be copied into $VENDROOT/lib. This may
>   require root access on your system, depending on how it is set up.
>      Next I changed directories to
/home/interch/verisign/payflowpro/linux/bin.
>   The file pfpro needs to be copied into $VENDROOT/bin.
>      The last file that needs to be moved is found in
>   /home/interch/verisign/payflowpro/linux/certs. It's a file named
f73e89fd.0.
>   first you need to make a directory in $VENDROOT/lib called certs. Then
this
>   file gets copied into the certs directory.
>
Making the Payflow Pro SDK work with Interchange
>      In order for interchange to know that you want to make the signio
>   module your default payment gateway, there are some things that we must
>   do.
>      First, edit $VENDROOT/interchange.cfg. On the last line, add the
>   the following:
>
>   Require module Vend::Payment::Signio
>
      Next we need to set up some variables in
$CATROOT/products/variables.txt.
>   Things that you must know for this section include:
>
>   VeriSign Login
>   VeriSign Password
>   VeriSign Partner
>
      We need to define these with the following lines in your variables.txt
>   file. ***** IMPORTANT ***** Remember that the space between each item in
a
>   line, is a tab not a space. We will be forming 3 columns on each line,
and
>   they go in this format.
>
>   VARIABLE_NAME<TAB>VARIABLE_VALUE<TAB>VARIABLE_CATEGORY<ENTER>
>
      The variables that we need to add here are as follows:
>
>   MV_PAYMENT_MODE signio  Payment
>   SIGNIO_SERVER   test-payflow.verisign.com       Payment
>   SIGNIO_ID       $login  Payment
>   SIGNIO_PARTNER  $partner        Payment
>   SIGNIO_SECRET   $password  Payment
>   SIGNIO_VENDOR   $login  Payment
>
      Replace $login, $partner, and $password with the correct values that
were
>   given to you by VeriSign.
>      Once this is done, you need to remove the variables.gdbm file. This
tells
>   interchange that it should re-create the variables.gdbm file from the
new
>   version of variables.txt that you have just created.
>      Now we can restart interchange and we should have a new payment
gateway
>   up and running.
>Troubleshooting:
>      If you still cannot get through the checkout process because it says
>   there is an error, but interchange doesn't say what the error was, there
>   are some things that you can do to figure out what has gone wrong.
>      The best, if on your system you can modify interchange.cfg, is to
>   uncomment the DEBUG line in your interchange.cfg. Once this is done, you
>   need to edit $VENDROOT/lib/Vend/Payment/Signio.pm and uncomment the
lines
>   that start with ::logDebug. These calls will output debugging text into
>   /tmp/icdebug on a normal install. Save the file, and then restart
>   interchange. Now you can do something like tail -f /tmp/icdebug and
watch
>   the debugging text as it occurs while you are trying to place an order.
>Suggestions to the document:
>      If you have suggestions for this document, or if I have left
something
>   out, please let me know by sending an email to signio_faq@davetotten.com
>
>--=-ZvIUpehq+30iawJuligE--