On This Page

Configuration Settings

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

General Settings

Figure:

General Settings tab
General Settings tab
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 might be required 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:
     This setting generates an authorize-only transaction for a customer order.
  • Sale:
    This setting generates a sale (bundled authorization and capture) transaction for a customer order.
If an authorization returns an
AVS FAILED
 error when you are in
Sale
 mode, merchants must manually review the transaction and decide whether to cancel or accept the transaction. If they accept it, they must manually capture it.

Payment Settings

Figure:

Payment Settings tab
Payment Settings
Card Payment
When this setting is set to
Yes
, payment cards are accepted as a payment method during checkout. The accepted card types list enables the merchant to control which card types are accepted.
Google Pay
When this setting is set to
Yes
, Google Pay is accepted as a payment method during checkout. The merchant's ID and name are needed to use Google Pay. These can be configured from the Google Pay Merchant account.
Apple Pay
When this setting is set to
Yes
, Apple Pay is accepted as a payment method during checkout. The merchant's Apple Pay Merchant ID, Path to Certificate file, and Path to Key file are needed to use Apple Pay. These can be configured from the Apple Developer account.
eCheck
When this setting is set to
Yes
, customers can use
eCheck
 as a payment method.
When this setting is set to
Yes
,
eCheck
 is accepted as a payment method during checkout.

Fraud Management Settings

Figure:

Fraud Management Settings tab
Fraud Management Settings tab
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 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 challenged to authenticate 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 how long that the card information can be saved:
  • Saved Card Limit Count
    : Maximum number of cards a customer can save to their account.
  • Saved Card Limit Time Frame
    : Time frame (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: The public key that renders reCAPTCHA on your web page.
  • reCAPTCHA Secret key: The private key that provides validation to the server.
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

Figure:

Report Settings tab
Report Settings tab
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
    .
It is strongly recommended 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
It is strongly recommended 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

Figure:

LATAM Settings tab
LATAM Settings tab
Installments
When 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. For more information about configureing installment payments, see Enabling 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. For more information about configuring grace period payments for Mexico (the only country for which this setting currently applies), see Enabling Grace Period Payments.