[ic] BoA/Cybersource HELP!!!
mdw1982 at mdw1982.com
Wed Jun 8 07:17:35 EDT 2005
Mark Weaver wrote:
> jeff at hisgirlfridays.com wrote:
>> On Tue, Jun 07, 2005 at 09:38:47PM -0400, Mark Weaver wrote:
>>> Any suggestions? Things are going from bad to worse...
>> - Get set up with cybersource, so you can log into their admin interface
>> - Get ICS.pm from Kevin's interchange site (interchange.rtfm.info or
>> something similar).
>> - Put ICS.pm in your interchange/lib/Vend/Payment directory and set the
>> permissions as appropriate
>> - Open a Cybersource support issue msg and ask them for the "older perl
>> CDK version 3.4.12, your existing interface doesn't work as well with
>> the new Simple API". They will send you a link to a tar.gz without any
>> - Download and install the aforementioned Cybersource CDK, you should
>> end up with a directory like ICS-3.4.12 . Do all the tests and make
>> sure everything is working OK.
>> - From the Cybersource directory run "./ecert <merchantid>" where
>> merchantid is (for me, at least) something like v289371983. This will
>> make a poorly-secured key system in /opt/CyberSource/SDK/keys . If
>> this directory doesn't exist after you complete this step, retry from
>> here, because the whole Cybersource API fails rather ungracefully and
>> uninformatively if the keys aren't present.
>> - Make sure the payment module ICS.pm is "required" in your
>> interchange.cfg file.
>> - Add the following line to your catalog.cfg:
>> Variable MV_PAYMENT_MODE ICS
>> - Add the following lines down in your Route section of your
>> catalog.cfg (I added it after itransact)
>> Route ICS server_host ics2.ic3.com
>> Route ICS server_port 80
>> Route ICS path /opt/CyberSource/SDK
>> Route ICS merchant_id v38417948
>> Route ICS apps
>> Route ICS timeout 20
>> Route ICS merchant_descriptor "SUBCULTURAL"
>> Route ICS merchant_descriptor_contact "561-433-9633"
>> Route ICS transaction sale
>> - Obviously some of the fields above will need to be replaced with
>> your mechant information.
>> If you have any problems with any step, let me know in this forum and we
>> will go from there. This was a total PITA for me to implement, until I
>> realized that the API that ICS.pm uses is no longer publically available
>> from Cybersource, and since I just did the BOA->CS conversion it's fresh
>> on my mind and I wanted to contribute the information.
> holy hanna! that is a lot to do, but I thank you for the information and
> as soon as I can get hold of Cybersource I'll start things going. We've
> already got an account with them. I'm wondering though, doesn't the
> current ICS.pm that is present in Interchange do the same thing?
Please disregard my remarks about ICS.pm already existing. It was late
and definitely time to step away from the keyboard and get some sleep.
I've downloaded the ICS.pm and placed it in the appropriate directory
within Interchange and contacted CyberSource about the package you
While I was on their site I noticed mention about "clients" for using
Simple Order Processing. I'm assuming those are the ones you mentioned
that don't work correctly, yes?
I also noticed, if I'm understanding you correctly, that Interchange
uses this client to communicate back to the payment gateway, yes? If I'm
understanding correctly, the client is using port 80 to send CC and
order information with the keys that are produced when the client is
installed. Now, as I understand things at the moment the checkout page
is called after interchange moves onto the SSL layer to take customer
CC, shipping and billing information, but the CyberSource client
communicates over port 80 to "phone home" as it were. Do I have this
Paid for by Penguins against modern appliances(R)
Linux User Since 1996
Powered by Mandrake Linux 8.2, 10.0 & RHEL 4
More information about the interchange-users