On This Page

Adobe Commerce Cloud

You can integrate Cybersource with the
Adobe Commerce Cloud
 platform to process payments using Magento checkout. The Cybersource
Adobe Commerce Cloud
 extension supports popular payment methods, safeguards payment data, minimizes fraud, and mitigates risks. This section describes the payment management capabilities offered by Cybersource through the
Adobe Commerce Cloud
 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

Cybersource 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

Cybersource 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 Cybersource 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 supports these combinations.

PayPal

The
Adobe Commerce Cloud
 integration includes the PayPal payment method. Processing your PayPal transactions through Cybersource allows 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 Cybersource
Adobe Commerce Cloud
 extension supports the following payment methods and corresponding online bank transfer services:
  • Bancontact
    • Sale
    • Check Status
    • Refund
    • Country: Belgium
  • iDEAL
    • Options
    • Sale
    • Check Status
    • Refund
    • Country: Netherlands

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 Cybersource
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 allows customers to pay with any payment method saved to their Google account.

Release Notes

This section provides information about functionality, bug fixes, and enhancements for the
Adobe Commerce Cloud
 Cybersource integration.

June 2024

Adobe Commerce Cloud
 Cybersource 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".

March 2024

Adobe Commerce Cloud
 Cybersource 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.

October 2023

Adobe Commerce Cloud
 Cybersource 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 Cardinal Cruise 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
 Cybersource 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
 Cybersource 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 the
Adobe Commerce Cloud

You must have a Cybersource
Business Center
 account to update
Adobe Commerce Cloud
.
If you do not have an account, go to the Business Center Registration website to create an account. Follow the email instructions that you received to activate your merchant account, and then log in to the Business Center to complete the registration process.
Follow these steps to update the Cybersource bundle to the latest version:
  1. In your directory, navigate to
    Adobe Commerce Cloud
     root directory
     /
    composer.json
    file
    .
  2. In the
    composer.json
     file, under
    require field
    , change the version to the plugin with the latest version.
  3. After you change the version in require field of
    composer.json
    , run the composer update command.

Configuring the
Adobe Commerce Cloud

Customer payments can be managed through the
Adobe Commerce Cloud
 or the Cybersource
Business Center
. This section describes the settings you must configure in the
Business Center
 as well as some general use cases that will be typical in the day-to-day management of your
Adobe Commerce Cloud
 store. Contact Cybersource for information about product availability and enablement.
You must complete all of the configuration tasks in order to use the features offered in the
Adobe Commerce Cloud
 Cybersource integration.

Configuring Security Credentials

The Cybersource module uses connection methods to access Cybersource 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 Cloud
 to function properly.
If you do not have a
Business Center
 account, go to the Business Center Registration website to create an account. Follow the email instructions that you received to activate your merchant account, and then log in to the Business Center to complete the registration process. Store your merchant key ID for later use.

Creating a SOAP Toolkit Key

The Cybersource
Adobe Commerce Cloud
 integration uses the SOAP Toolkit API to access several Cybersource services.
From your
Business Center
 account, you must generate the SOAP toolkit key. For steps on how to create a SOAP toolkit key, see Creating a SOAP Toolkit Key . Store your SOAP toolkit key for later use.

Creating a REST API Key

The Cybersource
Adobe Commerce Cloud
 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 Cloud
. For steps on how to generate a shared secret key, see Creating a Shared Secret Key Pair. Store your key ID and shared secret key for later use.

Configuring Additional Backend Settings

Certain Cybersource services supported on the
Adobe Commerce Cloud
 require additional backend setup on your
Business Center
 account. Contact your Cybersource 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

Follow these steps to access the configuration settings in the administration section of your
Adobe Commerce Cloud
 console:
  1. Go to the
    Adobe Commerce Cloud
     administration console.
  2. On the left navigation, 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 > Cybersource
    .

    ADDITIONAL INFORMATION

    Complete all of the required fields in the sections and subsections of the Cybersource settings to configure the Cybersource payment module and other payment methods. Expand each section to complete the fields.

