Apple Pay, Google Pay and saved cards for your Authorize.Net checkout
The free Authorize.Net Accept.js Payments module takes card payments through Authorize.Net’s current API, with the card tokenized in the browser. Pro adds the two wallets and card on file to that same payment block, without changing a line of the free module.
| Feature | What you get |
|---|
| Apple Pay | An Apple Pay button above the card fields in Safari on a Mac, iPhone or iPad that has a card in Wallet. Merchant validation runs through your own store with your merchant identity certificate, and the token is charged by the free module like any other payment. |
| Google Pay | A Google Pay button wherever the browser can pay. Test it against the Authorize.Net sandbox with no approval from Google at all; go live once Google approves your domain. |
| Card on file | “Save this card for next time” at checkout, saved cards offered on later orders, and a Saved Cards page where customers manage them. Cards live at Authorize.Net as customer profiles; your store keeps only the profile ids, the brand, the last four digits and the expiry. |
| Digital Wallet Setup | A Tools page that shows the state of every requirement, takes the Apple domain verification file and checks that your store serves it, reads your certificate’s expiry, and lists the registration steps with links. |
| One Page Checkout too | Works with the standard checkout and with One Page Checkout, including its redraws of the payment block. |
Requirements
Zen Cart v2.2.2 through v3.0.0 on PHP 8.2 through 8.5, a store served over https, and the free Authorize.Net Accept.js Payments plugin at version 1.0.1 or later installed and enabled. Pro attaches to extension points that arrived in that release; it refuses to install without them rather than installing quietly and doing nothing.
For the wallets on a live account, your Authorize.Net merchant account has to sit on an eligible processor (Chase Paymentech, Global Payments, TSYS, First Data Nashville, NAB EPX or Worldpay Vantiv Core; Google Pay adds Elavon); the Merchant Interface’s Digital Payment Solutions page shows what your account is offered. Apple Pay needs an Apple Developer Program membership ($99 a year) for the store, and Google Pay in production needs a free Google Pay & Wallet Console profile. Card on file needs nothing extra: customer profiles are part of every Authorize.Net plan.
What you get
- The plugin package, downloadable from your account as soon as your order is placed.
- The full documentation, available here once you’re signed in, with the Apple and Google walk-throughs.
- A Getting Started email with the links you need.
- Twelve months of support and updates. After that, a renewal buys another year: $24.95 for a single store, $59.95 for five, $99.95 for a developer license. The plugin keeps working whether or not you renew.
License
Three tiers, chosen above. Single Store ($59.95) covers one Zen Cart installation. Five Stores ($149.95) covers up to five installations you own or manage. Developer ($249.95) covers every store you manage, with no count. Use and modify it on those stores, and don’t redistribute it. No license key, no phone-home.
Need it tailored to your store? We customize our own plugins: an extra option, a different placement, a hook into something else you run, or a version for a template that names things differently. Tell us what you have in mind through
Contact Us, choosing Customization, and we'll quote it.
