Merchant Features
Discover the benefits, enablement steps, and
resources to get started.
The Apple Pay Payment Sheet
Give consumers a consistent way
to check out with Apple Pay
Opened when a consumer chooses Apple Pay at checkout, the Apple Pay payment sheet provides consumers with an easy, secure, and private way to review and confirm purchases across millions of apps and websites globally.
Consumer experience
Payment sheet
Card hub
Payment options
Payment sheet configurations
Merchants can configure the Apple Pay payment sheet based on their business model and checkout configuration. It supports a wide variety of transactions, such as one‑time, recurring, deferred, automatic reload, and installments.
Depending on the transaction type, the payment sheet gives merchants the flexibility to request only the necessary data to process the purchase, while automatically displaying the most relevant information so the consumer can confirm their purchase confidently.
Simple configurations
Payment method (with optional billing address)
Request the consumer’s preferred payment method, with the option to also collect a billing address.
Common use cases: Transactions when all other consumer information has already been gathered.
Payment method, billing address, and contact information
Request the consumer’s preferred payment method, billing address, and contact details (such as email and phone number).
Common use cases: Express checkout transactions (from product detail pages or cart) where physical shipping is not required, such as services, ticketing, or travel — or for transactions with in-store pickup.
Payment method, billing address, shipping address and options, and contact information
Request all details from the consumer, including the preferred payment method, billing address, contact details, and preferred shipping method.
Common use cases: Transactions involving the processing and shipping of physical products, including during express checkout.
Complex configurations
Recurring payments
Request the preferred payment method and contact information from the consumer, while including subscription details such as the billing interval, price, payment due, and starting and end date.
Common use cases: Transactions involving subscriptions.
Deferred payments
Request the preferred payment method and billing address from the consumer and include the total to be paid at a later date.
Common use cases: Hospitality transactions, such as booking a hotel stay or a car rental.
Automatic reloads
Request the preferred payment method, billing address, and contact information (such as email) while indicating the trigger conditions for an automatic card reload, such as a specific balance threshold or a set schedule.
Common use cases: Reload of stored value accounts or transit cards.
Installment repayments
Depending on the types of goods or services, request the preferred payment method, contact information, and shipping details while displaying the installment plan details in the payment summary, including the payment plan chosen, payment frequency, and total amount financed.
Disbursement
Enable consumers to select the payment card they want to transfer funds to, along with the funds out option (for example, standard or instant).
Coupons
Get started.
Customize the Apple Pay payment sheet
Plan
- Explore various payment sheet options using the Apple Pay on the Web Interactive Demo.
- Identify required data. Assess which consumer information elements you need for your checkout journey. For example, you may need shipping address and contact information if sending physical goods to your customers. For any ongoing payment models (such as a recurring subscription), refer to Merchant Tokens (MPANs).
- Map data to checkout stages. Determine when to collect each piece of information.
- Early checkout (cart or product pages): Request all required data from Apple Pay.
- Final checkout: Request only missing information to reduce friction.
- Single‑page checkout: Request all required data in one payment sheet.
- Learn about payment sheet best practices. Refer to the Streamlining checkout and Customizing the payment sheet section of Apple’s Human Interface Guidelines.
- Design flexible validation. Address fields in the Apple Pay payment sheet are free‑form text. Apple does not verify what consumers enter, and any information can be submitted. Ensure your validation logic is flexible enough to accommodate a wide range of address formats, without blocking legitimate purchases. Use your existing verification systems to validate address data as part of your standard transaction processing flow.
- Implement error handling. Use Apple Pay Error Handling APIs to guide consumers when they need to correct information or meet specific requirements.
Build
- For each payment you offer, configure your payment request to include the appropriate information for your business, referring to the common recommended configurations above as a starting point.
- Specify the contact information you need using the available fields:
postalAddress,phone, andemail.requiredBillingContactFields: ['postalAddress', 'name']
requiredShippingContactFields: ['postalAddress', 'name', 'phone', 'email'] - Define shipping methods (if applicable). Configure shipping options, costs, and delivery time frames using
shippingMethods. - Respond to consumer actions. Use delegates and event handlers to respond dynamically to consumer actions, such as changes to the payment method (credit or debit) or shipping address, ensuring that pricing and available shipping options stay accurate throughout checkout.
- Configure error responses by building error objects for validation failures (such as invalid shipping address, unsupported region).
Test
- Configure Apple Pay Sandbox cards. During development, use Apple Pay Sandbox cards on physical devices to simulate payment interactions without processing real payments. If you are building a native app using Xcode, you can alternatively use the cards already provisioned on the Simulators. When you’re ready for production testing, you can also use real cards provisioned to physical Apple devices.
- Test each payment sheet configuration to make sure the correct fields are displayed.
- Validate data collection. Confirm your app correctly receives and processes all of the relevant data requested from the consumer.
- Test the validation logic. Confirm that your validation handles:
- International address formats
- Various name formats (single name, multiple surnames)
- Different phone number formats
- Missing optional fields (for example, Address Line 2 in the payment sheet)
- Test error handling. Confirm that errors display correctly for:
- Invalid shipping addresses
- Unsupported regions
- Out‑of‑stock items for shipping address
- Payment failures
Launch
Optimize
Explore the resources
Documentation
PassKit (Apple Pay and Wallet)
TN3174: Diagnosing issues with the Apple Pay payment sheet on your website
Human Interface Guidelines
Frequently asked questions
The Apple Pay payment sheet is an official user interface (UI) triggered by the Apple Pay button across web and in‑app environments. The Apple Pay payment sheet provides consumers with an easy, secure, and private way to review and confirm purchases across millions of businesses globally.
Yes, the Apple Pay payment sheet is available across all markets where Apple Pay is available and should be integrated in all merchant checkout flows, on the web and in apps.
The Apple Pay payment sheet supports a variety of transactions. These include one‑time, recurring, deferred, automatic reload, and installments. Merchants can configure the payment sheet based on the needs of their business.
The Apple Pay payment sheet has been designed to display important information in a way that is easy to digest by the consumer. Information is organized into three sections:
- Main payment sheet: Provides consumers a clear, concise summary of their purchase, including the merchant’s name, order total, the selected payment method, requested contact or shipping information, shipping method, coupons or offers applied, and taxes and fees. Consumers can also easily switch their payment method and update their contact details before confirming their purchase.
- Card hub: Gives consumers an overview of all the payment options their card supports. Depending on the market and the issuer, this may include the card balance and the ability to pay in full, pay later, and pay with rewards. Related card offers and benefits may also be presented.
- Payment options: Gives consumers a full view of all of the cards in Apple Wallet that are available as a payment method for that purchase. This includes their default card, along with other debit cards, credit cards, stored credit cards, and buy now, pay later options.
This feature can be enabled as part of a new or existing Apple Pay implementation. As with other Apple Pay features, Apple does not charge implementation fees for its enablement.
Yes. Merchants can request shipping, billing, or contact fields individually. Omitting unnecessary fields can help speed checkout and improve conversion.
Yes, Apple Pay supports various types of recurring payments — from subscriptions to automatic reloads. Merchants should use PKRecurringPaymentRequest for app implementations and recurringPaymentRequest for web. Merchants must disclose the frequency, amount, and start date of payments in the payment sheet. Refer to Merchant Tokens (MPANs) for more information.
Yes. Line items can be marked as “Pending” and deferred charges can display expected charge dates. This is common for transactions where the final charges may change (for example, food delivery, ride‑hailing, or subscriptions) or where the payment will be made later (such as paying for a stay at a hotel or when pre‑booking a car rental).
Across all devices, the merchant’s name is displayed as part of the payment sheet, above the transaction total. Marketplaces should show both their name and the end merchant’s name.
On Mac, the merchant’s icon can also be displayed when consumers tap the more information (i) icon, where the line-by-line breakdown of their purchase is displayed.
The PassKit and Apple Pay JS classes highlight errors, and merchants can provide custom error messages (for example, “Zip code doesn’t match city”). Messages must be short, specific, and actionable. Refer to Handling problems in Apple’s Human Interface Guidelines for more information.
Yes, within Apple’s defined schema. The payment sheet supports two types of merchant‑configured information:
- Information requested from the customer — merchants can request fields such as shipping address, billing address, and contact details (name, email, phone number)
- Information provided to the customer — merchants can display order details such as line items, coupons, and recurring payment terms
Merchants are not able to add custom or freeform fields outside of these supported types. This helps create a consistent experience for consumers paying with Apple Pay across millions of merchants globally on the web and in apps.
Yes, merchants can detect whether a payment method is a debit, credit, pre‑paid, or stored value card using the ApplePayPaymentMethodType enumeration.
For all Apple Pay transactions, Apple processes consumer data to connect customers with their issuer. Apple does not retain personal financial data linked to the consumer.
Before a transaction is authorized, a merchant receives only redacted contact information — previously configured by the consumer in Apple Wallet — passed directly to their website or app by Apple Pay. The level of detail depends on the consumer’s region. For example, only the first part of a shipping postal code may be passed in some regions. Merchants use this limited information to estimate tax due or populate shipping options in the paymentDetails array, then update the payment sheet accordingly.
Once the consumer reviews their contact information, payment method, and purchase details in the payment sheet and authenticates the transaction with Face ID, Touch ID, or their device passcode, the merchant receives the complete set of requested contact information, passed directly to their website or app by Apple Pay to finalize the order.
Join the Apple Pay platform.
Continue to maximize your Apple Pay integration
- Monitor key metrics, including:
- Payment sheet presentation success rate
- Authorization completion rate
- Error rates by type
- Payment success rate
- Follow Apple Pay partner news and updates for the latest:
- Announcements
- Features
- Success stories
- Tech notes
More resources
Apple Pay Demo
in an interactive playground.
Apple Developer
build apps for Apple platforms.
Apple Business
presence across Apple apps.
-
In the US, Apple Pay is a service provided by Apple Payments Services LLC, a subsidiary of Apple Inc. Neither Apple Inc. nor Apple Payments Services LLC is a bank. Any card used in Apple Pay is offered by the card issuer.
-
Apple Pay is not available in all markets. View Apple Pay countries and regions.
-
Features are subject to change. Some features, applications, and services may not be available in all regions or all languages and may require specific hardware and software.