PrestaShop

The plugin for PrestaShop provides a payment solution for merchants using PrestaShop to manage their orders. This section describes the payment methods and services the plugin provides.
Supported payment methods:
  • Credit and debit cards
  • eCheck
  • Click to Pay
  • Apple Pay
  • Google Pay
Supported payment services:
  • Payment acceptance services:
    • Authorization only
    • Sale (bundled authorization and capture)
    • Electronic check debit (sale) for
      eCheck
      payment method
    • Installment payments for Brazil, Chile, Colombia, Mexico, and Peru
    • Grace period payments for Mexico
  • Order management services:
    • Capture an authorization (not for
      eCheck
      )
    • Multiple partial captures (not for
      eCheck
      )
    • Standard and partial refunds
    • Standard and partial void captures (not for
      eCheck
      )
    • Standard and partial void refunds
    • Full authorization reversal (not for
      eCheck
      )
  • Token Management Service
    (
    TMS
    ) for credit and debit card payments:
    • Create payment token along with authorization
    • Update an existing token along with authorization
    • Update an existing token from My Account section
    • Delete an existing token from My Account section
    • Create payment token for new payment methods during checkout
    • Make a payment with a stored token during checkout
  • Reporting services that allow you to import these Cybersource
    Business Center
    reports into PrestaShop:
    • Transaction Request Report
    • Payment Batch Detail Report
    • Conversion Detail Report

Release Information

This section provides information about the plugin releases.
Release Version
Release Date
Support End Date
2.1.0
April 5, 2022
September 29, 2022
3.1.0
September 29, 2022
April 5, 2022
4.1.0
September 21, 2023
July 2026
4.2.0
December 13, 2023
December 13, 2026
Version 4.2.0 includes the following enhancements:
  • Cybersource authentication signature updated.
  • Compatible with PrestaShop versions 1.7.6.0 to 1.7.8.10
Version 4.1.0 includes enhancements that provide customers with a flexible and convenient purchasing experience:
  • Installment payment options for customers in Mexico, Brazil, Colombia, Chile, and Peru. This feature enables customers to conveniently split their payments into installments.
  • Grace period payment options for customers in Mexico. This feature enables customers to delay a payment for a specified period after making a purchase.
  • Expanded card payment services, which includes credit and debit card options. This feature enables customers to securely make payments using their preferred card type.

Installation

Before you install the plugin, make sure that these requirements are met:
Follow these steps to install the plugin:
  1. Download the Plugin from the PrestaShop website to your local system.
    PrestaShop Modules > Payments > Other Payments > Cybersource Official
  2. Open PrestaShop Back Office and choose
    Modules > Module Manager
    from the Dashboard.
    The Module Manager page opens.
  3. Click
    Upload a Module
    on the Module Manager page.
    The Upload a module pane appears.
  4. Click
    select file
    from the Upload a module pane and select the file you downloaded to your local system. You can also drag the file into the Upload a module pane.
    The pane displays the status of the installation. After the Plugin is installed, the pane indicates that the module is installed. You can close it or click
    Configure
    to configure the Plugin.

Configuration

This section describes how to set up the plugin. You complete most of the Plugin configuration using PrestaShop Back Office.
When merchants support digital payment processing using Apple Pay or Google Pay, they must complete some setup using the Apple Pay or Google Pay Developer websites.

Configuring Plugin Settings

Use PrestaShop Back Office to configure these settings:
  • General settings
  • Payment method settings
  • Fraud management settings
  • Report settings
  • Latin American country settings, if they apply
For details about these settings, see Configuration Settings.
To configure these settings, follow these steps:
  1. Open PrestaShop Back Office and select
    Modules > Module Manager
    from the Dashboard. The Module Manager page opens.
  2. Find the Plugin in the Payment section on the Module Manager page, or enter Cybersource Official in the Search field and click
    Enter
    .
  3. Click
    Configure
    . The Configure Cybersource Official page opens.
  4. Under each tab, enter your configuration information, and click
    Save
    .

Configuration Settings

This section describes the configuration settings for the Cybersource Official Plugin.

General Settings

Sandbox Mode
When sandbox mode is set to
Yes
, PrestaShop operates in sandbox (test) mode so that you can test new changes and conduct experiments.
When sandbox mode is set to
No
, PrestaShop operates in production (live) mode.
Merchant ID
This setting specifies the shop or store Cybersource Merchant ID, which is a unique Cybersource identifier for the merchant.
Merchant Key ID
This setting identifies a specific key or token provided by a payment gateway to authenticate and authorize the merchant's integration with the gateway.
Merchant Secret Key
This setting identifies a confidential or private key used for secure communication between the merchant's online store and a payment gateway.
Payer Authentication/3-D Secure
When this setting is set to
Yes
, customers may receive one-time-password (OTP) pop-ups when placing orders using credit cards. This enables the exchange of data between the merchant, card issuer, and, when necessary, the customer, to validate that the transaction is being initiated by the rightful owner of the account. This may be a requirement for the country in which you are trading.
Enhanced Logs
When this setting is set to
Yes
, logs are generated and can be accessed by selecting
Configure > Advanced Parameters > Logs
.
Payment Action
Use the drop-down menu to choose one of these transaction settings:
  • Authorize:
    when selected, this setting generates an authorize-only transaction for a customer order.
  • Sale:
    when selected, this setting generates a sale (bundled authorization and capture) transaction for a customer order.

