RCP - CyberSource

Securely Create Memberships with CyberSource

Customers can easily & securely setup membership payments for your Restrict Content Pro enabled website with CyberSource's membership capabilities. Payment data and PCI compliance is handled by CyberSource’s secure servers.

This add-on allows you to keep the customer on your site for the whole membership setup process, allowing you maximum control over registration so that you can test and implement the most effective experience for your store. A SSL secured site is required for PCI compliance due to ensure that your customers’ credit card information is secure. You also need a merchant account to use CyberSource's payment processing services.

Changelog
  • 2.4.12
    • ENHANCEMENT - Adjusted Cybersource submission data for subscription handling  during upgrades or downgrades of memberships.
  • 2.4.11
    • FIX - Membership renewal start might not submit when customer used a discount code. Resulting in a membership renewal charge by Cybersource the following day.
    • Various tweaks
  • 2.4.10
    • FIX - Plugin would only send a subscription start date when the membership has a trail. Cybersource always needs the start date, otherwise a customer could get charge the following day. Same is true when discount coupons are used.
    • FIX - Device fingerprinting was running, even when the option is disabled in the Cybersource gateway settings.
  • 2.4.9
    • FIX - If production or test credentials where not present, data upgrades would fail for that mode.
  • 2.4.8
    • FIX - At times data upgrades, while retroactively looking for payments, will get stuck in a loop and keep going back in time for more payment data, even when reports are no longer available
  • 2.4.7
    • ENHANCEMENT - Data upgrades will retroactively attempt to log past payments for both production and sandbox data.
  • 2.4.6
    • FIX - Data upgrades would only check based on current RCP mode (i.e. sandbox or production) not both.
    • FIX - If site is in production mode, logging for Cybersource REST API would crash due to logging variable not being established.
  • 2.4.5
    • FIX - Cybersource subscription transaction were not being imported to keep memberships and payments up to date
    • FIX - Data update notice will do clean up RCP store Cybersource data and run a backlog of transaction imports for the previous fix.
  • 2.3.5
    • FIX - Resolved issues with device fingerprinting not profiling users device consistently
    • Various tweaks and clean up to code
  • 2.3.4
    • NEW - Members can now cancel subscriptions
    • NEW - Members can now update payment information for subscriptions
    • FIX - Updated Cybersource's Device Fingerprint ID web implementation, per current documentation standards, should help with issues that occur with an old web implementation method
    • Remove unnecessary JavaScript files
    • Code clean up
    • Various tweaks to functions and constants
  • 2.1.3
    • NEW - Device Fingerprint ID option
  • 2.0.3
    • Fixed an issue where activating the license key would fail and updates would not be received.
  • 2.0.2
    • Fixed an issue where one-time payments would not submit all the required purchase data
  • 2.0.1
    • Tweaked how Cybersource transactions get stored.
  • 2.0.0
    • Complete code rewrite and restructure.
    • Several updates to the payment and recurring payment process due to conflicting Cybersource documentation.
    • Removed unnecessary actions, filters, and functions
  • 1.0.3
    • Updated settings fields for web-hooks from Cybersource
    • Resolved issues with license handling/updating
    • Fixed conflicts if other QCTechJunkie plugins are active
  • 1.0.2
    • Fixed an issue where purchases would get submitted twice to Cybersource
  • 1.0.1
    • Fixed an issue where Cybersource error codes were not displaying when a transaction fails.
  • 1.0.0
    • Initial release