Follow the steps defined in the Cybersource documentation on setting up a Secure Acceptance profile. Note that you may need to contact CyberSource customer support to enable Secure Acceptance. (http://apps.cybersource.com/library/documentation/dev_guides/Secure_Acceptance_SOP/html/wwhelp/wwhimpl/js/html/wwhelp.htm#href=creating_profile.html)
Once you have established an account with CyberSource and configured your settings in the Business Center so that you have an active account,
begin by including the CyberSource Module dependency to your Broadleaf application's parent pom.xml.
<dependency> <groupId>com.broadleafcommerce</groupId> <artifactId>broadleaf-cybersource-payment</artifactId> <version>1.1.0-GA</version> <type>jar</type> <scope>compile</scope> </dependency>
Make sure to include the dependency in your CORE pom.xml as well:
<dependency> <groupId>com.broadleafcommerce</groupId> <artifactId>broadleaf-cybersource-payment</artifactId> </dependency>
The next step is to make Broadleaf Commerce aware of your CyberSource account credentials.
This is accomplished through environment configuration (see [[Runtime Environment Configuration]]).
Broadleaf allows you to create your own property files per environment (e.g. common.properties, local.properties, development.properties, integrationdev.properties, integrationqa.properties, staging.properties, and production.properties)
You will need to enter the following key/value pairs in the appropriate locations and replace the "?" with your Cybersource account details:
You can also store these configs in the Database by utilizing the
blSystemPropertiesService. See the java docs for more details.
By default, the system looks at the
decision reply field to determine whether or not a transaction is successful.
If instead, you would like to look at specific reason codes to determine its success, you can set the following property:
gateway.cybersource.secureAcceptance.success.reasonCodes. This property accepts a comma separated list of codes. If
this property is not set, it will default to looking at the
decision field. If you are still in need of a more complex
rule to determine success, the method can be overriden in
An example of the reason code system property:
Now that you have your environment set up, let's begin setting up the [[CyberSource Payment Quick Start]].