Adobe Commerce and Magento Payment Planning for Peptide Merchants

List the installation and every website in scope

Start with your product edition and version, checkout extensions, and store configuration. A setting that is available at one scope may be configured differently across websites or stores. Review the actual buyer storefronts and record the payment method configured for each.

Check capture behavior against fulfillment

Determine whether an order authorizes funds for later capture or is captured during checkout in the proposed payment method. Review how order, invoice, and credit memo workflows interact with the gateway. Confirm who will handle exceptions if a payment and order record disagree.

Example: two websites share one Adobe Commerce installation

Verify whether each website inherits its payment settings or has an override. Record the intended gateway and account for each. Run a test on both websites, even if only one was updated, and compare the gateway references before enabling production payments. This helps catch unexpected inheritance when checkout is configured centrally.

Before enabling a payment extension

• Confirm version support and approved provider compatibility with the extension publisher.
• Test the right payment method on each website and currency in scope.
• Compare an authorized order, captured invoice, and refund against gateway records.
• Keep rollback steps and a copy of the prior configuration before release.