Configuring the Plugin
note
If migrating from CyberSource plugin 1.x to 2.x, do the following:
- Connect to your database and update all CyberSource configurations to draft state by running
UPDATE TPAYMENTPROVIDERCONFIG SET STATUS = 'DRAFT' WHERE PAYMENT_PROVIDER_PLUGIN_ID IN ('directPostCybersourcePaymentProviderPlugin', 'hostedPageCreditCardCybersourceProviderPlugin') AND STATUS = 'ACTIVE';
. - In Commerce Manager, update the
REST_API_KEY
andREST_API_SECRET
values in the provider's Configuration data settings, and re-activate the configuration.
After the CyberSource plugin is added to the ep-commerce
directory, configure the plugin. In Commerce Manager, you can associate it to one or more stores and activate it.
Open Commerce Manager.
On the toolbar, click Configuration.
Go to Payment Methods > Payment Configurations.
Click Create.
In the New Payment Configuration wizard, enter the following details:
In the Provider field, select
CYBERSOURCE
.In the Method field, select either
DIRECT_POST_CREDIT_CARD
orHOSTED_PAGE_CREDIT_CARD
.In the Configuration field, enter a name for the payment provider.
This name is unique to the system and is shown in the Payments tab in store configuration.
In the Display name field, enter the name to display in the user interface.
In the Localized display name field, specify the localized value of the payment configuration.
In the Configuration data settings section, click the pencil icon to edit the following values:
MERCHANT_ID
: Your CyberSource merchant identifier.REST_API_KEY
: Your CyberSource REST API key.REST_API_SECRET
: Your CyberSource REST API secret.SA_ACCESS_KEY
: Your CyberSource Secure Acceptance access key.SA_SECRET_KEY
: Your CyberSource Secure Acceptance secret key.PRODUCTION_MODE
: A boolean value indicating whether the Cybersource requests should be made in production. Set either True or False.DEVELOPER_ID
: An optional field specifying your CyberSource developer identifier.
Click Save.
Activate the plugin within Commerce Manager. For more information about activating a plugin, see Configuring a payment provider.
Associate the plugin with a store. For more information, see Associating a payment plugin to a store.