Authorize.net Apple Pay & Google Pay
/
A store on Adobe Commerce and Magento Open Source takes cards through Authorize.net with a third-party card module, the one that keeps its customers' saved cards, and wants Apple Pay and Google Pay at checkout. The card module does not offer them, and the Marketplace listings that do are full card modules, so switching means migrating saved-card links out of the old module's tables, re-pointing webhooks and re-testing every checkout customisation – a large, risky project to gain two buttons.
Authorize.net Apple Pay & Google Pay is an extension for Magento Open Source and Adobe Commerce that adds the two wallets and nothing else. It installs next to the card module, migrates no saved cards, reads none of its settings and touches none of its webhooks. A wallet payment is an ordinary Authorize.net transaction, 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. Required fields and checkout agreements are checked before a wallet sheet opens, and the order completes on the store's own success page. A currency guard hides the wallets on any order that is not in the Authorize.net account's currency, and a Configuration Check in the admin tests the saved settings against Authorize.net and says what is missing. For Apple Pay the store validates itself with Apple using your Merchant Identity certificate, serves the domain association file, and warns from 60 days before the certificate expires.
Authorize.net Apple Pay & Google Pay is a rule-based, deterministic extension for Magento Open Source and Adobe Commerce. It calls Authorize.net and, to validate the store for Apple Pay, Apple; Google's and Apple's payment scripts run in the shopper's browser. It adds no database tables and stores no payment data: the wallet's encrypted payment is passed to Authorize.net and discarded, and the order keeps the card network, the last four digits and the transaction details. Storefronts: Luma, Hyvä Theme (with native Magento checkout); Hyvä Checkout, the separate Magewire-based product, is not supported. Google Pay 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.
Key Features
- Google Pay at Magento's own checkout payment step, with Google's button, offered only when Google says the shopper can pay with it
- Apple Pay at the same step: in Safari, and in desktop Chrome, Edge and Firefox through Apple's scan-a-code flow
- Installs next to the Authorize.net card module you already run: no saved-card migration, no webhook changes
- Required fields and checkout agreements checked before a wallet sheet opens; the order completes on the store's own success page
- Authorize or authorize and capture, per wallet
- Capture on invoice, online refunds and void from the Magento admin
- The card on every wallet order – network and last four digits – in the admin, the customer's account, the sales e-mails and the PDFs
- Accept or Deny for transactions the Authorize.net Advanced Fraud Detection Suite holds; such orders go to Payment Review
- Currency guard: the wallets hide on any order not in the Authorize.net account's currency
- Configuration Check: ten lines on the saved settings, the account checked live at Authorize.net, each pass, warning, failure or unknown, with what to fix
- Apple Pay merchant validation with your Merchant Identity certificate, pasted into the admin and stored encrypted; its passphrase is used once and never stored
- The Apple Pay domain association file served by Magento, per store view if needed
- Certificate expiry warnings in the admin from 60 days before; Apple Pay withdraws itself while the certificate is expired
- Allowed card networks per wallet; Google Pay authentication methods, button type and colour
- Debug Log: a redacted log file of every gateway call, and a browser console line saying why a wallet is not offered
- The one-time wallet payment is never stored or logged; the Authorize.net credentials never reach the browser
- Sandbox and production environments, switched in one field
- One implementation for Luma, the blank theme and Hyvä Theme with the native Magento checkout
Versions
First public release.
Show details Hide details
Added
- Google Pay and Apple Pay at the native Magento checkout, on Luma and Hyvä Theme, paid through the store's Authorize.net account and installed next to the Authorize.net card module the store already runs.
- Google's and Apple's own buttons. Apple Pay works in Safari, and in desktop Chrome, Edge and Firefox through Apple's scan-a-code flow.
- Required fields and checkout agreements are checked before a wallet sheet opens, and the order completes on the store's own success page.
- Authorize or authorize and capture per wallet; capture on invoice, online refunds and void from the admin; Accept or Deny for transactions the Authorize.net fraud filters hold, with the order in Payment Review.
- A currency guard: the wallets hide on any order that is not in the Authorize.net account's currency.
- Configuration Check in the admin: ten lines on the saved settings, the account checked live at Authorize.net, each with what to fix.
- Apple Pay merchant validation with the store's Merchant Identity certificate, stored encrypted; the domain association file served per store view; expiry warnings from 60 days before, and Apple Pay withdrawn from the checkout while the certificate is expired.
- Allowed card networks per wallet, and Google Pay authentication methods, button type and colour.
- The card on every wallet order: "Card Network" and "Card Number" (xxxx-1111) in the admin order views, the customer's account, the sales e-mails and the PDFs.
- Debug Log: a redacted log of every gateway call, and a browser console line saying why a wallet is not offered.
- The one-time wallet payment is never stored or logged, and the
Authorize.net credentials never reach the browser. A configuration dump
leaves the credentials and the certificate out of
app/etc/config.php.
Upgrade notes
- Google Pay 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.
FAQ
Stores on Adobe Commerce and Magento Open Source that take cards through Authorize.net usually do it with a third-party card module, and the common ones do not offer Apple Pay or Google Pay. The Marketplace listings that do are full card modules, so reaching two wallet buttons means migrating saved cards, re-pointing webhooks and re-testing the checkout. This extension adds the two wallets next to the card module you already run: nothing is migrated, and a wallet payment is an ordinary Authorize.net transaction in the same account, reports and fraud filters.
- You take cards through Authorize.net and want Apple Pay and Google Pay without replacing the card module that holds your customers' saved cards.
- Your storefront is Luma, the blank theme, or Hyvä Theme with the native Magento checkout.
- Much of your traffic is on phones, where a wallet sheet replaces typing a card number and an address.
- Your Authorize.net account settles in the currency your orders are placed in.
- Your store does not use Authorize.net. Braintree, Stripe and Adyen offer Apple Pay and Google Pay in their own extensions; use those.
- Your checkout is Hyvä Checkout (the Magewire-based product) or another checkout that replaces Magento's. The wallets live in Magento's native checkout payment step.
- Your Authorize.net processor does not support wallet payments. Authorize.net publishes the processor support list; this extension cannot add the entitlement to an account.
- You sell in several currencies through one Authorize.net account. The wallets hide on orders in any other currency than the account's.
- Your storefront is headless (PWA or another GraphQL front end). The extension has no GraphQL surface.
- Adds two payment methods, Google Pay and Apple Pay, to the checkout payment step, each with Google's or Apple's own button. Apple Pay works in Safari, and in desktop Chrome, Edge and Firefox through Apple's scan-a-code flow.
- Checks required fields and checkout agreements before a wallet sheet opens, and completes the order on the store's own success page.
- Authorizes, or authorizes and captures, per wallet. From the admin: capture on invoice, online refunds, void, and Accept or Deny for transactions the Authorize.net fraud filters hold.
- Settings under Stores > Configuration > Sales > Payment Methods > Authorize.net Wallets, in three groups: the Authorize.net account, Apple Pay and Google Pay.
- A Configuration Check of ten lines – the credentials and the account, checked live at Authorize.net, the account currency, each wallet's settings, the Apple Pay certificate and domain file – each saying what to fix.
- For Apple Pay: validates the store with Apple using your Merchant Identity certificate, serves the domain association file per store view, and warns in the admin from 60 days before the certificate expires.
- Keeps no payment data: the one-time wallet payment goes to Authorize.net and is removed; the order keeps the card network and the last four digits, and shows them in the admin, the customer's account, e-mails and PDFs.
- A Debug Log for setup, redacted, with a browser console line saying why a wallet is not offered.
- It takes no card numbers and keeps no saved cards. Card payments stay with your card module.
- It works with Authorize.net only.
- It shows the wallets in the checkout payment step only – no express button on the product page, the mini-cart or the cart.
- It does not open your Authorize.net, Google or Apple accounts, and it cannot approve your site with Google or verify your domain with Apple for you. Those steps are described in the user guide.
- It does not show shoppers the exact reason a payment was declined. They see Magento's general decline message; the reason is in the store's log.
- Apple Pay has not yet been verified with a live Apple Pay payment. Google Pay has been verified with a real payment against the Authorize.net sandbox.