Question 1

What is the difference between Magento 2, Adobe Commerce, and Adobe Commerce Cloud for payment processing?

Accepted Answer

Magento 2 is the open-source version of the platform (free to download, self-hosted). Adobe Commerce is the paid enterprise edition with additional B2B features, enhanced page builder, and Adobe integrations (self-hosted or cloud-hosted). Adobe Commerce Cloud is Adobe's managed PaaS hosting solution for Adobe Commerce. From a payment integration perspective, GetPayment supports all three: our Magento 2 extension works identically across all versions. Adobe Commerce Cloud introduces some additional deployment considerations (we support cloud-compatible extension deployment via composer) but the functionality is identical. Multi-source inventory, B2B module, and page builder features are all compatible with GetPayment's payment extension.

Question 2

How does GetPayment handle Magento's multi-store and multi-website architecture?

Accepted Answer

Magento's multi-store architecture (multiple websites, stores, and store views from a single installation) is fully supported. Configuration options: (1) Single merchant account for all stores — simplest configuration, consolidated reporting, (2) Separate merchant accounts per website — required if stores have different legal entities or significantly different risk profiles, (3) Store-specific payment method configurations — different payment methods, fraud rules, and currency settings per store view. This architecture is common for B2B + B2C hybrid operations, multi-brand retailers, and international Magento deployments. Our enterprise team has implemented GetPayment across complex multi-store setups including 15+ store views for international retailers.

Question 3

What Magento payment extension features are available for B2B wholesale operations?

Accepted Answer

GetPayment's Magento extension has specific B2B payment capabilities aligned with Magento's B2B module: (1) Company account payment — allow B2B customers to pay on account with credit limits, (2) Purchase order integration — payment collected against issued POs, (3) ACH/bank transfer payment method for wholesale orders (avoiding 2-3% card fees on $10k+ orders), (4) Net payment terms (Net 30/60/90) with automated invoice collection via ACH, (5) Payment on behalf of company — allow buyers to pay for other users within their company account, (6) Tiered payment method availability — different payment options based on customer group (wholesale vs. retail vs. VIP). These features integrate with Magento's native B2B module, not a third-party bolt-on.

Question 4

How do you handle Magento payment security — PCI DSS, vault tokens, and 3DS2?

Accepted Answer

GetPayment's Magento extension is PCI DSS Level 1 compliant. Card data never touches your Magento server — payment forms use our tokenization JavaScript that sends card data directly to GetPayment's PCI-compliant vault. Your Magento server receives and stores only a payment token. Vault functionality: customers can save payment methods to their Magento account using standard Magento Vault (integrated with the Braintree Vault API). Saved payment tokens are encrypted and stored in GetPayment's vault, not in your Magento database. 3DS2 integration: frictionless authentication for standard transactions, challenge flow for high-risk transactions, full liability shift for authenticated transactions. 3DS2 is configurable per payment method and can be applied selectively based on transaction value or customer segment.

Question 5

What is the deployment process for Adobe Commerce Cloud installations?

Accepted Answer

Adobe Commerce Cloud (Magento Commerce Cloud) uses a git-based deployment pipeline. GetPayment extension deployment: (1) Add extension to your cloud project via Composer (composer require getpayment/magento2), (2) Add configuration variables to your .magento.env.yaml for environment-specific API credentials, (3) Deploy to staging environment via git push, (4) Run integration tests in staging, (5) Deploy to production via git merge to master. Our cloud-compatible extension follows all Magento Cloud deployment best practices: no direct file writes outside of generated/ and pub/, no runtime database schema changes, and full support for the Ece-tools deployment pipeline. We provide a cloud deployment guide and our integration engineering team can assist with first deployments.

Enterprise Payment Processing for Magento 2 and Adobe Commerce — Multi-Store, B2B, and Cloud Ready

Enterprise Magento Requirements Checklist

Magento Enterprise Payment Challenges We Solve

Complete Magento Extension Features

Magento & Adobe Commerce Payments FAQ

What is the difference between Magento 2, Adobe Commerce, and Adobe Commerce Cloud for payment processing?

How does GetPayment handle Magento's multi-store and multi-website architecture?

What Magento payment extension features are available for B2B wholesale operations?

How do you handle Magento payment security — PCI DSS, vault tokens, and 3DS2?

What is the deployment process for Adobe Commerce Cloud installations?

Enterprise Payment Processing for Adobe Commerce