Payment Settings

Card Payment
When this setting is set to
Yes
, customers can use a credit or debit card as a payment method.
Click to Pay
When this setting is set to
Yes
, customers can use Click to Pay as a payment method. When the setting is set to
Yes
, you must also provide a Click to Pay API key, which you can configure in the Cybersource
Business Center
.
Google Pay
When this setting is set to
Yes
, customers can use Google Pay as a payment method. When the setting is set to
Yes
, you must also enter the Google Pay Merchant ID and Google Pay Merchant Name, which you obtain from a Google Pay Developer account.
Apple Pay
When this setting is set to
Yes
, customers can use Apple Pay as a payment method. When the setting is set to
Yes
, you must also enter the Apple Pay Merchant ID, Path to Certificate (file), and Path to Key (file), which you obtain from an Apple Developer account. See Enabling Apple Pay for information about the requirements for enabling Apple Pay and generating these files.
eCheck
When this setting is set to
Yes
, customers can use
eCheck
as a payment method.

Fraud Management Settings

Fraud Management
When this setting is set to
Yes
, merchants can identify and prevent fraudulent activities that might occur when their customers are using PrestaShop.
Tokenization
When this setting is set to
Yes
, customers can safely save and store their card information so that it can be used for future purchases.
Enforce Strong Customer Authentication
When this setting is set to
Yes
, the card holder is 3-D Secure challenged when saving their card information.
The Enforce Strong Customer Authentication setting is available only when the Payer Authentication/3-D Secure (general Plugin setting) and Tokenization (fraud management Plugin setting) are enabled.
Limited Saved Card Rate
When this setting is set to
Yes
, merchants can specify the number of cards that customers can save in their account, and they can specify the amount of time for which that card information can be saved:
  1. Saved Card Limit Count:
    specifies the maximum number of cards a customer can save to their account.
  2. Saved Card Limit Time Frame:
    specifies the time frame (from 1 to 24 hours) for which customers can save the specified number of cards to their account.
Google reCAPTCHA
When this setting is set to
Yes
, merchants enter the Google reCAPTCHA keys, which are used to provide an advanced risk analysis engine and adaptive challenges to keep malicious software from engaging in abusive activities on your website:
  • reCAPTCHA Site Key
  • reCAPTCHA Secret key, which can be configured on the Google reCAPTCHA website
See Generating a Google reCAPTCHA Site Key and Secret Key for the steps on how to generate these keys.
Device Fingerprint
When this setting is set to
Yes
, merchants can identify and track devices that access their website such as computers, smart phones, and tablets.

Report Settings

Transaction Request Report
This report includes details for individual transactions that are processed each day.
When this setting is set to
Yes
, this report is downloaded from the
Business Center
to PrestaShop. The report is downloaded to different locations, depending on the mode in which PrestaShop is operating:
  • In sandbox (test) mode, the report downloads to
    {PrestaShopModuleInstallationDirectory}/cybersourceofficial/Reports/Sandbox
  • In production (live) mode, the report downloads to
    {PrestaShopModuleInstallationDirectory}/cybersourceofficial/Reports/Production
    .
Cybersource strongly recommends that PrestaShop and the
Business Center
operate in the same time zone so that the Transaction Request Report and Payment Batch Detail Report work properly.
Payment Batch Detail Report
This report includes transactions that are processed with the applications. This report is available shortly after captured transactions are batched.
When set to
Yes
, this report is downloaded from the
Business Center
to PrestaShop. The report is downloaded to different locations, depending on the PrestaShop mode:
  • In sandbox (test) mode, the report downloads to this location:
    {PrestaShopModuleInstallationDirectory}/cybersourceofficial/Reports/Sandbox
  • In production (live) mode, the report downloads to this location:
    {PrestaShopModuleInstallationDirectory}/cybersourceofficial/Reports/Production
Cybersource strongly recommends that PrestaShop and the
Business Center
operate in the same time zone so that the Transaction Request Report and Payment Batch Detail Report work properly.
Conversion Detailed Report
This report retrieves Case Management changes from the
Business Center
at regular intervals to ensure that orders are updated in PrestaShop.

Latin American Country Settings

Installments
When this setting is set to
Yes
, customers can make installment payments ranging from 1 to 24 months. You can configure installment payment settings for these Latin American countries: Brazil, Chile, Columbia, Mexico, and Peru. See Enabling Installment Payments for how to configure installment payments.
Merchant Descriptor Name
This configuration applies only to Brazil and Mexico.
This setting enables merchants to add a short description that appears on a customer credit card statement or bank statement to identify a particular transaction.
Grace Period
This setting stipulates a time period after a due date during which a payment can be made without incurring late fees or penalties. See Enabling Grace Period Payments for further information about configuring grace period payments for Mexico, the only country for which this setting currently applies.

