On This Page {#jumplink-list} [Markdown](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o.md) Recent Revisions to This Document {#isv-doc-revisions} ====================================================== 26.02.02 -------- New Adobe Commerce Open Source Plug-in : A new Adobe Commerce Open Source plug-in was added to augment the existing Adobe Commerce Cloud plug-in. See [Adobe Commerce REST API](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-25-2-0-intro.md ""). Github link : Added a link to ISV Toolkits available at GitHub. See [About the Integrated Solutions](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/plugins_overview.md ""). Adobe Commerce Cloud : Updated the section on configuring web services to refer to a change in the procedure where SOAP p12 certificates are uploaded to a section now called Simple Order P12 Key File. See [Configuring WebService](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview/adobe-commerce-m-backend-conf-settings/adobe-commerce-m-config-gen-settings/adobe-commerce-m-conf-webserv.md ""). : Updated the section on creating a SOAP security key to refer to the SOAP P12 certificate. See [Configuring Security Credentials](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview/adobe-commerce-m-sec-cred-intro.md ""). PrestaShop : Revised the PrestaShop section. See [PrestaShop](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/prestashop-introduction.md ""). Shopify : Added note to the configuring section to ensure that the Test mode is used when testing. See [Configuring Shopify](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/shopify-overview/shopify-configuring.md ""). : The testing section was revised to describe how to install and use a new test app. For more information, see [Reference Information](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/shopify-overview/shopify-reference.md ""). WooCommerce : Updated the WooCommerce plug-in. For more information, see [WooCommerce](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/wc-introduction.md ""). {#isv-doc-revisions_dc} 25.12.01 -------- Oracle Netsuite : Removed Oracle Netsuite module from guide. {#isv-doc-revisions_dl_akc} 25.10.01 -------- Shopify : Added note that when using the test server, ensure that the Test Mode option is enabled. See [Configuring Shopify on page 122](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/shopify-overview/shopify-configuring.md ""). WooCommerce : Added note to the troubleshooting section to check with support services for configuration guidance when your account is managed by a merchant services provider. See [Support and Troubleshooting on page 129](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/wc-introduction/wc-support-troubleshooting.md ""). {#isv-doc-revisions_dl_a44_k} 25.09.02 -------- PrestaShop : This revision contains only editorial changes and no technical updates. Shopify : The app now supports Shopify subscriptions. : Clarified that during installation, you use the transacting merchant ID as your credentials. See [Installing the Live App](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/shopify-overview/shopify-install.md ""). {#isv-doc-revisions_dl_a44_kc} 25.09.01 -------- This revision contains only editorial changes and no technical updates. 25.08.01 -------- WooCommerce : Updated all information in this section. See [WooCommerce](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/wc-introduction.md ""). {#isv-doc-revisions_dl_a44_kjf_hgc} VISA Platform Connect: Specifications and Conditions for Resellers/Partners {#vpc-partner-reseller-disclaimer} ============================================================================================================== The following are specifications and conditions that apply to a Reseller/Partner enabling its merchants through Visa Acceptance platform. Failure to meet any of the specifications and conditions below is subject to the liability provisions and indemnification obligations under Reseller/Partner's contract with Visa/Cybersource. 1. Before boarding merchants for payment processing on a VPC acquirer's connection, Reseller/Partner and the VPC acquirer must have a contract or other legal agreement that permits Reseller/Partner to enable its merchants to process payments with the acquirer through the dedicated VPC connection and/or traditional connection with such VPC acquirer. 2. Reseller/Partner is responsible for boarding and enabling its merchants in accordance with the terms of the contract or other legal agreement with the relevant VPC acquirer. 3. Reseller/Partner acknowledges and agrees that all considerations and fees associated with chargebacks, interchange downgrades, settlement issues, funding delays, and other processing related activities are strictly between Reseller and the relevant VPC acquirer. 4. Reseller/Partner acknowledges and agrees that the relevant VPC acquirer is responsible for payment processing issues, including but not limited to, transaction declines by network/issuer, decline rates, and interchange qualification, as may be agreed to or outlined in the contract or other legal agreement between Reseller/Partner and such VPC acquirer. DISCLAIMER: NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR ANY ERRORS OR OMISSIONS BY THE Visa Platform Connect ACQUIRER IN PROCESSING TRANSACTIONS. NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR RESELLER/PARTNER BOARDING MERCHANTS OR ENABLING MERCHANT PROCESSING IN VIOLATION OF THE TERMS AND CONDITIONS IMPOSED BY THE RELEVANT Visa Platform Connect ACQUIRER. About the Integrated Solutions {#plugins_overview} ================================================== `Visa Acceptance Solutions` offers integrated solutions to enhance payment acceptance, fraud management, recurring billing, reconciliation, and reporting processes. Our integrated solutions provide significant and vast use cases for product managers to developers and business professionals. Reduce your operational costs through streamlined payment integrations and improve customer satisfaction through flexible and secure payment options. Our solutions can easily scale to your growing business needs, help increase sales and conversion rates, and provide a clear value proposition to distinguish your business from competitors. The solutions detailed in this document are: * [Visa Acceptance Solutions for Adobe Commerce](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-25-2-0-intro.md "") * [Adobe Commerce Cloud](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview.md "") * [BigCommerce](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-them/bigcommerce-overview.md "") * [OpenCart](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview.md "") * [PrestaShop](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/prestashop-introduction.md "") * [Shopify](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/shopify-overview.md "") * [Salesforce B2C](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/salesforce-b2c-introduction.md "") * [WooCommerce](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/wc-introduction.md "") For information on how to become a partner, see the [*Partner Getting Started*guide](https://developer.visaacceptance.com/docs/vas/en-us/isv-plugins/get-started/all/na/isv-getting-started/isv-partner-starter-intro.md ""). See these additional resources for more information about the ISV Plugins documented in this guide: * *[Adobe Commerce `Visa Acceptance Solutions` Payment Platform](https://commercemarketplace.adobe.com/cybersource-global-payment-management.md#description "")* * [*`Connecting with ``Visa Acceptance Solutions`*](https://support.bigcommerce.com/s/article/Connecting-with-Cybersource?language=en_US "") * [*Getting Started with OpenCart*](https://docs.opencart.com/en-gb/getting-started/ "") * [*PrestaShop*](https://addons.prestashop.com/en/other-payment-methods/49944-cybersource-official.md "") Built by Us {#isv-built-by-us} ============================== Welcome to `Visa Acceptance Solutions`'s suite of solutions built by `Visa Acceptance Solutions` for you. These solutions offer potential use cases that improve operational efficiency, enhance security, and provide comprehensive reporting and invoicing. Reduce the risk of errors, protect against fraudulent transactions, and ensure accurate financial records through streamlined reconciliation processes. Our solutions are ideal for various industries including financial services, healthcare, manufacturing, and distribution. For example, in healthcare, our solutions can manage payment operations efficiently, ensuring secure and accurate processing of payments for services rendered, and support timely invoicing actions. These guides are created by `Visa Acceptance Solutions`: * [Adobe Commerce REST API](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-25-2-0-intro.md "") * [Adobe Commerce Cloud](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview.md "") * [OpenCart](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview.md "") * [PrestaShop](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/prestashop-introduction.md "") * [Shopify](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/shopify-overview.md "") * [WooCommerce](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/wc-introduction.md "") Adobe Commerce REST API {#adobe-commerce-25-2-0-intro} ====================================================== The Visa Acceptance Solutions extension for `Adobe Commerce`/Magento Open Source enables merchants to connect their `Adobe Commerce`/Magento Open Source store to the Visa Acceptance Platform to directly take credit and debit cards, Apple Pay, Google Pay, and Click to Pay payments. For simplicity in this document, any reference to `Adobe Commerce` will apply for Magento Open Source also, unless otherwise stated. Supported Features {#adobe-commerce-25-2-0-supported-features} ============================================================== The Visa Acceptance Solutions extension supports various payment methods and security features. Payment Methods --------------- * Credit/debit cards * Apple Pay * Google Pay * Click to Pay Security Features ----------------- * `Payer Authentication` / `3-D Secure` * Tokenization Supported Versions {#adobe-commerce-25-2-0-supported-versions} ============================================================== The `Adobe Commerce` extension has these system requirements: * `Adobe Commerce` 2.4.5+ * PHP 8.1+ Unsupported `Adobe Commerce` Features {#adobe-commerce-25-2-0-unsupported-features} =================================================================================== These features are not supported by this extension: * Order void * Multi-shipping * Multiple node implementation * Google reCAPTCHA Visa Acceptance Solutions Prerequisites {#adobe-commerce-25-2-0-prerequisites} ============================================================================== Mandatory Prerequisites ----------------------- This Visa Acceptance Solutions product must be configured for your Merchant ID: * `Unified Checkout` You also must have a REST Shared Secret Key. See the [Getting Started with REST Developer guide](https://developer.visaacceptance.com/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-http-message-intro/restgs-security-key-pair-intro/restgs-security-key-pair-task.md "") for information on how to get a REST Shared Secret Key. Optional Prerequisites ---------------------- These Visa Acceptance Solutions products are optional. If you want these products you must enable and configure your Merchant ID with them. * `Payer Authentication` for `3-D Secure` * Tokenization * Apple Pay * Google Pay * Click to Pay You can also enable Message-Level Encryption (MLE) for additional security. A [REST 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 "") is required for MLE. Release Notes {#adobe-commerce-25-2-0-release-notes} ==================================================== Version history and changes for the Visa Acceptance Solutions extension for `Adobe Commerce`. Version 25.2.0 January 2026 --------------------------- These enhancements were added with this release: * Request Message Level Encryption * API endpoint updates * Support for Jaywan card * Implemented Sub Resource Integrity (SRI) * Updated `Unified Checkout` to version 0.33 These bugs were addressed in this release: * Corrected the country field source in the `Unified Checkout` capture context. * CSP violation This release is compatible with: * `Adobe Commerce` 2.4.5+ * PHP 8.1+ Version 25.1.0 May 2025 ----------------------- Initial release that supports: * `Unified Checkout` * Apple Pay * Google Pay * Click to Pay * `TMS` * `Payer Authentication` This release is compatible with: * `Adobe Commerce` 2.4.5+ * PHP 8.1+ Installation {#adobe-commerce-25-2-0-installation} ================================================== Follow these steps to install the Visa Acceptance Solutions extension for `Adobe Commerce`. Before starting the installation, ensure you have `Adobe Commerce` authentication keys and that they are set correctly in your environment. See Authentication Keys for details. Go to the `Adobe Commerce` Marketplace and get the free extension. Choose the appropriate installation method based on your environment: * `Adobe Commerce Cloud`: For cloud-based installations, go to the [Adobe Commerce Cloud](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-25-2-0-intro/adobe-commerce-25-2-0-installation/adobe-commerce-25-2-0-install-cloud.md ""). * `Adobe Commerce` On-Premise / Magento Open Source: For self-hosted installations, go to [Adobe Commerce On-Premise](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-25-2-0-intro/adobe-commerce-25-2-0-installation/adobe-commerce-25-2-0-install-onpremise.md ""). `Adobe Commerce Cloud` {#adobe-commerce-25-2-0-install-cloud} ============================================================= Follow these steps to install in `Adobe Commerce Cloud` environments. 1. Run this command in your local Cloud project directory: ``` composer require Cybersource/module-payment:25.2.0 ``` 2. After Composer finishes, commit the updated files using these commands: ``` git add composer.json composer.lock git commit -m "Add Cybersource Payment module" git push ``` 3. Enable the module with this command: ``` php bin/magento app:config:dump ``` 4. After enabling the module, commit the updated configuration file with these commands: ``` git add app/etc/config.php git commit -m "Enable Cybersource> Payment module" git push ``` `Adobe Commerce` On-Premise / Magento Open Source {#adobe-commerce-25-2-0-install-onpremise} ============================================================================================ To install the module using Composer, run these commands in your `Adobe Commerce` On-Premise and Magento Open Source environments. ``` php bin/magento module:enable Cybersource_Payment php bin/magento setup:di:compile php bin/magento indexer:reindex php bin/magento setup:upgrade php bin/magento setup:static-content:deploy -f php bin/magento cache:clean php bin/magento cache:flush php bin/magento module:status ``` Configuration {#adobe-commerce-25-2-0-configuration} ==================================================== To configure the Visa Acceptance Solutions extension, go to Stores \> Configuration \> Sales \> Payment Methods \> Visa Acceptance. Configure these fields: Configure General settings: * Environment: * Test: Choose for testing of your `Visa Acceptance Solutions` test account. * Production: Choose for live transactions. * Merchant ID: Enter the transacting Merchant ID (MID) assigned to you by Visa Acceptance Solutions. * API Key: Enter the Key from your REST API Shared Secret Key. * API Shared Secret Key: Enter the Shared Secret from your REST API Shared Secret Key. * Accepted Card Types: Choose the card brands you want to accept. Configure Debug Mode: * Yes: Compiles detailed logs for every transaction. This option is only recommended for the Test Environment or when troubleshooting issues in Production. * No: Only basic logging occurs. Configure Message Level Encryption: Enabled * Yes: Encrypts the full request message using JSON Web Tokens before being transmitted to the Visa Acceptance Platform. * No: Uses the HTTP Signature. JSON Web Tokens use a digital certificate to prove who you are, while HTTP Signature uses a shared secret key to confirm the message is genuine. Both methods are PCI compliant. * Certificate File: Upload the p12 certificate for your `Visa Acceptance Solutions` Merchant ID. * Key Password: Enter the password that was used when you created your p12 certificate. Configure Secure Payment Methods: * Enable: Choose `Yes` to enable the extension. * Title: Enter the label your customers see on the checkout page. * Payment Action: Choose one of these options: * Authorize and Capture: Captures the transaction automatically when the authorization is approved. * Authorize only: Sends an authorization request and if approved, you must manually request a capture. * Payment Card Types: Choose the card brands you want to offer to your customers. * Allowed Payment Methods: Choose the payment methods you want to offer to your customers. These payment card types must be enabled for your MID in the `Business Center`. See here for details. * Select Layout: * Embedded: The payment widget appears inline on the checkout page. * Sidebar: The payment widget appears on the right side on the checkout page. * Payment from Applicable Countries: * All Allowed: Uses the `Adobe Commerce` global settings to determine which countries are available. * Specific Countries: Specify which countries you want to accept payments from. * `Payer Authentication`/`3-D Secure`: Choose `Yes` to enable `3-D Secure`. * Tokenization: Choose `Yes` to enable your customers to save their payment cards for future purchases. * Tokenization Title: Enter the label you want your customers to see when they pay with a saved card. * Saved Card Verification: Choose `Yes` to request that your customer enter their card security code when paying with a saved card. * Enforce Strong Customer Authentication: Choose `Yes` to enforce a `3-D Secure` challenge when a customer saves their card for the first time. Order Management {#adobe-commerce-25-2-0-order-management} ========================================================== The Visa Acceptance Solutions extension provides comprehensive order management capabilities for handling transactions after they are processed. This includes capturing authorized payments and processing refunds when necessary. The order management features enable you to: * Capture authorized transactions to collect funds. * Process full or partial refunds for completed transactions. * Manage the payment lifecycle from authorization to settlement. Capture {#adobe-commerce-25-2-0-capture} ======================================== When you have the Payment Action set to `Authorization`, you must capture the transaction to collect the funds. 1. Enter an order from the list of orders. 2. Click Invoice. 3. Check the item(s) that require capturing. 4. Ensure the drop-down capture option is set to Capture Online. 5. Click Submit Invoice. Refund {#adobe-commerce-25-2-0-refund} ====================================== To refund an order: 1. From the list of orders, choose the order you want. 2. Click on Invoices. 3. Select the appropriate invoice. 4. Click the Credit Memo button. 5. Check the item(s) to be refunded. 6. Verify and if necessary update the Refund Totals. 7. Click Refund. Support \& Troubleshooting {#adobe-commerce-25-2-0-support} =========================================================== Get support for the Visa Acceptance Solutions extension by providing detailed information about your issue. If you require support with this extension, sign into the Support Center to raise a case, providing these details: * Summary of the issue * Steps needed to reproduce the issue * Platform version * Extension version * `Visa Acceptance Solutions` Merchant ID * Configuration screenshots * List of themes/additional extensions installed * Log file and any other data or screenshots related to the issue Upgrade {#adobe-commerce-25-2-0-upgrade} ======================================== To upgrade from an earlier version of our `Adobe Commerce` extension, run these composer commands 1. Update the extension to the latest version: ```keyword composer require Visa Acceptance Solutions/module-payment:25.2.0 ``` 2. Run the setup upgrade command: ``` bin/magento setup:upgrade --keep-generated ``` 3. Deploy static content: ``` bin/magento setup:static-content:deploy ``` 4. Clean the cache: ``` bin/magento cache:clean ``` `Adobe Commerce` {#adobe-commerce-m-overview} ============================================= You can integrate `Visa Acceptance Solutions` with the `Adobe Commerce` platform to process payments using Magento checkout. The `Adobe Commerce` extension supports popular payment methods, safeguards payment data, minimizes fraud, and mitigates risks. This section describes the payment management capabilities offered by `Visa Acceptance Solutions` through the `Adobe Commerce` integration. This guide also applies to installing this extension in a Magento Open Source environment. Fraud Management ---------------- Fraud Management prevents fraud losses and gives you the flexibility to control business practices and policies in real time. Fraud Management can help you accurately identify and review potentially risky transactions while minimizing the rejection of valid orders. Fraud Management comprises these capabilities: * Real-time fraud screening performed only during authorization * Device fingerprinting * On-demand Conversion Detail Report for changes in order status Account Takeover Protection --------------------------- Account Takeover Protection defends customers and merchants from fraudulent use of online accounts. It monitors suspicious account changes and helps identify high risk users at account creation and login. These capabilities comprise Account Takeover Protection: * Real-time event screening of account creation, login, and changes * Device fingerprinting Payer Authentication -------------------- Payer Authentication enables you to add support to your web store for card authentication services offered by Visa, Mastercard, and other card brands. These programs verify the cardholder's identity directly with the card-issuing bank in real time to increase payment security and reduce the risk of fraud. However, Payer Authentication is not a fraud management service, and `Visa Acceptance Solutions` recommends that you configure a comprehensive fraud management program such as Decision Manager in addition to Payer Authentication services. These services comprise Payer Authentication: * Verified by Visa * Mastercard Identity Check * American Express SafeKey * Discover ProtectBuy * JCB * Diners * Maestro International To comply with the recent mandates for French local processors that support Payer Authentication, CMCIC, Atos and BNP processors no longer support these combinations. PayPal ------ The `Adobe Commerce Cloud` integration includes the PayPal payment method. Processing your PayPal transactions through `Visa Acceptance Solutions` enables you to consolidate all payment types under a single gateway account, simplify integration efforts, screen PayPal transactions for fraud with Decision Manager, and streamline reporting. These services comprise PayPal: * Sessions * Check Status * Order * Authorization * Authorization Reversal * Capture * Sale * Refund * PayPal Credit * Billing Agreements PayPal Credit ------------- PayPal Credit is a payment method that allows merchants to accept a PayPal transaction when the customer chooses to finance their purchase through PayPal. Electronic Check (`eCheck` Service) ----------------------------------- The `eCheck` Service a form of digital payment that serves the same function as a physical check. When a merchant accepts an electronic check payment, the funds are pulled directly from the customer's checking or savings account. These are the `eCheck`s include both debit and credit services. `eCheck` Service process refunds with the credit payment service. Online Bank Transfers --------------------- Online banking services enable customers to pay for goods by sending money from their bank account to the merchant. The `Adobe Commerce Cloud` extension supports the following payment methods and corresponding online bank transfer services: * Bancontact * Sale * Check Status * Refund * Country: Belgium {#adobe-commerce-m-overview_ul_elt_h5m_5bc} * iDEAL * Options * Sale * Check Status * Refund * Country: Netherlands {#adobe-commerce-m-overview_ul_i5q_4ym_5bc} Tax Calculation --------------- The Tax Calculation service provides real-time tax calculation during order checkout for orders placed worldwide with your business. Delivery Address Verification ----------------------------- The Delivery Address Verification service verifies the entered address and suggests the recommended address for city, state, and zip code combinations in real time. If this feature is enabled in the `Adobe Commerce Cloud` console, the `Adobe Commerce Cloud` extension verifies the delivery address on shipping information updated by the user. Klarna ------ Klarna credit provides a seamless user experience for online customer financing to merchants of all sizes, which helps in increasing customer choice, loyalty and growth in sales. Google Pay ---------- Google Pay is a digital wallet that enables customers to pay with any payment method saved to their Google account. Release Notes {#adobe-commerce-m-release-info} ============================================== This section provides information about functionality, bug fixes, and enhancements for the `Adobe Commerce Cloud` `Visa Acceptance Solutions` integration. January 2026 ------------ `Adobe Commerce Cloud` `Visa Acceptance Solutions` Version 3.5.11 is compatible with `Adobe Commerce Cloud`: 2.4.8-p3, 2.4.8-p2, 2.4.8-p1, 2.4.8, 2.4.7-p8, 2.4.6-p13 and PHP 8.4, 8.3, 8.2 : * Implemented Request Message Level Encryption * Implemented Google Pay Payer Authentication * Fixed Anonymous Script Load Error (Integrity and Cross Origin) * Updated authenticationStatus flag for Payer Authentication in Google Pay {#adobe-commerce-m-release-info_ul_fsh_skg_lhc} August 2025 {#adobe-commerce-m-release-info_section_c5h_4kg_lhc} ---------------------------------------------------------------- `Adobe Commerce Cloud` `Visa Acceptance Solutions` Version 3.5.10 is compatible with `Adobe Commerce Cloud`: 2.4.8-p1, 2.4.8, 2.4.7-p6, 2.4.6-p11,2.4.5-p13 and PHP 8.4, 8.3, 8.2, 8.1 : * Extended support for `Adobe Commerce Cloud` v2.4.8. * Changed path for certificate folder from root to var directory. * Updated the certificate folder name to certificates. April 2025 {#adobe-commerce-m-release-info_section_jl3_tjg_lhc} --------------------------------------------------------------- `Adobe Commerce Cloud` `Visa Acceptance Solutions` Version 3.5.9 is compatible with `Adobe Commerce Cloud`: 2.4.7-p4, 2.4.7-p3, 2.4.7-p2, 2.4.7-p1, 2.4.7, 2.4.6-p9, 2.4.5-p11 and PHP 8.3, 8.2, 8.1 : * Upgraded Microform to v2. * Implemented SOAP p12 Authentication. * Remove legacy Click to Pay payment module. * Fixed issue of declined cases and SCA transactions on Firefox browser. {#adobe-commerce-m-release-info_ul_btl_kkg_lhc} June 2024 --------- `Adobe Commerce Cloud` `Visa Acceptance Solutions` Version 3.5.8 is compatible with `Adobe Commerce Cloud`: 2.4.6 p3, 2.4.6 p2, 2.4.6 p1, 2.4.6, 2.4.5 p5, 2.4.4 p6 and PHP 8.2, 8.1 : * Fixed Logger and CSP issue for Magento v2.4.7. * PHP support added for v8.3. * Removed unused class in Apple Pay. * Added required field for Merchant ID in Back Store. * Fixed issue for admin order redirecting to blank page. * Made Payer Authentication common for both Secure Acceptance (Stored Card) and Soap Toolkit API. * Fixed Visa Checkout error "No such cart entity id with cartid". {#adobe-commerce-m-release-info_ol_mkn_4zm_5bd} March 2024 ---------- `Adobe Commerce Cloud` `Visa Acceptance Solutions` Version 3.5.7 is compatible with `Adobe Commerce Cloud`: 2.4.6 p3, 2.4.6 p2, 2.4.6 p1, 2.4.6, 2.4.5 p5, 2.4.4 p6 and PHP 8.2, 8.1 : * Removed zend dependency and replaced with laminas. * Removed Payer Authentication Cardinal key dependency from Back Store Configuration. * Google Pay and Apple Pay refund issue fixed for multiple websites. * Apple Pay customer billing address fixes for downloadable and virtual products. * The issue has been fixed for JSON error message in the 3-D Secure pop-up. * Fixed invalid card type message that appeared in credit card Flex Microform. * Added error message for Apple Pay session failure. * Fixed Device Fingerprint raw parameter for Secure Acceptance. * Fixed Payer Authentication failure scenario. {#adobe-commerce-m-release-info_ol_mkn_4zm_5bc} October 2023 ------------ `Adobe Commerce Cloud` `Visa Acceptance Solutions` Version 3.5.6 is compatible with `Adobe Commerce Cloud`: 2.4.6 p2, 2.4.6 p1, 2.4.6, 2.4.5 p4, 2.4.4 p5, and PHP 8.2, 8.1 : * Implemented Direct Connection API Payer Authentication. * Removed dependency on `sales_order_grid` table for Google Pay and Secure Acceptance. * Apple Pay order cancel fixes. * PayPal billing address line 2 issue fixes. * Removed parenthesis for http signature request-target in core and `eCheck` module. * Upgraded version for the lcobucci/jwt from 3.4.2 to 3.4.6. May 2023 -------- `Adobe Commerce Cloud` `Visa Acceptance Solutions` 3.5.5 is compatible with `Adobe Commerce Cloud`: 2.4.6, 2.4.5 p2, 2.4.5p1, 2.4.4 and PHP 8.2, 8.1 : * PHP support added for v 8.2. * Compatibility with `Adobe Commerce Cloud` v2.4.6 -- Changed few components of zend framework to laminas as per the latest `Adobe Commerce Cloud` changes. * Fixed bugs related to supported card types and sandbox/production issue in Apple Pay. * Fixed jQuery deprecated functions. February 2023 ------------- `Adobe Commerce Cloud` `Visa Acceptance Solutions` 3.5.4 is compatible with `Adobe Commerce Cloud`: 2.4.5 p2, 2.4.5 p1, 2.4.x, 2.3.x : * New implementation for `eCheck` cron -- `EventStatus`. * Fixed bug related to Strong Customer Authentication. * Removed required validation from reCAPTCHA fields. * Updated Klarna library from credit to payments. * Added `PaymentFlowMode` as inline and `PaymentMethodName` as `pay_now` in Klarna app session request. * Updated WSDL version to latest V1.206. * Add new payment reject status as `AUTHORIZED_RISK_DECLINED` for Decision Manager reject. Updating `Adobe Commerce` {#adobe-commerce-m-install} ===================================================== Follow these steps to update the `Visa Acceptance Solutions` bundle to the latest version: 1. In your directory, navigate to the `Adobe Commerce`root directory and find the *composer.json* file. 2. Open the *composer.json* file and in the Require field, change the version to the latest version of the plugin. 3. After you change the version in the Require field of the *composer.json* file, run the composer update command. Configuring `Adobe Commerce` {#adobe-commerce-m-config} ======================================================= Customer payments can be managed through the `Adobe Commerce` or the Visa Acceptance Solutions `Business Center`. This section describes the settings you must configure in the `Business Center` as well as some general use cases that are typical in the day-to-day management of your `Adobe Commerce` store. Contact Visa Acceptance Solutions for information about product availability and enablment. You must complete all of the configuration tasks in order to use the features offered in the `Adobe Commerce` Cybersource integration. Configuring Security Credentials {#adobe-commerce-m-sec-cred-intro} =================================================================== The module uses connection methods to access services that require their own security credentials for authentication. You must create and configure the SOAP toolkit key and REST API key for the `Adobe Commerce` to function properly. If you do not have a `Business Center` account, go to the website to create an account. To activate your merchant account, follow the instructions that are emailed to you. Then log in to the `Business Center` to complete the registration process. Be sure to store your merchant key ID for later use. Creating a SOAP P12 Certificate ------------------------------- The `Adobe Commerce` integration uses the SOAP Toolkit API to access several services. Generate a SOAP P12 certificate from your `Business Center` account. For information on how to create a SOAP P12 certificate, see [Creating a SOAP p12 Certificate](https://developer.cybersource.com/docs/cybs/en-us/so-p12/migration/all/so/so-p12/so-p12-create-p12.md ""). Creating a REST API Key ----------------------- The `Adobe Commerce` integration requires REST API key creation to use some services like Flex Microform and the Fraud Management report. From your `Business Center` account, you also need your merchant key ID and shared secret key to enable the integration with `Adobe Commerce`. For information on how to generate a shared secret key, see . Be sure to store your key ID and shared secret key for later use. Configuring Additional Backend Settings {#adobe-commerce-m-backend-conf-settings} ================================================================================= Some services supported on `Adobe Commerce` require additional backend setup on your `Business Center` account. Contact your `Visa Acceptance Solutions` account representative to enable any of these services: * Payment Tokenization: Required by the module for credit card processing * `Decision Manager` * Payer Authentication * PayPal Express Checkout * `eCheck` Service * Online Bank Transfers * Tax Calculation * Klarna * `Click to Pay`: Enabled in the `Business Center` * Apple Pay: Enabled in the `Business Center` Configuring Backend Settings {#adobe-commerce-m-backend-conf} ============================================================= Follow these steps to access the configuration settings in the administration section of your `Adobe Commerce` console: 1. Go to the `Adobe Commerce` administration console. 2. On the left navigation panel, click Stores. 3. Under Settings, click Configuration. 4. On the Configuration page, click Sales to expand the menu. 5. Click Payment Methods. 6. Choose OTHER PAYMENT METHODS \> `Visa Acceptance Solutions`. #### ADDITIONAL INFORMATION Complete all of the required fields in the sections and subsections of the settings to configure the `Visa Acceptance Solutions` payment module and other payment methods. Expand each section to complete the fields. Configuring General Settings {#adobe-commerce-m-config-gen-settings} ==================================================================== The settings under the General section apply to all payment methods. Follow these steps to complete this section: 1. From the Cybersource setting, click the arrow to expand the General section. 2. From the Debug Mode drop-down list, choose Yes to troubleshoot using the `Adobe Commerce` logs (*cybs.log* ). Diagnostic information is stored in log files on the `Adobe Commerce` web server. 3. From the Sort Order drop-down list, change the default module sort order. 4. In the Show Exact Rejection or Error Message to Users option set to: 5. * No to display general error messages according to `Adobe Commerce Cloud` in all rejection and error cases. * Yes to display general error message according to the responses from `Visa Acceptance Solutions` in all rejection and error cases. {#adobe-commerce-m-config-gen-settings_ul_xsb_hzl_1gc} 6. In the Override Payment Error Route Path field, enter the error page route path. When you leave the default Use system value box checked, the checkout or cart route is used if no path is entered. Configuring WebService {#adobe-commerce-m-conf-webserv} ======================================================= The WebService configuration includes the default `Adobe Commerce` merchant ID (applies to all the payment methods), the REST shared key, and the SOAP key detail. Follow these steps to complete the configuration: 1. Click WebService Configuration to expand the section. 2. In the Merchant ID field, enter your `Visa Acceptance Solutions` merchant ID. 3. From the Test Mode drop-down list, choose: 4. * Yes to use the `Business Center` testing environment. * No to use the production `Business Center`. Optionally, in the Developer ID field, you can enter the developer ID. The ID cannot exceed eight characters. You can also request that `Visa Acceptance Solutions` assign you a developer ID. {#adobe-commerce-m-conf-webserv_ul_hz4_vwz_qhc} 5. In the Simple Order P12 Key File section, upload the SOAP p12 certificate and then enter the Key Password. If you did not generate a key, see [Creating a SOAP p12 Certificate](https://developer.cybersource.com/docs/cybs/en-us/so-p12/migration/all/so/so-p12/so-p12-create-p12.md "") for instructions. 6. In the REST API Key Detail field, enter the REST key you generated from the `Business Center`. If you do not have a REST Shared Secret Key Pair, see [Creating a Shared Secret Key Pair](https://developer.cybersource.com/docs/cybs/en-us/security-keys/user/all/ada/security-keys/keys-manage/keys-rest-shared-intro/restgs-security-key-pair-task.md "") for instructions. #### ADDITIONAL INFORMATION Proper configuration of the SOAP WebService is required for the functioning of other services including Tax Calculation, Secure Acceptance, PayPal, Account Takeover Protection, and Apple Pay. If you experience issues with these modules, verify that the SOAP WebService options are configured correctly. The SOAP p12 Certificate must have the correct password and the Test Mode option must match the correct environment for the `Visa Acceptance Solutions` `Business Center` (test). 7. In the REST API Shared Secret Key field, enter the Shared Secret key you generated from the `Business Center`. If you do not have a REST Shared Secret Key Pair, see [Creating a Shared Secret Key Pair](https://developer.cybersource.com/docs/cybs/en-us/security-keys/user/all/ada/security-keys/keys-manage/keys-rest-shared-intro/restgs-security-key-pair-task.md "") for instructions. #### ADDITIONAL INFORMATION Proper configuration of the REST Web Service is required for other services including Flex Microform, `Decision Manager`, , Google Pay, and the Account Updater. If you experience issues with these modules, verify that the REST Web Service options are configured properly. The API Key Detail and API Shared Secret Key must have the correct value, and the Test Mode option must match the environment for the `Visa Acceptance Solutions` `Business Center`. Configuring Device Fingerprinting {#adobe-commerce-m-conf-device-fp} ==================================================================== Device Fingerprinting is used with `Decision Manager` for all relevant payment methods. If you are not using `Decision Manager`, you must disable this module. Follow these steps to configure device fingerprinting: 1. Click Device Fingerprint to expand the section. 2. In the Active field, choose Yes to activate it or No to deactivate it if you are not using `Decision Manager`. 3. In the Org ID field, enter the value provided to you. To obtain this value either for test or production, contact your `Visa Acceptance Solutions` representative. Configuring the Delivery Address Verification Service {#adobe-commerce-m-backen-conf-davs} ========================================================================================== The Delivery Address Verification Service acts as an additional layer of address verification and normalization on the shipping page. Follow these steps to configure this section: 1. Click Delivery Address Verification Service to expand the section. 2. From the Address verification drop-down list, choose Yes to enable this service or No to disable this service. 3. From the Address Force Normalization drop-down list, choose Yes to require the use of suggested address alternatives or No to make suggested address alternatives optional. {#adobe-commerce-m-backen-conf-davs_ol_pts_cvn_5bc} Configuring Credit Card Payments {#adobe-commerce-m-conf-cc-pay} ================================================================ Follow these steps to configure `Visa Acceptance Solutions` credit card payments: 1. From the Enabled drop-down list, choose Yes to activate or No to deactivate the credit card payment method. 2. In the Title field, enter the text you want to display as the name for credit card payment method. This name will be used for Web Mobile, Flex Microform, and Silent Order Post. 3. In the Payment API drop-down list, choose Payment API to have an authorization performed and post card data to `Visa Acceptance Solutions`. Choose SOAP Toolkit API to have the card information tokenized. The SOAP service separately requests authorizations. 4. In the Checkout Flow Type drop-down list, choose a desired checkout type. #### ADDITIONAL INFORMATION `Visa Acceptance Solutions` recommends that you choose Flex Microform. Flex Microform is a REST-based Microform Integration to access new enhancements, easier configuration, and updated technology. You will use all of the benefits from the Hosted Checkout and Checkout API. The customer never leaves your checkout page and is a potential SAQ A qualification. For more information about Microform Integration, see [Microform Integration](https://developer.cybersource.com/docs/cybs/en-us/digital-accept-flex/developer/all/rest/digital-accept-flex/microform-integ-v2.md ""). 5. In the CSRF Token Expiration Time (Seconds) field, enter the expiration time in seconds. This is the lifetime of the SOP security token used to prevent card testing attacks. For the default of 600 seconds, leave this field blank. Configuring Strong Customer Authentication {#adobe-commerce-m-conf-sca} ======================================================================= When payer authentication is enabled and a transaction is declined with reason code `478` (Strong Customer Authentication required), another request is sent from the `Adobe Commerce` module for the same order. The customer must complete a `3-D Secure` challenge. To configure this setting, click Strong Customer Authentication to expand the section. In the Enforce Strong Customer Authentication when saving a card drop-down list, choose Yes to have the cardholder complete a `3-D Secure` challenge while saving a card. Configuring Credit Card Settings {#adobe-commerce-m-conf-cc-settings} ===================================================================== Follow these steps to complete the Credit Card Settings section: 1. Click Credit Card Settings to expand the section. 2. From the Payment Action drop-down list, choose Authorize Only or Authorize and Capture. Authorize Only reserves funds during checkout and captures when making an invoice. The Authorize and Capture payment action authorizes and captures funds during the customer checkout. 3. From the Auth Indicator drop-down list, choose the purpose of the authorization. 4. From the New Order Status field drop-down list, choose the order status assigned to the order when successfully paid, or leave the default Use system value box checked for Processing order status. 5. From the Ignore AVS drop-down list, choose Yes to have the results of AVS verification ignored. 6. In the Ignore CVN field, choose Yes to have the results of CVN verification ignored. 7. In the Skip Fraud Management for Tokenization field, choose **No** to have Skip Decision Manager field set to `false` for Secure Acceptance tokenization requests and set to `true` otherwise. 8. In the Skip Pre-Authorization Check for Tokenization field, choose to No to have the skip preauthorization field set to `false` for Secure Acceptance tokenization requests and set to `true` otherwise. 9. In the Pass expiration date for tokenized card via SOAP field, specify the card expiration date with SOAP Toolkit Authorization Calls for card tokenization. 10. In the Credit Card Types box, choose which card types you want to accept. This only applies to Checkout API and Flex Microform configuration. This option is not used for Hosted Checkout. 11. In the Payment from Applicable Countries field, leave the default Use system value box checked to accept credit card payments from the countries choose, or clear the Use system value box to specify countries in the next field. 12. To specify the countries from which to accept credit card payments, in Payment from Specific Countries box choose the countries. 13. From the Override secure acceptance locale drop-down list, leave the default Use system value box checked to use the store locale language. Configuring Payer Authentication {#adobe-commerce-m-config-payer-auth} ====================================================================== The Payer Authentication (`3-D Secure`) protocol reduces fraud and security to online payments. `3-D Secure` adds frictionless authentication and improves the user experience. You must have the SOAP Toolkit configured to use this service. Follow these steps to configure the Payer Authentication section: 1. Click Payer Authentication to expand the section. 2. From the Enabled drop-down list, choose Yes to activate the Payer Authentication Module or No to deactivate it. 3. From the Credit Card Types field box, choose the card types to be enabled for Payer Authentication. Configuring Save Card for Later Service {#adobe-commerce-m-conf-save-later-service} =================================================================================== Follow these steps to configure Save Card for Later Service settings: 1. Click Save Card for Later Service to expand the section. 2. From the Enabled drop-down list, choose Yes to enable the customer to save their credit card information securely for later use. 3. In the Saved Card Section Title field, enter the name of the saved cards payment method. 4. From the Save Card for Later for Admin orders drop-down list, choose Yes to enable storing card details for orders placed in the admin area. 5. From the Use CVV for Saved Credit Cards drop-down list, choose Yes to enable the customer to enter the Card Security Code when paying with a stored card. 6. From the Use CVV for Saved Credit Cards in Admin drop-down list, choose Yes to allow the merchant to enter the customer's Card Security Code when the customer is paying with a stored card. 7. Click Save Config. Configuring reCAPTCHA {#adobe-commerce-m-conf-recaptcha} ======================================================== The `Adobe Commerce` SOAP Toolkit API provides an option to use reCAPTCHA. This feature is essential in protecting the merchant's store from brute force attacks. Most of the time, the reCAPTCHA is invisible to normal users, but it will provide a visible challenge when necessary. The module providing reCAPTCHA is an optional package. Installing reCAPTCHA {#adobe-commerce-m-conf-recaptcha_Installation} -------------------------------------------------------------------- To install reCAPTCHA, run the following command for composer installation: `composer require ``Visa Acceptance Solutions``/module-recaptcha ` Creating reCAPTCHA {#adobe-commerce-m-conf-recaptcha_Creating_reCAPTCHA} ------------------------------------------------------------------------ Follow these steps to generate Google reCAPTCHA Site Key and Secret Key: 1. Visit the Google reCAPTCHA website: [](https://www.google.com/recaptcha/about/ ""). 2. Log in to the reCAPTCHA Admin Console. 3. Click the Create icon. 4. Fill in the required details. 5. After you submit the details, the reCAPTCHA site key and secret key are generated. Use these keys to configure the module in Back Store. Configuring reCAPTCHA in `Adobe Commerce` {#adobe-commerce-m-conf-recaptcha_Configure_reCAPTCHA_in_back-store} -------------------------------------------------------------------------------------------------------------- 1. Go the `Adobe Commerce` console. 2. On the Payment Methods page, under the `Visa Acceptance Solutions` settings, click reCaptcha to expand the section. 3. From the Enabled drop-down list, choose Yes to activate, or No to deactivate reCAPTCHA. 4. In the Website API Key field, enter your site key obtained from reCAPTCHA Admin Console. 5. In the Secret API Key field, enter your secret key obtained from reCAPTCHA Admin Console. 6. From the reCAPTCHA type drop-down list, choose the reCAPTCHA type that you choose for your API keys. 7. In the Badge position field, choose the reCAPTCHA badge position. 8. In the reCAPTCHA language field, choose a language code for reCAPTCHA or leave the Auto option selected. 9. Click Save Config. 10. Clear the `Adobe Commerce` cache. {#adobe-commerce-m-conf-recaptcha_ol_hth_wl5_pbc} Configuring the `eCheck` Payment Module {#adobe-commerce-m-conf-echeck-pay-module} ================================================================================== The `Visa Acceptance Solutions` `eCheck` module enables customers to make purchases using a routing number and an account number. During checkout, an `eCheck` transaction request is sent to `Visa Acceptance Solutions`. If successful, the transaction is sent to the Automated Clearing House (ACH). The `Adobe Commerce` queries `Visa Acceptance Solutions` periodically to check on the status of each pending `eCheck` transaction. In response, `Visa Acceptance Solutions` provides an updated transaction status, known as a *Payment Event Type* . Various outcomes can occur during ACH processing. For each pending transaction included in the `Visa Acceptance Solutions` response, the `Adobe Commerce` determines whether a transaction remains pending, settles, or is rejected. You can configure these `eCheck` payment event types : * Pending Event Type: No change is made to the transaction or order status. The order remains in Payment Pending state. * Reject Event Type: The order is cancelled. * Accept Event Type: An invoice is prepared for that order, and the order status changes to processing. {#adobe-commerce-m-conf-echeck-pay-module_ul_gyb_bwg_qbc} Testing `eCheck` Payment Settings {#adobe-commerce-m-conf-echeck-pay-settings} ============================================================================== You can test the `eCheck` Payment Event Types using two `Adobe Commerce` settings that simulate possible event types during the processing of the requested report. While the status request goes to `Visa Acceptance Solutions`, the `Adobe Commerce` ignores the returned Payment Event Type in the response and uses the Test Event Type instead. Follow these steps to test the `eCheck` Payment Event Types: 1. Click `eCheck` to expand the section. 2. From the Enabled drop-down list, choose Yes to enable the `eCheck` payment method. 3. In the Title field, enter the text that is displayed to customers as the name of this payment method. 4. Configure the payment statuses for these event types: #### ADDITIONAL INFORMATION * In the Accept Event Type box, choose which payment statuses will mean accept, and signify the receipt of funds and move the order status to processing. * In the Pending Event Type box, choose which payment statuses will mean pending. * In the Reject Event Type box, choose which payment statuses will mean reject because they were rejected after processing by ACH despite being initially accepted during checkout. {#adobe-commerce-m-conf-echeck-pay-settings_ul_fx5_1rx_x2c} 5. Configure how to accept the `eCheck` payment method: #### ADDITIONAL INFORMATION * To accept the default country configuration, in the Payment From Applicable Countries field, ensure the Use system value box is checked. * To specify any other countries you will accept the `eCheck` payment method from, clear the Use system value box and in the Payment From Specific Countries box, choose the countries. {#adobe-commerce-m-conf-echeck-pay-settings_ul_vhk_v5x_x2c} 6. To require customers to enter a drivers license number, from the Enabled Drivers License Number drop-down list, choose Yes. For `TeleCheck`, contact a representative to see if this field is required. 7. To require the customer to enter the check number, from the Enabled Check Number drop-down list, choose Yes. These processors have specified whether it is required or optional: #### ADDITIONAL INFORMATION * `Chase Paymentech Solutions`: Optional. * `Cybersource ACH Service`: Not used. * : Optional on debits, and required on credits. * `TeleCheck`: Strongly recommended on debit requests, and optional on credits. {#adobe-commerce-m-conf-echeck-pay-settings_ul_trs_z1h_qbc} 8. To require an agreement at the checkout page, from the Agreement Required drop-down list, choose Yes. 9. From the SEC code drop-down menu, choose a code that specifies the authorization method for the transaction. 10. In the Sort Order field, enter the number of entries to be sorted on a page. 11. Click Save Config. Configuring Fraud Management {#adobe-commerce-m-fraud-mgmt-intro} ================================================================= You must configure the `Adobe Commerce` to work with Fraud Management to use all of the features. Follow these steps to configure Fraud Management in `Adobe Commerce`: 1. Click Fraud Management to expand the section. 2. From the Enable Fraud Management CRON Job drop-down list, choose Yes. 3. In the Fraud Management fail email sender option, leave the Use system value box checked. 4. In the Fraud Management fail email template option, leave the Use system value box checked. 5. From the Settle Fraud Management accepted order automatically drop-down list, choose Yes. 6. Expand the **On-Demand Job** section to see the Report Date field. 7. Enter a date to download an accepted or rejected transactions report, and click **Run**. 8. Click Save Config. {#adobe-commerce-m-fraud-mgmt-intro_ol_gmv_mn5_3bc} Fraud Management Orders ----------------------- The `Decision Manager` rule setting and the response received for authorizations and sales service determine whether the `Adobe Commerce Cloud` marks the orders as Pending Review. On the `Decision Manager` Case Management page, when you change an order from REVIEW to REJECT or ACCEPT, the `Adobe Commerce Cloud` updates payment transaction states periodically (by cron every two minutes) by contacting Cybersource and querying for changes. In the settings, find the `Adobe Commerce Cloud` Cron settings and configure them to trigger an `Adobe Commerce Cloud` task. The task looks for `Decision Manager` changes in the `Business Center` and updates the `Adobe Commerce Cloud` Orders accordingly. If the module detects a change in state, it updates the order status in the `Adobe Commerce Cloud` from Pending Review to one of these states: * Processing * Pending * Closed {#adobe-commerce-m-fraud-mgmt-intro_ul_r3w_jkr_4bc} If an order is Pending Review in `Decision Manager`, you cannot prepare an invoice in the `Adobe Commerce Cloud` until `Decision Manager` accepts it. Fraud Management Refunds ------------------------ `Decision Manager` must either accept or reject an order before issuing a refund. If you reject an order in `Decision Manager`, an Authorization Reversal for the order automatically occurs as part of the Cron process that queries for updates in `Decision Manager`. Configuring Custom Fields ------------------------- `Decision Manager` supports custom fields known as merchant-defined data fields. You must configure the fields inside `Decision Manager` in the `Business Center` to use them. The Module for the `Adobe Commerce Cloud` sends 10 of these fields. Follow these steps to add custom fields provided by the `Adobe Commerce Cloud`: 1. Log in to the `Business Center` and go to `Decision Manager` \> Shared Configuration \> Custom Fields. 2. Choose Merchant Custom Fields. 3. To add a field, click ADD CUSTOM FIELD, enter a name, and choose an order element. Use the list below to map the correct names and elements for each field: * Logged-in customer: Merchant_defined_data1 * Account creation date: Merchant_defined_data2 * Purchase History Count: Merchant_defined_data3 * Last Order Date: Merchant_defined_data4 * Member account age: Merchant_defined_data5 * Repeat customer: Merchant_defined_data6 * Coupon Code Used: Merchant_defined_data20 * Discount Amount: Merchant_defined_data21 * Gift Message: Merchant_defined_data22 * Order Source: Merchant_defined_data23 * Shipping Method Code: Merchant_defined_data31 * Shipping Method Description: Merchant_defined_data32 {#adobe-commerce-m-fraud-mgmt-intro_ul_wmw_5fh_sbc} 4. Click Save. For detailed instructions on how to add custom fields, see the *Decision Manager* Guide. In the `Business Center`, go to the left navigation panel, and choose Decision Manager \> Documentation \> Guides. Configuring Apple Pay {#adobe-commerce-m-conf-apple-pay} ======================================================== To use Apple Pay, you must meet these prerequisites: * Have a valid Apple Developer Account. {#adobe-commerce-m-conf-apple-pay_ul_pgs_kgh_qbc} * All pages that incorporate Apple Pay must be served over HTTPS. * Your website must comply with the Apple Pay guidelines. For more information, see [Apple Pay on the Web Acceptable Use Guidelines](https://developer.apple.com/documentation/applepayjs/setting_up_server_requirements ""). * Your website must have HTTPS mode enabled and used at checkout. For more information, see [Setting Up Your Server](https://developer.apple.com/documentation/applepayjs/setting_up_server_requirements ""). {#adobe-commerce-m-conf-apple-pay_ul_r1f_kgh_qbc} To configure Apple Pay with the `Adobe Commerce` module, you must complete these tasks: 1. Register an Apple Pay merchant ID. For more information, see [Create Your Apple Pay Merchant ID](https://developer.apple.com/documentation/applepaywebmerchantregistrationapi/registering_with_apple_pay_and_applying_to_use_the_api/#3696536 ""). 2. Create a Payment Processing certificate in the `Business Center`. For more information, see [Part 2: Create an Apple Pay Payment Processing Certificate](https://developer.cybersource.com/docs/cybs/en-us/apple-pay/developer/ctv/rest/applepay/applepay-cfg/applepay-cfg-2-pay-proc-cert.md ""). 3. Validate your store domain in Apple Pay. For more information, see [Register a Merchant Domain](https://developer.apple.com/help/account/configure-app-capabilities/configure-apple-pay-on-the-web#register-a-merchant-domain ""). 4. Create a Merchant Identity certificate. For more information, see [Create a Merchant Identity Certificate](https://developer.apple.com/help/account/configure-app-capabilities/configure-apple-pay-on-the-web#create-a-merchant-identity-certificate ""). {#adobe-commerce-m-conf-apple-pay_ol_kmf_zgh_qbc} Configuring the Apple Pay Extension {#adobe-commerce-m-conf-apple-pay-ext} ========================================================================== Follow these steps to configure the Apple Pay extension: 1. Go the `Adobe Commerce` console, and open the Payment Methods page. 2. Under the `Visa Acceptance Solutions` settings, click Apple Pay to expand the section. 3. From the Enable drop-down list, choose Yes to activate Apple Pay. (or No to deactivate it.) 4. In Title box, enter the text to display to customers on the checkout page. 5. From the Payment Action drop-down list, choose Authorize Only to reserve funds during checkout and capture during invoice creation. Choose Authorize and Capture to authorize and capture during customer checkout. 6. From the New Order Status drop-down list, choose the order status assigned to an order that was successfully paid with `Visa Acceptance Solutions`. 7. In the Apple Merchant ID box, enter your Apple Pay Merchant ID. 8. In the Apple Display Name box, enter the business name that appears on a bank or credit card statement. For example, COMPANY, INC. 9. In the Certified Domain box, enter the validated site domain on which the service is meant to be used. Do not enter a `https://` prefix. 10. In the Path to Certificate box, enter the full path to the Merchant ID Certificate file. 11. In the Path to Key box, enter the full path to the Merchant ID Certificate Private key file. 12. In the Credit Card Types box, choose the types of credit cards to accept for payment. 13. In the Sort Order box, enter a number for the sort order. Configuring Apple Pay {#adobe-commerce-m-conf-apple-pay-storefront} =================================================================== You must configure Apple Pay on your storefront that is displayed to the customer. Follow these steps to configure Apple Pay on your storefront: 1. While the customer is making a payment, in the Reviewing the order page, the customer chooses `Adobe Commerce` Apple Pay. 2. An Apple Pay window appears, requesting fingerprint (Touch ID) authentication but you can also choose a saved card. 3. After authentication is complete, an order success page appears. Verify the transaction details in `Business Center`. Configuring Google Pay {#adobe-commerce-m-conf-google-pay} ========================================================== To use Google Pay on the `Adobe Commerce`, your site must be running through HTTPS. Follow these steps to configure Google Pay in the `Adobe Commerce`: 1. Click Google Pay to expand the section. 2. From the Enable drop-down list, choose Yes to activate Google Pay. (or No to deactivate Google Pay.) 3. In the Title box, enter text to display to customers on the checkout page. 4. From the Payment Action drop-down list, choose Authorize Only to reserve funds during checkout and capture during invoice creation. Choose Authorize and Capture to authorize and capture funds during customer checkout. 5. In the Google Pay Merchant ID box, enter your Google Pay merchant ID. 6. In the Merchant Display Name box, define your business name that appears on a customer's bank or credit card statement. For example, "COMPANY, INC." 7. Configure which countries you will accept Google Pay from: #### ADDITIONAL INFORMATION * To accept payment from the default countries, in the Payment From Applicable Countries field, leave the Use system value box checked. * To specify other countries, clear the Use system value box and in the Payment From Specific Countries box, choose the countries from where you want to accept Google Pay. {#adobe-commerce-m-conf-google-pay_ul_rjq_zxx_x2c} 8. In the Credit Card Types field box, choose which card types to accept. 9. To show the Google Pay button on the product page, in the Google Pay button on Product Page field, choose Yes. 10. To show the mini cart widget, in the Google Pay button in mini cart field, choose Yes. 11. In the Sort Order box, enter a number to change the default module sort order. 12. Click Save Config. Configuring Alternate Payments {#adobe-commerce-m-conf-alt-pay} =============================================================== The `Adobe Commerce` has four types of Alternate Payments modules: * PayPal. For more information, see [Configuring PayPal](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview/adobe-commerce-m-backend-conf-settings/adobe-commerce-m-conf-alt-pay/adobe-commerce-m-conf-paypal.md ""). * Klarna. For more information, see [Configuring Klarna](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview/adobe-commerce-m-backend-conf-settings/adobe-commerce-m-conf-alt-pay/adobe-commerce-m-conf-klarna.md ""). * Bank Transfer. For more information, see [Configuring Bank Transfers](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview/adobe-commerce-m-backend-conf-settings/adobe-commerce-m-conf-alt-pay/adobe-commerce-m-conf-bank-transfers.md ""). * WeChat Pay. For more information, see [Configuring WeChat Pay](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview/adobe-commerce-m-backend-conf-settings/adobe-commerce-m-conf-alt-pay/adobe-commerce-m-conf-wechat-pay.md ""). {#adobe-commerce-m-conf-alt-pay_ul_m5y_3j3_qbc} Click Alt Payments to expand the section. Configuring Klarna {#adobe-commerce-m-conf-klarna} ================================================== Follow these steps to configure Klarna payments.You can use the default merchant ID or you can manually configure a new merchant ID: 1. Click Klarna to expand the section. 2. From the Enable drop-down list, choose Yes or No to activate or deactivate Klarna. 3. From Title box, enter the text to display to customers on the checkout page. 4. From the Use Default Merchant ID drop-down list, leave Yes selected to use the Merchant ID given in Web Service Configuration under General Settings. Choose No to enter another merchant ID and transaction key in the next two fields. 5. If you choose not to use the default merchant ID, in the Merchant ID field, enter a different merchant ID. 6. In the Transaction Key field, enter the transaction key for the merchant ID you entered. 7. From the New Order Status drop-down list, choose the order status assigned to the order successfully paid with `Visa Acceptance Solutions`. 8. Configure which countries you will accept Klarna from: #### ADDITIONAL INFORMATION * To accept payment from the default countries, in the Payment From Applicable Countries field, leave the Use system value box checked. * To specify other countries, clear the Use system value box and in the Payment From Specific Countries box, choose the countries from where you want to accept Google Pay. {#adobe-commerce-m-conf-klarna_ul_rjq_zxx_x2c} Configuring PayPal {#adobe-commerce-m-conf-paypal} ================================================== Follow these steps to configure the PayPal Express Checkout, PayPal Credit, and PayPal Billing Agreement: 1. Click PayPal to expand the section. 2. From the Enable drop-down list, choose Yes or No to activate or deactivate PayPal. 3. In Title box, enter the text to display to customers on the checkout page. 4. From the New Order Status drop-down list, choose the order status assigned to the order successfully paid with Cybersource. 5. In the Merchant ID field, enter your `Adobe Commerce Cloud` merchant ID. 6. From the PayPal Redirection Type drop-down list, choose Traditional Express Checkout to redirect the customer PayPal Payment Page, or choose In-Context Express Checkout for a PayPal pop-up to appear for customers to complete payment. 7. From the Payment Action drop-down list, choose Authorize Only to check the account for validity, but not charge until the order is approved and invoiced. Choose Authorize and Capture to charge the PayPal account at the time the order is submitted. 8. Configure which countries you will accept PayPal from: #### ADDITIONAL INFORMATION * To accept payment from the default countries, in the Payment From Applicable Countries field, leave the Use system value box checked. * To specify other countries, clear the Use system value box and in the Payment From Specific Countries box, choose the countries from where you want to accept PayPa. {#adobe-commerce-m-conf-paypal_ul_rjq_zxx_x2c} 9. From the Enable PayPal Credit drop-down list, choose Yes to enable financing through PayPal Credit. 10. In the PayPal Credit Title box, enter the text customers will see as the title of PayPal Credit payment option. 11. From the Enable PayPal Billing Agreements drop-down list, choose Yes to allow registered customers to create a billing agreement for faster purchases. 12. In the Sort Order box, enter a numeric value to place this payment method amongst all the other `Adobe Commerce` payment methods. Configuring Bank Transfers {#adobe-commerce-m-conf-bank-transfers} ================================================================== Online banking services enable customers to pay for goods using direct online bank transfers from their bank account to your `Adobe Commerce` merchant account. Click Bank Transfer to expand the section. In the Store Name field, enter the name you want customers to see on their bank transfer invoices. Configuring iDEAL {#configuring-ideal} -------------------------------------- Follow these steps to configure an iDEAL payment: 1. Click iDEAL to expand the section. 2. In the Enable drop-down list, choose Yes to activate the iDEAL bank transfer (or No to deactivate iDEAL bank transfer.) 3. In Title box, enter the text to display to customers on the checkout page. 4. In the Use Default Merchant ID field, leave Yes selected to use the merchant ID given in the Web Service Configuration under General Settings page. Choose No to enter another merchant ID and transaction key in the next two fields. 5. If you choose not to use the default merchant ID, enter your `Visa Acceptance Solutions` Merchant ID in the Merchant ID field. 6. In the Transaction Key field, enter the transaction key for the merchant ID you entered. 7. In the Allowed Currencies box, choose which currencies you will accept payment. 8. In the Sort Order box, change the default module sort order. 9. Configure which countries you will accept Klarna from: #### ADDITIONAL INFORMATION * To accept payment from the default countries, in the Payment From Applicable Countries field, leave the Use system value box checked. * To specify other countries, clear the Use system value box and in the Payment From Specific Countries box, choose the countries from where you want to accept iDEAL. {#configuring-ideal_ul_rjq_zxx_x2c} Configuring Bancontact {#Configuring-Bancontact} ------------------------------------------------ Follow these steps to configure Bancontact bank transfer payments: 1. Click Bancontact to expand the section. 2. In the Enable drop-down list, choose Yes or No to activate or deactivate Bancontact Bank Transfer. 3. In Title box, enter the text to display to customers on the checkout page. 4. In the Use Default Merchant ID field, leave Yes selected to use the Merchant ID given in Web Service Configuration under General Settings. Select No to enter another merchant ID and transaction key in the next two fields. 5. If you choose not to use the default merchant ID, enter your `Visa Acceptance Solutions` merchant ID in the Merchant ID field. 6. In the Transaction Key field, enter the transaction key for the merchant ID you entered. 7. In the Allowed Currencies box, choose the currencies with which to accept payment. 8. In the Sort Order box, change the default module sort order. 9. Configure which countries you will accept Klarna from: #### ADDITIONAL INFORMATION * To accept payment from the default countries, in the Payment From Applicable Countries field, leave the Use system value box checked. * To specify other countries, clear the Use system value box and in the Payment From Specific Countries box, choose the countries from where you want to accept Bancontact. {#Configuring-Bancontact_ul_rxx_b1y_x2c} Configuring WeChat Pay {#adobe-commerce-m-conf-wechat-pay} ========================================================== WeChat Pay is a digital wallet that enable customers to make mobile payments and online transactions. Customers who have provided bank account information can use the app to pay bills, order goods and services, transfer money to other users, and pay in stores if the stores have a WeChat payment option. Follow these steps to configure WeChat Pay: 1. Click WeChat Pay to expand the section. 2. From the Enable drop-down list, choose Yes to activate or deactivate WeChat Pay (or No to deactivate WeChat Pay.) 3. In the Sort Order box, change the default module sort order. 4. In Title box, enter the text to display to customers on the checkout page. 5. In the Use Default Merchant ID field, leave Yes selected to use the merchant ID from the Web Service Configuration section under General Settings. Choose No to enter another merchant ID and transaction key in the next two fields. 6. If you choose not to use the default merchant ID, enter your `Visa Acceptance Solutions` merchant ID in the Merchant ID field. 7. In the Transaction Key field, enter the transaction key for the merchant ID you entered. 8. In the QR Code Expiration Time field, enter an expiration time in seconds for the WeChat pay QR code. 9. In the Check Status Frequency field, enter an interval in seconds between transaction status checks. 10. In the Max Status Requests field, enter a limit for transaction status checks. 11. Configure which countries you will accept WeChat Pay from: #### ADDITIONAL INFORMATION * To accept payment from the default countries, in the Payment From Applicable Countries field, leave the Use system value box checked. * To specify other countries, clear the Use system value box and in the Payment From Specific Countries box, choose the countries from where you want to accept WeChat Pay. {#adobe-commerce-m-conf-wechat-pay_ul_rxx_b1y_x2c} 12. In the Success/Failure Message Delay field, enter a delay in seconds between the transaction check and redirection to the result page. 13. In the Check Status query Simulated Response field, choose a simulated status check response code for testing. 14. Click Save Config. Configuring Taxes {#adobe-commerce-m-conf-taxes} ================================================ `Visa Acceptance Solutions` offers a service that calculates taxes to be charged on orders. You must configure your settings in order to receive accurate results Contact your `Visa Acceptance Solutions` representative to have this feature enabled. This feature includes activation of sandbox capabilities as well. Before configuring the Tax Calculation service, you must have the SOAP Web Service configured. For more information, see [Configuring Security Credentials](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview/adobe-commerce-m-sec-cred-intro.md ""). To use the Tax Calculation Service, you must have the Product Tax Class codes and `Visa Acceptance Solutions` Tax Services settings configured. For more information, see [Configuring Product Tax Classes](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview/adobe-commerce-m-backend-conf-settings/adobe-commerce-m-conf-taxes/adobe-commerce-m-conf-prod-tax-class.md "") and [Configuring Visa Acceptance Solutions Tax Services Settings](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/adobe-commerce-m-overview/adobe-commerce-m-backend-conf-settings/adobe-commerce-m-conf-taxes/adobe-commerce-m-conf-tax-serv-settings.md ""). Configuring Product Tax Classes {#adobe-commerce-m-conf-prod-tax-class} ======================================================================= Each product in the `Adobe Commerce` has a setting for Tax Class. This setting defines the product and how it should be taxed. Contact your `Visa Acceptance Solutions` representative for a list of available product tax class IDs and your tax consultant for advice on which IDs you should use for products you sell. Follow these steps to set the product tax class IDs in `Adobe Commerce`: 1. Go the `Adobe Commerce` Admin console. 2. On the left panel, click Stores, and then click Tax Classes. 3. On the Tax Classes page, click Add New to create a new tax class entry for each tax class ID that your representative provides. 4. In the Tax Class Code field, enter the code provided to you. 5. From the Tax Class Type drop-down list, choose Product. 6. Click Save. 7. Complete these steps for each tax class ID. Configuring `Visa Acceptance Solutions` Tax Services Settings {#adobe-commerce-m-conf-tax-serv-settings} ======================================================================================================== Follow these steps to configure `Visa Acceptance Solutions` Tax Services in the `Adobe Commerce Cloud`: 1. Go to the `Adobe Commerce Cloud` admin console, and in the left panel, click Stores, and then click Configuration. 2. On the Configuration page, go to Sales \> Tax \> Cybersource Tax Services. 3. From the Tax Calculation drop-down list, choose Yes to activate the `Visa Acceptance Solutions` Tax Services per your business requirements. 4. In the Nexus regions box, select the regions where your business has a physical presence in the U.S. or Canada. 5. In the Customer countries to calculate Tax for box, choose the countries for which you will calculate tax. 6. In the Customer Tax classes to exclude from Tax calculation box, choose the customer tax classes to exclude from tax calculation. 7. In the Ship From fields, enter the city, postcode, country, and region from which the orders are shipped. 8. In the Acceptance fields, enter the city, postcode, country, and region in which you will accept or approve customers' orders. 9. In the Origin fields, enter the city, postcode, country, and region of the point of origin from which the order is picked up. 10. In the Merchant VAT fields, enter the merchant VAT seller registration number. 11. Click **Save Config**. Calculating Taxes for Shipping Rates {#calc-ship-rates} ------------------------------------------------------- You might have taxes calculated for shipping rates if your site offers dynamic shipping rates from a carrier that is presented to the customer at checkout. However, if you offer a flat-rate shipping charge, you might want to add taxes to that flat rate. Follow these steps to add taxes to flat shipping rates: 1. On the Configuration page, go to Sales \> Tax \> Tax Classes. 2. From the Tax Class for Shipping drop-down list, select the product tax code that references the taxes applied to shipping services. 3. Click **Calculation Settings**. 4. In the Shipping Prices field, choose Excluding Tax when the shipping rates need to be taxed. Select Including Tax when the shipping rates already include taxes , and no taxes are applied through the `Visa Acceptance Solutions` tax service. 5. Click **Save Config**. Configuring Transactional Emails {#adobe-commerce-m-conf-trans-emails} ====================================================================== When an order is flagged for `Decision Manager` review, the customer is not informed that their transaction was not fully accepted. If a manual review leads to a rejection of the transaction, the customer is then informed that their order is no longer active. You can configure the email sent to the customer. Follow these steps to configure the transactional emails sent to the customers: 1. Go to the `Adobe Commerce` console. 2. On the left panel, choose Marketing. 3. Click Email Templates. 4. In the table, find the Template column, and click the DM Fail Transaction template row. The Template Information page opens. 5. On the Template Information page, complete the required information in the template name, subject, and content text boxes. 6. Click Save Template. Configuring Cron Settings {#configuring-cron-settings} ====================================================== Follow these steps to configure Cron settings for `Decision Manager`: 1. In the `Adobe Commerce` console. 2. On the left panel, click Stores. 3. Go to Configuration \> Advanced \> System \> Cron (Scheduled Tasks). 4. Scroll down and click Cron configuration options for group:dm. 5. Complete the required fields. 6. Click Save Config. For further instructions on how to configure Cron settings, see [Cron (scheduled tasks)](https://experienceleague.adobe.com/en/docs/commerce-admin/systems/tools/cron ""). Configuring Tokens {#adobe-commerce-m-conf-tokens} ================================================== When a customer is logged in and is checking out, their card data can be stored in a secured `Visa Acceptance Solutions` data center. After the card data is saved, a token is provided to you through this module. This token represents the customer record. When a returning customer uses your checkout, they can opt to use a previously stored card so they don't have to enter their card data again. When a token is used, the customer is still redirected to the `Visa Acceptance Solutions` Hosted Payment page for payment confirmation. If a customer chooses to checkout as a guest, the token system is not used. Saving a Card for Later Use --------------------------- To save the card, log in or register a new customer account. During the checkout process, check the Save for later use box. After the order is placed, the card information is securely saved with `Visa Acceptance Solutions`. Managing the `Adobe Commerce` Tokens ------------------------------------ Customers who are logged in can delete their tokens at any time. To do so, they must visit the My Account section of the `Adobe Commerce` and choose the Stored Payment Methods menu item. Customers can use the delete links beside any stored tokens to remove a stored token. Paying with Tokens ------------------ To pay the order with a stored card, the customer chooses it from the list at the top of the Billing and review checkout page. Multi-Shipping Feature {#adobe-commerce-m-multi-ship} ===================================================== The plugin supports the multi-shipping feature only for the `Adobe Commerce` registered users when they place orders with stored credit cards. Node Implementation {#adobe-commerce-m-node-impl} ================================================= The plugin does not support multiple-node implementation. Support {#adobe-commerce-m-support} =================================== If you require support with this software, create a support ticket at [support](https://visaacceptance.com/support "") and provide this information: * Summary of the issue * Steps to reproduce the issue * Magento platform version `Visa Acceptance Solutions` plug-in version * Visa Acceptance Solutions merchant ID * Configuration screenshots * All the themes/additional extensions that are installed * Log files To retrieve log files, navigate to this path in the root directory of Magneto: `Magento Folder Name\var\log`. These log files are needed: * `system.log` * `debug.log` * `cybs.log` * `exception.log` OpenCart {#opencart-overview} ============================= The plugin for OpenCart provides a payment solution for merchants using OpenCart to manage their orders. This section describes the payment methods and services the Plugin provides. Supported payment methods {#opencart-overview_section_xnl_nkh_sbc} ------------------------------------------------------------------ These are the supported payment methods for OpenCart: * Credit and debit cards * `eCheck` * `Click to Pay` {#opencart-overview_ul_znl_nkh_sbc} Supported payment services -------------------------- These are the supported payment services available for OpenCart: * **Payment acceptance services** * Authorization only * Sale (bundled authorization and capture) * Electronic check debit (sale) for `eCheck` payment method * **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 cards 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 theses `Business Center` reports into OpenCart** : * Transaction Request Report * Payment Batch Detail Report * Conversion Detail Report Release Information {#opencart-release-info} ============================================ This section provides information about the releases for the plugin. | Release Version | Release Date | Support End Date | |:----------------|:-----------------|:-----------------| | Version 22.1.0 | October 25, 2022 | October 14, 2025 | | Version 23.1.0 | December 8, 2023 | December 7, 2026 | Version 23.1.0 includes the following enhancements: * Updated authentication signature * Added DAV enable/disable button for admin configuration * Updated reCAPTCHA key generation tooltip URL * Fix for target origin issue for different domain in the flex form capture context * Compatible with OpenCart versions 3.0.3.7 and 3.0.3.8 Version 22.1.0 * Initial release. Installation {#opencart-install-plugin} ======================================= Before you install the plugin, make sure that these requirements are met: * You are using `OpenCart` version 23.1.0. * You have a `Business Center` account and have generated `Business Center` REST API keys: * To create an account, go to the website. * To generate REST API keys, see . Follow these steps to install the plugin: 1. [Download the plugin](https://www.opencart.com/index.php?route=marketplace/extension/info&extension_id=44321 "") from the `OpenCart` website to your local system. 2. Open `OpenCart` Back Office and from the Dashboard, choose Extensions \> Installer. 3. Click Upload and browse to the file you downloaded to your local system. 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 Overview {#opencart-config-intro} =============================================== This section describes how to set up the plugin. The following table shows where to access the plugin configuration settings. From the left navigation panel in `OpenCart` Back Office, select **Extensions** and follow the path indicated in the table for the configuration settings you want to configure. | Settings | Path | |-------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| | * General Configuration * Report Configuration * Order Status Configuration | Extensions \> Extensions \> Modules \> `Visa Acceptance Solutions` Configuration | | `Unified Checkout` * Payment Action * Payer Authentication * Status * Sort Order * Tokenization * Limit Saved Card Rate * Enforce SCA for Saving Card | Extensions \> Extensions \> Payments \> `Visa Acceptance Solutions` `Unified Checkout` | | `eCheck` * Status * Sort Order | Extensions \> Extensions \> Payments \> `Visa Acceptance Solutions` `eCheck` | [Configuration Settings] Enable Basic Configuration {#opencart-config-basic} =================================================== This section describes the required and optional basic configuration settings for the plugin. To enable Basic Configuration, follow these steps: 1. In `OpenCart` Back office, navigate to Extensions \> Extensions \> Modules \> `Visa Acceptance Solutions` Configuration. 2. Click the Edit icon. 3. In the General Configuration tab of the Edit `Visa Acceptance Solutions` Configuration Module pane, from the drop down list or text box, select or enter a setting. 4. Click the Save icon. 5. Repeat for each required setting and each optional setting you want to enable. Required Settings ----------------- These settings are required for using the plugin: Sandbox Mode : Set to Enable to operate in Sandbox (T) mode. You can test new changes in this mode and no funds are affected. : Set to Disable to operate in Production (Live) mode. Merchant ID : Enter the `Business Center` Merchant ID or Organization ID, which is a unique identifier for the merchant. Merchant Key ID : Enter your REST Shared Secret Key generated from within the `Business Center`. This specific key authenticates and authorizes the merchant's integration with the gateway. Merchant Secret Key : Enter the complimentary Secret key that is generated at the same time as the Merchant Key ID. It is used for secure communication between the merchant's online store and a payment gateway. {#opencart-config-basic_dl_djx_z1n_sbc} reCAPTCHA Site key : For each request, this key returns a score based on the user interactions with your site. Based on these scores, you can take appropriate actions for your site, such as allowing or blocking users. reCAPTCHA Secret key : This key authorizes communication between the plugin's backend and the reCAPTCHA server to verify the user's response. The secret key should be kept safe for security purposes. {#opencart-config-basic_dl_ejx_z1n_sbc} Optional Settings ----------------- These settings are optional for using the plugin. Fraud Management : Click Enable to enable merchants to identify and prevent fraudulent activities. Delivery Address Verification : Click Enable to enable merchants to verify the delivery address. Device Fingerprint : Click Enable to enable merchants to identify and track devices accessing an online store. Developer ID : Identifier for the developer that helps integrate a partner solution with `Visa Acceptance Solutions`. This settings is only required for `Visa Acceptance Solutions` System Integrators. Status : Click Enable for the `Visa Acceptance Solutions` integration to be active and visible at checkout. Payment Action : Click Enable to enable card payments for Authorize Only or Sale (Authorization and Capture) for front office transactions. Enhanced Logs : Click Enable to generate logs that can be accessed by selecting Configure \> Advanced Parameters \> Logs. `Visa Acceptance Solutions` strongly recommends that you map your Order Status responses to your preferred order status under the Order Status Configuration section. Enable `Unified Checkout` {#opencart-config-card-payment} ========================================================= This section describes the required and optional configuration settings for `Unified Checkout` for the plugin. To enable Card Payment follow these steps: 1. In `OpenCart` Back office, navigate to Extensions \> Extensions \> Payments \> `Visa Acceptance Solutions` `Unified Checkout`. 2. Click the Edit icon. 3. In the Edit `Visa Acceptance Solutions` `Unified Checkout` pane, from the drop down list or text box, select or enter the setting you want. 4. Click the Save icon. 5. Repeat for each required setting and each optional setting you want to set. Required Settings {#opencart-config-card-payment_section_xrn_kln_sbc} --------------------------------------------------------------------- The following settings are required: * [Enable Basic Configuration](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-basic.md "") The following settings are required for enabling `Unified Checkout` for the plugin: Payment Option Label : Enter the text you want displayed to the customer at checkout. {#opencart-config-card-payment_dl_yrn_kln_sbc} Allow Card Types : Select the card types that you want to accept. {#opencart-config-card-payment_dl_fqh_pln_sbc} Optional Settings ----------------- The following settings are optional for enabling `Unified Checkout` for the plugin: Status : Click Enable for the `Visa Acceptance Solutions` integration to be active and visible at checkout. Sort Order : Specify an order in which a payment method displays at checkout. Enable Tokenization {#opencart-config-token} ============================================ This section describes the required and optional configuration settings for Tokenization for the plugin. To enable Tokenization follow these steps: 1. In OpenCart Back office, navigate to Extensions \> Extensions \> Payments \> `Visa Acceptance Solutions`
 `Unified Checkout`. 2. Click the Edit icon. 3. In the Edit `Visa Acceptance Solutions` pane, from the drop down list or text box, select or enter the setting you want. 4. Click the Save icon. 5. Repeat for each required setting and each optional setting you want to set. Required Settings ----------------- The following settings are required: * [Enable Basic Configuration](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-basic.md "") * [Enable Unified Checkout](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-card-payment.md "") The following setting is also required for enabling Tokenization for the plugin: Tokenization : Setting enables customers to save cards for future use while making a card payment. Optional Settings ----------------- The following settings are optional for enabling Tokenization for the plugin: Network Token Updates : Enable this setting to subscribe to Network Token life cycle updates. Limit Saved Card Rate : With this setting enabled, a limit is set to save only a specified number of cards in the My Account section in Front Office. There are two settings: * **Saved Card Limit Count**: Number of cards that can be saved in a certain period of time. * **Saved Card Limit Time Frame**: Number of hours that saved card attempts are counted. {#opencart-config-token_ul_xzs_gx2_hgc} Enforce SCA for Saving Card : If enabled, card holders are `3-D Secure` challenged when saving a card. Enable Fraud Management {#opencart-config-fraudmgmt} ==================================================== This section describes the required and optional configuration settings for Fraud Management for the plugin. To enable Fraud Management follow these steps: 1. In `OpenCart` Back office, navigate to Extensions \> Extensions \> Modules \> `Visa Acceptance Solutions` Configuration. 2. Click the Edit icon. 3. In the General Configuration tab of the Edit `Visa Acceptance Solutions` Configuration Module pane, from the drop down list or text box, select or enter the setting you want. 4. Click the Save icon. 5. Repeat for each required setting and each optional setting you want to enable. Required Settings ----------------- The following settings are required: * [Enable Basic Configuration](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-basic.md "") * [Enable Unified Checkout](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-card-payment.md "") The following settings are also required for enabling Fraud Management for the plugin. * Fraud Management * Device Fingerprint (not technically required, but highly recommended) Optional Settings ----------------- The following setting is optional for enabling Fraud Management for the plugin: Conversion Detailed Report : This report (enabled in the Report Configuration tab) pulls Case Management changes from `Visa Acceptance Solutions` at regular intervals to ensure orders are kept updated within `OpenCart`. Enable `3-D Secure` (Payer Auth) {#opencart-config-3ds} ======================================================= This section describes the required and optional configuration settings for `3-D Secure` (Payer Authentication) for the plugin. To enable `3-D Secure` follow these steps: 1. In `OpenCart` Back office, navigate to Extensions \> Extensions \> Payments \> `Visa Acceptance Solutions` `Unified Checkout`. 2. Click the Edit icon. 3. In the Edit `Visa Acceptance Solutions` pane, select from the dropdown or specify in the text box the configuration setting option you want to set. 4. Click the Save icon. 5. Repeat for each required setting and each optional setting you want to enable. Required Settings ----------------- The following settings are required: * [Enable Basic Configuration](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-basic.md "") * [Enable Unified Checkout](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-card-payment.md "") The following setting is also required for enabling `3-D Secure` for the plugin: Payer Authentication : When this setting is enabled, an extra layer of security is added at checkout. Optional Settings ----------------- The following setting is optional but recommended for regions enforcing `3-D Secure` for the plugin: Enforce SCA for Saving Card : When this setting is enabled, card holders are `3-D Secure` challenged when saving a card. Enable `eCheck` {#opencart-config-echeck} ========================================= This section describes the required and optional configuration settings for `eCheck` for the plugin. To enable `eCheck` follow these steps: 1. In `OpenCart` Back office, navigate to Extensions \> Extensions \> Payments \> `Visa Acceptance Solutions` `eCheck`. 2. Click the Edit icon. 3. In the Edit `eCheck` pane, from the drop down list or text box, select or enter the setting you want. 4. Click the Save icon. 5. Repeat for each required setting and each optional setting you want to enable. Required Settings ----------------- The following settings are required: * [Enable Basic Configuration](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-basic.md "") * [Enable Unified Checkout](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-card-payment.md "") The following setting is also required for enabling `eCheck` for the plugin: Status : With this setting enabled, `eCheck` is active. Optional Settings ----------------- The following setting is optional but recommended for enabling `eCheck` for the plugin: Sort Order : Order in which a payment method displays at checkout. Enable Reporting {#opencart-config-reporting} ============================================= This section describes the required and optional configuration settings for Reporting for the plugin. To enable Reporting follow these steps: 1. In `OpenCart` Back office, navigate to Extensions \> Extensions \> Modules \> `Visa Acceptance Solutions` Configuration. 2. Click the Edit icon. 3. In the Report Configuration tab of the Edit `Visa Acceptance Solutions` Configuration Module pane, from the drop down list or text box, select or enter the configuration setting you want. 4. Click the Save icon. 5. Repeat for each required setting and each optional setting you want to enable. Required Settings ----------------- The following settings are required: * [Enable Basic Configuration](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-basic.md "") * [Enable Unified Checkout](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-card-payment.md "") The following settings are also required for enabling Reporting for the plugin: 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 `Enable`, this report is downloaded from the `Business Center` to `OpenCart`. The report is downloaded by default to different locations, depending on the mode in which `OpenCart` is operating: * In Sandbox (Test) mode, the report downloads to `{OpenCartModuleInstallationDirectory}/cybersourceofficial/Reports/Sandbox` * In Production (Live) mode, the report downloads to `{OpenCartModuleInstallationDirectory}/cybersourceofficial/Reports/Production`. : > ` Visa Acceptance Solutions ` strongly recommends that ` OpenCart ` and the ` Business Center ` operate in the same time zone so that the Transaction Request Report and Payment Batch Detail Report work properly. Transaction Request Report : This report includes details for individual transactions that are processed each day. : When set to `Enable`, this report is downloaded from the `Business Center` to `OpenCart`. The report is downloaded to different locations, depending on the mode in which `OpenCart` is operating: * In Sandbox (Test) mode, the report downloads to `{OpenCartShopModuleInstallationDirectory}/cybersourceofficial/Reports/Sandbox` * In Production (Live) mode, the report downloads to `{OpenCartModuleInstallationDirectory}/cybersourceofficial/Reports/Production`. : > ` Visa Acceptance Solutions ` strongly recommends that ` OpenCart ` and the ` Business Center ` operate in the same time zone so that the Transaction Request Report and Payment Batch Detail Report work properly. Optional Settings ----------------- The following settings are optional but recommended for enabling Reporting for the plugin: Download path : If you want to download the report to a path other than the default, specify that path here. Conversion Detail Report : When set to `Enable`, this report pulls Case Management changes from the `Business Center` at regular intervals to ensure orders are updated in `OpenCart`. Enforcing Strong Customer Authentication {#opencart-config-sca} =============================================================== 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 only available when the Payer Authentication/` 3-D Secure ` (General Plugin setting) and Tokenization (Fraud Management Plugin setting) are enabled. See [Enable 3-D Secure (Payer Auth)](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-3ds.md "") and [Enable Tokenization](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-config-token.md "") for information about enabling these settings. Follow these steps to enable Enforce Strong Customer Authentication: 1. Open `OpenCart` Back Office and select Extensions \> Extensions \> Payments \> `Visa Acceptance Solutions` `Unified Checkout`. 2. Select the Edit icon. 3. From the drop down menu next to Enforce SCA for Saving Card, select **Enable**. 4. Click the Save icon. Scheduling Report Generation {#opencart-cron-tab} ================================================= 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.opencart_1.7.8.6.com/module/cybersourceofficial/paymentReport` {#opencart-cron-tab_ul_pvb_hln_jyb} Cron Tab Syntax for Mac and Linux Systems {#opencart-cron-tab_section_jt4_x3n_jyb} ---------------------------------------------------------------------------------- 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] ``` {#opencart-cron-tab_codeblock_ipw_1jn_jyb} 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) {#opencart-cron-tab_ul_rk4_fjn_jyb} 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 a.m. and 10 a.m. * `@reboot [command]`: Runs every time after the server reboots. * `*/5 * * * * [command]`: Runs every five minutes of every day. {#opencart-cron-tab_ul_hw5_mjn_jyb} Setting Up Cron Scheduler for Linux {#opencart-sched-cron-linux} ================================================================ 1. Open a Linux terminal. 2. Enter `crontab-e` to enter editor mode. For example: ``` root@OpencartQA4:/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.opencart.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@OpencartQA4:/etc# crontab -l ``` The scheduled cron job should appear on the screen. For example: ``` 15 * * * * curl https://www.dev.opencart.cybsplugin.com/mps1760/module/mybank/paymentReport ``` {#opencart-sched-cron-linux_codeblock_wpn_xpn_jyb} Setting Up Cron Scheduler for Mac {#opencart-sched-cron-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.opencart.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.opencart.cybsplugin.com/mps1786/module/cybersourceofficial/paymentReport ``` Setting Up Task Scheduler for Windows {#opencart-sched-task-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. {#opencart-sched-task-windows_ul_dn2_ksn_jyb} 7. Click OK in the Create Task pane to create the task. The new task displays in the Task Scheduler Summary. Using the Plugin {#opencart-using-extension} ============================================ The plugin provides [merchants](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-merchant-tasks.md "") a frictionless way to process payments, [prevent fraud](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-fraud-screening.md ""), and generate [reports](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-wkfw-reporting.md "") within the `Business Center` while making it easy for [customers](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-customer-tasks.md "") to place and cancel orders, and save or update stored credit or debit card information. Order Management {#opencart-using-intro} ======================================== This section describes the order management process that occurs after a customer places an order. The order management process is handled using these `OpenCart` office interfaces: * **[`OpenCart`Front Office](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-customer-tasks.md "")**: Customers use this interface to place and cancel orders, and save or update stored credit or debit card information. * **[`OpenCart` Back Office](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-merchant-tasks.md "")** : Merchants use this interface to configure the Plugin and manage orders, which includes these tasks: * [Capture an authorization](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-using-intro/opencart-ordermgmt-workflows/opencart-wkfw-after-capture.md "") (multiple partial captures are also supported). * [Reverse an authorization](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-using-intro/opencart-ordermgmt-workflows/opencart-wkfw-after-auth.md "") (full authorization is supported). * [Void a capture](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-using-intro/opencart-ordermgmt-workflows/opencart-wkfw-after-capture.md "") (standard and partial voids are supported). * [Refund a capture](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-using-intro/opencart-ordermgmt-workflows/opencart-wkfw-after-capture.md "") (standard and partial refunds are supported). * [Void a refund](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-using-intro/opencart-ordermgmt-workflows/opencart-wkfw-after-refund.md "") (standard and partial voids are supported). {#opencart-using-intro_ul_y4v_ytj_3yb}Merchants also use the Back Office interface to configure [fraud management](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-fraud-screening.md "") and [reporting services](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-wkfw-reporting.md ""). {#opencart-using-intro_ul_urd_cjf_3yb} Order Status {#opencart-order-status} ===================================== Order status is triggered and updated when transactions are processed. The plugin supports custom and default status states for orders. **Custom order status states:** * Cancel error * Canceled * Canceled Reversal * Chargeback * Complete * Denied * Expired * Failed * Order cancelled by merchant * Partial Refunded * Partial Voided * Payment error * Payment pending for review * Pending * Processed * Processing * Refund Error * Refunded * Reversal * Shipped * Void Error * Voided {#opencart-order-status_ul_nfg_3fm_3yb} **Default order status states:** * Processed * Canceled * Shipped * Delivered * Refunded {#opencart-order-status_ul_spy_qfm_3yb} Only the shipped and delivered status states can be manually updated. Order Management Workflows {#opencart-ordermgmt-workflows} ========================================================== This section describes the order of events that the merchant completes after a customer submits an order. After-Authorization Workflow {#opencart-wkfw-after-auth} ======================================================== This workflow comprises the sequence of events that occur after a customer places a new order using `OpenCart` 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 `OpenCart` Back Office and the order status is *Pending*. 2. The merchant chooses one of these actions: * 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 *Order cancelled by merchant*. 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 *Processing*. 4. When the merchant initiates a full capture, the entire authorization amount is captured and the order status is set to *Processed*. After-Capture Workflow {#opencart-wkfw-after-capture} ===================================================== 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 selects one of these actions: * 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. When 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 {#opencart-wkfw-after-refund} =================================================== 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 *Voided* or *Partially Voided*. * When the refund is processed **after** the order is shipped, the refund is cancelled and the order status is set to *Voided* or *Partially Voided*. * When the voided refund amount is equal to the refund amount, the refund is cancelled and the order status is set to *Voided* or *Partially Voided*. > ` OpenCart ` does not provide an option to return Gift Certificates. For orders associated with Gift Certificates, the services mentioned below are not available: > > * Front Office Cancel > * Back Office Cancel * Void a Capture Customer Tasks {#opencart-customer-tasks} ========================================= Customers can use the My Account option on the merchant's `OpenCart` website to manage orders and their payment information. The following sections contain the steps to complete these tasks. Saving Credit/Debit Card Information {#opencart-save-cards} =========================================================== Saving card information enables customers to use that information for future transactions. Using `OpenCart` Front Office, customers can save their card information during the checkout process, or they can add their card's information to their registered `OpenCart` accounts using the `Visa Acceptance Solutions` 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 during checkout. The card information can also be saved using the `Visa Acceptance Solutions` My Cards page in `OpenCart`: 1. Open `OpenCart` Front Office. 2. Click My Account \> Managed Stored Credit Cards \> `Visa Acceptance Solutions` My Cards \> Add New Card. 3. * 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 an address is already associated with the customer account, the customer can select and use the address or add a new address. * When 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. {#opencart-save-cards_ul_sjc_snh_bgc} 4. To update the expiration information (expiration month/year) for the card, under Saved Cards the customer clicks the blue arrow beneath More, then clicks either Update, or Delete to remove the card from the account. #### ADDITIONAL INFORMATION Customers can only add 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 {#opencart-default-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 will be set as the default card. In the `Visa Acceptance Solutions` My Cards page, the default card is identified using an asterisk (\*) that appears to the right of the card number. To change the default card, the customer follows these steps: 1. Open `OpenCart` Front Office. 2. Open the `Visa Acceptance Solutions` My Cards page. The page displays the saved cards associated with the account. 3. Choose the card to set as the default card and select More \> SET AS DEFAULT. The card is set as the default card. #### ADDITIONAL INFORMATION The default card cannot be deleted unless all other saved cards from the `Visa Acceptance Solutions` My Cards section are deleted. Cancelling an Order {#opencart-cancel-order} ============================================ This task describes the steps a customer takes to cancel an order. They cannot cancel an order if the order is in review with the merchant. The Cancel option is also not available in direct Settlement for Captured and `eCheck` orders. 1. Open `OpenCart` Front Office. 2. Select My Account \> Order History. The Order history page displays the customer's orders. 3. Select the View icon for the order. The Order details page appears. 4. Click the Cancel Order icon to cancel the order. A Cancel Order confirmation notice appears. 5. Click Yes on the Cancel Order confirmation notice to cancel the order. #### ADDITIONAL INFORMATION Above the Order History, a notification appears stating **Success: Entire order was successfully cancelled.** The order is cancelled and the order status is set to *Canceled*. If the order was a sales transaction or was captured, the cancellation is sent to the merchant and the status is set to *Canceled* . After the customer cancels an order, the merchant can accept or reject the order cancellation (as instructed in [Processing a Cancelled Order](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-using-extension/opencart-merchant-tasks/opencart-process-cancel-orders.md "")). If the merchant accepts the cancellation request, a refund for the order amount is initiated and the order status is set to *Refunded* . If the merchant rejects the cancellation request, the order status is set to *Denied*. Merchant Tasks {#opencart-merchant-tasks} ========================================= Merchants use `OpenCart` Back Office to manage orders. This section describes the steps to complete these tasks. Processing a Cancelled Order {#opencart-process-cancel-orders} ============================================================== When a customer cancels an order, a request is sent to the merchant and the order status is set to *Cancelled*. Merchants can accept or reject an order that a customer cancels. 1. Open `OpenCart` Back Office and select Orders from the Dashboard. 2. Click the box beside the order the customer cancelled. 3. Click the View icon. Under Order Details, the information for that order displays. 4. Under **Add Order Status**, choose the order status that describes your processing of the cancellation. Processing a Merchandise Return {#opencart-process-merch-returns} ================================================================= When a customer requests to return merchandise, the information appears on the Merchandise Returns page in `OpenCart` Back Office. Follow these steps to process the return. 1. Open `OpenCart` Back Office and select Sales \> Returns. The Product Returns page displays and identifies the order or orders for which customers have requested a return. 2. Click the box beside the order that you want to process the return and then click the Edit icon. The Edit Product Return page displays. 3. In the Product Information and Reason for Return pane, choose one of these options from the Return Action drop-down menu: * Credit issued * Refunded * Replacement Sent 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 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 {#opencart-fraud-screening} ============================================ The plugin provides fraud management functionality for merchants who also use the `Business Center`. You can apply fraud management functionality to transactions when: * 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 `Visa Acceptance Solutions` 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 Decision Manager uses when an order is triggered for review. > When these 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 OpenCart 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 OpenCart Back Office fail. > * A follow-on void capture does not trigger from OpenCart Back Office. While accepting review transactions, merchants should not select the settle option. | Decision | Execution Timing | Outcome of Decision | |:---------|:---------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Monitor | Before authorization | Authorization will be 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 will be 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 OpenCart 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 is 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*. | [Decision Manager Decisions, Execution Timings, and Outcomes for Orders] Reporting {#opencart-wkfw-reporting} ==================================== The plugin provides reporting functionality for merchants who also use the `Business Center`. You can import these reports from the `Business Center` into OpenCart: * **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 `OpenCart`. 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 `OpenCart`. There are some Cron Job modules available for `OpenCart`, such as the Cron Tab, that support reporting. Merchants can use any Cron Job module that `OpenCart` supports, or any other online Cron service provider to generate reports. See [Scheduling Report Generation](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-cron-tab.md "") for information about how to schedule report generation. Workflow -------- The reports are processed and orders are updated in `OpenCart` using this workflow: 1. Orders with an *AUTHORIZED_PENDING_REVIEW* or *AUTHORIZED_RISK_DECLINED* status are included in the *ps_cybersourceofficial_order* table in the OpenCart 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 `OpenCart` Back Office Orders page. 3. The merchant uses the `Business Center` to accept the order that is in review, and, if not already enabled, 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 *op_cybersourceofficial_order* table in the `OpenCart` database. 5. The original decision and the new decision are updated and displayed in the *op_cybersourceofficial_conversion_detail_report* table in the `OpenCart` database. 6. The order is updated as *Awaiting payment* status for the authorization and displayed on the `OpenCart` 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 {#opencart-test-extension} ================================== If you have not done so already, configure these settings using OpenCart Back Office: * **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 OpenCart Front Office to place an order and OpenCart Back Office to manage the order. 1. Open OpenCart Front Office to place an order. 2. At Checkout, enter any required personal information and select the payment method you want to use to place the order. 3. Enter the card information you want to use to place the order and click Confirm Order. If the order is successful, an order confirmation message displays. 4. Open OpenCart Back Office to manage the order. 5. Select Orders from the Dashboard. The Orders page displays and lists all active orders. 6. Select the checkbox next to the order you processed in Step 1. Then click the View icon. The order status for the order should display *Pending*. 7. Click Capture to capture the authorized amount, then **Yes** . The order status changes to *Processed*. 8. Click Partial capture to capture part of the authorized amount. The order status changes to *Processing*. 9. Click Cancel to cancel the order. The order status changes to *Order Cancelled by Merchant*. #### ADDITIONAL INFORMATION For more information about testing, including test cards, see Upgrading {#opencart-upgrade-plugin} ==================================== You can install a newer version of the plugin using `OpenCart` Back Office. 1. To uninstall `Visa Acceptance Solutions` Payment, navigate to Extensions \> Extension Types \> Payments and then uninstall all of the `Visa Acceptance Solutions` payment modules. 2. To uninstall `Visa Acceptance Solutions` Tax, under the same Extension dropdown, select Order Totals and uninstall `Visa Acceptance Solutions` Tax. 3. To uninstall the `Visa Acceptance Solutions` Payment extension, under the Extension dropdown, select Modules, and uninstall the `Visa Acceptance Solutions` Payment extension. 4. Navigate to the Extensions tab and click Installer, then click Delete to remove the `Visa Acceptance Solutions` extension. 5. Navigate back to the Extensions tab and click Modification, then click Refresh. 6. To install the new `Visa Acceptance Solutions` Payment extension, follow the steps mentioned in [Installation](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-us/opencart-overview/opencart-install.md ""). Troubleshooting Assistance {#opencart-trblshoot-help} ===================================================== For help with troubleshooting, contact *GlobalPartnerSolutionsCS@visa.com* and provide this 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 `PrestaShop` {#prestashop-introduction} ======================================= This is an overview of the `Cybersource Official Plugin` extension for PrestaShop, which enables merchants to accept various payment methods. The `Visa Acceptance Solutions` extension for PrestaShop enables merchants to connect their PrestaShop store to the `Visa Acceptance Solutions` Platform to directly take credit and debit cards, Apple Pay, Google Pay, `Click to Pay`, ACH, and `eCheck` payments. Supported Features {#prestashop-supported-features} =================================================== This is a list of payment methods and features supported by the `Cybersource Official Plugin` Prestashop extension. * Credit and debit Cards * Apple Pay * Google Pay * `Click to Pay` * ACH and `eCheck` * `3-D Secure` Payer Authentication * Tokenization including network tokens * `Visa Acceptance Solutions` `Decision Manager` and `Fraud Management Essentials` Supported Versions ------------------ This PrestaShop integration works with PrestaShop 8.0.4 to 9.0.1. `Visa Acceptance Solutions` Prerequisites {#prestashop-prerequisites} ===================================================================== These required and optional `Visa Acceptance Solutions` products and configurations are needed for the PrestaShop extension. Mandatory --------- These `Visa Acceptance Solutions` products must be enabled and configured for your Merchant ID: * `Unified Checkout` You must also have a [REST Shared Secret Key Pair](https://developer.cybersource.com/docs/cybs/en-us/platform/developer/all/rest/rest-getting-started/restgs-http-message-intro/restgs-security-key-pair-intro.md ""). Optional -------- These Visa Acceptance Solutions products are optional. If you choose to use any of these products, they must be enabled and configured for your Merchant ID: * Payer Authentication for `3-D Secure` * Tokenization * Apple Pay * Google Pay * `Click to Pay` * `eCheck` * `Decision Manager` * `Fraud Management Essentials` You can also enable [Message-Level Encryption (MLE)](https://developer.cybersource.com/docs/cybs/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-message-intro/restgs-mle-intro.md#restgs_mle_prereq "") for additional security. MLE requires a REST Certificate. Release Notes {#prestashop-release-notes} ========================================= This information is a version history and release notes for the `Cybersource Official Plugin` PrestaShop extension. Version 7.0.0 ------------- **Enhancements:** * PrestaShop 9 support * Hummingbird Theme compatibility * Replaced Microform with Unified Checkout * Apple Pay, Click to Pay, Google Pay, and ACH and eCheck were included in Unified Checkout, removing individual components * Latin America processing logic was removed. Version 6.3.1 ------------- **Enhancements:** * PrestaShop 8.2.3 support **Bug Fixes:** * Installation error Version 6.3.0 ------------- **Enhancements:** * Message Level Encryption * CVV capture for transactions with saved cards was removed. * PrestaShop 8.2.1 support * Support for PrestaShop 1.7.x was ended. Earlier Versions ---------------- For a complete release history including versions 6.2.1, 6.2.0, 6.1.0, 5.1.0, 4.2.0, 4.1.0, 3.1.0, 2.10, and 1.x, refer to the complete release notes documentation. Installation {#prestashop-installation} ======================================= Follow these steps to install the `Cybersource Official Plugin` extension for PrestaShop. 1. Go to the PrestaShop Marketplace and download our extension. 2. Log into your PrestaShop back office. 3. Go to Modules \> Module Manager \> Upload a module. 4. Upload the module downloaded from the marketplace. 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 `Visa Acceptance Solutions` 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 `Visa Acceptance Solutions`, 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 `Visa Acceptance Solutions` test account. * No Choose for live transactions. * Merchant ID: The transacting Merchant ID (MID) that `Visa Acceptance Solutions`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 `Visa Acceptance Solutions` containing details for transactions processed each day. Set to `Yes` to enable. * Payment Batch Detail Report: When enabled, the extension downloads a report from `Visa Acceptance Solutions` 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 `Visa Acceptance Solutions` `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}/``Visa Acceptance Solutions``official/Reports/Production` * Conversion Detail Report: When you are using fraud screening with REVIEW rules, this toggle polls the `Visa Acceptance Solutions` 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/vas/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: `Visa Acceptance Solutions` generated ID string issued to development partners. Order Management {#prestashop-order-management} =============================================== This topic explains how to manage orders including captures, refunds, and voids in the `Cybersource Official Plugin` Prestashop extension. Orders are marked differently depending on the Payment Action that is chosen. * For Authorize, orders are marked as `Awaiting Payment`. * For Sale, orders are marked as `Payment accepted`. Fraud Screening --------------- When fraud screening is enabled, transactions are marked as follows: * Approved orders are marked as `Awaiting Payment` or `Payment Accepted`, (depending on your Payment Action setting) * Orders to review are marked as `Payment pending for review`. * Rejected orders are marked as `Order cancelled by merchant`. Orders marked as **Payment pending for review** must be reviewed in the `Business Center`. The `Visa Acceptance Solutions` extension checks for transaction status in the intervals as set by your scheduled tasks. Rejected transactions are marked as `Order cancelled by merchant`. Accepted transactions are marked according to your Payment Action settings. Capture ------- Enter the order from the list of orders and choose one of these options: * Partial Capture: Select the items to capture and then click `Partial Capture`. The order is marked as `Partial payment accepted.` * Standard Capture: Captures the entire order and marks the order as `Payment accepted`. Refund ------ Orders can only be refunded if they are marked as `Payment accepted` or `Partial payment accepted`. * To refund the entire order, click Standard Refund. * To refund part of the order, click Partial Refund, choose the item(s) to refund, and then click Partial Refund. Void ---- * For an order that was not captured, click Cancel products, choose the item(s) to cancel, then click Cancel products. This reverses the authorization. * For an order that was captured, click Void capture. * For an order that was refunded, click Void refund. Support \& Troubleshooting {#prestashop-support-troubleshooting} ================================================================ Information about getting support and troubleshooting common issues with the `Cybersource Official Plugin` PrestaShop extension. Support ------- If you require support with this extension, visit [support.visaacceptance.com](https://support.visaacceptance.com "") to raise a support case. For resold accounts, contact your reseller. For the support case, provide this information: * Summary of issue * Steps to reproduce the issue * PrestaShop version * `Cybersource Official Plugin` extension version * `Visa Acceptance Solutions` Merchant ID * Configuration screenshots * List of the additional themes and extensions installed * Log file * Any additional information related to the issue FAQ --- **PrestaShop Language Pack Installation Error** When you get a `Cannot download language pack` error message while installing the extension, follow these steps: 1. Go to `/htdocs/PrestaShop root/Classes` and open `tools.php`. 2. Search for `curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);`. 3. Change `false` to `true`. 4. Save the file, reload your browser, and attempt installation again. Upgrade ------- To upgrade to the latest version of the PrestaShop extension, go to Modules \> Module Manager. Scroll down to `Visa Acceptance Solutions` Official and click Upgrade. Appendix {#prestashop-appendix} =============================== This is additional information about report scheduling for the `Cybersource Official Plugin` Prestashop extension. Report Scheduling ----------------- Schedulers for Linux and Mac systems are set up using a Cron Tab. The scheduler for a Windows system is configured using the Windows Task Scheduler app. When configuring a schedule for generating a specific report, use this format: **Format:** `<shop domain name>/module/cybersourceofficial/paymentReport` **Example:** `https://www.prestashop_8.2.2.com/module/cybersourceofficial/paymentReport` Cron Tab Syntax for Mac and Linux Systems ----------------------------------------- When setting up the reporting schedule on Linux or Mac, use crontab commands to determine how often and when the report is generated. The syntax is: \* \* \* \* \* \[command\] Each asterisk (\*) represents one of the timing parameters: * Minute (0-59) * Hour (0-23) * Day of Month (1-31) * Month (1-12) * Day of week (0-6) 0 = Sunday Cron Scheduler Setup -------------------- 1. Open a Linux or Mac terminal. 2. Enter `crontab-e` to enter editor mode. 3. Enter the command to set the timing for the cron job. 4. For example, for 15-minute intervals: `15 * * * * curl` https://www.prestashop_8.2.2.com/module/cybersourceofficial/paymentReport 5. Close the editor. 6. Enter `crontab -l` to check the scheduled cron job. Windows Task Scheduler ---------------------- 1. Open Task Scheduler and click Create Task. 2. Select the General tab and enter a name. 3. Select the Triggers tab and click New. 4. Enter the desired timings and click OK. 5. Select the Actions tab in the Create Task pane and click New. 6. Enter this information into these fields and then click OK. * Action: `Start a program` * Program/script: `curl` * Add arguments (optional): Enter the reporting URL. `Salesforce` B2C Commerce {#salesforce-b2c-introduction} ======================================================== The `Visa Acceptance Solutions` cartridge for `Salesforce` B2C Commerce enables merchants to connect their `Salesforce` B2C Commerce store to the Visa Acceptance Platform to directly take credit/debit card, Apple Pay, Google Pay, `Click to Pay`, and `eCheck` payments. Supported Features {#salesforce-b2c-supported-features} ======================================================= The `Visa Acceptance Solutions` cartridge for `Salesforce` B2C Commerce supports multiple payment methods and features. Payment Methods --------------- * Credit/debit cards * Apple Pay * Google Pay * `Click to Pay` * `eCheck` Security and Fraud Management ----------------------------- * `Payer Authentication`/`3-D Secure` * Tokenization * `Visa Acceptance Solutions` `Decision Manager` and `Fraud Management Essentials` Additional Services ------------------- * `Visa Acceptance Solutions` Delivery Address Verification * `Visa Acceptance Solutions` Tax Calculation Supported Versions {#salesforce-b2c-supported-versions} ======================================================= The `Visa Acceptance Solutions` extension is compatible with specific versions of `Salesforce` Store Front Reference Architecture (SFRA). Compatibility ------------- Our `Visa Acceptance Solutions` extension is compatible with `Salesforce` Store Front Reference Architecture (SFRA) version 7.0 and below. Cybersource Prerequisites {#salesforce-b2c-prerequisites} ========================================================= Before implementing the `Visa Acceptance Solutions` cartridge, ensure that you have the required and optional `Visa Acceptance Solutions` products configured. Mandatory --------- You must have a [REST Shared Secret Key](https://developer.visaacceptance.com/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-intro.md "") Optional -------- These `Visa Acceptance Solutions` products are optional, but if you choose to use them, they must be enabled and configured for your Merchant ID: * `Unified Checkout` * `Payer Authentication` for `3-D Secure` * Tokenization * Apple Pay (standalone or through `Unified Checkout`) * Google Pay (standalone or through `Unified Checkout`) * `Click to Pay` (through `Unified Checkout` only) * `Visa Acceptance Solutions` `Decision Manager` * `Visa Acceptance Solutions` `Fraud Management Essentials` You can also enable Message-Level Encryption (MLE) for additional security. A REST certificate is required for MLE. Rules-based `Payer Authentication` is also supported and requires both `Payer Authentication` and `Decision Manager` to be enabled. Release Notes {#salesforce-b2c-release-notes} ============================================= Release history and updates for the `Visa Acceptance Solutions` `Salesforce` B2C Commerce cartridge. Version 26.1.0 (January 2026) ----------------------------- * Added support for `3-D Secure` Data Only transactions. Version 25.4.0 (December 2025) ------------------------------ * Added support for `Unified Checkout` v0.32 (Card Payments, Apple Pay, Google Pay, `Click to Pay`, and `eCheck`). * End of support for `Click to Pay` legacy. Version 25.3.0 (May 2025) ------------------------- **New Features:** * Added `Payer Authentication` support for Google Pay. * Added multi-currency support for Google Pay. **Bug Fixes:** * Handled session variables in SCA flow. * Removed encryption type from Microform v2 request. Version 25.2.0 (March 2025) --------------------------- **New Feature:** * Message-Level Encryption (MLE). **Enhancement:** * Added support for Cartes Bancaires, Elo, China Union Pay, and JCrew. Version 25.1.0 (January 2025) ----------------------------- **New Feature:** * Replaced Microform v0.11 with v2. **Bug Fixes:** * Added webhook subscription deletion if the subscription is deleted at `Visa Acceptance Solutions` or `Salesforce` custom object. * Handled undefined exception scenario for `3-D Secure` transactions. Version 24.4.0 (September 2024) ------------------------------- **New Feature:** * DMPA support. **Enhancement:** * Upgraded to jQuery v3.7.0. Version 24.3.0 (August 2024) ---------------------------- **Enhancements:** * Upgraded the cartridge to support SFRA v7.0. * Added MOTO Commerce Indicator. Version 24.2.1 (May 2024) ------------------------- **Bug Fixes:** * Checkmarx issues fixed. * Device fingerprint bug fixed. Version 24.2.0 (April 2024) --------------------------- **New Features:** * Network token support **Enhancements:** * Implemented Direct API integration for `Payer Authentication`, adding Payer Authentication Setup and Device Data Collection. * Enhanced Strong Consumer Authentication (SCA). Version 24.1.0 (February 2024) ------------------------------ **New Features:** * Added Strong Customer Authentication retries for card payments. **Enhancements:** * SFRA v6.3 support. * `Salesforce` B2C Commerce Release 22.7 support. * Renamed Visa SRC to `Click to Pay`. * Implemented Sale functionality for Credit Card, Google Pay, `Click to Pay` and Apple Pay. * Updated flex script referring from v0.11.0 to v0.11. * Updated API header in Http Signature Authentication. Version 21.1.0 (June 2021) -------------------------- **Enhancements:** * Improved `Payer Authentication` screen (modal). **Bug Fixes:** * Added descriptive error messages on certain fail cases and invalid inputs. * Reloading on final confirmation page does not result on failed authorization. Version 20.2.0 (Feb 2021) ------------------------- **New Features:** * Google Pay * Visa Secure Remote Commerce payment method * Improved the security on the My Account page by adding Microform to tokenize payment cards. **Bug Fixes:** * Improved the security of keys by changing data type of password fields from `String` to `password`. * Added more security to the exposed parameters of device fingerprint. Version 20.1.1 (Nov 2020) ------------------------- **Bug Fixes:** * Improved the security on accessing and modifying sensitive fulfilment-related actions on an order (for example, order acceptance, cancelling etc.). Version 20.1.0 (Aug 2020) ------------------------- Initial release supporting: * Credit/debit cards * Apple Pay * `Payer Authentication`/`3-D Secure` * Delivery Address Verification service * Tax Calculation service * Authorization, Capture, Authorization Reversal Install `Visa Acceptance Solutions` for Salesforce B2C Commerce {#salesforce-b2c-installation} ============================================================================================== Download and install the `Visa Acceptance Solutions` cartridge for `Salesforce` B2C Commerce. Before beginning installation, ensure that you have: * Access to your `Salesforce` B2C Commerce instance. * Node.js installed on your development machine. * Appropriate IDE (VSCode recommended with Prophet Debugger extension). 1. Download the `Visa Acceptance Solutions` cartridge for `Salesforce` B2C Commerce from the ISV Integration Toolkits section on [GitHub](https://github.com/cybersource/cybersource-plugins-rest-salesforceb2ccommerce ""). 2. Set up your workspace. 1. Create a folder named `Visa Acceptance Solutions` folder in your `Salesforce` workspace and copy the downloaded cartridges (*int_cybs_sfra* and *int_cybs_sfra_base*) to the workspace. 2. If the project's base path is different from the one available in the `Visa Acceptance Solutions` package.json, open the file */package.json* and modify the `paths.base` value to point to your *app_storefront_base* cartridge. This path is used by the JS and SCSS build scripts. 3. Configure IDE (VSCode). #### ADDITIONAL INFORMATION If you use VSCode, install the extension Prophet Debugger and include these lines in *dw.json()*: #### ADDITIONAL INFORMATION ``` { "hostname": "your-sandbox-hostname.demandware.net", "username": "yourlogin", "password": "yourpwd", "version": "version_to_upload_to", "cartridge": [ "int_cybs_sfra", "int_cybs_sfra_base", "app_storefront_base", "modules" ] } ``` #### ADDITIONAL INFORMATION If you are using a different IDE, refer to the respective guide to set up your workspace. 4. Build and Upload Code 1. Install the node in the `Visa Acceptance Solutions` folder 2. Install *sgmf-scripts* and *copy-webpack-plugin* with this command: #### ADDITIONAL INFORMATION ``` npm install sgmf-scripts && npm install copy-webpack-plugin ``` 3. Compile JS and SCSS with this command: #### ADDITIONAL INFORMATION ``` npm run compile:js && npm run compile:scss ``` 4. Upload the code to the `Salesforce` Commerce Cloud instance: #### ADDITIONAL INFORMATION ``` npm run uploadCartridge ``` #### RESULT The `Visa Acceptance Solutions` cartridge is now installed and ready for configuration in your `Salesforce` B2C Commerce environment. Configure `Visa Acceptance Solutions` for Salesforce B2C Commerce {#salesforce-b2c-configuration} ================================================================================================= Configure the `Visa Acceptance Solutions` cartridge in `Salesforce` B2C Commerce `Salesforce` Business Manager. After installation, configure the cartridge through the `Salesforce` Business Manager to enable payment processing capabilities. 1. Base Configuration 1. Set up the cartridge path. #### ADDITIONAL INFORMATION In `Salesforce` Business Manager, go to Administration \> Sites \> Manage Sites \> \[yourSite\] \> Settings. #### Step Result For Cartridges, enter int_cybs_sfra:int_cybs_sfra_base:app_storefront_base and click Apply. 2. Upload metadata #### ADDITIONAL INFORMATION Go to the folder *`Visa Acceptance Solutions`/metadata/payments_metadata/sites/*. #### ADDITIONAL INFORMATION 1. Rename the folder `yourSiteID` with your site ID from `Salesforce` Business Manager (this can be found by looking up Administration-\>Sites-\>Manage Sites). 2. Zip the *payments_metadata* folder. 3. Go to Administration-\>Site Development-\>Site Import \& Export and upload the *payments_metadata.zip* file. 4. Import the uploaded zip file. #### Step Result Upon successful import, this metadata is created: * Site Preferences: `Visa Acceptance Solutions`_Core, `Visa Acceptance Solutions`_DeliveryAddressVerification, `Visa Acceptance Solutions`_DeviceFingerprint, `Visa Acceptance Solutions`_PayerAuthentication, `Visa Acceptance Solutions`_TaxConfiguration, `Visa Acceptance Solutions`_Tokenization, `Visa Acceptance Solutions`_DecisionManager, `Visa Acceptance Solutions`_MLE, `Visa Acceptance Solutions`_ApplePay, `Visa Acceptance Solutions`_GooglePay, VisaAcceptance_SecureIntegrationConfiguration * Service: PaymentHttpService * Payment Processor * Payment Method * Job: Payment :Decision Manager Order Update 2. Minimum Configuration 1. `Visa Acceptance Solutions` Core #### ADDITIONAL INFORMATION Go to Merchant Tools \> Site Preferences \> Custom Preferences \> `Visa Acceptance Solutions` Core and set these configuration parameters: * Enable `Visa Acceptance Solutions` Cartridge: Enable the cartridge. * `Visa Acceptance Solutions` Merchant ID: The transacting Merchant ID (MID) assigned to you. * `Visa Acceptance Solutions` REST KeyId: The Key from your REST API Shared Secret Key. * `Visa Acceptance Solutions` REST Secret Key: The Shared Secret from your REST API Shared Secret Key. * Commerce Indicator: * Use `internet` for eCommerce transactions. * Use `MOTO` if you are using the store for call center transactions only. {#salesforce-b2c-configuration_ul_rjz_zkn_yhc} 2. Services #### ADDITIONAL INFORMATION The target endpoint must be set to send transactions to test or production (live). #### ADDITIONAL INFORMATION Go to Administration \> Operations \> Services \> Payment Credentials and enter the appropriate URL: * Test: `https://apitest.visaacceptance.com` * Production (live): `https://api.visaacceptance.com` 3. Accept Payment Cards #### ADDITIONAL INFORMATION Prerequisite: Go to Merchant Tools \> Ordering \> Payment Methods, select `CREDIT_CARD` and verify that the payment processor is `PAYMENTS_CREDIT`. 1. Select Card Capture Method #### ADDITIONAL INFORMATION Our cartridge supports these card capture methods: `Unified Checkout`, Microform, and Direct API. #### ADDITIONAL INFORMATION If you enable Apple Pay, Google Pay, and/or `Click to Pay` in `Unified Checkout`, these payment methods are displayed in a single widget. `Unified Checkout` and Microform might qualify you for PCI-DSS SAQ:A as the card number is collected in secure fields and never resides on your server. If you need access to the card number, select `Direct API`. This option increases your PCI burden. #### ADDITIONAL INFORMATION To select the card capture method, go to Merchant Tools \> Site Preferences \> Custom Preferences \> Secure Integration Configuration. #### RESULT The `Visa Acceptance Solutions` cartridge is now configured with basic settings. Additional optional configurations can be applied based on your specific requirements. Digital Payment Methods {#salesforce-b2c-digital-payment-methods} ================================================================= Apple Pay and Google Pay can be standalone options, or they can be offered as payment options with `Click to Pay` within `Unified Checkout`. You can configure digital payment methods in two ways: `Unified Checkout` or as standalone options. 1. To configure `Unified Checkout`, go to Merchant Tools \> Site Preferences \> Custom Preferences \> Secure Integration Configuration. 2. In the Digital Payment Methods in `Unified Checkout` field, select Apple Pay, Google Pay, or `Click to Pay`. You can choose any or all of the options. #### ADDITIONAL INFORMATION > If you are using ` Unified Checkout ` for digital payment methods, the payment methods must be enabled for your Merchant ID in ` Business Center `. For more information about enabling digital payments, see [Enable Digital Payments](https://developer.visaacceptance.com/docs/vas/en-us/unified-checkout/developer/all/rest/unified-checkout/uc-configuration-intro/uc-enable-digital-pay-intro.md ""). 3. Enable `Unified Checkout` for Cart and Mini Cart: Enable this option to display digital payment methods for quick checkout on the cart and mini cart pages. 4. Go to Merchant Tools \> Ordering \> Payment Methods and confirm that these options are enabled for the methods you accept: #### ADDITIONAL INFORMATION * DW_APPLE_PAY: Verify that the Payment Processor is `PAYMENTS_APPLEPAY`. * DW_GOOGLE_PAY: Verify that the Payment Processor is ` PAYMENTS_CREDIT`. * CLICK_TO_PAY: Verify that the Payment Processor is `PAYMENTS_CLICK_TO_PAY`. Apple Pay Standalone Configuration {#salesforce-b2c-apple-pay-standalone} ========================================================================= To offer Apple Pay outside of `Unified Checkout`, follow these steps to enable Apple Pay in your `Salesforce` B2C Commerce store. Follow the steps documented [here](https://developer.visaacceptance.com/docs/vas/en-us/apple-pay/developer/ctv/rest/applepay/applepay-cfg.md "") first, before you follow this procedure to enable Apple Pay in your `Salesforce` B2C Commerce store. 1. `Salesforce` Business Manager Configuration 1. Go to: Merchant Tools \> Site Preferences \> Apple pay. 2. Check Apple Pay Enabled? 3. Complete the "Onboarding" form: #### ADDITIONAL INFORMATION * Ensure the Apple Merchant ID and the Apple Merchant Name values you enter match the settings in your Apple account. * Ensure all other fields match your supported `Visa Acceptance Solutions` settings. * Country Code: Enter the country code for the location of your site. The country code is a two letter ISO 3166 country code (for example, `US`). * Merchant Capabilities: Check the box for 3-D Secure, leave the other fields unchecked. * Supported Networks: Select the types of payment you support: `Amex`, `Mastercard`, and `Visa` are supported by `Visa Acceptance Solutions`. * Required Shipping Address Fields: Select the fields that are required on the shipping form. `Visa Acceptance Solutions` recommends Email, Name, Phone, and Postal Address. * Required Billing Address Fields: Select Name and Postal Address. {#salesforce-b2c-apple-pay-standalone_ul_lj4_14n_yhc} 4. Fill in the Storefront Injection form: #### ADDITIONAL INFORMATION Select where to display Apple Pay buttons on your site. 5. Fill in the Payment Integration form: #### ADDITIONAL INFORMATION * Use Commerce Cloud Apple Pay Payment API? Checked * Payment Provider URL: * Test: https://apitest.cybersource.com/partner/demandware/payments/v1/authorizations * Production: https://api.cybersource.com/partner/demandware/payments/v1/authorizations {#salesforce-b2c-apple-pay-standalone_ul_h3d_w4n_yhc} * Payment Provider Merchant ID: Enter your `Visa Acceptance Solutions` merchant ID. * API Version: v1 * Use Basic Authorization? Unchecked * Payment Provider User: Not Applicable * Payment Provider Password: Not Applicable * Use JWS? == Yes * JWS Private Key Alias: Merchant.p12 Key Alias #### Step Result The private key alias is created when a merchant uploads their .p12 key file (from `Visa Acceptance Solutions` self-serve) to Commerce Cloud's `Salesforce` Business Manager Module, Private Keys and Certificates (Administration \> Operations \> Private Keys and Certificates) 6. Click Submit. 2. Domain Registration in `Salesforce` Business Manager 1. Go to Merchant Tools \> Site Preferences \> Apple Pay. 2. Under Domain Registration section #### ADDITIONAL INFORMATION * In the Apple Sandbox section, click Register Apple Sandbox to register `Salesforce` B2C to the Apple Sandbox account. * In the Apple Production section, click on Register Apple Production to register `Salesforce` B2C to the Apple Production account. 3. Transaction Type #### ADDITIONAL INFORMATION Go to Merchant Tools \> Site Preferences \> Custom Preferences \> Apple Pay and choose `Authorization` or `Sale`. Google Pay Standalone Configuration {#salesforce-b2c-google-pay-standalone} =========================================================================== To offer Google Pay outside of `Unified Checkout`, follow these steps to enable Google Pay in your `Salesforce` B2C Commerce store. 1. Go to Merchant Tools \> Site Preferences \> Custom Preferences \> Google Pay. 2. Configure Google Pay settings: 1. Enable Google Pay: Enable. 2. Enable Google Pay on Mini Cart: Enable to show Google Pay as a checkout option in the mini cart. 3. Enable Google Pay on Cart: Enable to show Google Pay as a checkout option in the cart. 4. Google Pay Merchant Id: Enter your Google Pay merchant ID (for live processing only). 5. Google Pay Environment: Choose `Test` for testing and `Production` for live. 3. Google Pay Transaction Type: Choose `Authorization` or `Sale`. Alternative Payment Methods {#salesforce-b2c-alternative-payment-methods} ========================================================================= Configure alternative payment methods such as `eCheck` for your `Salesforce` B2C Commerce store. Follow this procedure to enable `eCheck` as a payment option within `Unified Checkout`. 1. Go to Merchant Tools \> Site Preferences \> Custom Preferences \> Secure Integration Configuration. 2. Set the Enable `eCheck` option to `Yes`. 3. Go to Merchant Tools \> Ordering \> Payment Methods and confirm that the payment processor is set to `BANK_TRANSFER`. `Payer Authentication` and `3-D Secure` {#salesforce-b2c-payer-authentication} ============================================================================== Configure `Payer Authentication` and `3-D Secure` for enhanced transaction security. 1. Go to Merchant Tools \> Site Preferences \> Custom Preferences \> Cybersource_PayerAuthentication. 2. In `Payer Authentication` Mode, choose one of these options: #### ADDITIONAL INFORMATION * `Yes`: All transactions will process with `3-D Secure`. * `No`: No transactions will process with `3-D Secure`. * `Data Only + Yes`: Data Only will be used for Visa and Mastercard/Maestro. All other card brands will process with `3-D Secure`. * `Data Only + No`: Data Only will be used for Visa and Mastercard/Maestro. All other card brands will process without `3-D Secure`. {#salesforce-b2c-payer-authentication_ul_h4j_nlm_whc} 3. IsSCAEnabled: Enable this option to enforce Strong Consumer Authentication (`3-D Secure` Challenge) when a customer is saving their payment card for future transactions. Tokenization {#salesforce-b2c-tokenization} =========================================== Tokenization enables your customers to save their payment cards securely for future payments. 1. To enable tokenization, go to Merchant Tools \> Site Preferences \> Custom Preferences \> Cybersource_Tokenization. 2. Enable the Enable Tokenization Services option to turn on Tokenization. 3. Enable the Enable Limiting Saved Cardoption to set the limits associated to saving cards. 4. In the Saved Cards Allowedoption, enter the number of cards a customer can save in the defined time limit. 5. In the Reset Interval option, specify the number of hours before the saved card limit resets. 6. Enable the Network Token Updates option to prompt the cartridge to subscribe for Token Life Cycle Updates webhooks when your `Visa Acceptance Solutions` MID is configured for network tokens. 7. Go to Merchant Tools \> Custom objects \> Custom Object Editor and verify that the custom object type Network Tokens Webhook exists. Fraud Screening {#salesforce-b2c-fraud-screening} ================================================= Enabling Fraud Screening alerts the cartridge to look for fraud screening responses. Fraud Screening profiles must be set up in the `Business Center`. 1. Go to Merchant Tools \> Site Preferences \> Custom Preferences \> `Visa Acceptance Solutions`_DecisionManager and set these options: 1. Enable the Enable `Decision Manager` Services option. 2. Conversion Detail Report Lookback Time: If you are using REVIEW rules and configure the `Decision Manager` Update Job, set the number of hours to look back for updates to transactions in REVIEW status. The maximum is 24 hours. 2. To enable the `Decision Manager` Update Job to poll for updates to the reviewed transactions, go to Administration \> Operations \> Jobs and select Payment: `Decision Manager` Order Update and set these values: #### ADDITIONAL INFORMATION * ID: Enter a job ID. * Description: Enter the job description. * ExecuteScriptModule.Module: int_cybs_sfra_base/cartridge/scripts/jobs/DMOrderStatusUpdate.js * ExecuteScriptModule.FunctionName: orderStatusUpdate * ExecuteScriptModule.Transactional: * `True`: All changes occur as a single atomic operation. If any error occurs during the job, the system rolls back all changes to maintain data consistency. * `False`: No automatic rollback is applied. Merchants must handle transaction logic manually. This is often preferred for large batch jobs. {#salesforce-b2c-fraud-screening_ul_g3x_1tn_yhc} * ExecuteScriptModule.TimeoutInSeconds: Set the function timeout value. {#salesforce-b2c-fraud-screening_ul_ows_m2d_c3c} Device FingerPrint {#salesforce-b2c-device-fingerprint} ======================================================= Device FingerPrinting collects information about the device used when paying for an order and can assist in fraud screening decisions. 1. Go to Merchant Tools \> Site Preferences \> Custom Preferences \> Cybersource_DeviceFingerprint. 2. Enable the Enable DeviceFingerprint Service option. 3. In the Organization ID field, enter the Organization ID. Contact support if you do not know this value. 4. In the ThreatMetrix URL field, enter the URL that points to the JavaScript that generates and retrieves the fingerprint of the device. 5. In the TTL (Time to Live)field, enter how many milliseconds to wait before generating a new fingerprint for any given customer session. Delivery Address Verification {#salesforce-b2c-delivery-address-verification} ============================================================================= To verify the customers shipping address during checkout, configure Delivery Address Verification services. 1. Go to Merchant Tools \> Site Preferences \> Custom Preferences \> `Visa Acceptance Solutions`_DeliveryAddressVerification. 2. Enable the Delivery Address Verification Services option. Tax Calculation {#salesforce-b2c-tax-calculation} ================================================= To calculate local taxes once the customer enters their address at checkout, configure the Tax Calculation services. 1. Go to Merchant Tools \> Site Preferences \> Custom Preferences \> Cybersource_TaxConfiguration and set these options: 2. Enable the Enable Tax Calculation field. 3. Configure these tax settings: #### ADDITIONAL INFORMATION * List of Nexus States: List the states to calculate tax for. * List of Nexus States to Exclude: List the states to not calculate tax for. * Merchants VAT Registration Number: Enter your VAT registration number if you have one. * Default Product Tax Code: Enter the default tax code to use for products in the basket without a tax code. * Purchase Order Acceptance City * Purchase Order Acceptance State Code * Purchase Order Acceptance Zip Code * Purchase Order Acceptance Country Code * Purchase Order Origin City * Purchase Order Origin State Code * Purchase Order Origin Zip Code * Purchase Order Origin Country Code * Ship From City * Ship From State Code * Ship From Zip Code * Ship From Country Code #### RESULT If you enable Tax Calculation and do not specify any states in List of Nexus States or List of Nexus States to Exclude, Tax Calculation assumes every state or province is taxable. You can leave either the List of Nexus States or the List of Nexus States to Exclude as empty, but both cannot be empty. Message Level Encryption {#salesforce-b2c-message-level-encryption} =================================================================== Message Level Encryption (MLE) uses certificates to 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. > Message Level Encryption requires that a [.p12 certificate to be created](https://developer.visaacceptance.com/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-message-intro/restgs-security-p12-intro.md ""). 1. Extract and convert the p12 certificate to the .*pem* format using this command: ``` openssl pkcs12 -in <key filename>.p12 -cacerts -nokeys -out <key filename>.crt ``` {#salesforce-b2c-message-level-encryption_codeblock_e5t_13d_c3c} Be sure to note the serial number of the ` Visa Acceptance Solutions `_SJC_US certificate. 2. Import the certificate, by going to Administration \> Operations \> Private Keys and Certificates and importing the extracted *.crt*. Make a note of the alias. 3. Enable Message Level Encryption, by going to Merchant Tools \> Site Preferences \> Custom Preferences \> Cybersource_MLE. 4. Enable the Enable Message-Level Encryption option. 5. In the Alias of the Certificatefield, enter the Alias from when the certificate was imported. 6. In the Certificate Serial Numberfield, enter the serial number from the `Visa Acceptance Solutions`_SJC_US certificate. Order Management {#salesforce-b2c-order-management} =================================================== `Salesforce` B2C Commerce does not natively support order management functions. This cartridge has functions that can be utilized to process captures and authorization reversals. > These functions must be customized before use in the ` Salesforce ` B2C Commerce user interface. Capture ------- The capture function can be found in the script *scripts/http/capture.js*. A working example is available in the ServiceFrameworkTest-TestCaptureService controller. Reference the capture.js object and make this request: ``` var captureObj = require("~/cartridge/scripts/http/capture.js"); var serviceResponse = captureObj.httpCapturePayment(requestID, merchantRefCode, paymentTotal, currency); ``` The resulting serviceResponse object contains the full response object generated by the request. The contents of this object determine your logic in handling errors and successes. These are the Capture request parameters: **Capture Request Parameters:** * requestID: The `Visa Acceptance Solutions` Request ID from the initial authorization. * merchantRefCode: The `Salesforce` Order Number. * purchaseTotal: The capture amount. * currency: Currency Code. **Function Signature:** ``` httpCapturePayment(requestID, merchantRefCode, purchaseTotal, currency) ``` Authorization Reversal ---------------------- The authorization reversal function can be found in the script called *scripts/http/authReversal.js*. A working example is in the ServiceFrameworkTest-TestAuthReversal controller. Reference the AuthReversal.js object and make this request: ``` var reversalObj = require("~/cartridge/scripts/http/authReversal.js"); var serviceResponse = reversalObj.httpAuthReversal(requestID, merchantRefCode, paymentTotal, currency); ``` The resulting serviceResponse object contains the full response object generated by the request. The contents of this object determine your logic in handling errors and successes. These are the Authorization reversal request parameters: **Authorization Reversal Request Parameters:** * requestID: The `Visa Acceptance Solutions` Request ID from the initial authorization. * merchantRefCode: The `Salesforce` Order Number * purchaseTotal: The reversal amount * currency: Currency Code Customization {#salesforce-b2c-customization} ============================================= The `Visa Acceptance Solutions` cartridge for `Salesforce` B2C Commerce has built-in custom hooks that can be utilized to customize the request data that is sent to each service. These hooks can send additional custom data, such as, if you want to include Merchant Defined Data in your authorization requests. How Custom Hooks Work --------------------- After a request for a particular service is built, there is a check for any code registering to the hook `app.payment.modifyrequest`. If present, the hook is called for that specific request and the request object is passed into the hook. The return value of the hook is sent to `Visa Acceptance Solutions` as the final request object. Through this process, you can inject your own data into the request object from the custom code you write in a separate cartridge. Implementation -------------- To customize request objects, register the hook `app.payment.modifyrequest` in your cartridge's *hooks.json* file. An example would look like this, replacing the script path with your own script: ``` { "name": "app.payment.modifyrequest", "script": "./cartridge/scripts/hooks/modifyRequestExample" } ``` You can copy the *scripts/hooks/modifyRequestExample* script from this cartridge into your own to use as a template for extending and modifying service request objects. Note that every hook must return a valid request object for the given service. Refer to the `Visa Acceptance Solutions` Developer Guide for information about any field you want to customize or add. Support \& Troubleshooting {#salesforce-b2c-support-troubleshooting} ==================================================================== Getting Support --------------- If you require support with this extension, visit [support.visaacceptance.com](https://support.visaacceptance.com "") to raise a support case. Required Information for Support Cases -------------------------------------- Provide this information for your support case: * Summary of the issue. * Steps to reproduce the issue. * `Visa Acceptance Solutions` B2C Commerce cartridge version. * `Visa Acceptance Solutions` Merchant ID. * Configuration screenshots: Provide screenshots of custom preference configurations. * Log file and other relevant data: Download the logs from Administration \> Site Development \> Development Setup \> Log files. Upgrade {#salesforce-b2c-upgrade} ================================= To upgrade to a later version of our cartridge, follow these steps. 1. Download the code from the ISV Integration Toolkits section on [GitHub](https://github.com/cybersource/cybersource-plugins-rest-salesforceb2ccommerce ""). 2. Zip *payments_metadata* folder. 3. Go to Administration \> Site Development \> Site Import \& Export and upload *payments_metadata.zip* file. 4. Import the uploaded zip file. 5. Check release notes for any configuration parameters that might have changed. #### RESULT The cartridge is successfully upgraded to the latest version. `Shopify` {#shopify-overview} ============================= This section details the features, transaction types, and fraud solutions available in `Shopify`. The Cybersource app on `Shopify` provides commerce tools to start, grow, market, and manage retail businesses. You can accept payments in multiple currencies and get paid in your local currency. The Cybersource app on `Shopify` supports popular payment methods to meet your business needs. The Cybersource app on `Shopify` supports these features: * 3-D Secure * Apple Pay * Card payments * Google Pay * Fraud Management tools * Shopify Subscriptions {#shopify-overview_ul_rsp_15w_lcc} Cybersource supports these transaction types on `Shopify`: * Authorization (authorize only) {#shopify-overview_ul_bdh_frp_lcc} * Sale (auth and capture) {#shopify-overview_ul_cdh_frp_lcc} * Capture (capture only) {#shopify-overview_ul_ddh_frp_lcc} * `Payer Authentication` (3-D Secure) * Refund (credit) * Void (reversal) {#shopify-overview_ul_edh_frp_lcc} The Cybersource app on `Shopify` supports the following fraud solutions: * `Decision Manager` (DM) * `Fraud Management Essentials` (FME) {#shopify-overview_ul_chg_myj_42c} We recommend an accept/reject model only for fraud management. Configuring Security Credentials {#shopify-config-cred} ======================================================= You must have a Cybersource `Business Center` account. If you do not have one, you must create one before installing the Cybersource app on `Shopify`. You also must retrieve details from that account to install the plugin. Creating a `Business Center` Account {#id_hyt_zjc_mcc} ------------------------------------------------------ Follow these steps to create your `Business Center` account: 1. Go to the [Business Center Registration](https://ebc2.cybersource.com/ebc2/registration/external "") website, and create an account. 2. Follow the email instructions that you received to activate your merchant account. 3. Log in to the [Business Center](https://ebctest.cybersource.com/ebc2/ "") to complete the registration process. {#id_hyt_zjc_mcc_steps_jmr_kx3_lcc} Installing the Cybersource App on `Shopify` {#shopify-install} ============================================================== You must enable the Cybersource app in your `Shopify` account settings. You can install the Cybersource CAS app if you are using a sandbox account, or the live app if you have completed the go live process. Installing the Cybersource CAS App {#shopify-install_section_vdt_h35_52c} ------------------------------------------------------------------------- Follow these steps to install the Cybersource CAS app: 1. Go to [cybersource-cas](https://apps.shopify.com/cybersource-cas "") 2. Select the app and click Install. 3. A page opens on `Shopify`. Provide the required permissions to the payment app. 4. After you set the permissions, the `Business Center` log in opens. 5. Log in to the `Business Center` with your Cybersource credentials. This must be your transacting merchant ID. An agreement page opens. 6. Check or clear the 3-D Secure enrollment box based on your business needs. If you choose to enroll for 3-D Secure, ensure that the `Payer Authentication` feature is enabled and configured. 7. Submit the form. The `Shopify` store settings page re-opens so that you can configure and activate the Cybersource app. 8. You must repeat these steps if you have more than one `Shopify` store. Installing the Cybersource Live App {#shopify-install_section_f2y_h35_52c} -------------------------------------------------------------------------- Follow these steps to install the Cybersource live app: 1. Go to . 2. Select the app and click Install. 3. A page opens on `Shopify`. Provide the required permissions to the payment app. 4. After you set the permissions, the `Business Center` log in opens. 5. Log in to the `Business Center` with your Cybersource credentials. This must be your transacting merchant ID. An agreement page opens. 6. Check or clear the 3-D Secure enrollment box based on your business needs. If you choose to enroll for 3-D Secure, ensure that the `Payer Authentication` feature is enabled and configured. 7. Submit the form. The `Shopify` store settings page re-opens so that you can configure and activate the Cybersource app. 8. You must repeat these steps if you have more than one `Shopify` store. Configuring `Shopify` {#shopify-configuring} ============================================ This section details how to configure `Shopify` and set up `3-D Secure`. Configure the `Shopify` payment settings. Follow these steps to configure the Cybersource App in your `Shopify` store: 1. Log in to your `Shopify` account. 2. Go to your `Shopify` store, and go to Settings \> Payments \> Manage. 3. Select the card brands and payment methods that you want to accept. 4. Click Save. #### ADDITIONAL INFORMATION > If you are using the test server, ensure that the Test Mode toggle is set to ` On `. {#shopify-configuring_ol_rc5_cdg_gcc} Using `3-D Secure` {#task_eyj_brc_mcc} -------------------------------------- If you are going to use `3-D Secure`, you must have `Payer Authentication` enabled and have your Cardinal keys stored within the `Business Center`. To enable `Payer Authentication`, contact `Visa Acceptance Solutions` support or your account manager. Request that the `Payer Authentication` enablement include support for the direct integration method. After `Payer Authentication` is enabled, follow these steps to verify your `Payer Authentication` credentials: 1. Log in to your `Business Center` account. 2. Go to Payment Configuration \> Payer Authentication Configuration. 3. View the Org Unit ID, API Identifier, and API Key to verify your credentials. {#task_eyj_brc_mcc_ul_s5b_tsc_mcc} Because you verified the `Payer Authentication` credentials and enabled the `3-D Secure` feature when you installed the Cybersource app, the transactions will support `3-D Secure` flows. Reference Information {#shopify-reference} ========================================== This section contains reference information to help you use the `Visa Acceptance Solutions` app on `Shopify`. Testing ------- You can test your integration before you start accepting payments. To test the application before moving to the production environment, you must use the dedicated the test app from `Visa Acceptance Solutions`. Go to [cybersource-cas](https://apps.shopify.com/cybersource-cas "") to install the test app. Follow these steps to verify that the app is enabled and configured properly: 1. Go to your `Shopify` web store. 2. Add an item to the cart and proceed to checkout. 3. Enter the shipping information. 4. Enter the test card information. 5. Click Pay Now. 6. Log in to your `Business Center` account. 7. Review the test transaction. 8. If there is a problem with the transaction or it does not appear in the `Business Center`, contact `Visa Acceptance Solutions` support. Troubleshooting and Support --------------------------- If you require support, visit [support.visaaceptance.com](https://support.visaaceptance.com ""). If your account is provided by a reseller, contact `Visa Acceptance Solutions` Include this information when you contact `Visa Acceptance Solutions`: * `Visa Acceptance Solutions` merchant ID * `Shopify` store name * `Shopify` payment ID * `Shopify` reason string and code * Date and time * Production environment * Steps to recreate the error {#shopify-reference_ul_jyr_15z_pcc} `WooCommerce` {#wc-introduction} ================================ The `Visa Acceptance Solutions` extension for `WooCommerce` enables merchants to connect their `WooCommerce` store to the `Visa Acceptance Solutions` platform to directly take credit/debit card, Google Pay, and Click to Pay payments. Supported Features {#wc-supported-features} =========================================== * Credit/debit cards * Apple Pay * Google Pay * Click to Pay * Paze * Payer Authentication/`3-D Secure` * Tokenization * `Decision Manager` and `Fraud Management Essentials` * `WooCommerce` Subscriptions * `WooCommerce` Checkout Blocks Supported Versions {#wc-supported-versions} =========================================== The `WooCommerce` extension requires these versions: * `WooCommerce` 10.3.7+ * WordPress 6.9+ * PHP 8.2+ `Visa Acceptance Solutions` Prerequisites {#wc-prerequisites} ============================================================= This section outlines the required and optional prerequisites for using the `Visa Acceptance Solutions` extension with `WooCommerce`. Required Products {#wc-req-prerequisites} ========================================= The Unified Checkout product must be enabled and configured for your merchant ID. See the [*Unified Checkout Developer Guide*](https://developer.visaacceptance.com/docs/vas/en-us/unified-checkout/developer/all/rest/unified-checkout/uc-intro.md ""). You must also have a REST Shared Secret Key. See the [*Getting Started with the REST API*](https://developer.visaacceptance.com/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-http-message-intro/restgs-security-key-pair-intro/restgs-security-key-pair-task.md "") guide. Optional Products {#wc-opt-prerequisites} ========================================= These products are optional, but need to be enabled and configured for your merchant ID if you choose to use them: * Payer Authentication for 3-D Secure * Tokenization * Apple Pay * Google Pay * Click to Pay * Paze * `Decision Manager` * `Fraud Management Essentials` You can also choose to enable Message-Level Encryption (MLE) for additional security. A REST certificate is required for MLE. See the [*Getting Started with the REST API*](https://developer.visaacceptance.com/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-http-message-intro/restgs-security-key-pair-intro/restgs-security-key-pair-task.md "") guide. Release Notes {#wc-release-notes} ================================= Version 2.2.0: February 2026 ---------------------------- This version provides these enhancements: * Updated Unified Checkout to v0.33 * Added support for China UnionPay, Maestro, Jaywan, and Paze * Added Payer Authentication/`3-D Secure` for Google Pay * Added Express Pay for Product and Checkout pages * Replaced `Visa Acceptance Solutions` endpoints with Visa Acceptance Solutions endpoints * Added compatibility for Wordpress v6.9 The following bugs were addressed: * IP address is now collected for all requests. * CVV input field text was updated. * Saved card tokens are now only accessible when tokenization is enabled. * Administrative state field is now properly passed for non-US addresses in `3-D Secure` transactions. {#wc-release-notes_ul_f1f_5kw_c3c} Version 2.0.1: October 2025 --------------------------- This version provides these bug fixes: * Removed the Customer ID for a guest user because it exceeded limits within the platform for some processors. * Removed Commerce Indicator from the Payment Acceptance Request. Version 2.0.0: August 2025 -------------------------- This version provides these enhancements: * Unified Checkout Version 0.23 * Apple Pay * Adoption of Visa Acceptance REST Client SDK * Message-Level Encryption * `WooCommerce` subscriptions and HPOS compatibility This version is compatible with: * `WooCommerce` 7.6+ * WordPress 6.5.3+ * PHP 8.0+ Version 1.0.0: June 2025 ------------------------ This initial release supports these products: * Unified Checkout * Google Pay * Click to Pay * Token Management Service (TMS) * Payer Authentication * `Decision Manager` and `Fraud Management Essentials` This version is compatible with: * `WooCommerce` 7.6+ * WordPress 6.5.3+ * PHP 7.4+ Install the Extension {#wc-installation} ======================================== Follow these steps to install the extension: 1. Download our extension from[WordPress](https://wordpress.org/plugins/visa-acceptance-solutions/ "") or [`WooCommerce`](https://woocommerce.com/products/visa-acceptance-solutions/ ""). 2. Log into your `WooCommerce` admin account. 3. Go to **Extensions \> Add New \> Upload**. 4. Click **Install Now**. 5. After the extension is installed, click **Activate**. 6. Click **Configure** to start configuring the extension. Alternatively, you can use the *Add to store* functionality in the `WooCommerce` order confirmation page or the [My Subscriptions](https://woocommerce.com/my-account/my-subscriptions/ "") section in your `WooCommerce` account. Configure the Extension {#wc-configuration} =========================================== Follow these steps to configure the extension: 1. Select **Extensions \> Installed Extensions** , then select Visa Acceptance Solutions or **Payments**. 2. Click Manage on the Visa Acceptance Solutions line. Minimum Configuration Requirements {#wc-minimum-configuration} ============================================================== These extension settings must be configured to accept payments with `Visa Acceptance Solutions`: Enable/Disable : Set to *enable* to allow the extension to take payments from your `WooCommerce` store. When the extension is enabled, card payments are enabled by default. Title : Enter the *title* text that you want to display for your customers on the checkout and order received page. Description : Enter the *description* text that you want to display during the checkout process. Transaction Type : * **Charge:** When this option is selected, the transaction is automatically captured if the authorization is approved. * **Authorization**: When this option is selected, the system only sends an authorization request and if approved. If the authorization is approved, you need to manually request a capture. Charge Virtual-Only Orders : When this setting is selected, if the order is exclusively for digital or virtual items, this the transaction is automatically captured if the authorization is approved. Capture Paid Order : When this setting is selected, if you mark an order as *Processing* or *Completed*, capture requests are automatically sent. Environment : * Set to *Test* for testing to your test account. * Set to *Production* for live transactions. Merchant ID/Test Merchant ID : Enter the transacting merchant ID (MID) assigned to you when you set-up your account. API Key Detail/Test API Key Detail : Enter the key from your REST API shared secret key. API Shared Secret Key/Test API Shared Secret Key : Enter the shared secret from your REST API shared secret key. Accepted Card Types : Select the card brands you want to accept. Message Level Encryption {#wc-message-level-encryption} ======================================================= Message-Level Encryption (MLE) enables you to store information or communicate with other parties while helping to prevent uninvolved parties from understanding the stored information. MLE is optional and supported only for payments services. A REST certificate is required for MLE. Follow these steps to enable MLE,: 1. Check **Message Level Encryption**. 2. Enter the **Key Directory Path** where you have stored the certificate in your `WooCommerce`/WordPress environment. 3. Enter the **Key File Name**. 4. Enter the **Key Password** which you set when generating the REST certificate. {#wc-message-level-encryption_ol_x4b_zx2_ggc} Digital Payment Methods {#wc-digital-payment-methods} ===================================================== Digital Payment Methods: Choose from Apple Pay, Google Pay, Click to Pay, and Paze. > You must enable these for your MID in the ` Business Center `. > See the [*Unified Checkout Developer Guide*](https://developer.visaacceptance.com/docs/vas/en-us/unified-checkout/developer/all/rest/unified-checkout/uc-intro.md "") for more information. Tokenization {#wc-tokenisation} =============================== Tokenization allows you to offer the ability for your customers to save their payment cards securely for future payments. 1. Select **Tokenization** to enable this feature. 2. Select **Saved Card Verification** to request customers to enter their card security code when paying with a saved card. Payer Authentication/3-D Secure {#wc-payer-authentication} ========================================================== 1. Select **Payer Authentication/3-D Secure** to enable added payment security. Some countries/regions mandate this feature. 2. Select **Strong Consumer Authentication** to force a 3-D Secure Challenge when a customer chooses to save their card for future transactions. Fraud Screening {#wc-fraud-screening} ===================================== 1. Select Fraud Screening to enable `Decision Manager` or `Fraud Management Essentials`. 2. Configure your fraud screening profiles using the `Business Center`. Debug Mode {#wc-additional-options} =================================== 1. Select one of these debugging mode options: * On: enables the creation of detailed logs for every transaction. This setting is recommended only for use in the test environment or when troubleshooting issues in the production (live) environment. * Off: enables the creation of basic logs for transactions. {#wc-additional-options_choices_tym_gxh_jgc} Order Management {#wc-order-management} ======================================= Orders are marked differently, depending on the selected transaction type: * **Authorization:** if this option is selected, successful transactions are marked as *On Hold*. * **Charge** : if this option is selected, successful transactions are marked as *Processing*. Fraud Screening {#wc-fraud-screening-orders} ============================================ If fraud screening is enabled, transactions are marked as follows: * Approved orders are marked as *On Hold* or *Processing*, depending on your transaction type setting. * Orders to review are marked as *On Hold*. * Rejected orders are marked as *Failed* or *Cancelled*. Orders marked as *On Hold* need to be reviewed in the `Business Center`. The extension checks for transaction status updates every 15 minutes. Rejected transactions are marked as *Cancelled*. Accepted transactions are marked according to your transaction type settings. If you need to manually trigger the transaction update, follow these steps using the `WooCommerce` Dashboard: 1. Select Tools \> Scheduled Actions \> Pending. 2. Find and select wc_payment_gateway_update_order. 3. Click Apply. Capture an Order {#wc-capture} ============================== There are two ways to capture an order if you have the transaction type set to *Authorization*. Enter the order from the list of orders and choose one of these actions: 1. Click the Capture Charge button. 2. Change the order status to *Processing* , then click Apply. Refund an Order {#wc-refund} ============================ To refund an order, enter the order from the list of orders and complete these steps: 1. Click the Refund button. 2. Enter the refund amount. 3. Click Refund via `Visa Acceptance Solutions`. Void an Order {#wc-void} ======================== Voids can only be performed for transactions when the transaction type is set to *Authorization* and the transaction has not yet been captured. To void an authorization, complete these steps: 1. Click the Refund button. 2. Enter the refund amount. 3. Click Refund via `Visa Acceptance Solutions`. Upgrade the Extension {#wc-upgrade} =================================== Follow these steps to upgrade to a later version of the `WooCommerce` extension. 1. Select Extensions \> Installed Extensions. 2. Locate the Visa Acceptance Solutions extension and click Update Now. Support and Troubleshooting {#wc-support-troubleshooting} ========================================================= If you need support installing or using this extension, contact the [Support Center](https://support.visaacceptance.com/ "") to raise a case, and provide this information: * Summary of the issue * Steps needed to reproduce the issue * Platform version * Extension version * Platform merchant ID * Configuration screenshots * List of themes and additional extensions installed * Log file and any other data or screenshots related to the issue Built by Our Partners {#built-by-them} ====================================== Explore solutions built by our industry-leading partners that offer real-time fraud screening, account takeover protection, and comprehensive payment solutions. Our partners provide potential use cases such as personalizing shopping experiences through advanced analytic. Offer your customers a seamless omnichannel experience and improve site performance for higher customer satisfaction. Benefit from the centralized management of product information, automated order processing and fulfillment, and real-time data synchronization between SAP Commerce Cloud and existing ERP systems. Moreover, our partners' solutions offer scalable infrastructure, flexible integration capabilities, advanced reporting tools, and enhanced visibility into supply chain and inventory management. This is built by our partner: * [BigCommerce](/docs/vas/en-us/isv-plugins/admin/all/na/isv-plugin-o/built-by-them/bigcommerce-overview.md "") Visa Acceptance Solutions Payments for Adobe Commerce User Guide {#vas-adobe-commerce-intro} ============================================================================================ Recent Revisions to This Document {#vas-adobe-commerce-doc-revisions} ===================================================================== 25.01 ----- Initial release. About this Guide {#doctemp-about-guide} ======================================= This section describes how to use this guide and where to find further information. Audience and Purpose : This document outlines the configuration details for the Visa Acceptance Solutions payment extension in the Adobe Commerce platform. The configuration steps are related to payment acceptance, payment security, fraud management, and order management services for `Unified Checkout`, including Payment Card, Google Pay, and `Click to Pay`. This guide also applies to Magento Open Source. Adobe Commerce will be referenced throughout for simplicity. Conventions : These statements appear in this document: > An *Important* statement contains information essential to successfully completing a task or learning a concept. Customer Support : For support information about any service, visit the Support Center: Installing the Visa Acceptance Solutions Extension {#vas-adobe-commerce-install-extension} ========================================================================================== 1. Place an order in the Adobe Commerce Marketplace with the Visa Acceptance Solutions module. Go to [](https://commercemarketplace.adobe.com/ ""). 2. Go to **My Profile \> My Products \> Access Keys** and copy the keys. ![Adobe Commerce Marketplace](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-marketplace.png/jcr:content/renditions/original) ```ph codeph { "http-basic": { "repo.magento.com": { "username": "Your_Public_Key", "password": "Your_Private_Key" } } } ``` {#vas-adobe-commerce-install-extension_codeblock_zq4_bvs_rdc} ![auth.json file](/content/dam/documentation/cybs/en-us/isv-plugin-o.ditamap) 3. Rename the *auth.json.sample* file to *auth.json* in your server's Magento root directory and enter your access keys. 4. In your Magento root directory, run the commands listed below: ```ph codeph composer require visaacceptance/module-payment php bin/magento module:enable VisaAcceptance_Payment php bin/magento setup:di:compile php bin/magento indexer:reindex php bin/magento setup:upgrade php bin/magento setup:static-content:deploy -f php bin/magento cache:clean php bin/magento cache:flush php bin/magento module:status ``` {#vas-adobe-commerce-install-extension_codeblock_kb4_t5s_rdc} {#vas-adobe-commerce-install-extension_ol_b1q_2qs_rdc} Prerequisites {#vas-adobe-commerce-prereqs} =========================================== Before using the extension, ensure that you have done these prerequisites: * A Visa Acceptance Solutions account with `Unified Checkout` enabled. * Payer Authentication direct connection if `3-D Secure` is required. * A Token Management Service if you allow customers to save their payment cards on your website. {#vas-adobe-commerce-prereqs_ul_s5v_wvs_rdc} Contact [support](https://support.visaacceptance.com/ "") or your reseller if any of these prerequisites are not completed. If you do not yet have a Visa Acceptance Solutions account, you can create one [here](https://developer.visaacceptance.com/hello-world/sandbox.md ""). Demo accounts are created with United States dollars as the default currency. Refer to this [article](https://developer.visaacceptance.com/docs/vas/en-us/platform/developer/all/rest/rest-getting-started/restgs-intro.md "") on how to create REST API keys in the `Business Center`. General Settings {#vas-adobe-commerce-settings} =============================================== This section provides General Settings Configuration details for the Visa Acceptance Solutions extension in Adobe Commerce. | Serial Number | Settings | Description | |---------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | Environment | Configure the sandbox or production environment by providing the Merchant ID, API key detail, and API shared secret key. If sandbox is chosen, the website is available for testing new changes and experiments. | | 2 | Merchant ID | Your Visa Acceptance Solutions Merchant ID | | 3 | API Key | Refers to a specific key provided by a payment gateway to authenticate and authorize the merchant's integration with the gateway. | | 4 | API Shared Secret | Refers to a confidential or private key used for secure communication between the merchant's online store and a payment gateway. | | 5 | Debug Mode | Enabling debug mode provides an option to troubleshoot using the Visa Acceptance Solutions logs, named visaacceptance.log. The diagnostic information will be stored in log files in the Adobe Commerce web server. | ![General Settings](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-generalsettings.png/jcr:content/renditions/original) Configuration Details {#vas-adobe-commerce-config-details} ========================================================== To configure the Visa Acceptance Solutions extension, a merchant needs to log in to the administration section of their Adobe Commerce website. The configuration panel can be accessed by navigating to the Payment Methods screen: Stores \> Configuration \> Sales \> Payment Methods. On this screen, you can see the settings to configure the Visa Acceptance Solutions extension. ![Configuration Page](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-config.png/jcr:content/renditions/original) Secure Payment Methods {#vas-adobe-commerce-secure-paymt} ========================================================= This section provides the configuration details of the services supported by Visa Acceptance Solutions extension in Adobe Commerce for `Unified Checkout`. | Sl. No. | Settings | Description | |---------|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | Enable | Choose `Yes` to enable the Visa Acceptance Solutions extension. | | 2 | Title | Customers see the text saved here as the payment method name. | | 3 | Payment Action | Choose either `Authorize` or `Capture` to decide the payment action during customer checkout. | | 4 | Payment Card Types | Choose accepted payment card brands. | | 5 | Allowed Payment Method | Choose payment methods through which customer can complete their order. | | 6 | Select Layout | Choose `Embedded` or `Side bar` as the layout to display the `Unified Checkout` payment widget. | | 7 | Payment from Applicable Countries | By choosing `All Allowed Countries`, the payment method will use the Adobe Commerce global settings for the customer's country. By choosing `Specific Countries`, the merchant can manually choose the allowed countries for the customer. | | 8 | Payment from Specific Countries | Choosing countries in this setting allows the store owner to specify which countries are allowed for our payment method. | | 9 | Payer Authentication/`3-D Secure` | Enabling this option adds an additional layer of security to payments by authenticating the customer's identity before authorization. | | 10 | Tokenization | Enabling this option allows customers to save their payment cards for future payments. | | 11 | Tokenization Title | This text specifies the title of the saved card payment method. | | 12 | Saved Card Verification | This option allows the merchant to configure whether saved card transactions are processed with CVV. | | 13 | Enforce Strong Customer Authentication | If enabled, the card holder will be `3-D Secure` challenged when saving a card. | ![Secure Payment Methods Settings](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-secpymtsettings.png/jcr:content/renditions/original) Tokenization {#vas-adobe-commerce-tokenization} =============================================== This setting determines if registered customers can save cards securely to their account. > To use this feature choose **Yes** in the tokenization setting in the admin configuration panel. If you want the customer to enter CVV while using the saved card, choose **Yes** for Saved Card Verification as well. > ![Tokenization Settings](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-tokenization.png/jcr:content/renditions/original) Payer Authentication {#vas-adobe-commerce-payer-auth} ===================================================== Visa Acceptance Solutions supports `3-D Secure` 2.x services. To process with `3-D Secure`, choose `Yes` in the Payer Authentication/`3-D Secure` setting in the admin configuration panel. ![Payer Authentication Configuration](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-payerauth.png/jcr:content/renditions/original) Strong Customer Authentication {#vas-adobe-commerce-sca} ======================================================== Payer Authentication (`3-D Secure`) is used for Strong Consumer Authentication (SCA) in e-commerce payments. Some card issuers require cardholders to authenticate with a `3-D Secure` challenge when saving their card with a merchant. If you operate in a region where this is common, you can enable this setting to require a challenge each time a customer saves a card. To enforce SCA, choose `Yes` in the Enforce Strong Customer Authentication setting in the admin configuration panel. If SCA is not enforced and an issuer requires it, this extension replays the transaction and requests the challenge. ![Strong Customer Authentication Configuration](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-sca.png/jcr:content/renditions/original) Managing Orders {#vas-adobe-commerce-order-mgmt} ================================================ Merchants can manage follow-up order management services in Adobe Commerce Back Office after placing an order from the Adobe Commerce Front Office. The merchant side services in Adobe Commerce Back Office are: * Full authorization reversal * Authorization capture or multiple partial captures * Standard refund and partial refund {#vas-adobe-commerce-order-mgmt_ul_ij1_tgd_h2c} Full Authorization Reversal {#vas-adobe-commerce-auth-reversal} =============================================================== Merchants can perform a full authorization reversal after an authorization. To cancel a completed order authorization, the merchant can click **Cancel**. ![Cancel Button](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-authrev.png/jcr:content/renditions/original) Capture an Authorization {#vas-adobe-commerce-capture-auth} =========================================================== While in authorize mode, the system will create an order record, but not an invoice. Capturing funds for authorized transactions is done implicitly when you prepare an invoice. To create an invoice, navigate to the below path in the administration section of Adobe Commerce: Navigate to **Sales \> Orders \>** choose an **Order Pending** invoice \> then click **Invoice**. ![Admin View of Payment Pending Order Featuring the Invoice Button](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-authcapture.png/jcr:content/renditions/original) The merchant can perform a full capture or multiple partial captures using the invoice button. When creating an invoice, the merchant can do multiple partial captures by choosing specific quantities. Alternatively, the merchant can do complete capture by choosing the entire order. ![List of Items to Invoice During Partial Capture](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-partialcapture.png/jcr:content/renditions/original) To complete invoice creation and capture funds, click **Submit Invoice**. ![Submit Invoice Button](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-invoicebutton.png/jcr:content/renditions/original) ![Invoice Submitted](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-invoice.png/jcr:content/renditions/original) Refund a Captured Order {#vas-adobe-commerce-refund} ==================================================== You must create a credit memo to refund a captured order. To refund an order, navigate to the administration section of your Adobe Commerce website: Sales \> Orders \> open an invoiced order **\>** click Invoices from the left panel **\>** and click View. ![Invoice Grid Showing Invoices Created for a Particular Order](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-capturerefund.png/jcr:content/renditions/original) Click View on an invoice to open it. You can create a credit memo within the invoice record. ![Credit Memo Button inside Invoice Record](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-creditmemo.png/jcr:content/renditions/original) When creating a credit memo, you can refund all or part of an invoice. To issue a partial refund, alter the numbers in the **Qty to Refund** column. Click the Update Qty's button. ![Quantity to Refund Column on Items to Refund Grid](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-refundgrid.png/jcr:content/renditions/original) To complete the credit memo, click Refund. ![Refund Button](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-refundbutton.png/jcr:content/renditions/original) ![Refund Submitted](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-refundsubmit.png/jcr:content/renditions/original) Payment Methods and Services {#vas-adobe-commerce-paymt-methods-services} ========================================================================= This extension supports the following payment methods and services. These services can be enabled or disabled using the admin panel configuration: * Payment Card * Payment acceptance services * Payment security services * Fraud management services * Order management services {#vas-adobe-commerce-paymt-methods-services_ul_ikf_hlp_sdc} * Google Pay * Payment acceptance services * Fraud management services * Order management services {#vas-adobe-commerce-paymt-methods-services_ul_qxb_hlp_sdc} * `Click to Pay` * Payment acceptance services * Order management services {#vas-adobe-commerce-paymt-methods-services_ul_fc5_glp_sdc} {#vas-adobe-commerce-paymt-methods-services_ul_y1l_flp_sdc} ![Payment Method Configuration](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-paymt-mthd-config.png/jcr:content/renditions/original) Appendix {#vas-adobe-commerce-appendix} ======================================= Saving Card at Checkout {#vas-adobe-commerce-appendix_section_rbf_nlp_sdc} -------------------------------------------------------------------------- Customers can choose **Save for later use** for payment cards only. Once the order is placed, card information is securely stored in `Visa Acceptance Platform`. ![Saving a Card at Checkout](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-save-card.png/jcr:content/renditions/original) Payment With a Saved Card {#vas-adobe-commerce-appendix_section_db5_4lp_sdc} ---------------------------------------------------------------------------- Customers can make payments using previously saved cards under **Stored Cards** by choosing a card to proceed with. ![Stored Cards at Checkout](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-storedcards.png/jcr:content/renditions/original) Deleting a Card {#vas-adobe-commerce-appendix_section_jbb_qlp_sdc} ------------------------------------------------------------------ Customers can view their stored cards under **My Account** in Adobe Commerce by navigating to **Stored Payment Methods** . The customer has the option to delete their previously saved cards by clicking **Delete**. ![Deleting a Card](/content/dam/documentation/cybs/en-us/topics/isv/platform/vas-adobe-commerce/images/vas-adobe-commerce-deletecard.png/jcr:content/renditions/original) Unsupported Adobe Commerce Features {#vas-adobe-commerce-appendix_section_a1k_vfs_12c} -------------------------------------------------------------------------------------- The following features are not supported by this module: * Multi-shipping * Multiple node implementation * Google reCAPTCHA {#vas-adobe-commerce-appendix_ul_tzs_wfs_12c} `BigCommerce` {#bigcommerce-overview} ===================================== `BigCommerce` provides a software-as-a-service (SaaS) payment platform where you can manage your online business. `BigCommerce` provides customizable functionality ready for you to build and integrate with `Visa Acceptance Solutions`. This section describes the payment methods and services that the platform provides. These payment features and methods are supported: * Card Payments * Apple Pay * Google Pay * `3-D Secure` * Token Management Service * `Decision Manager` and `Fraud Management Essentials` * OAuth for connecting your `BigCommerce` account with `Visa Acceptance Solutions` {#bigcommerce-overview_ul_c2x_sq2_3yb} Release Information {#bigcommerce-release-info} =============================================== This section provides information about the releases for `BigCommerce`. Version 2 includes the following features: * Global availability in more than 190 countries * Transaction currency support in all available countries * [`3-D Secure` 2.0](https://support.bigcommerce.com/s/article/3D-Secure "") * Support for the these card brands: * American Express * Diners Club * Discover * JCB * Maestro * Mastercard * Visa {#bigcommerce-release-info_ul_m44_wxd_gzb} * [Stored Credit Cards](https://support.bigcommerce.com/s/article/Enabling-Stored-Payment-Methods "") * [Apple Pay](https://support.bigcommerce.com/s/article/Connecting-with-Apple-Pay "") * [Google Pay](https://support.bigcommerce.com/s/article/Connecting-with-Google-Pay "") * [`Decision Manager` and `Fraud Management Essentials`](https://www.cybersource.com/en-us/solutions/fraud-and-risk-management/decision-manager.md "") {#bigcommerce-release-info_ul_whf_kxd_gzb} For more information, see [New Features Available in `Visa Acceptance Solutions`](https://support.bigcommerce.com/s/blog-article/aAn4O000000GpA1SAK/new-features-available-in-cybersource?language=en_US ""). Requirements and Prerequisites {#bigcommerce-prod-reqs} ======================================================= Before installing and configuring the `Visa Acceptance Solutions` Extension ensure that you meet these requirements: * Have a `BigCommerce` [merchant account](https://www.bigcommerce.com/start-your-trial/ ""). * Have Optimize One Page Checkout. For more information, see [Optimize One Page Checkout](https://support.bigcommerce.com/s/article/Optimized-Single-Page-Checkout ""). * Have a `Business Center` account. To create an account, go to the website. * Can accept payments in one of the [supported currencies](https://support.bigcommerce.com/s/article/Connecting-with-Cybersource?language=en_US#eligibility ""). * Have cardinal credentials saved within your `Business Center` account for `3-D Secure` transactions. {#bigcommerce-prod-reqs_ul_ops_2hc_kyb} Supported Features {#bigcommerce-features-intro} ================================================ This section describes payment, services, and features provided by `BigCommerce` through `Visa Acceptance Solutions`. These are the supported payment methods: * Credit and debit card payments * Card types: * American Express * Diners Club * Discover * JCB * Maestro * Mastercard * Visa {#bigcommerce-features-intro_ul_vry_qc2_gzb} {#bigcommerce-features-intro_ul_usr_kc2_gzb} * [Apple Pay](https://support.bigcommerce.com/s/article/Apple-Pay?language=en_US#cybersource "") * [Google Pay](https://support.bigcommerce.com/s/article/Connecting-with-Google-Pay?language=en_US "") {#bigcommerce-features-intro_ul_c2x_sq2_3yb} These are the supported services: * Authorization only * Authorization and capture * Captures * Partial Refunds * Refunds {#bigcommerce-features-intro_ul_ig4_ccc_hzb} These are the supported features: * [`3-D Secure`](https://support.bigcommerce.com/s/article/3D-Secure?language=en_US "") * Token Management Service (TMS): Removes your customer's stored card information from your environment and exchanges sensitive payment data for tokens that cannot be reversed. Contact to request that TMS be enabled to use the [Stored credit cards](https://support.bigcommerce.com/s/article/Connecting-with-Cybersource?language=en_US#stored-cc "") feature on your `Visa Acceptance Solutions` merchant account. * [`Fraud Management Essentials`: `Decision Manager`](https://support.bigcommerce.com/s/article/Connecting-with-Cybersource?language=en_US#fraud-management "") * OAuth is an industry-standard authorization protocol that enables you to use your `Business Center` account credentials to connect to `BigCommerce` for transaction processing. For more information about OAuth, see the . {#bigcommerce-features-intro_ul_c34_dnf_gzb} Configuring `BigCommerce` {#bigcommerce-config-intro} ===================================================== This section describes how to set up your `BigCommerce` account to `Visa Acceptance Solutions`. Before you begin, make sure that you have a `Business Center` account. Create an Evaluation Account If you do not have an `Business Center` account, go to the website[Registration](https://ebc2.cybersource.com/ebc2/registration/external "") website to create one. To complete the registration process, follow the email instructions that you received to activate your merchant account, and log in to the `Business Center`. Enabling the Extension {#bigcommerce-config-settings} ===================================================== Follow these steps to enable the `Visa Acceptance Solutions` extension. 1. Login to the [Big Commerce website](https://login.bigcommerce.com/login "") and navigate to Store Setup \> Payments. 2. From the list of Online Payment Methods, choose `Visa Acceptance Solutions`. 3. From the `Visa Acceptance Solutions` Settings tab, click Sign up to create an account. ![](/content/dam/documentation/cybs/en-us/topics/isv/platform/bigcommerce/images/cybersource-sign-up.png/jcr:content/renditions/original) Connecting to `Visa Acceptance Solutions` {#bigcommerce-config-installments} ============================================================================ Follow these steps to connect `BigCommerce` on the `Visa Acceptance Solutions` Settings page. 1. From `Visa Acceptance Solutions` Settings page, choose the environment you want to connect to your `BigCommerce` account, and choose Connect with. You are redirected to the `Visa Acceptance Solutions` login page. ![](/content/dam/documentation/cybs/en-us/topics/isv/platform/bigcommerce/images/connectwith.png/jcr:content/renditions/original) 2. Enter your credentials and click Allow to give `BigCommerce` permission to connect to your account. If you used OAuth to log in, your account automatically connects to `Visa Acceptance Solutions` with the appropriate permissions. {#bigcommerce-config-installments_ol_ljs_rpk_dzb} Configuration Settings {#bigcommerce-config-settings-info} ========================================================== This section describes the configuration settings for the `Visa Acceptance Solutions` Extension. In the `Visa Acceptance Solutions` Settings page, configure your preferences based on the services you use. Display Name: Manages how the payment gateway appears at checkout. `Visa Acceptance Solutions` recommends something like *Credit/Debit*. Merchant ID: Enter the merchant ID (such as *87654321* ) that you received when you signed up with `Visa Acceptance Solutions`. ![](/content/dam/documentation/cybs/en-us/topics/isv/platform/bigcommerce/images/cybersource-settings-merchant-id.png/jcr:content/renditions/original) Transaction Type: Choose Authorize and Capture or Authorize Only. Authorize Only enables you to capture the funds manually. See[Manually Capturing Transactions (Authorize Only)](https://support.bigcommerce.com/s/article/Manually-Capturing-Transactions-Authorize-Only "") to learn more. ![](/content/dam/documentation/cybs/en-us/topics/isv/platform/bigcommerce/images/cybersource-settings-transaction-type.png) Test Mode: Determines whether your store is in Test Mode. When you are ready to take payments, set to No (Recommended). ![](/content/dam/documentation/cybs/en-us/topics/isv/platform/bigcommerce/images/cybersource-settings-test-mode.png) Require CVV (credit card security codes): Using this option requires users to enter the CVV/CVV2/CVD code for their credit card during checkout. Enabling this option adds extra security on credit card transactions. ![](/content/dam/documentation/cybs/en-us/topics/isv/platform/bigcommerce/images/cybersource-settings-req-cvv.png) Enable `3-D Secure`: This option enables an additional security layer that helps to prevent unauthorized transactions. For more information, see [`3-D Secure`](https://support.bigcommerce.com/s/article/Connecting-with-Cybersource?language=en_US#3d "") . Enable Google Pay: This option enables shoppers to use Google Pay on your storefront. For more information, see [Connecting with Google Pay](https://support.bigcommerce.com/s/article/Connecting-with-Google-Pay "") . Set up Apple Pay: This option enables shoppers to use Apple Pay on your storefront. To configure this feature, see [Connecting with Apple Pay](https://support.bigcommerce.com/s/article/Connecting-with-Apple-Pay?language=en_US#setup "") for more information. Show the Card Element: This option displays or hides the credit card field at checkout. For more information on this feature, see [Show Card Element](https://support.bigcommerce.com/s/article/Connecting-with-Cybersource?language=en_US#card-element "") . ![](/content/dam/documentation/cybs/en-us/topics/isv/platform/bigcommerce/images/cybersource-settings-card-element.png/jcr:content/renditions/original) Click Save. Upgrade {#bigcommerce-upgrade} ============================== If you already have an account, you can upgrade to V2 from the `Visa Acceptance Solutions` Settings page. For more details, see [Upgrading from `Visa Acceptance Solutions` to `Visa Acceptance Solutions` V2](https://support.bigcommerce.com/s/article/Connecting-with-Cybersource?language=en_US#upgrade "").