Configuring General 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 Cloud
     Cybersource logs (
    cybs.log
    ). Diagnostic information is stored in log files on the
    Adobe Commerce Cloud
     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
    No
     when you want the general error message displays according to
    Adobe Commerce Cloud
     in all rejection and error cases. Set to
    Yes
     when you want the general error message displays according to the responses from Cybersource in all rejection and error cases.
  5. In the
    Override Payment Error Route Path
     field, enter the error page route path. When no path is entered, the checkout/cart route is used when you leave the default
    Use system value
     box checked.

Configuring WebService

The WebService configuration includes the default
Adobe Commerce Cloud
 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 Cybersource merchant ID.
  3. From the
    Test Mode
     drop-down list, choose
    Yes
     when you are using the
    Business Center
     testing environment, or
    No
     when you are using the production
    Business Center
    .
  4. This field is optional. In the
    Developer ID
     field, enter the developer ID. It must not be longer than eight characters. You can request Cybersource to assign you a developer ID.
  5. In the
    SOAP Key Detail
     field, enter the key you generated from the SOAP toolkit API. If you have not generated a key, see Creating a SOAP Toolkit Key for instructions.
  6. In the
    REST API Key Detail
     field, enter the REST key you generated from the
    Business Center
    . If you have not generated a REST Shared Secret Key Pair, see Creating a Shared Secret Key Pair 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, ensure that the SOAP WebService options are configured correctly. The SOAP API Key Detail should have the correct value and the Test Mode option should match the correct environment for the Cybersource
    Business Center
     is set to the testing environment.
  7. In the
    REST API Shared Secret Key
     field, enter the Shared Secret key you generated from the
    Business Center
    . If you have not generated a REST Shared Secret Key Pair, see Creating a Shared Secret Key Pair for instructions.

    ADDITIONAL INFORMATION

    Proper configuration of the REST Web Service is required for other services including Flex Microform,
    Decision Manager
    , and the Account Updater. If you experience issues with these modules, ensure that the REST Web Service options are configured properly. The API Key Detail and API Shared Secret Key should have the correct value, and the Test Mode option should match the correct environment for the Cybersource
    Business Center
    .

Configuring Device Fingerprinting

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 by Cybersource. To obtain this value either for test or production, contact your Cybersource representative.

Configuring the Delivery Address Verification Service

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 the suggested address alternatives optional.

Configuring Credit Card Payments

Follow these steps to configure
Adobe Commerce Cloud
 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 Cybersource. Choose
    SOAP Toolkit API
     to have the card information tokenized through Cybersource. The SOAP service separately requests authorizations.
  4. In the Checkout Flow Type drop-down list, choose a desired checkout type.

    ADDITIONAL INFORMATION

    Cybersource
     recommends 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.
  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. Leave blank for the default of 600 seconds.

Configuring Strong Customer Authentication

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 Cloud
 Cybersource 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

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
     field 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 uncheck 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

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

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

The
Adobe Commerce Cloud
 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

To install reCAPTCHA, run the following command for composer installation:
composer require Cybersource/module-recaptcha

Creating reCAPTCHA

Follow these steps to generate Google reCAPTCHA Site Key and Secret Key:
  1. Visit the Google reCAPTCHA website: .
  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 Cloud

  1. Go the
    Adobe Commerce Cloud
     console.
  2. On the Payment Methods page, under the Cybersource 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 Cloud
     cache.

Configuring the
eCheck
 Payment Module

The Cybersource
eCheck
 module allows customers to make purchases using a routing number and an account number. During checkout, an
eCheck
 transaction request is sent to Cybersource. If successful, the transaction is sent to the Automated Clearing House (ACH).
the
Adobe Commerce Cloud
 queries Cybersource periodically to check on the status of each pending
eCheck
 transaction. In response, Cybersource 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 Cybersource response, the