Enabling Installment Payments

Use PrestaShop Back Office to enable installment payments, which are applicable for payments in Brazil, Chile, Colombia, Mexico, and Peru.
  1. Open PrestaShop Back Office and select
    Modules > Module Manager
    from the Dashboard. The Module Manager page opens.
  2. Find the Plugin in the Payment section on the Module Manager page, or enter Cybersource Official in the Search field and click
    Enter
    .
  3. Click
    Configure
    . The Configure Cybersource Official page opens.
  4. Select the
    LATAM SETTINGS
    tab.
  5. From the
    Country
    drop-down menu, choose the country for which you want to configure the installment payments.
  6. Choose the relevant options from each drop-down menu for these settings and click
    Save
    :
    • Processor
    • Installments (In Months)
    • Choose Card Types
    When a specific card type is selected for a processor in a certain country, it cannot be chosen for any other processor within that country.

Enabling Grace Period Payments

Use PrestaShop Back Office to enable grace period payments, which are applicable only for payments in Mexico.
  1. Open PrestaShop Back Office and select
    Modules > Module Manager
    from the Dashboard. The Module Manager page opens.
  2. Find the Plugin in the Payment section on the Module Manager page, or enter Cybersource Official in the Search field and click
    Enter
    .
  3. Click
    Configure
    . The Configure Cybersource Official page opens.
  4. Select the
    LATAM SETTINGS
    tab.
  5. From the
    Country
    drop-down menu, choose
    Mexico
    .
    You must select Mexico as the country to get access to the Grace Period setting because this setting is only applicable in Mexico.
  6. To enable grace period payments, set
    Grace Period
    to
    Yes
    , and click
    Save
    .

Enforcing Strong Customer Authentication

Select the Enforce Strong Customer Authentication setting to prompt a 3-D Secure challenge when a customer saves their credit card information. The customer is 3-D Secure challenged when a transaction is declined as reported by response code 478 (Strong Customer Authentication required). After the transaction is declined, another request is sent for the same order.
The Enforce Strong Customer Authentication setting is available only when the Payer Authentication/3-D Secure (general Plugin setting) and Tokenization (fraud management Plugin setting) are enabled. See Configuration Settings for information about these settings and Configuring Plugin Settings for information about how to set them.
Follow these steps to enable Enforce Strong Customer Authentication:
  1. Open PrestaShop Back Office and select
    Modules > Module Manager
    from the Dashboard. The Module Manager page opens.
  2. Find the Plugin in the Payment section on the Module Manager page, or enter Cybersource Official in the Search field and click
    Enter
    .
  3. Click
    Configure
    . The Configure Cybersource Official page opens.
  4. Select the
    FRAUD MANAGEMENT SETTINGS
    tab.
  5. Set the Enforce Strong Customer Authentication setting to
    Yes
    .
  6. Click
    Save
    .

Enabling Apple Pay

This section describes the requirements for configuring and using the plugin to process Apple Pay transactions through PrestaShop.

Account and Website Requirements

Before you configure the Plugin to process Apple Pay transactions, ensure that these requirements are met:

Setting Up Apple Pay

This section describes the requirements for setting up Apple Pay to process Apple Pay transactions through PrestaShop.
  1. Follow the instructions for enabling Apple Pay on the
    Setting Up Apple Pay
    page on the Apple Developer website. Before proceeding, ensure that you have completed these steps:
    1. Create a Merchant ID
    2. Create a Payment Processing Certificate
    3. Validate the merchant domain
    4. Create a Merchant Identity Certificate
  2. Download the Merchant Identity Certificate.
  3. Convert the downloaded certificate to a PEM format:
    openssl x509 -inform der -in merchant_id.cer -out merchant_id.pem
    After the certificate is converted, it displays in the Keychain Access menu.
  4. Double-click the certificate on the Keychain Access menu. The certificate is installed and the associated private key displays in the Keychain Access menu.
  5. Right-click the private key, select the
    Export
    option, and export the key as
    merchant_id.p12
    .
  6. Convert the exported private key to a KEY format:
    openssl pkcs12 -in merchant_id.p12 -out merchant_id.key -nodes
  7. Upload the converted key (
    merchant_id.key
    ) and certificate (
    merchant_id.pem
    ) files to your website server.
  8. Open PrestaShop Back Office and select
    Modules > Module Manager
    from the Dashboard. The Module Manager page opens.
  9. Find the Plugin in the Payment section on the Module Manager page, or enter Cybersource Official in the Search field and click
    Enter
    .
  10. Click
    Configure
    . The Configure Cybersource Official page opens.
  11. Select the
    PAYMENT SETTINGS
    tab and enter the complete path to the certificate and key in the Apple Pay section.

