Adobe Commerce payments and Magento setup in 2026
Configuring Adobe Commerce payments? Separate Payment Services from other gateways, check Magento compatibility and verify capture, refunds and orders.
- Published
- Last updated
Adobe Commerce payments can run through Adobe Payment Services or a separate gateway integration. Choose the route for your platform version and merchant country, then test capture and refunds against the order records before accepting payments.
For an Australian store, Payment Services supports Advanced onboarding on eligible Adobe Commerce and Magento Open Source installations. The setup below follows that route, with Braintree as a separately configured alternative.
Adobe Commerce payments and the available routes
Adobe Payment Services is Adobe’s payment integration for both Adobe Commerce and Magento Open Source. Installing a different gateway extension gives you that provider’s configuration and transaction workflow.
Adobe’s compatibility guide lists Australia among the countries eligible for Advanced Payment Services. Standard onboarding provides a smaller Express Checkout set. Hosted card fields and Apple Pay require Advanced onboarding.
Payment Services can also supply PayPal buttons alongside an existing card provider. Disable its card fields and debit or credit card button when the existing provider handles cards. Each payment still belongs to the integration that processed it.
Braintree is a separate route in Adobe’s payment settings. Adobe documents its integration for cloud infrastructure and on-premises installations, including Magento Open Source. Use its own merchant account and credentials, rather than the Payment Services merchant ID.
If you’re still selecting a processor, the ecommerce payments guide explains the roles behind a payment and the merchant selection criteria.
Prerequisites and payment configuration
Payment Services needs a compatible platform, its payment module and an approved PayPal account for live processing. The Commerce Services Connector connects the installed store to Adobe’s services.
PayPal’s Adobe Commerce upgrade guide places the extension installation boundary at versions 2.4.4 to 2.4.6. The module is pre-installed from 2.4.7. That installation boundary doesn’t establish whether an old platform release remains supported.
Record your edition and full platform version before choosing the module release. Adobe’s compatibility policy covers supported platform versions. For a separate extension, use that extension’s compatibility requirements instead.
Match the merchant’s country and the store’s transaction currency to the account’s supported payment methods. An Australian business with a foreign-currency store still needs that currency supported by its chosen provider.
Follow this sequence in an isolated test installation:
- If installation is required, obtain
magento/payment-servicesthrough Adobe’s installation instructions. Magento Open Source uses the on-premises path. - Connect the instance through System > Services > Commerce Services Connector. Use a testing data space for the test installation.
- Create a PayPal Developer account, a Business sandbox account and a separate shopper sandbox account. Complete Sales > Payment Services > Sandbox onboarding with the Business sandbox credentials.
- In Stores > Settings > Configuration > Sales > Payment Methods, enable Payment Services and set Method to Sandbox. Set the merchant country and each payment method’s capture action.
- Save the configuration and clear the cache. Complete the sandbox cases below before configuring live payments.
Adobe’s sandbox setup uses generated sandbox credentials. Your real PayPal business login belongs to live onboarding.
For production, request Adobe payments entitlement for Advanced onboarding, then complete Live onboarding using the production account. After approval, select Production and clear the cache. Adobe’s production procedure keeps those steps separate from sandbox onboarding.
For the Braintree route, follow Adobe’s Braintree configuration. Select Sandbox and enter the sandbox merchant ID with its public and private keys. Validate Credentials before enabling card payments. Select the merchant account ID for the required currency. Production has separate credential fields.
Payment methods at checkout
Payment Services supports card fields and PayPal buttons, with Apple Pay and Google Pay among its wallet options. The merchant’s onboarding route and the customer’s eligibility determine which methods appear.
For an Australian Advanced setup, configure the card and wallet methods you intend to accept. PayPal Pay Later remains subject to the applicable offer and customer eligibility. Venmo is a US option, so don’t promise it to Australian shoppers.
Adobe’s payment options guide distinguishes the product page, mini cart, cart and checkout. A button enabled on one surface doesn’t prove it works on another.
Use the Admin configuration to enable each intended placement at the correct website or store-view scope. Then open those surfaces on the supported customer devices. For Apple Pay, confirm the domain verification file responds successfully and the domain is registered for the environment being tested.
For a custom or headless checkout, include the payment integration in that checkout implementation. An installed backend extension alone doesn’t establish that customers can pay through a custom storefront.
Authorisation, capture and order records
Authorisation reserves the amount, while capture collects the authorised funds. Payment Services calls the actions Authorize and Authorize and Capture.
With Authorize, create the invoice with Capture Online when you’re ready to capture. With Authorize and Capture, checkout performs the capture and invoice workflow. Payment Services also supports partial capture through invoicing parts of an order.
Adobe’s invoice guidance explains the records behind these actions. An invoice and a shipment are separate records, even when your workflow creates both together.
Records to check before answering a payment query
| What staff see | What it means | What to inspect next |
|---|---|---|
| Authorised payment | Funds are reserved | Authorisation transaction and whether an invoice has captured it |
| Pending Payment | The gateway return information hasn’t arrived | Provider transaction and callback processing before asking the customer to retry |
| Capture requested or pending | Collection isn’t yet confirmed | Capture transaction and any Payment Review status |
| Capture failed | The capture failed | Provider response and order history before another collection attempt |
| Complete order | The standard status means paid and shipped | Shipment and capture records if the customer reports a mismatch |
Adobe’s order status documentation separates the underlying order state from its visible status label. A custom label doesn’t change which payment operations are possible.
For Payment Services on cloud infrastructure or on-premises, the Order Payment Status report separates capture requested, confirmed and failed. Refresh stale report data and compare it with the provider transaction. These financial reports require live onboarding and activation, even when selecting sandbox data. The same report views aren’t shown in Adobe Commerce as a Cloud Service.
If an order remains under payment review, staff must resolve its payment record before treating it as paid. Avoid collecting again merely because the customer can’t see a confirmation.
Refunds and reconciliation
Payment Services records full and partial refunds through credit memos for invoiced orders. PayPal and card orders can have multiple partial refunds within the remaining refundable amount.
Follow Adobe’s credit memo procedure for an online refund:
- Open Sales > Orders, select the order and open its captured invoice.
- Choose Credit Memo. Set the quantities to refund and review shipping or adjustments.
- Update Totals, then choose Refund to request the online refund. Send the credit memo email if required.
- Match the credit memo amount to the provider’s refund transaction and its status.
Refund Offline records a refund that you arrange separately. It doesn’t send the online refund request to the payment provider.
As an illustrative reconciliation, a $120 captured payment with an earlier $30 refund has $90 remaining before further adjustments. A new $40 refund leaves $50. Compare cumulative refunds with the original capture, including the applicable shipping and tax amounts.
Adobe’s Payment Services refund rules reject refunds above the remaining amount. A saved credit memo and a completed return of funds are different points in the process. Tell the customer the refund amount and recorded status, without promising a bank arrival time the provider hasn’t confirmed.
Verify the customer and support journey
Test a successful payment and its refund in the sandbox, then test the failure response through the payment integration. Use Adobe’s test and validate procedure for sandbox checkout with generated test card details or a sandbox PayPal shopper account.
Run the cases against the same checkout surfaces your customers will use:
| Sandbox case | Expected result to verify |
|---|---|
| Successful card or PayPal payment | One order with the expected amount and payment transaction |
| Authorize followed by capture | An authorisation first, then an invoice and capture for the intended amount |
| Full or partial refund | A credit memo and matching provider refund record within the captured balance |
| Customer cancels a wallet flow | The customer returns without a paid confirmation or an unintended capture |
| Provider rejects the payment or capture | The checkout reports the failure, and staff can identify the failed transaction without creating a duplicate charge |
For a developer-controlled PayPal sandbox request, PayPal’s negative-testing headers simulate supported Orders and Payments API errors. The documented header is PayPal-Mock-Response, with the selected error in mock_application_codes. Apply it only through a sandbox integration test that exercises the store’s error handling. A standalone API error response doesn’t verify the storefront’s recovery.
Check the customer’s account and confirmation email against each resulting order. Ask support to answer whether payment was captured and whether a refund completed, using the linked transaction records. A shopping assistant answering order questions must use those same recorded outcomes.
Keep failed payments out of paid-order messages and keep pending refunds distinct from completed refunds. Retain the order number and provider transaction identifiers with each test result so staff can investigate the same case.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.