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 Additional Backend Settings

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 Additional Backend Settings

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 Additional Backend Settings

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.
Configuring Additional Backend Settings

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 Additional Backend Settings

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 Additional Backend Settings

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 Additional Backend Settings

Configuring Alternate Payments

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

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 Additional Backend Settings

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 Additional Backend Settings

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 Additional Backend Settings

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.
Configuring Additional Backend Settings

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.
Configuring Additional Backend Settings

Node Implementation

The plugin does not support multiple-node implementation.
Configuring Additional Backend Settings