Enabling Google Pay

This section describes the requirements for using and configuration steps to enable the plugin to process Google Pay transactions through PrestaShop.

Account Requirements

Before you configure the Plugin to process Google Pay transactions, ensure that you have a Google Pay Developer account.

Generating a Google reCAPTCHA Site Key and Secret Key

The Google reCAPTCHA site and secret keys allow you to safely process Google Pay payments. These keys protect your website when your customers use Google Pay to make payments.
  1. Go to the Google reCAPTCHA website and click the
    Admin Console
    link.
  2. Complete these steps to register a new site:
    1. Enter a label that will be used to identify the site.
    2. Choose the Score based (v3) option for the reCAPTCHA type.
    3. Enter the domain on which PrestaShop is hosted.
    4. Enter the email address of the website owner.
    5. Check the box to accept the terms of service and click
      Submit
      .The reCAPTCHA site key and secret key are generated.
  3. Open PrestaShop Back Office and select
    Modules > Module Manager
    from the Dashboard. The Module Manager page opens.
  4. Find the Plugin in the Payment section on the Module Manager page, or enter Cybersource Official in the Search field and click
    Enter
    .
  5. Click
    Configure
    . The Configure Cybersource Official page opens.
  6. Select the
    FRAUD MANAGEMENT SETTINGS
    tab and enter the keys in the Google reCAPTCHA section of the tab.

Scheduling Report Generation

Schedulers on a Linux, Mac, or Windows system are used to set up how often a specified report is generated. Schedulers for Linux and Mac systems are set up using a Cron Tab. The scheduler for a Windows system is set up using the Windows Task Scheduler app.
When setting up a schedule for generating a specific report, use this format:
  • Format:
    <
    shop domain name
    >/module/cybersourceofficial/paymentReport
  • Example:
    http://www.prestashop_1.7.8.6.com/module/cybersourceofficial/paymentReport
    h

Cron Tab Syntax for Mac and Linux Systems

When setting up the reporting schedule on a Linux or Mac system, you use
crontab
commands that determine how often and when the report is generated.
The syntax is:
* * * * * [command]
The asterisk (*) represents each of these timing parameters:
  • Minute (0-59)
  • Hour (0-23)
  • Day of Month (1-31)
  • Month (1-12)
  • Day of week (0-6), (0-Sunday)
For example, these timing parameters indicate how often a specified report is generated:
  • * * * * * [command]
    : Runs every minute of every day of every week of every month.
  • 0 * * * * [command]
    : Runs every hour of every day of every week of every month.
  • 30 2 * * * [command]
    : Runs at 2:30 a.m. every day of every week of every month.
  • 0 0 2 * * [command]
    : Runs once a month every month on the second day of the month.
  • 0 * * * 1 [command]
    : Runs every Monday at every hour.
  • 0,10,20 * * * * [command]
    : Runs on 0, 10, 20 minute of every hour of every day of every week of every month.
  • 0 5-10 * * * *[command]
    : Runs every hour between 5 and 10 a.m.
  • @reboot [command]
    : Runs every time after the server reboots.
  • */5 * * * * [command]
    : Runs every 5 minutes of every day.

Setting Up Cron Scheduler for Linux

  1. Open a Linux terminal.
  2. Enter
    crontab-e
    to enter editor mode. For example:
    root@PrestashopQA4:/etc# crontab -e
  3. Enter the command to set the timing for the cron job. For example, this command sets the cron job to run every 15th minute of every hour, every day, every week, and every month:
    15 * * * * curl https://www.dev.prestahop.cybsplugin.com/mps1760/module/mybank/paymentReport
  4. Enter
    Ctrl + X
    to close the editor.
  5. Enter the
    crontab -l
    command to check the scheduled cron job. For example:
    root@PrestashopQA4:/etc# crontab -l
    The scheduled cron job should appear on the screen. For example:
    15 * * * * curl https://www.dev.prestahop.cybsplugin.com/mps1760/module/mybank/paymentReport

Setting Up Cron Scheduler for Mac

  1. Open a Mac terminal.
  2. Enter
    crontab-e
    to enter editor mode.
    C02X63PRJG5J:~ $crontab -e
  3. Enter the command to set the timing for the cron job. For example, this command sets the cron job to run every 45th minute of every hour, every day, every week, and every month:
    45 * * * * curl https://www.qa.prestahop.cybsplugin.com/mps1786/module/cybersourceofficial/paymentReport
  4. Enter
    Esc + : + w + q
    to close the editor. The editor closes and displays this message:
    crontab: installing new crontab
  5. Enter the
    crontab -l
    command to check the scheduled cron job.
    C02X63PRJG5J:~ $crontab -l
    The scheduled cron job should display on the screen. For example:
    45 * * * * curl https://www.qa.prestahop.cybsplugin.com/mps1786/module/cybersourceofficial/paymentReport

