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, java.io.PrintWriter@2c58e4ff 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.