mikew
Starting Member
USA
2 Posts |
Posted - May 09 2007 : 10:40:03
|
Hi All,
Has anyone encountered any issues with implementing cybersource keys with a vpasp install?
We've configured our cybersourceshoppayment.asp page to have our valid merchant id in it, set PFPDebug="No" and set the serverhost="https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor".
We went to the cybersource site and went through their key generation process. We renamed the key to [merchantid].crt and had our host place it in the requested directory on the c drive of the server.
However, in testing, when we go to process the credit card transaction, we get the following error:
Microsoft VBScript runtime (0x800A01FB) An exception occurred: "oICS.Send" /shop/cybersourceshoppayment.asp, line 133
Our host checked their logs and responded with this:
In the log file in the database folder, it has the error encryption error (Could not open file. Could not get certificate from C:\Program Files\CyberSource Corporation\CyberSource SDK for ASP\keys\[merchantid].crt for merchant_id [merchantid]: No such file or directory
Though they can confirm that the file is in that location.
We've tried setting the Account to use both the Hosted and the Simple API, but no luck.
Any thoughts?
Thanks in advance! |
|
mikew
Starting Member
USA
2 Posts |
Posted - May 11 2007 : 12:07:05
|
Well, we finally fixed it. Basically, cybersource has a page set up on their site to generate a key/certificate. DO NOT USE IT. I have no idea what it's for, but it's useless for VPASP integration.
You need to grab their ecert app (http://apps.cybersource.com/cgi-bin/pages/additional.cgi?kit=Update_to_ECert_Application) available in several formats. Once compiled/installed, you need to run it with your merchant id. That spits out four files-- cybersource_sjc_us.crt, [merchantid].crt, [merchantid].pvt, [merchantid].pwd. All of those must be dumped into the cybersource keys directory on the server (in our case: C:\Program Files\CyberSource Corporation\CyberSource SDK for ASP\keys\).
That seemed to get everything up and running and eliminate all errors . . . it's really simple and painless, but the lack of documentation across the board makes it a lot more nebulous than it should be.
|
|
|