Setting Up Task Scheduler for Windows

  1. Open the Task Scheduler app and click
    Create Task
    .
    The Create Task pane displays.
  2. Select the
    General
    tab and enter a name for the task in the
    Name
    field.
  3. Select the
    Triggers
    tab and click
    New
    .
    The New Trigger pane displays.
  4. Make the desired timing selections for the task in the New Trigger pane and click
    OK
    .
  5. Select the
    Actions
    tab in the Create Task pane and click
    New
    .
    The New Action pane displays.
  6. Select and enter this information in the New Action pane and click
    OK
    .
    • Action drop-down menu:
      choose Start a program.
    • Program/script field:
      enter the
      curl
      command.
    • Add arguments (optional):
      enter the reporting URL.
  7. Click
    OK
    in the Create Task pane to create the task. The new task displays in the Task Scheduler Summary.

Using the Plugin

The plugin provides merchants a frictionless way to process payments, prevent fraud, and generate reports within the
Business Center
while making it easy for customers to place and cancel orders, and save or update stored credit or debit card information.

Order Management

This section describes the order management process that occurs after a customer places an order.
The order management process is handled using these PrestaShop office interfaces:

Order Status

Order status is triggered and updated when transactions are processed. The plugin supports custom and default statuses for orders.
Custom order statuses:
  • Awaiting payment
  • Awaiting cancel
  • Cancel rejected
  • Cancelled, refund initiated
  • Payment pending for review
  • Partial payment accepted
  • Partial payment cancelled
  • Payment cancelled
  • Partial refunded (before shipped)
  • Partial refunded (after shipped)
  • Partial refund cancelled (before shipped)
  • Partial refund cancelled (after shipped)
  • Payment error
  • Refund cancel error
  • Payment cancel error
  • Refund error
  • Refund cancelled
  • Order cancelled by merchant
Default order statuses:
  • Payment accepted
  • Cancelled
  • Shipped
  • Delivered
  • Refunded
Only the shipped and delivered statuses can be manually updated.

Order Management Workflows

This section describes the order of events that the merchant completes after a customer submits an order.

After-Authorization Workflow

This workflow comprises the sequence of events that occur after a customer places a new order using PrestaShop Front Office. The workflow shows how the order status is updated when the authorized transaction is captured or reversed (full authorization reversal).
  1. The new order displays in PrestaShop Back Office, and the order status is
    Awaiting payment
    .
  2. The merchant chooses one of these options:
    • Standard capture
      .
    • Partial capture
      .
    • Cancel products
      . For a full authorization reversal, the merchant must also cancel the order, which requires that they select all the quantities and all the items included in the order.
      A partial authorization reversal is not supported.
  3. When the merchant initiates a full authorization reversal, the authorization is cancelled and the order status is set to
    Cancelled
    .
  4. When the merchant initiates a multiple partial capture, they choose how many quantities to capture and whether to include the shipping costs.
    After multiple partial captures are processed, the order status is set to
    Partial payment accepted
    .
  5. When the merchant initiates a full capture, the entire authorization amount is captured, and the order status is set to
    Payment accepted
    .

After-Capture Workflow

This workflow comprises the sequence of events that occur after an authorization is captured. The workflow shows how the order status is updated when the captured transaction is refunded or voided.
  1. The merchant chooses one of these options:
    • Standard refund
      .
    • Partial refund
    • Void capture
      .
  2. If the merchant voids the capture, the captured transactions are voided.
    When all quantities of the transaction are captured, the entire order is voided and the order status is set to
    Payment cancelled
    .
    If only a few quantities are captured, only the captured quantities are voided, and the order status is set to
    Partial payment accepted
    .
  3. If the merchant initiates a standard refund
    before
    updating the order status to
    shipped
    , the order status is set to
    Partial refunded (before shipped)
    until the refunded amount becomes equal to the captured amount. When the refunded amount becomes equal to the captured amount, the order status is set to
    Refunded
    .
  4. When the merchant selects a refund
    after
    updating the order status to
    shipped
    , the order status is set to
    Partial refunded (after shipped)
    until the refunded amount becomes equal to the captured amount. After the refunded amount becomes equal to the captured amount, the order status is set to
    Refunded
    .
    To refund the amount of an order, merchants can either generate a voucher or a credit slip for the refund. Depending on the type of refund they select and whether they issue a voucher or a credit slip, one of these actions occurs:
    • When the merchant chooses
      Generate a voucher
      for a partial refund, the sum of the items is not refunded. Instead, a voucher is generated that can be used for future transactions.
    • When the merchant chooses
      Generate a voucher
      and enters the amount in the shipping costs field for a partial refund, then a voucher equal to the sum of the items and the shipping amount is generated.
    • When the merchant chooses
      Generate a credit slip
      for a standard refund, the sum of the items is refunded.
    • When the merchant chooses both
      Generate a credit slip
      and
      Repay shipping costs
      for a standard refund, the sum of the items and the shipping amount are both refunded.
    • When the merchant chooses both
      Generate a voucher
      and
      Repay shipping costs
      for a standard refund, a voucher equal to the sum of the items and shipping amount is generated.
    • When the merchant chooses both
      Generate a voucher
      and
      Generate credit slip
      for a standard refund, a voucher is generated and a refund for the sum of the items is not generated.