Adobe Commerce Cloud
 determines whether a transaction remains pending, settles, or is rejected.
These are the
eCheck
 payment event types you can configure:
  • 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.

Testing
eCheck
 Payment Settings

You can test the
eCheck
 Payment Event Types using two the
Adobe Commerce Cloud
 settings that simulate possible event types during the processing of the requested report. While the status request goes to Cybersource, the
Adobe Commerce Cloud
 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. From the
    Title
     field, enter the text that is displayed to customers as the name of this payment method.
  4. In the
    Accept Event Type
     box, choose which payment statuses to accept, which signify the receipt of funds and the order status moved to processing.
  5. In the
    Pending Event Type
     box, choose which payment statuses to consider for pending.
  6. In the
    Reject Event Type
     box, choose which payment statuses to reject which were initially accepted during checkout, but rejected after processed by ACH.
  7. In the
    Payment From Applicable Countries
     field, leave the
    Use system value
     box checked to accept the
    eCheck
     payment method, or uncheck the
    Use system value
     box to specify countries in the next field.
  8. In the
    Payment From Specific Countries
     box, choose the countries from which to accept the
    eCheck
     payment method.
  9. From the
    Enabled Drivers License Number
     drop-down list, choose
    Yes
     or
    No
     to require customers to enter a drivers license number. For
    TeleCheck
    , contact a representative to see if this field is required.
  10. From the
    Enabled Check Number
     drop-down list, choose
    Yes
     or
    No
     to require the customer to enter the check number. These processors have specified whether it is required or optional:

    ADDITIONAL INFORMATION

    • Chase Paymentech Solutions
      : Optional
    • Cybersource ACH Service
      : Not used
    • RBS WorldPay Atlanta
      : Optional on debits, and required on credits
    • TeleCheck
      : Strongly recommended on debit requests, and optional on credits
  11. From the
    Agreement Required
     drop-down list, choose
    Yes
     or
    No
     to indicate whether you want to require an agreement at the checkout page.
  12. From the
    SEC code
     drop-down list, choose a code that specifies the authorization method for the transaction.
  13. In the
    Sort Order
     field, enter the number of entries to be sorted on a page.
  14. Click
    Save Config
    .

Configuring Fraud Management

You must configure the
Adobe Commerce Cloud
 to work with Fraud Management to use all of the features.
Follow these steps to configure Fraud Management in the
Adobe Commerce Cloud
:
  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
    .

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
Adobe Commerce Cloud
 Cron settings to configure them to trigger an
Adobe Commerce Cloud
 task. The task looks for
Decision Manager
 changes in the Cybersource
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
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 Cybersource 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 Cybersource 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
  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

To use Apple Pay, you must meet these prerequisites:
  • Have a valid Apple Developer Account.
To configure Apple Pay with the Cybersource
Adobe Commerce Cloud
 module, you must complete these tasks:
  1. Register an Apple Pay merchant ID. For instructions on how to do it, see Create Your Apple Pay Merchant ID.
  2. Create a Payment Processing certificate in the
    Business Center
    . For instructions on how to do this, see Generating and Loading a New Certificate Signing Request.
  3. Validate your store domain in Apple Pay. For instructions on how to do it, see Register a Merchant Domain.
  4. Create a Merchant Identity certificate. For instructions on how to do it, see Create a Merchant Identity Certificate.

Configuring the Apple Pay Extension

Follow these steps to configure the Apple Pay extension:
  1. Go the
    Adobe Commerce Cloud
     console, and open the Payment Methods page.
  2. Under the Cybersource settings, click
    Apple Pay
     to expand the section.
  3. From the
    Enable
     drop-down list, choose
    Yes
     or
    No
     to activate or deactivate Apple Pay.
  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 the order that was successfully paid with Cybersource.
  7. In the
    Apple Merchant ID
     box, enter the Apple Pay Merchant ID you previously created.
  8. In the
    Apple Display Name
     box, enter the business name that will appear 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

