Apple Pay and Google Pay on Authorize.net, without replacing your card module
The Authorize.net card modules stores run on Magento do not offer Apple Pay or Google Pay, and the listings that do are full card modules. Authorize.net Apple Pay & Google Pay adds the two wallets next to the card module you already run – no saved-card migration, no webhook changes.
ExtensionA store that takes cards through Authorize.net has usually run the same card module for years. It holds the customers' saved cards, the checkout has been tuned around it, and it works. Then the question arrives – from a customer, a phone-heavy traffic report or a competitor's checkout: why no Apple Pay, why no Google Pay?
What it is for
On Adobe Commerce and Magento Open Source, the answer has been awkward. The platform has had no Authorize.net integration of its own since 2.4.0, and the wallets it ships come through Braintree and Adobe's PayPal-based Payment Services – both of which mean moving card processing off Authorize.net. The most widely used Authorize.net card module, ParadoxLabs' free CIM extension, has said on its own listing that it will not add the wallets: "After consulting with Authorize.net, we do not have further plans to add Apple Pay or Google Pay support to this extension." And the Marketplace listings that do offer them are full card modules, so adopting one means moving saved cards from one module's storage to another's, re-pointing webhooks and testing every checkout customisation again – to gain two buttons.
Authorize.net Apple Pay & Google Pay takes the other route. It is an extension for Magento Open Source and Adobe Commerce that adds the two wallets and nothing else, next to the card module the store already runs. It migrates no saved cards, reads none of the card module's settings and touches none of its webhooks. A wallet payment is an ordinary Authorize.net transaction in the same account, so reporting, settlement and the fraud filters carry on as before, and the order is captured, refunded or voided from the Magento admin like any other.
Both wallets sit in Magento's own checkout payment step, with Google's and Apple's own buttons. Required fields and checkout agreements are checked before a wallet sheet opens, and the order completes on the store's own success page. The store never sees a card number: Google and Apple encrypt the payment for Authorize.net, and the extension passes it on once and keeps nothing but the card network and the last four digits.
How it can be used
A store on a CIM card module that wants wallets for its mobile shoppers. This is the case the extension was built for. The card module keeps doing what it does – saved cards, admin orders, whatever else it offers – and the checkout's payment step gains Google Pay and Apple Pay beside it. The trade-off: the wallets appear at the payment step, not as express buttons on the product page or in the cart.
A store that wants Google Pay now and Apple Pay later. Google Pay needs an Authorize.net account with Digital Payment Solutions and, for production, a Google Merchant ID. Apple Pay needs more: an Apple Developer account, a Merchant ID, its Merchant Identity certificate and a verified domain. The two methods switch on independently, and the Configuration Check in the admin says, line by line, what is still missing for each.
A store on Hyvä Theme. Hyvä stores that use the native Magento checkout get the same two methods as Luma stores, from the same implementation. Hyvä Checkout, the separate Magewire-based product, is not supported.
A store that sells in one currency. An Authorize.net account settles in one currency. The extension hides the wallets on any order in another, so a €50 order can never become a $50 charge. A store that sells in several currencies through one account will see the wallets only on orders in the account's currency.
How it compares
Measured on 2026-11-17 on the Adobe Commerce Marketplace. Six listings take payments through Authorize.net. All six are full card modules, and two of them carry a wallet – both from Rootways:
- Authorize.Net CIM With Apple Pay (Rootways), USD 249 on Magento Open Source and 349 on Adobe Commerce: Apple Pay and Google Pay inside a full card module.
- Authorize.Net CIM (Rootways), USD 139 / 249: Google Pay only.
- ParadoxLabs, MageDelight, Pronko Consulting and Weblytic: card modules, from free to subscriptions, none of which mentions a wallet.
Off the Marketplace, we found one Apple Pay-only Authorize.net method and build-to-order work from USD 999.
Where this extension is different:
- It is an add-on, not a replacement. Every Marketplace listing with an Authorize.net wallet is a card module. This one leaves the card module, its saved cards and its webhooks where they are – which matters most to the stores whose card module has said wallets are not coming.
- Hyvä Theme is stated and tested. The extension was verified on a Hyvä store with the native Magento checkout. We found no competing Authorize.net wallet listing that mentions Hyvä.
- The Apple Pay housekeeping is done in the store. The domain association file is served by Magento, per store view if needed, and the admin warns from 60 days before the Merchant Identity certificate expires; Apple Pay withdraws itself from the checkout while it is expired. We found no competitor that describes certificate expiry warnings.
- A fuller Configuration Check. Rootways checks the API credentials; this extension checks ten lines – the account at Authorize.net, the currency, each wallet's settings, the certificate and the domain file.
- No licence key to activate per domain.
Where the alternatives are stronger:
- Rootways is the complete answer for a store starting from nothing. It brings card payments, saved cards, eCheck and admin orders with it; this extension needs an Authorize.net card module to sit beside.
- Express buttons. Rootways offers "Instant purchase from the cart and mini cart using Apple Pay". This extension offers the wallets at the checkout payment step only.
- Track record. Rootways has offered Apple Pay since its first version and has reviews that mention it in production. Google Pay in this extension has been verified with a real payment against the Authorize.net sandbox; Apple Pay has not yet been verified with a live Apple Pay payment.
- Hyvä Checkout. ParadoxLabs supports Hyvä Checkout for cards; this extension does not.
What it does not try to be
It is not a card module and keeps no saved cards. It works with Authorize.net only, has no express buttons and no GraphQL surface for headless storefronts, and it shows shoppers Magento's general decline message rather than the exact reason, which stays in the store's log. The rest of the absences are in the FAQ on the extension's page.