Adobe Commerce Cloud

Last updated: October 30, 2026

Overview

The Adobe Commerce Cloud Shop plugin optimizes payment processing and analytics through seamless integration.

Our Adobe Commerce payment extension helps you launch or expand your business rapidly. If you are launching your business first time on Adobe Commerce, we can help you quickly roll out through our configuration capabilities. If you are already on Adobe Commerce and thinking of expansion, we offer a wide variety of secure local and global payment options.

Our Adobe Commerce extension, built on the Payments Orchestration Platform, delivers a competitive advantage over payment gateways, including payment processing optimization and advanced analytics, through a single integration. We help you manage payments across multiple P2Ps, acquirers, and banks across all channels—online, mobile, or recurring—using a strategic, streamlined approach.

Looking for the step-by-step journey (prepare, install, configure, test, go live)? See the Adobe Commerce Cloud overview on the Shop Plugins page. This page contains the detailed reference.

↑ Back to top


Compatibility

Our plugin supports Adobe Commerce version 2.4.7-p1-EE  or later.

Important

It is strongly recommended that the plugin installation is first completed and validated in a non‑production environment (for example, a QA or staging environment) before proceeding with installation in production.

This plugin is designed to work with the out‑of‑the‑box (OOTB) native Adobe Commerce checkout.

If your store uses a custom checkout implementation or a heavily modified checkout flow, additional customization by the merchant or their implementation partner (agency/integrator) may be required to ensure compatibility with the plugin.

↑ Back to top


Configure

You need the Entity ID, API key and webhook decryption key from the Onboard section.

Open the plugin settings

In the admin panel, access the payment settings:

  1. Access the configuration menu: go to Stores → Settings → Configuration → Sales → Payment Methods → ACI Payments → General Setting.

Field reference

General Setting

Field Name in Adobe Commerce cloud Configuration Mandatory/Optional/ConditionalPossible ValuesComments
EnabledMandatoryEnabled or DisabledConfigure this to enable or disable the payment plugin
EnvironmentMandatoryTest or Live

Test - For test environment Configuration

Live - for Live environment Configuration

Test Entity IDMandatoryEntity ID of your Channel or Merchant from Open Payment PlatformRefer to onboarding configuration.
Test API KeyMandatoryAccess token of your Channel or Merchant from Open Payment PlatformRefer to onboarding configuration.
Test ModeMandatoryINTERNAL or EXTERNAL 

Connector test mode 

  • EXTERNAL causes test transactions to be forwarded to the processor's test system for 'end-to-end' testing
  • INTERNAL causes transactions to be sent to our simulators.
Webhook URLMandatory
The value will be auto-populated to configure the webhook URL in Open Payment Platform
JavascriptMandatory

use this option to customize the payment widget,

Note- while using Google Pay, providing gatewayMerchantId is mandatory. 

window.wpwlOptions={
googlePay: {
        gatewayMerchantId: "ValueOfYourEntityID"
    },
};

Additional information - Advanced Options

Google Pay

CSSOptional
CSS helps to customize default checkout payment page experience, possible examples and options on Google Pay
Enable Debug LoggingOptionalYes or NoDebug logs for investigation of the transactions
Webhook Decryption KeyMandatory
Fill in the Secret for the encryption value generated during webhook endpoint creation in the Open Payment Platform.

Sample Configuration

Figure 1: Sample Configuration

Adobe Commerce Cloud: Sample Configuration

Figure 2: Live Configuration

Adobe Commerce Cloud: Live Configuration

↑ Back to top


Onboard

After installing the plugin, follow the provided instructions to configure the extension in Adobe Commerce Cloud and the Open Payment Platform using the given configuration details.

You will need to set up merchant accounts and brands in Open Payment Platform to ensure they work with the checkout process using the plugins.

Credentials from the Open Payment Platform

To start processing with plugins, plugin configuration in the Open Payment Platform needs to be enabled for your PSP or merchant. Without this configuration, you won’t be able to send transaction requests from the plugin platform to the payment platform for processing.

Please contact your account manager or project team to enable plugin usage from the Open Payment Platform.

You will need the following information from the Open Payment Platform to configure and onboard with the payment plugin:

Field Name in Adobe Commerce cloud Configuration Open Payment Platform Field NameMandatory/OptionalComments
Entity IDEntityIdMandatory

From Merchant or Channel level, according to Open Payment Platform configuration setting of Merchant accounts

In Open Payment Platform - Administration→ Account data

API KeyAccess TokenMandatory

From Open Payment Platform at Merchant or Channel level, according to Open Payment Platform configuration setting of Merchant accounts

In Open Payment Platform - Administration→ Account data → Merchant Info/Channel Info