After-Refund Workflow

This workflow comprises the sequence of events that occur when the merchant voids a refund under specific conditions:
  • When the refund is processed
    before
    the order is shipped, the refund is cancelled and the order status is set to
    Partial refund cancelled (Before shipped)
    .
  • When the refund is processed
    after
    the order is shipped, the refund is cancelled and the order status is set to
    Partial refund cancelled (After shipped)
    .
  • When the voided refund amount is equal to the refund amount, the refund is cancelled and the order status is set to
    Refund cancelled
    .

Customer Tasks

Customers can use the My Account option on the merchant's PrestaShop website to manage orders and their payment information. The following sections contain the steps to complete these tasks.

Saving Credit/Debit Card Information

Saving card information enables customers to use that information for future transactions. Using PrestaShop Front Office, customers can save their card information during the checkout process, or they can add their card information to their registered PrestaShop accounts using the My cards feature.
If a customer wants to save their card information during the checkout process, they can select the
Save my card for future payment
option when entering their credit/debit card payment (as shown below) during checkout.
The card information can also be saved on the My cards page in PrestaShop:
  1. Open PrestaShop Front Office.
  2. Go to the My cards section of the page and click
    ADD CARD
    .
    If no current address is associated with the customer account, the customer is prompted to add an address. The customer can enter the required address information and click
    Save
    .
    If there is already an address associated with the customer account, the customer can select and use the address or add a new address.
    After the address information is complete and selected, the customer can update the card expiration information, if needed, or delete the existing card from the account.
  3. To update the expiration information for the card (expiration month/year), the customer clicks
    Update
    , or clicks
    Delete
    to remove the card from the account. The customer can also change the billing address for the card by clicking
    Change
    .
    Customers can add only the number of cards that the merchant specified in the account configuration. The updated card information is tokenized and securely saved. The customer can use the saved card information for future transactions without having to enter that card information during the checkout process.

Selecting a Default Credit/Debit Card

When a customer has multiple cards associated with their account, they can designate the default card. By default, the first card added to the account is set as the default card. In the My cards page, the default card is identified with an asterisk (*) that appears to the right of the card number.
To change the default card, the customer follows these steps:
  1. Open PrestaShop Front Office.
  2. Open the My cards page. The page displays the saved cards associated with the account.
  3. Choose a card to set as the default card, and choose
    More > SET AS DEFAULT
    . The card is set as the default card.
    The default card cannot be deleted unless all other saved cards from the My cards section are deleted.

Cancelling an Order

This task provides the steps a customer takes to cancel an order. They cannot cancel an order if the order is in review with the merchant.
  1. Open PrestaShop Front Office.
  2. Select
    My Account > Order History
    . The Order history page displays the customer's orders.
  3. Select the
    Details
    icon for the order to cancel. The Order details page appears.
  4. Click the
    Cancel
    icon to cancel the order.
    An Order cancellation confirmation notice appears.
  5. Click
    Yes
    on the Order cancellation confirmation notice to cancel the order.
    The order is cancelled and the order status is set to Cancelled.
    If the order was a sales transaction or was captured, the cancellation is sent to the merchant and the status is set to
    Awaiting cancel
    .
    After the customer cancels an order, the merchant can accept or reject the order cancellation (as instructed in Processing a Cancelled Order). If the merchant accepts the cancellation request, a refund for the order amount is initiated, and the order status is set to
    Cancelled, refund initiated
    . If the merchant rejects the cancellation request, the order status is set to
    Cancel rejected
    .

Merchant Tasks

Merchants use PrestaShop Back Office to manage orders. This section describes the steps to complete these tasks.

Processing a Cancelled Order

When a customer cancels an order, a request is sent to the merchant, and the order status is set to
Awaiting cancel
. Merchants can accept or reject an order that a customer cancels.
  1. Open PrestaShop Back Office and select
    Orders > Orders
    from the Dashboard.
  2. Locate and select the order the customer cancelled. The information for that order displays.
  3. Choose one of these options:
    • Click
      Accept cancellation
      to accept and process the cancelled order. A refund for the order amount is processed, and the order status is set to
      Cancelled, refund initiated
      .
    • Click
      Reject cancellation
      to reject the cancelled order. The order status is set to
      Cancel rejected
      .

Processing a Merchandise Return

