Release Notes
3.0.0.6f0360dc44
Release Highlights
New Microform and Unified Checkout methods
CyberSource is retiring Secure Acceptance (see KA-11531), so version 3.x of the CyberSource Plugin adds support for two new payment methods that use the replacement CyberSource APIs:
MICROFORM_CREDIT_CARD: The storefront keeps its own payment form, where CyberSource fields replace only the card number and security code inputs.UNIFIED_CHECKOUT_CREDIT_CARD: The storefront shows a card form that CyberSource builds, inline on its own page.
With both payment methods, the plugin runs a zero dollar authorization on the card and saves the token that CyberSource returns as the payment instrument. For more information, see the Overview and Frontend Integration.
Direct Post and Hosted Page are deprecated
The DIRECT_POST_CREDIT_CARD and HOSTED_PAGE_CREDIT_CARD payment methods depend on Secure Acceptance. They keep working until your CyberSource sunset date and are planned for removal in an upcoming release. To move a store to a new payment method, see Migrating from Secure Acceptance.
CyberSource REST client upgrade
The plugin now uses version 0.0.95 of cybersource-rest-client-java, upgraded from 0.0.71.
Configuration keys per method
Each method now shows only the configuration keys that it uses. The Microform and Unified Checkout methods add the STOREFRONT_BASE_URLS key, and the Microform method also adds the CARD_BRANDS key. For more information, see Configuring the Plugin.
Token types
Payment instruments created with the Microform or Unified Checkout method store a TOKEN_TYPE value of CUSTOMER when CyberSource returns a Token Management Service customer token. The plugin uses that customer token for reservations and credits. Payment instruments without a TOKEN_TYPE value, such as cards saved with Direct Post or Hosted Page, work as before.
2.0.0.0a1b7f3186
Released: Jan 2025
Release Highlights
Upgraded from the CyberSource Simple Order API to the CyberSource REST API
Version 2.x of the CyberSource Plugin switches from the CyberSource Simple Order API to the CyberSource REST API.
The fields that are populated in the payment instrument tables are different. However, transactions started with version 1.x of the plugin can be completed with version 2.x of the plugin. See the note in Configuring the Plugin for detailed instructions.
Secure Acceptance Improvements
Fields such as bill_to_forename and bill_to_surname are now included automatically as part of the data passed to CyberSource in Direct Post Secure Acceptance. They are populated from the given-name and family-name fields of the address specified during the request instructions operation.
The testing instructions for Secure Acceptance have also been improved.
Authentication Improvements
The plugin now uses the REST API key and REST API secret values from the CyberSource console for authentication, instead of the p12 certificate file. This makes setting up authentication simpler, and removes the need to ensure that the p12 file is installed properly on the service instances. The p12 file should be removed from your environment-specific files if upgrading from version 1 of the plugin.
For more information, see Generating Credentials and Configuring the Plugin.