The Apple Pay button is an official user interface (UI) element of the Apple Pay payment experience. Designed by Apple for web and app environments, it initiates Apple Pay transactions across millions of merchants globally.

Yes, Apple Pay button varieties are available across all markets where Apple Pay is live and should be integrated in all merchant checkout flows, on the web and in apps.

The color or font of the Apple Pay button cannot be changed. However, merchants can select from a wide variety of Apple Pay button types, styles, and sizes to customize the payment experience to their business. Refer to Apple’s Human Interface Guidelines for Apple Pay button details.

No, merchants should not create their own version of the Apple Pay button. Apple provides a wide selection of buttons that allow merchants to select the most appropriate one for their web and app environments.

Yes, the Apple Pay button has a consistent experience and look and feel in web‑based and app environments. This consistency in experience across millions of merchants signals trust to the consumer when paying with Apple Pay.

Apple provides localized versions of all the Apple Pay buttons in a wide range of languages.

• Web integrations: The merchant can set the locale on the button attributes to determine which localized button will be rendered. When locale has not been set, localizations are determined by the language settings of the web browser or device.
• App integrations: Localizations are determined by the device’s language settings.

When a consumer is presented with an Apple Pay button in an app and certain conditions are met, the button can display an image of their default payment card in Apple Wallet. This customizes the experience for consumers and helps maximize engagement. Refer to the Enhanced payments experience in What’s new in Apple Pay session video from WWDC25 for details.

The dynamic capabilities of the Apple Pay button are not currently available on web integrations.

While the Apple Pay button typically displays a consumer’s default card dynamically, this may not be the case at all times. If a consumer has a private label or co‑brand card they can use with Apple Pay for a particular merchant’s app, then the button for that merchant will display that card, even if it’s not the default debit or credit card in Apple Wallet. Additionally, if the default card is not accepted by the merchant, then there are two possible scenarios depending on how the merchant’s app was built:

• SwiftUI: The button will automatically update the card art to show a card the merchant does accept if available in Apple Wallet, as long as the merchant is passing the payment request with the button
• UIKit: The button might still display the unsupported default card

The Apple Pay button dynamically displays the consumer’s default card art when both of the following conditions are met:

• The button appears within the merchant’s app
• The button meets the minimum width required to display card art

Additional conditions may apply, including merchant acceptance of the consumer’s default card.

Yes. Merchants can suppress the dynamic capabilities of the Apple Pay button in their merchant environment. Refer to the Enhanced payments experience in What’s new in Apple Pay session video from WWDC25 for details.