This module integrates CyberSource's Secure Acceptance Hosted Checkout and Flex Microform payment APIs. It provides off-site redirect and on-site iframe payment solutions, requiring specific CyberSource account configuration. Due to dependency conflicts with the official CyberSource PHP client, a forked version is used.
This module integrates two of CyberSource's payment APIs, Secure Acceptance Hosted Checkout (an off-site redirect based solution) and Flex Microform v2 (an on-site iframe based solution). Using either API requires specific account configuration options in your CyberSource account (live or sandbox) and may require manual configuration changes to your Drupal codebase as documented in README.md. Please review this carefully, especially as it pertains to altering Drupal's default SameSite cookie attribute for SAHC usage.
Furthermore, CyberSource's own PHP REST API client library has outdated dependencies that conflict with Drupal's own dependencies. Until those are updated upstream, this module makes use of a fork of the client library maintained by Centarro. If / when it is possible to switch back to the official client library, we will be sure to highlight it in the relevant release notes.
Integration testing
You can create a developer account to test your integration against at:
Find testing details and test card numbers at:
Drupal 9 compatibility
Due to third party dependency changes between Drupal 9 and Drupal 10 that conflict with dependencies of a CyberSource maintained REST client, we cannot have a version that is both Drupal 9 and Drupal 10 compatible. As such, 8.x-1.0-beta7 is the last release of this module that supports Drupal 9, and the 8.x-1.0 release is Drupal 10 compatible only. (This release was packaged after the Drupal 9 end of life, so from the 1.0 on we will not be backporting any fixes into a Drupal 9 compatible release.)
Drupal 7 branch notice
This branch was never fully released nor marked ready for production, though some sites may have deployed it with additional improvements to ensure its proper working order. It remains "supported" on the module page to ensure those sites don't show error message, but you should not be using it on new sites.