OpenCart
Opencart is an easy to-use, powerful, Open Source online store management program that can manage multiple online stores from a single back-end.
OpenCart is a FREE, open-source and easy to use ecommerce platform.
No monthly fees, no catches; just an effective and customizable platform for your new ecommerce store. Simply install, choose your template, and add products and you’re ready to start accepting orders
Check with your platform contact for product availability
Product overview
OpenCart are an small business focused eCommerce Cart solution providing services to a global base of merchants. OpenCart is an OpenSource solution providing an extension marketplace.
- Card Payments
- 3D Secure (SCA Compliant)
- Secure Tokenization
- In-App payments
- Recurring payments
- eCheck
- Fraud Management Tools
- Delivery Address Verification
- Reporting
Compatible with OpenCart versions: 3.0.3.7 & 3.0.3.8
Getting started
Obtaining, installing and configuring your OpenCart plugin.
Pre-Requisites
Before starting configuration of your OpenCart instance you are required to generate your Cybersource REST keys within your Business Center for both (Live) and (Test)
a. Sign into your Cybersource Business Center account (Live) or (Test)
b. Access Payment Configuration -> Key Management
c. Select the 'Generate Key' button in the top right hand corner
d. Select your key type as 'REST - Shared Secret' and Generate Key
e. Copy your Shared Secret Key values and save them securely
Installation
This section explains the steps involved installing the Payment method in OpenCart Back Office.
First, obtain the official Cybersource plugin from OpenCart ensuring you save the zip file locally.
a) In the Navigation Panel “Extensions” tab, click on “Installer”.
b) In Installer, click on “Upload” button to upload the module.
c) Confirm that the progress bar is to 100% and that the downloaded Cybersource extension zip "cybersource.ocmod.zip" is now showing in installed files
Configuration - Module Settings
General Configuration
This section provides the details about the steps for configuring the high level Merchant configuration:
a. In the Back Office Dashboard, click on “Extensions” dropdown and select “Extensions”.
b. In the dropdown shown, select the extension type as “Modules”.
c. Click on the install button to install the "Cybersource Configuration" module and then click on edit to enter the configuration menu.
d. Under the general configuration menu, configure the below as required
- Sandbox - Enable (transactions will point to our Test system), disable (transaction will point to our Production system
- Merchant ID - Enter your Cybersource Merchant ID (often called your OrganisationID)
- Merchant Key ID - Your Cybersource REST Key ID created in Step 1
- Merchant Secrey Key - Your Cybersource REST Secret Key created in Step 2
- Fraud Management - Enable or disable dependent on you having a Cybersource Fraud Management product on your account.
- Device Fingerprint - Enable or Disable (recommend to enable)
- Developer ID - Only required for Cybersource affiliated developers
- Status - Enable/Disable (Set to enable)
- Google reCAPTCHA - Enable/Disable (recommend to enable)
- reCAPTCHA Site Key - available directly from Google
- reCAPTCHA Secret Key - available directly from Google
- Enhanced Logs - Enable/Disable (recommend to enable)
e. Click the save icon.
Report Configuration
- Payment Batch Configuration - Enable/Disable
- Transaction Request Report - Enable/Disable
- Conversion Detail Report - Enable/Disable, if running Manual Fraud reviews in Cybersource this will pull fraud updates into OpenCart
Order Status Configuration
The settings within this section are compleltely dependent on your chosen statuses for orders, please ensure all settings match your requirements.
Configuration - Credit Card
To access Credit Card configuration log into OpenCart Back Office -> Extensions -> Extensions. Then select "Payments" under Extension Type -> Select Cybersource Credit Card -> Edit
This section provides the configurations for Payment Card specific settings, the below settings are available to edit:
- Payment Action - Authorize/Sale, Authorize will immediately ring fence funds in customers account if successful a capture will need to be run at time of fulfilment to fully obtain funds. Sale will authorize and capture funds immediately.
- Payer Authentication - Enable/Disable set to enable if you are required to process customers through Strong Customer Authentication (3-D Secure)
- Status - Enable/Disable (Set to enable to allow Card Payments)
- Sort Order - only needed to change sort order of plugin visibility
- Tokenization - Enable/Disable, when set to enabled logged in customers will be able to store their cards for future use n.b. requires tokenization to be enabled on your Cybersource account
- Limit Saved Card Rate - Simple fraud tool to limit the number of cards a customer can save in an hour to prevent card enumeration attacks
- Enforce Strong Customer Authentication - When Payer Authentication is enabled every customer will be challenged, this may be required in some geographies
Configuration - eCheck
To access eCheck configuration log into OpenCart Back Office -> Extensions -> Extensions. Then select "Payments" under Extension Type -> Select Cybersource eCheck -> Install (1st time only) -> Edit
This section provides the configurations for eCheck specific settings, the below settings are available to edit:
Status - Enable (must be enabled to be visible in checkout)
Sort Order - Set to control display order in checkout
Cybersource extension
Key features of the OpenCart and Cybersource Payment Integration:
• Enable the users to accept and manage payments in OpenCart.
• Enable hassle-free, completely secure, PCI Compliant, Fraud management enabled - end to end payment transaction for Credit Card payment method and eCheck debits.
• Extends the order management features for payment methods and the follow-on services such as Full Authorization Reversal, Capture, Refund and Void.
• Supports Tokenization which eliminates electronic cardholder details from being stored in the Merchant environment thereby reduces the scope of Payment Card Industry (PCI) compliance considerations.