Configuration {#prestashop-configuration} ========================================= This is the complete configuration guide for the `Cybersource Official Plugin` PrestaShop extension, including minimum and optional settings. To configure the `Cybersource Official Plugin` extension for PrestaShop, go to Modules \> Module Manager. Scroll down to `Cybersource` Official and click Configure. It is recommended to click Save after working on each configuration tab. Minimum Configuration --------------------- As a minimum to accept payments with `Cybersource`, configure these settings. **General Settings Tab** * Payment Option Label: This text is displayed on your checkout page to your customers. * Sandbox Mode: * Yes: Choose for testing your `Cybersource` test account. * No Choose for live transactions. * Merchant ID: The transacting Merchant ID (MID) that `Cybersource`assigned to you. * Merchant Key ID: The Key from your REST API Shared Secret Key. * Merchant Secret Key: The Shared Secret from your REST API Shared Secret Key. * Accepted Card Types: Choose the card brands to accept. **Payment Settings Tab** * Card Payments: To enable, set to `Yes`. * Payment Action: * Authorize: Sends an authorization request and if approved, you must manually request a capture. * Sale: Captures the transaction automatically if the authorization is approved. {#prestashop-configuration_ul_lwy_k54_rhc} In the Sale mode, if an authorization returns an `AVS Failed` error, the merchant must manually review the transaction and decide whether to cancel or accept the transaction. If the merchant accepts the transaction, the merchant must manually capture the transaction. Message Level Encryption ------------------------ Message Level Encryption (MLE) uses certificates that ensure each message is securely encrypted and tied to the sender's verified identity, without needing to share secret keys in advance. MLE provides stronger authentication, easier key management, and better protection against fraud or tampering. A shared secret uses the same key for both sending and receiving messages, meaning both parties must securely exchange and protect that key in advance. While MLE can be simpler, it offers less identity verification and can be more vulnerable if the key is compromised. **Prerequisite** : Message Level Encryption requires a [P12 certificate](https://developer.visaacceptance.com/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-message-intro/restgs-security-p12-intro.md ""). * Message Level Encryption: To enable MLE, set to `Yes`. * Enter the path to the folder containing the certificate. * Enter the key name. * Enter the key password. * Enter the key alias. Digital Payment Methods ----------------------- * Google Pay: To enable Google Pay, set to `Yes`. * Apple Pay: To enable Apple Pay, set to `Yes`. * `Click to Pay`: To enable Click to Pay, set to `Yes`. You must enable these payment methods for your MID in the `Business Center`. For more information, see this [Unified Checkout Developer Guide](https://developer.cybersource.com/docs/cybs/en-us/unified-checkout/developer/all/rest/unified-checkout/uc-configuration-intro/uc-enable-digital-pay-intro.md ""). Alternative Payment Methods --------------------------- * `eCheck`: To enable alternative payment methods, set to `Yes`. Tokenization ------------ * Tokenization: To enable customers to save their card for future purchase, set to `Yes`. * Network Token Updates: If your MID is enabled for network tokens, set this option to `Yes` to subscribe to the lifecycle updates associated with the token. * Limit Saved Card Rate: To limit the saved card rate, set to `Yes`. * Saved Card Limit Count: Specify the maximum number of cards a customer can save to their account. * Saved Card Limit Time Frame: Specify the time frame (1 to 24 hours) when customers can save the specified number of cards to their account. Payer Authentication/`3-D Secure` --------------------------------- * Payer Authentication/`3-D Secure`: To enable payer authentication, set to `Yes`. * Enforce Strong Consumer Authentication: To enforce a `3-D Secure` challenge when a customer saves their card for future payments, set to `Yes`. Fraud Screening --------------- **Fraud Management Settings Tab** * Fraud Management: To configure the extension to look for fraud screening responses, set to `Yes`. * Google reCAPTCHA: Set to `Yes` to enable. * reCAPTCHA Site Key: Enter the public key that renders reCAPTCHA on your web page. * reCAPTCHA Secret Key: Enter the private key that provides validation to the server. Go to Google reCAPTCHA to sign up and create keys. The `Cybersource Official Plugin` extension supports v3. * Device Fingerprint: To collect information about your customers' device as part of fraud screening, set to `Yes`. Report Settings --------------- **Report Settings Tab** * Transaction Request Report: When enabled, the extension downloads a report from `Cybersource` containing details for transactions processed each day. Set to `Yes` to enable. * Payment Batch Detail Report: When enabled, the extension downloads a report from `Cybersource` containing details of all captures and refunds that were submitted to your payment processor. Set to `Yes` to enable. For all reports, it is strongly recommended that your PrestaShop store and the `Cybersource` `Business Center` user profile operate in the same time zone. Report download locations: * In test mode: `{PrestaShopModuleInstallationDirectory}/cybersourceofficial/Reports/Sandbox` * In production (live) mode: {`PrestaShopModuleInstallationDirectory}/``Cybersource``official/Reports/Production` * Conversion Detail Report: When you are using fraud screening with REVIEW rules, this toggle polls the `Cybersource` platform to check for updates to transactions and the associated orders in PrestaShop. Set to `Yes` to enable. A scheduled task is required for the updates. For details on how to set up a task, see the [Appendix](/docs/cybs/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/prestashop-introduction/prestashop-appendix.md ""). Additional Options ------------------ **General Settings Tab** * Enhanced Logs: To generate logs that can be accessed from Configure \> Advanced Parameters \> Logs, set to `Yes`. This feature is not recommended for Production (live) mode. * Developer ID: `Cybersource` generated ID string issued to development partners.