Digital wallet FAQ

What is Apple Pay?

Apple Pay is a digital payment service that lets customers use eligible payment methods stored in Apple Wallet to authorize purchases with supported Apple devices. Customers may use it at contactless checkouts, inside participating apps, or on websites that present Apple Pay as an available payment option.

For a merchant, Apple Pay is an acceptance method within a broader payment setup. It does not replace the merchant's payment processor, acquiring arrangement, checkout controls, order records, or customer-service policies. Availability depends on the sales channel and the documented support provided by the merchant's payment platform or service provider.

How an Apple Pay purchase works

The customer first adds an eligible credit, debit, prepaid, or other supported payment method to Apple Wallet. At checkout, the customer selects Apple Pay or presents a supported device near a contactless reader. Apple explains that the customer then confirms the purchase using the authentication method available on the device, such as Face ID, Touch ID, a device passcode, or an Apple Watch control.

At a physical checkout

The customer holds an iPhone or Apple Watch near a contactless reader after confirming the payment on the device. The reader and merchant payment environment still need to be configured for the relevant contactless transaction flow.

On a website

A supported checkout displays an Apple Pay button or payment choice. The customer reviews the payment sheet, chooses an available method, supplies any requested shipping or contact details, and confirms the transaction on a supported device.

Inside an app

An app can present an Apple Pay payment sheet for eligible goods, services, donations, or subscriptions. The merchant or its payment provider must implement the applicable Apple Pay and payment-processing requirements for that app.

What the merchant receives

Apple states that the customer's actual credit or debit card number is not sent to the merchant when the customer pays with Apple Pay. Instead, the payment flow uses a device-specific account number and transaction-specific security information. For an app or website, Apple Pay encrypts the payment data so the merchant's configured payment provider or authorized payment-processing environment can handle it.

This distinction is useful, but it should not be turned into a blanket security claim. A merchant still needs to protect its website, app, devices, accounts, order data, employee access, refund process, and any customer information collected outside the Apple Pay payment credential. Apple Pay does not by itself secure every part of a merchant's operation.

Keep customer data out of general forms

Do not ask customers or staff to place complete card numbers, security codes, passwords, bank credentials, device passcodes, or secret API keys into a general contact form or ordinary email. Use the payment and support channels approved for the specific system.

Apple Pay is not the same as Apple Wallet

Apple Wallet is the app that can organize eligible payment cards and other items such as tickets, passes, keys, and IDs where supported. Apple Pay is the payment capability used when an eligible item in Wallet is presented for a purchase. The terms are related, but they are not interchangeable.

It is also helpful to distinguish Apple Pay from Tap to Pay on iPhone. Apple Pay is used by the customer to make a payment. Tap to Pay on iPhone is a merchant acceptance capability offered through supported payment apps; it can accept eligible contactless cards and digital wallets. A business should evaluate each capability according to its own role in the transaction.

What merchants should confirm before offering Apple Pay

A merchant should verify the complete acceptance path rather than assuming that one contactless device, gateway, or ecommerce feature enables Apple Pay everywhere. Apple directs merchants that use an ecommerce provider or payment platform to consult that provider about its Apple Pay implementation.

  • Sales channel: Identify whether acceptance is needed at a counter, on a mobile device, within an app, on a website, or across several channels.
  • Provider documentation: Confirm current support with the payment processor, platform, gateway, or application responsible for that channel.
  • Implementation: Determine whether the setup requires a supported reader, platform setting, merchant identifier, certificate, domain verification, approved payment button, or provider-led configuration.
  • Testing: Test authorized payments, declined attempts, cancellations, refunds, receipts, order status, and reconciliation before making the option broadly available.
  • Operations: Train staff to recognize the customer-facing flow without asking to handle or unlock the customer's device.

No statement on this page confirms compatibility between Apple Pay and a particular Payments Max offering, terminal, gateway, processor, website, or app. Compatibility should be established from current documentation for the exact configuration.

Where Apple Pay fits among digital wallets

Apple Pay is one example of a digital wallet payment experience. The broader category includes other services that can present stored payment credentials at checkout. Merchants comparing wallet acceptance should look at customer demand, supported channels, checkout design, provider documentation, reporting, refund handling, and operational fit.

Understand the category

Read what a digital wallet is to see how wallet services relate to stored payment credentials, devices, and checkout.

Common Apple Pay questions

Does Apple Pay process the merchant's payment by itself?

No. Apple Pay provides the customer-facing payment and authorization experience, while the merchant's configured payment provider and acceptance environment handle the transaction through their documented processing flow.

Can every contactless terminal accept Apple Pay?

Do not assume so from the appearance of a contactless symbol alone. Confirm the terminal, software, processor configuration, payment networks, and merchant account setup with the responsible providers.

Does the merchant receive the customer's actual card number?

Apple states that the actual credit or debit card number is not sent to the merchant for an Apple Pay transaction. Merchants may still receive other information needed for the order, such as contact or shipping details, according to the checkout and privacy notices.

Is Apple Pay available for every customer?

No. Customer use depends on factors including country or region, supported devices, eligible cards, participating issuers, software requirements, and the merchant's acceptance setup.

Evaluate the full payment workflow

Start with the channel where customers will pay, then document the exact terminal, app, website, platform, and provider involved. Use current provider guidance to confirm support and test the end-to-end workflow before promoting Apple Pay as an option.

For more educational context, browse the Payments Max payment FAQ library. If you contact Payments Max about a payment workflow, share only general business requirements and the names of the systems you use. Do not submit cardholder data, passwords, bank credentials, complete account numbers, or secret keys.

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.

CONTACT US