You must configure Apple Pay on your storefront, which is what 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 will choose
    Adobe Commerce Cloud
     Apple Pay
    .
  2. An Apple Pay window appears, requesting fingerprint (Touch ID) authentication. Or, you can choose a saved card.
  3. After authentication is complete, an order success page appears. Verify the transaction details in Cybersource
    Business Center
    .

Configuring Google Pay

To use Google Pay on the
Adobe Commerce Cloud
, your site must be running through HTTPS. Follow these steps to configure Google Pay in the
Adobe Commerce Cloud
:
  1. Click
    Google Pay
     to expand the section.
  2. From the
    Enable
     drop-down list, choose
    Yes
     or
    No
     to activate or 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 the payer will see for the charge on a bank or credit card statement. For example, “COMPANY, INC.”
  7. In the Payment From Applicable Countries field, leave the
    Use system value
     box checked if you want to accept payment from the default countries choose, or uncheck the
    Use system value
     box to specify countries in the next field.
  8. In the
    Payment From Specific Countries
     box, choose the countries from where you want to accept Google Pay.
  9. In the
    Credit Card Types
     field box, choose which card types to enabled.
  10. In the
    Google Pay button on Product Pag
    e field, choose
    Yes
     to show the Google Pay button on the product page.
  11. In the
    Google Pay button in mini cart
     field, choose
    Yes
     to show the mini cart widget.
  12. In the
    Sort Order
     box, enter a number to change the default module sort order.
  13. Click
    Save Config
    .

Configuring Alternate Payments

the
Adobe Commerce Cloud
 has four types of Alternate Payments modules:
Click
Alt Payments
 to expand the section.

Configuring 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 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 Cybersource.
  8. In the
    Payment From Applicable Countries
     field, leave the
    Use system value
     box checked to accept payment the from default countries selected, or uncheck the
    Use system value
     box to specify countries in the next field.
  9. In the
    Payment From Specific Countries
     box, choose the countries from which you will accept Klarna.

Configuring 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. In the
    Payment From Applicable Countries
     field, leave the
    Use system value
     box checked to accept PayPal, or uncheck the
    Use system value
     box to specify countries in the next field.
  9. In the
    Payment From Specific Countries
     box, choose which countries you will accept PayPal.
  10. From the
    Enable PayPal Credit
     drop-down list, choose
    Yes
     to enable financing through PayPal Credit.
  11. In the
    PayPal Credit Title
     box, enter the text customers will see as the title of PayPal Credit payment option.
  12. From the
    Enable PayPal Billing Agreements
     drop-down list, choose
    Yes
     to allow registered customers to create a billing agreement for faster purchases.
  13. In the
    Sort Order
     box, enter a numeric value to place this payment method amongst all the other
    Adobe Commerce Cloud
     payment methods.

Configuring 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

Follow these steps to configure an iDEAL payment:
  1. Click
    iDEAL
     to expand the section.
  2. In the
    Enable
     drop-down list, choose
    Yes
     or
    No
     to activate or 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 Cybersource
    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. In the
    Payment From Applicable Countries
     field, leave the
    Use system value
     box checked to accept payments from the default countries select, or uncheck the
    Use system value
     box to specify countries in the next field.
  10. To specify which countries you will to accept iDEAL from, choose the countries in the
    Payment From Specific Countries
     box.

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 Cybersource 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. In the
    Payment From Applicable Countries
     field, leave the
    Use system value
     box checked to accept payments from the default countries selected, or uncheck the
    Use system value
     box to specify countries in the next field.
  10. To specify the countries from which to accept Bancontact, choose the countries in the
    Payment From Specific Countries
     box.

