
The commuter
She saw the product at lunch, opened it again on the train home and has one bar of signal. Apple Pay finishes the order before the tunnel; the card form would not have.
Apple Pay & Google Pay
A customer on a train, on a phone, with thirty seconds before the tunnel. Apple Pay and Google Pay turn a form into a double-click, and the Payments Suite puts them in the checkout automatically once they are switched on. No card to type, no address to retype, 3DS2 handled inside the wallet.
Why it matters
The card form is where phone checkouts die. A wallet button above it removes the typing, the retyping and the bank redirect, which is most of the drop-off.
The wallet supplies name, email and shipping address, so a first-time buyer never fills in a form and still ends up as a proper Magento customer.
Face ID or a fingerprint is the strong customer authentication. No one-time code, no expired bank session, no "try again later".
The buttons come with the suite and follow the checkout through upgrades, including the Hyvä build. No wallet SDK on your side, no certificate renewals.
How it works
Update the Payments Suite to the current release and enable Apple Pay and Google Pay in the suite's configuration in the Magento admin. The setup flow creates the free payments account behind them.
Apple requires the store domain to be verified for Apple Pay. The suite handles the verification file and keeps it in place across deployments.
On an iPhone in Safari, on a Mac with Touch ID, in Chrome on Android, the wallet button shows above the card form. Where the device cannot pay by wallet, the card form is all the customer sees.
The customer confirms with biometrics, the wallet passes the address and contact details, the payment is authorised with 3DS2 satisfied, and the Magento order is created with the same records as any card order.
Ways merchants use it
Anywhere the buyer is on a phone: the commuter, the buyer between meetings, the customer who found you on Instagram.

She saw the product at lunch, opened it again on the train home and has one bar of signal. Apple Pay finishes the order before the tunnel; the card form would not have.

The cleanser ran out at eleven at night. A phone on the kitchen counter, Face ID, done. The wallet remembered the address, so she did not have to.

A campaign email lands while she is walking to a meeting. The offer, the product page and the wallet take under a minute on the pavement, and the order lands in Magento tagged to the campaign.
What you need
Also in Payments Suite
Questions
No. Apple Pay and Google Pay are part of the ebizmarts Payments Suite. Update to the current release and switch them on from the Magento admin; the setup flow there creates the free payments account they run on.
Yes. The Hyvä build of the suite shows the wallet buttons natively in Hyvä's flow.
The wallet performs the authentication with the device biometrics, which satisfies strong customer authentication without a redirect.
Only where the device and browser can pay by wallet: Apple Pay in Safari on iPhone, iPad and Mac, Google Pay in Chrome on Android and on desktop Chrome with a saved card. Elsewhere the card form is shown alone, so nothing breaks.
No. They are Magento orders with an invoice, a payment record and the customer details the wallet supplied, refundable from the credit memo like any other.
The payments team will tell you plainly what switching this on involves for your store, and what it costs.