Setting Up Your Store > Setting Up Your Payment Gateway > CyberSource Gateway

CyberSource Gateway

Related Topics: Payment Methods |Transaction Modes | Void, Capture, Refund Orders |Gateway Settings

Overview:

The CyberSource gateway is supported, but it requires complicated set of instructions to install, most likely to be performed by a developer.

CyberSource provides an application, ECert, for you to generate your certificate. The certificate generation process also creates your private key. Your certificate and private key, along with the CyberSource certificate, are stored on your servers where the CyberSource client software is installed.

 

User Set Up Instructions:

If you have not already compiled the storefront to support CyberSource, please follow the procedures below. If you need help, contact Support, to send you a compiled version.

  1. Register then login to the CyberSource business center (https://ebc.cybersource.com). For first time users, it will ask you to set a new password.

 

  1. Click on Account Management.

 

  1. Click on Transaction Keys.

 

  1. Click on Generate Key.

 

* You may need to install the Java Plug In in order to proceed with the Key generation.

 

  1. Click Generate Certificate Request.

 

  1. Click Process Certificate Request.

 

  1. To accept the certificate, click Yes or Always.

Messages continue to appear in the box. Your browser opens its Save As dialog box.

  1. Choose a safe location for your key (<username>.p12).
  • The last line of the sample below informs you that the process is finished and that a new key is stored in the location that you indicated.
  • To verify that your key is active, click Transaction Security in the side navigation pane. Your new key is listed at the bottom of the table.

Sample message while key is generated:

Generating the certificate request.

This may take several seconds.

Certificate request generated successfully.

Encoding the certificate request.

Certificate request encoded successfully.

.

.

Creating the key file contents.

Key file contents created successfully.

Please select a save location for your key file using the popup dialog.

Writing the key file to the file system.

Writing the key file to C:\Full_Path_that_you_chose.

Key file written to the file system successfully.

The password for the key file is your merchant id: <Merchant_ID>.

The Certificate Manager has successfully completed all operations.

 

  1. Go to Home.

  2. Go Live! - then follow additional instructions for going live.

  3. Upload the merchantid.p12 file to your web host.

  4. Modify these web.config files:

    <add key="cybs.merchantID" value="v2186853"/>
    <add key="cybs.keysDirectory" value="C:\inetpub\websites\ComfortFuton_com\"/>
    <add key="cybs.keyFilename" value="v2186853.p12"/>
    <add key="cybs.sendToProduction" value="true"/>

    merchantId is your username or the name of the file without the .p12 extension
    The keysDirectory is something you need from your host - it is the location of all of your webfiles on their server
    keyFilename is the name of the file you saved in step 7
    cybs.sendToProduction should always be true.

     

Instructions for Compiling
 
To compile support for the CyberSource gateway into AspDotNetStorefront you must have the following System Requirements installed:
 

1. CyberSource Simple Order API for .NET Framework 2.0 SDK
    http://apps.cybersource.com/cgi-bin/pages/dev_kits.cgi?kit=_.NET/_.NET2.0

2. Microsoft Web Services Enhancements (WSE) 3.0
    http://msdn.microsoft.com/webservices/webservices/building/wse/default.aspx

3. Add a reference to Cybersource.Clients.dll which is installed with the SDK to this project. Then uncomment the first line of this file: cybersource.cs
 

4. The settings for this gateway are in the Web.config file in the main web site directory.

    This gateway requires the following settings be update with valid values for your account: 

  • cybs.merchantID

  • cybs.keysDirectory

  • cybs.keyFilename

  • cybs.sendToProduction


 NOTE:

This Gateway ignores the AppConfig setting "UseLiveTransactions" and will use the value for key "cybs.sendToProduction" in the Web.config file

  

Troubleshooting:


Q: Why do I keep getting the error message: "Failed to sign the request with error code '1862' and message 'IO error'."


A: The CyberSource application interface is not able to sign the request with the key file. Here are a few things to check:
     1. Verify settings in Web.Config for cybs.keyFilename and cybs.keysDirectory.
     2. Does the ASP.NET user have read permission for the key file?

 
 
FAQ:

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: Void is not supported universally. CyberSource supports the void service for the following processors:

•   American Express Brighton
•   American Express Phoenix
•   Barclays
•   Concord EFS
•   FDI Australia
•   FDMS Nashville
•   FDMS South
•   GE Capital
•   HBoS
•   HSBC
•   LloydsTSB Cardnet
•   Paymentech New Hampshire
•   Streamline
•   UATP
•   Vital

 

   

   System Requirements | Security Best Practices | Support & Upgrade Contracts | Downloads | Contact Us

   Copyright © 1995-2006 All rights reserved.