When a customer requests to return merchandise, the information appears on the Merchandise Returns page in PrestaShop Back Office. Follow these steps to process the return.
  1. Open PrestaShop Back Office and select
    Customer Service > Merchandise Returns
    . The Merchandise Returns page displays and identifies the order or orders for which customers have requested a return.
  2. Select the order for which you want to process the return. The Edit > Return Merchandise Authorization (RMA) menu displays.
  3. Choose one of these options from the Status drop-down menu and click
    Save
    :
    • Waiting for confirmation
    • Waiting for package
    • Package received
    • Return completed
    The status is updated for the order on the Merchandise Returns page. Next, you can proceed with selecting a return or refund option for the order.
  4. Select
    Orders > Orders
    from the Dashboard.
  5. Select the order for which you want to process a return, and select one of these options:
    • Return products
    • Partial refund

Fraud Management

The plugin provides fraud management functionality for merchants who also use the Cybersource
Business Center
. You can apply fraud management functionality to transactions in these situations:
  • Fraud management is enabled in the plugin.
  • You have a fraud management profile in the
    Business Center
    .
Fraud screening includes these features:
  • Fraud Management Essentials (FME):
    used to enforce the rules created by the Cybersource Machine Learning System (MLS). Fraud management is used to define the merchant’s rules.
  • Fraud Management Rules:
    • When the decision status from the
      Business Center
      is AUTHORIZED_PENDING_REVIEW or PENDING_REVIEW, the order is in review and the order status is set to
      Payment pending for review
      .
    • When the decision status from the
      Business Center
      is AUTHORIZED_RISK_DECLINED, the order is rejected and the order status is set to
      Order cancelled by merchant
      .
The table below describes the possible decisions, outcomes, and timing that Decision Manager uses when an order is triggered for review.
When the following transactions are in a Decision Manager review state, certain settlement considerations apply:
  • For authorizations:
    while accepting this transaction it is not recommended to settle it in the
    Business Center
    . When the transaction is settled in the
    Business Center
    , the follow-on services initiated from PrestaShop Back Office are impacted.
  • For sales:
    • The entire authorized amount should be settled in the
      Business Center
      when accepting the transaction. When the settlement is not performed in the
      Business Center
      , the follow-on services initiated from PrestaShop Back Office fail.
    • A follow-on void capture will not initiate from PrestaShop Back Office. While accepting review transactions, merchants should not select the settle option.
Decision Manager Decisions, Execution Timings, and Outcomes for Orders
Decision
Execution Timing
Outcome of Decision
Monitor
Before authorization
Authorization is successful and no action from the Decision Manager is required. Use this decision to understand the outcome of a rule.
Accept
Before authorization
The order is processed normally and is placed successfully.
Review
Before authorization
The authorization is successful, and follow-on services are put on hold until the merchant accepts or rejects it. The order status is set to
Payment pending for review
.
Reject
Before authorization
The order is rejected and the authorization is not processed. The merchant is not able to view the order in PrestaShop Back Office.
Monitor
After authorization
The authorization is successful and no action from Decision Manager is required. Use this decision to understand the outcome of a rule.
Accept
After authorization
The order is processed normally and placed successfully.
Review
After authorization
The authorization is successful, and follow-on services are put on hold until the merchant accepts or rejects it. The order status will be set to
Payment pending for review
.
Reject
After authorization
The original authorization is successful and then is automatically reversed and the order status is set to
Order cancelled by merchant
.

Reporting

The plugin provides reporting functionality for merchants who also use the
Business Center
. You can import these reports from the
Business Center
into PrestaShop:
  • Transaction Request Report:
    includes details for individual transactions that are processed each day.
  • Payment Batch Detail Report:
    includes transactions that are processed with the applications. This report is available shortly after captured transactions are batched.
  • Conversion Detail Report:
    includes Case Management changes recorded in the
    Business Center
    to ensure that updated orders are also included in PrestaShop. This report is generated at regular intervals and includes the results of the converted orders for each reviewer. This information provides an overview of all orders that were not immediately accepted.

Scheduling

The Plugin reporting functionality works with a system scheduler to generate and update reports for PrestaShop. There are some Cron Job modules available for PrestaShop, such as the Cron Tab, that support reporting. Merchants can use any Cron Job module that PrestaShop supports or any other online Cron service provider to generate reports.
See Scheduling Report Generation for information about how to schedule report generation.

Workflow

The reports are processed and orders are updated in PrestaShop as described in this workflow:
  1. Orders with an
    AUTHORIZED_PENDING_REVIEW
    or
    AUTHORIZED_RISK_DECLINED
    status are included in the
    ps_cybersourceofficial_order
    table in the PrestaShop database.
  2. If a review is trigged for an order based on the profile rule in Decision Manager, a
    Payment pending for review
    order status displays for that order on the PrestaShop Back Office Orders page.
  3. The merchant uses the
    Business Center
    to accept the order that is in review, and, if not already enabled, the merchant enables the reports using the Report Settings on the Plugin Configuration page.
  4. The scheduler runs the report at regular intervals according to the intervals the merchant configured. The order is accepted or rejected by the merchant in the
    Business Center
    , is retrieved, and the new status is updated as
    AUTHORIZED
    or
    DECLINED
    . The updated order status displays in the
    ps_cybersourceofficial_order
    table in the PrestaShop database.
  5. The original decision and the new decision are updated and displayed in the
    ps_cybersourceofficial_conversion_detail_report
    table in the PrestaShop database.
  6. The order is updated as
    Awaiting payment
    status for the authorization and displayed on the PrestaShop Back Office Orders page. The payment is accepted for the sale and any associated follow-on transactions (capture, void capture, refund, void refund, and full authorization reversal).