Configuring 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
     or
    No
     to activate or 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 Cybersource 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. In the
    Payment From Applicable Countries
     field, leave the
    Use system value
     box checked to accept payments from the default countries selected, or uncheck the
    Use system value
     box to specify countries in the next field.
  12. To specify which countries from which to accept WeChat Pay, choose the countries in the
    Payment From Specific Countries
     box.
  13. In the
    Success/Failure Message Delay
     field, enter a delay in seconds between the transaction check and redirection to the result page.
  14. In the
    Check Status query Simulated Response
     field, choose a simulated Status Check response code for testing.
  15. Click
    Save Config
    .

Configuring Taxes

Cybersource offers a service that calculates taxes to be charged on orders. You must configure your settings in order to receive accurate results from Cybersource.
Contact your Cybersource 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.
To use the Tax Calculation Service, you must have the Product Tax Class codes and Cybersource Tax Services settings configured. For more information, see Configuring Product Tax Classes and Configuring Cybersource Tax Services Settings.

Configuring Product Tax Classes

Each product in the
Adobe Commerce Cloud
 has a setting for Tax Class. This setting defines the product and how it should be taxed. Contact your Cybersource 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 Cloud
:
  1. Go the
    Adobe Commerce Cloud
     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 Cybersource representative provides.
  4. In the
    Tax Class Code
     field, enter the code Cybersource 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 Cybersource Tax Services Settings

Follow these steps to configure Cybersource Tax Services in the
Adobe Commerce Cloud
:
  1. Go to the
    Adobe Commerce Cloud
     admin console.
  2. On the left panel, click
    Stores
    , and then click
    Configuration
    .
  3. On the Configuration page, go to
    Sales
     >
    Tax
     >
    Cybersource Tax Services
    .
  4. From the
    Tax Calculation
     drop-down list, choose
    Yes
     to activate the Cybersource Tax Services per your business requirements.
  5. In the
    Nexus regions
     box, select any relevant regions your business has a physical presence in the U.S. or Canada.
  6. In the
    Customer countries to calculate Tax for
     box, choose the countries for which you will calculate tax.
  7. In the
    Customer Tax classes to exclude from Tax calculation
     box, choose the customer tax classes to exclude from tax calculation.
  8. In the
    Ship From
     fields, enter the city, postcode, country, and region from which the orders are shipped.
  9. In the
    Acceptance
     fields, enter the city, postcode, country, and region in which you will accept or approve customers' orders.
  10. In the
    Origin
     fields, enter the city, postcode, country, and region of the point of origin from which the order is picked up.
  11. In the
    Merchant VAT
     fields, enter the merchant VAT seller registration number.
  12. Click
    Save Config
    .

Calculating Taxes for Shipping 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 offered need to have taxes added to them. Select
    Including Tax
     when shipping rates offered have taxes included, and no taxes will be applied through the Cybersource tax service.
  5. Click
    Save Config
    .

Configuring Transactional 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 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 be sent to the customers:
  1. Go to the
    Adobe Commerce Cloud
     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

Follow these steps to configure Cron settings for
Decision Manager
:
  1. In the
    Adobe Commerce Cloud
     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).

Configuring Tokens

When a customer is logged in and is at checkout, their card data can be store in a secured Cybersource 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 Cybersource 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 Cybersource.

Managing the
Adobe Commerce Cloud
 Tokens

Customers who are logged into can delete their tokens at any time. To do so, they must visit the My Account section of the
Adobe Commerce Cloud
 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

The plugin supports the multi-shipping feature only for the
Adobe Commerce Cloud
 registered users when they place orders with stored credit cards.

Node Implementation

The plugin does not support multiple-node implementation.

Support

If you require support with this software, contact GlobalPartnerSolutionsCS@visa.com and provide this information:
  1. Summary of the issue
  2. Steps to reproduce the issue
  3. Magento platform version
  4. Cybersource plug-in version
  5. Cybersource merchant ID
  6. Configuration screenshots
  7. All the themes/additional extensions installed
  8. Log files:
    system.log
    ,
    debug.log
    ,
    cybs.log
     and
    exception.log
    . To generate logs, navigate to this path in the root directory of Magneto:
    Magento Folder Name\var\log