Cybersource SDK Installation

Download the 'Simple API' SDK for .NET 2.0 (.NET2.0 .NET net2.0 v.5.0.2) from CyberSource and install it. You also need to download and install the WSE 3.0 components from Microsoft.

Set the application pool your site is running in to allow 32 bit applications. Consult your host or whoever maintains your server for information on doing this.

Log in to your CyberSource merchant account. NOTE: That you may need to use Firefox or other browser that supports the Java security applet.

Go to Account Management, then Transaction Security Keys. In the Transaction Security Keys page click on Security Keys for the Simple Order API link.

Click on the 2048-Bit Key button. NOTE: There should be a Java security applet visible and functional on the New Security Key page you are taken to. If there is not, please try using a different browser such as Firefox.

Then click the Generate Certificate Request button.

Once the key has been generated, copy it to your sdk directory under the keys folder. The extension of the key must be .p12 and the filename should be the same as your merchant ID.

Admin Console Setup

2. In the Payment Gateway section, click the 'configure' link next to the Cybersource entry.

3. Put in the value you obtained from Cybersource for the 'Merchant ID'.

4. Put in the filename (with extension) that you saved in step 7 above for the 'Key Filename' and the full path to the SDK folder you saved that key in for the 'Keys Directory', ending with a backslash such as ...\keys\ .

5. Click 'Save and Close'.

6. Finally, click the radio button next to Cybersource and then click the 'Submit' button.

Frequently Asked Questions

Q: What CyberSource API should I use for transaction keys?
A: Security Keys for the Simple Order API (SOAP).

Q: I keep getting this error: Failed to sign the request with error code N`1862' and message N `IO error'
A: The CyberSource application interface was not able to sign the request with the key file.

Here are a few things to check:

1 - Verify that these AppConfigs have the proper value:

a. CYBERSOURCE.keysDirectory – should be the absolute path of your SOAP Security Keys.

2 - Does the ASP.NET or NETWORK SERVICE user have read access permission to the key file?

Q: When I try to void a transaction, it always fails with the following error even if the capture has not been done: “The capture or credit is not voidable because the capture or credit information has already been submitted to your processor. Or, you requested a void for a type of transaction that cannot be voided.”
A: A transaction can only be voided if CyberSource has not yet submitted the debit or credit information to your processor. Usually CyberSource submits that type of information to your processor once a day, so your window for successfully performing a void is relatively small. CyberSource will decline your void request if the debit or credit information has already been sent to the processor.
CyberSource supports the void service for the following processors:

• Chase Paymentech Solutions
• TeleCheck

Note: When you void a transaction, the transaction is at the end of its life. You cannot undo a void, and you cannot perform a follow-on credit for a debit that has been voided.

Q: Why won't Cybersource work on my 64-bit server?
A: The 3rd party DLLs required for Cybersource to work don't support 64 bit environments. Unfortunately, there is nothing AspDotNetStorefront can do to alleviate this limitation.

Q: Can I use my Bank of America account through Cybersource?
A: Yes, Cybersource supports Bank of America accounts. See here for more information.

For more information about CyberSource error messages, go to the CyberSource page where they have a list of reason codes for the errors and contact CyberSource support directly if you are experiencing these, they should be able to assist you further.