Figure 3: Credentials from the Open Payment Platform

Adobe Commerce Cloud: Credentials from the Open Payment Platform

Webhook configuration

The webhooks are HTTP-based callbacks that notify your plugin platform of all the events you subscribed for on an entity. Instead of constantly polling for updates, a webhook is set up once and only sends data when a specific event occurs. The events can be about tokens, payments, payment schedules, risks, or any transaction state updates related to payments or transactions connected to a payment, it is necessary to configure webhooks for seamless communication and transaction updates. 

Merchant/PSP to configure webhooks and generate the webhook decryption key in the Open Payment Platform for
webhook handling.

Steps:

  1. Login to merchant dashboard (Open Payment Platform)
  2. Select your division (here OPP_Division)
  3. Go to Administration - Webhooks
  4. Click on “Add New Webhook” button

Figure 4: Webhook configuration

Adobe Commerce Cloud: Webhook configuration

Follow further steps below to configure Webhook

  1. URL: https://<domain-name>/acipayment/process/notification
  2. Notification types: Select the notification types as required by the merchant
  3. Fields to include: Select the option as required by the merchant
  4. Secret for encryption: (Copy the value and add in the “Webhook Decryption Key” field under general settings in Adobe Commerce Cloud check Sample Configuration)
  5. Wrapper for encrypted notification: JSON
  6. Emails: Enter email IDs to receive notification alert
  7. Save

Figure 5: Webhook configuration (continued)

Adobe Commerce Cloud: Webhook configuration (continued)

↑ Back to top


Features

Payment types

Payment TypeSupportedComments 
Authorization (PA)✔
Debit (DB)✔
Credit (CD)–

Capture (CP)

Full✔
Partial

✔


Multiple✔

Refund (RF)

Full✔
Partial✔
Multiple✔

Reversal (RV)

Full✔
Partial–
Multiple–
Receipt (RC)–
Rebill (RB)–

Note: Some functionalities available in the plugin might not be supported by the connector in use. Please refer to the respective connector integration sheet for details.

Features

We offer standard plugin integration with Adobe Commerce Cloud through our Payment Orchestration Platform Integration option. This provides you with full access to all features and utilizes COPYandPAY to present payment options to your shoppers.

FeatureSupportedComments
Supported Brands✔

ALL

Note - VISA, Mastercard, Amex, PayPal, Klarna, Apple, and Google Pay are the brands certified internally, Plugin integration can adopt other card and APM brands, for any additional field support specific to APM or card please contact your account manager. 

Supported Payment Methods✔

Credit Card, Virtual Account

Countries✔ALL (if Adobe Commerce Cloud is in countries)
Authorization Currencies✔ALL
Late Notification✔

Payment Facilitator

–
Recurring/Subscription ✔
Reference ID✔
Timeout Autoreversal✔
TLS 1.2✔
Internal Tokenization
✔PSP Internal tokenization supported
Omni Tokenization–
External Tokenization–
Zero Authorization/ Account Verification–
Digital Wallet✔Apple Pay and Google Pay
3D Secure ✔Using our MPI
Airline Data–
Settlement Reporting–

Settlement reporting as per specific brand connector in use. 

COPYandPAY OneClick Checkout (Save Card)✔
COPYandPAY widget or full-page redirect✔
Customization through standard COPYandPAY JS✔
Customization through standard COPYandPAY CSS✔
PayByLink–
Manage Saved Card in User Profile✔
Download Audit Log✔
Guest Checkout ✔
Transaction identifier ✔merchantTransactionID
Fast Checkout–
Fraud with Payment✔
Standalone Fraud–
PCI DSS 4✔

↑ Back to top


Supported fields

As part of the integration with the plugin platform, we have included the following fields. This information is provided for your reference only; you do not need to handle the transmission or integration of these fields, as the plugin extension manages this automatically.

Please note: The following fields are supported by default. If you require support for any specific fields related to APM for Card brand, please contact your account manager.

  • entityId
  • testMode
  • locale
  • amount
  • currency
  • merchantTransactionId
  • paymentType
  • customer.givenName
  • customer.surname
  • customer.phone
  • customer.email
  • customer.ip
  • customer.merchantCustomerId
  • registrations[N].id
  • billing.city
  • billing.country
  • billing.postcode
  • billing.state
  • billing.street1
  • billing.street2
  • shipping.city
  • shipping.country
  • shipping.postcode
  • shipping.state
  • shipping.street1
  • shipping.street2
  • cart.items[N].name
  • cart.items[N].quantity
  • cart.items[N].sku
  • cart.items[N].price
  • cart.items[N].currency
  • cart.items[N].description
  • cart.items[N].totalAmount

↑ Back to top


Resources

↑ Back to top


See also