Testing

If you have not done so already, configure these settings using PrestaShop Back Office. See Configuring Plugin Settings for information about how to access these settings:
  • General Settings:
    merchant ID, merchant key ID, and/or merchant secret key
  • Payment Settings:
    applicable payment methods
After configuring the Plugin, complete this task to test the configuration using PrestaShop Front Office to place an order and PrestaShop Back Office to manage the order.
  1. Open PrestaShop Front Office to place an order.
  2. Enter any required personal information and select the payment method that you want to use to place the order.
  3. Enter the card information you want to use to place the order and click
    Pay
    . If the order is successful, an order confirmation message displays.
  4. Open PrestaShop Back Office to manage the order.
  5. Select
    Orders > Orders
    from the Dashboard. The Orders page displays and lists all active orders.
  6. Select and open the order you processed in Step 1. The order status for the order should display
    Awaiting payment
    .
  7. Click
    Standard Capture
    icon to capture the authorized amount, and click
    Yes
    to capture the entire order. The order status changes to
    Payment accepted
    .
  8. Click
    Standard Refund
    to refund the full captured amount. The order status changes to
    Refunded
    .
  9. Click
    Void Refund
    to void the refunded amount. The order status changes to
    Refund cancelled
    .
    For more information about testing, including test cards, see

Upgrading

You can install a newer version of the plugin using PrestaShop Back Office.
  1. Open PrestaShop Back Office and select
    Improve > Modules > Module Manager
    from the Dashboard.
  2. Click the arrow next to the plugin
    Configure
    icon and choose
    Upgrade
    from the drop-down menu.

Troubleshooting

This section might help you resolve specific issues that can occur during the installation and upgrade processes for the plugin.

Issue: PrestaShop Language Pack Installation Error

You get a
1: Cannot download language pack "en"
error message when installing the Plugin.
To resolve this issue, complete these steps:
  1. Locate and open the
    Tools.php file
    , which resides in
    htdocs/PrestaShop root/Classes
    directory on your system.
  2. Search for and select this string in the Tools.php file:
    curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);
  3. Replace the selected string with this string:
    curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, true);
  4. Save the file and reload your browser page.

Issue: Debug Mode is Enabled in Production

When debug mode is enabled in the production instance, you need to disable it.
  1. Open PrestaShop Back Office and select
    Configure > Advanced Parameters
    from the Dashboard. The Advanced Parameters page appears.
  2. Select
    Performance
    from the Advanced Parameters page.
  3. Set Debug mode to
    No
    .

Issue: User Interface Appears Incorrectly After a Plugin Upgrade

After upgrading the Plugin, if the user interface looks incorrect, you need to clear the cache.
  1. Open PrestaShop Back Office and select
    Configure > Advanced Parameters
    from the Dashboard. The Advanced Parameters page appears.
  2. From the Advanced Parameters page, click
    Performance
    .
  3. Click
    Clear Cache
    .

Configuring and Testing Email

Follow these steps to configure the email that customers receive during order management.
  1. Open PrestaShop Back Office and select
    Advance Parameters > Email
    from the Dashboard. The email page appears.
  2. Select these options from the Email section of the page to configure how email is sent:
    • Send emails to: Customer service
    • Set my own SMTP parameters (for advanced users ONLY)
    • Both HTML and text formats
    • Yes for log emails
  3. Select and specify this information for your SMTP parameters:
    • Mail domain name: do not enter information (leave this field empty)
    • SMTP server: enter the server domain. For example,
      smtp.gmail.com
      .
    • SMTP username: enter the email address from which emails are sent. For example,
      csproduct@gmail.com
      .
    • SMTP password: enter the password for the email address provided above.
    • Encryption: select TLS
    • Port: enter 587
  4. Click
    Save
    to save the configuration.
  5. Test your email configuration by entering an email address to which you want to send the test message, and click
    Send a test email
    .

Configuring Order Status Visibility

You can choose to hide order status messages that you do not want customers to view.
  1. Open PrestaShop Back Office, and select
    Customer Service > Order Messages
    from the Dashboard.
  2. Click the pencil icon beside the order status message you would like to hide.
  3. In the Order status pane, select
    hide this status in all customer orders
    .
  4. Click
    Save
    .

Troubleshooting Assistance

For help with troubleshooting, contact GlobalPartnerSolutionsCS@visa.com and provide the following information:
  • Summary of the issue
  • Steps needed to reproduce the issue
  • Platform version
  • Plugin version
  • Platform Merchant ID
  • Configuration screenshots
  • List of themes/additional extensions installed
  • Log file and any other data or screenshots related to the issue