Configure the Adobe Commerce Magento Extension
Customer payments can be managed through Adobe Commerce or the . This section describes the settings you must configure in the as well as some general use cases that are typical in the day-to-day management of your Adobe Commerce store. Contact for information about product availability and enablement.
You must complete all of the configuration tasks to use the features offered in the Adobe Commerce integration.
Configure Security Credentials
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 module to function properly.
If you do not have a account, go to the Registration website to create an account.
To activate your merchant account, follow the instructions that are emailed to you. Then log in to the to complete the registration process. Be sure to store your merchant key ID for later use.
Create a SOAP P12 Certificate
The Adobe Commerce integration uses the SOAP Toolkit API to access several services. Generate a SOAP P12 certificate from your account. For information on how to create a SOAP P12 certificate, see Creating a SOAP p12 Certificate.
Create 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 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 Creating a Shared Secret Key Pair. Be sure to store your key ID and shared secret key for later use.
Settings Configuration
Some services supported on Adobe Commerce require additional backend setup on your account. Contact your 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
- Apple Pay: enabled in the
Administration
To access the configuration settings in the administration section of your Adobe Commerce console, go to Stores. Under Settings, click Configuration. On the Configuration page, click Sales to expand the menu, then click Payment Methods, then choose OTHER PAYMENT METHODS > Cybersource. Complete all of the required fields in the sections and subsections of the settings to configure the payment module and other payment methods. Expand each section to complete the fields.
General
From the setting, click the arrow to expand the General section.
Debug Mode — Choose Yes to troubleshoot using the Adobe Commerce logs (cybs.log). Diagnostic information is stored in log files on the Adobe Commerce web server.
Sort Order — Change the default module sort order.
Show Exact Rejection or Error Message to Users
- Choose No to display general error messages according to Adobe Commerce Cloud in all rejection and error cases.
- Choose Yes to display a general error message according to the responses from in all rejection and error cases.
Override Payment Error Route Path — 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.
WebService Configuration
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. Click WebService Configuration to expand the section.
Merchant ID — Enter the merchant ID assigned to you by .
Test Mode
- Choose Yes to use the testing environment.
- Choose No to use the production .
Optionally, in the Developer ID field, you can enter the developer ID. The ID cannot exceed eight characters. You can also request that assign you a developer ID.
Simple Order P12 Key File — Upload the SOAP p12 certificate and then enter the Key Password. If you did not generate a key, see Creating a SOAP p12 Certificate for instructions.
REST API Key Detail — Enter the REST key you generated from the . If you do not have a REST Shared Secret Key Pair, see Creating a Shared Secret Key Pair for instructions.
REST API Shared Secret Key — Enter the Shared Secret key you generated from the . If you do not have a REST Shared Secret Key Pair, see Creating a Shared Secret Key Pair for instructions.
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. Click Device Fingerprint to expand the section.
Active — Choose Yes to activate it or No to deactivate it if you are not using Decision Manager.
Org ID — Enter the value provided to you. To obtain this value either for test or production, contact your representative.
Delivery Address Verification Service
The Delivery Address Verification Service acts as an additional layer of address verification and normalization on the shipping page. Click Delivery Address Verification Service to expand the section.
Address verification — Choose Yes to enable this service or No to disable this service.
Address Force Normalization — Choose Yes to require the use of suggested address alternatives or No to make suggested address alternatives optional.
Payment Methods
The General Settings section also contains the configuration fields for each payment method the module supports. See these reference pages for the configuration settings specific to each payment method:
- Credit Card Payments — Configure credit card payment settings, Strong Customer Authentication, Payer Authentication, Save Card for Later, and Google reCAPTCHA.
- eCheck — Configure the eCheck payment module, Payment Event Types, and processor-specific check number requirements.
- Fraud Management — Configure Fraud Management settings, review how orders are marked for Decision Manager review, and configure Decision Manager custom fields.
- Apple Pay — Configure Apple Pay merchant registration prerequisites, extension settings, and the storefront checkout experience.
- Alternative Payments — Configure Klarna, PayPal, Online Bank Transfers, and WeChat Pay.
- Taxes — Configure the Tax Calculation service and product tax class settings.
- Google Pay — Configure Google Pay checkout display and payment action settings.
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 then informed that their order is no longer active. You can configure the email sent to the customer.
Follow these steps to configure the email template:
- Go to the Adobe Commerce console. On the left panel, choose Marketing, then click Email Templates.
- In the table, find the Template column, and click the DM Fail Transaction template row. The Template Information page opens.
- Complete the required information in the template name, subject, and content text boxes.
- Click Save Template.
Cron Settings
Follow these steps to configure Cron settings for Decision Manager:
- Open the Adobe Commerce console. On the left panel, click Stores, then go to Configuration > Advanced > System > Cron (Scheduled Tasks).
- Scroll down and click Cron configuration options for group:dm.
- Complete the required fields.
- Click Save Config.
For further instructions on how to configure Cron settings, see Cron (scheduled tasks).
Tokens
When a customer is logged in and is checking out, their card data can be stored in a secured 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 do not have to enter their card data again.
When a token is used, the customer is still redirected to the Hosted Payment page for payment confirmation. If a customer chooses to checkout as a guest, the token system is not used.
Save 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 .
Manage 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 their Adobe Commerce store and choose the Stored Payment Methods menu item. Customers can use the delete links beside any stored tokens to remove a stored token.
Pay 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 registered Adobe Commerce users when they place orders with stored credit cards.
Node Implementation
The plugin does not support multiple-node implementation.
Thanks for your feedback!
Last published: November 18, 2026