CyberSource Payment Processor Configuration

Summary

This article describes how to configure CyberSource as a payment processor in EngageIP. EngageIP is integrated with iBiz to support payment processors, for more information see the Payment Processing Using iBiz article.

Configuration

Credit Card Processor Configuration

1. Load Setup

2. Click on Card Processors

3. Click Add

4. Populate the Processor details (required fields will be shown in red)

   Open

   

    

   • Name - enter a name for reference purposes (not passed to CyberSource)

   • Card Gateway - select CyberSource from the list

   • Merchant Login - the username provided by CyberSource

   • Merchant Password - the CyberSource security key is entered into the Attribute field, this Merchant Password field is unused and can be populated with any value

   • Gateway URL - enter the production or test URL here

     • Live/Production URL - CyberSource Transaction Web Service: transaction-servlet

     • Test/CAS URL - https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor/

   • Attribute - enter the security key provided by CyberSource

   • Configuration - specify the options desired (separated by semicolons)

     • Currency Configuration - CurrencyCode=xxx, for instance CurrencyCode=USD

     • Security Configuration - SSLEnabledProtocols=3072 will disable TLS 1.0

5. Click Save

Once the processor is setup Card Types can be configured that use the processor.

Card Type Configuration

Once the Credit Card processor is configured you can add a Card Type which will use the processor, to do this:

1. Load Setup

2. Click on Card Types

3. Click Add

4. Enter the Card Details (sample image below)

   Open

   

    

   • Name - enter a descriptive name for the Card Type

   • Card Processor - select the CyberSource credit card processor you setup

   • Credit Card Token Processor - used if you have configured a Credit Card Token Processor, not applicable in this case

   • Enable AVS - Address Verification System, leave unchecked

   • Card Type - select the appropriate Credit Card type from the list

   • Pre Auth Req - enable this if you want pre-authorization to be required when this card type is added as a Payment Method on an Account/User

   • Pre Auth Amount Overridable - enable this option if you want to be able to change the pre-authorization amount when the pre-authorization prompt appears

   • Pre-Auth Default Amount - if pre-authorization is enabled the value entered here will be the amount that is pre-authorized

5. Click Save

At this point you can add the Card Type as a Payment Method on a User (Account / Tools / Payment Methods / Add / Credit Card) and ensure a payment can be processed.

ACH Processor Configuration

The configuration steps are very similar to the Credit Card Processing configuration above.

1. Load Setup

2. Click on ECheck Processors

3. Click Add

4. Configure the ECheck processor with the same details as the CyberSource Credit Card Processor configuration steps above, except:

   • Gateway URL: enter the eCheck URL provided by CyberSource

     • Test URL: https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor

   • Attribute - specify the currency desired and security key (attributes are separated by semicolons)

     • Currency Configuration - purchaseTotals_currency,xxx, for instance purchaseTotals_currency,USD to charge in US dollars

     • Security Key - SecurityKey,key

5. Click Save

6. On the Setup page add your Payment Types and associate them with the eCheck processor

7. Test by adding an ECheck Payment Type to an account and processing a payment using the same ECheck Payment Type

8. Review Payment Decline or Payments reports for any errors / detail respectively

Testing

Test Credit Card numbers can be seen here for Cybersource: http://www.cybersource.com/developers/other_resources/quick_references/test_cc_numbers/

Triggering failures for testing is described below and requires setup on Cybersource: https://support.cybersource.com/cybskb/index?page=content&id=C6&actp=LIST

Troubleshooting

If you encounter an error configuring a processor, card type or payment method the error message returned in the UI may be generic. To obtain more detail on the issue reference reports such as the Event Log or if the failure occurs during processing the PaymentProcessLog table in the EngageIP database.

Gateway Error / XML Parse Error

If you receive a gateway error, or see in the PaymentProcessLog table an 'xml parse error', check that there are no special characters in the account name such as an '&'. These will cause CyberSource to parse the data stream incorrectly and prevent ACH payments from going through for the User/Account.

'PCI.DataEncryptingKey' cannot be null or empty

This indicates that the PCI Data key which is used to encrypt credit card data is not configured in your EngageIP environment. Please contact support to get your system configured to encrypt card data.