Silvio Pacitto
Jun 6, 2024
  1629
(2 votes)

Integrating Apple Pay within Optimizely - Lesson's Learned

Hello Optimizely world,

I have recently undertaken the responsibility of assisting our client in the integration of Apple Pay onto their website through Adyen. This endeavor holds significant importance, considering that 48% of smartphone users in the US and 25% worldwide utilize an iPhone as their preferred device.

In this article, I will delineate the pivotal steps we took in achieving this integration, elucidate the challenges we encountered, and expound upon the solutions implemented along with the lessons gleaned for future endeavors.

1. Creation of an Apple Developer Account

Initiating the process with the creation of an Apple Developer account emerges as a paramount action item. It is imperative to note that acquiring this account from Apple may necessitate a span of 2-3 weeks, underscoring the need for timely initiation.

Reference: https://developer.apple.com/programs/enroll/

 

2. Placement of Apple Pay Button

It is crucial to bear in mind that the Apple Pay button exclusively manifests for Apple devices. Given this, particular attention must be paid to its placement vis-à-vis other design elements within the checkout interface. Notably, special consideration should be given to potential empty displays on non-Apple devices, prompting the strategic positioning of the Apple Pay button above other payment methods, akin to the prominence afforded to a PayPal Express Checkout button.

3. Establishment of a Site Settings Folder for Apple Pay within the Optimizely CMS

Within this designated folder, the creation of functionality to enable/disable Apple Pay on a country-by-country basis emerges as a strategic imperative. Although the current acceptance of Apple Pay may be confined to a limited number of countries, its global proliferation is anticipated to escalate over time. As such, facilitating the ongoing enablement of Apple Pay for new countries aligns with a forward-looking approach.

 

4. Testing of Apple Pay

Navigating the testing phase of Apple Pay posed a notable challenge, given the exclusive utilization of Windows devices within our team. To surmount this obstacle, manual testing was conducted through BrowserStack. This necessitated the acquisition of "Team Pro" account access, facilitating a comprehensive examination of the Apple Pay integration. 

Reference: BrowserStack

 

To wrap up, my aim with this article is to offer valuable insights into the essential steps required for integrating Apple Pay.

Hope you enjoyed the read. 

Jun 06, 2024

Comments

Please login to comment.
Latest blogs
Forcing Lowercase URLs in Optimizely CMS During Auto-Translation

Learn how to fix uppercase and punctuation issues in Optimizely CMS 12 URL segments caused by LanguageManager auto-translation using a custom...

Stuart | Apr 2, 2026 |

Stott Robots Handler v7 for Optimizely CMS 13

Stott Robots Handler version 7 is now available for  Optimizely PaaS CMS 13 . This is includes updates to support the switch from a Site based...

Mark Stott | Apr 2, 2026

Automating Block Translations in Optimizely

Stop manual block-by-block translations. Learn how to use the TranslateOrCopyContentAreaChildrenBlockForTypes config to automate Optimizely CMS...

Stuart | Apr 1, 2026 |

How to Disable automatic indexing in Optimizely Search & Navigation

Learn how automatic event-based indexing works in Optimizely Search & Navigation and how you can temporarily disable it.

Tomas Hensrud Gulla | Apr 1, 2026 |

Fixing “Published By” After OKTA SSO in Optimizely CMS

Enabling Okta SSO significantly strengthened our authentication and security model in Optimizely CMS . However, like many real-world implementation...

Sanjay Kumar | Apr 1, 2026

OptiPowerTools.Hangfire: A Drop-in Hangfire Integration for Optimizely CMS 12

Back in 2024, I wrote a post on Adding Hangfire to Episerver/Optimizely CMS 12, walking through each step of integrating Hangfire into an Optimizel...

Stanisław Szołkowski | Mar 31, 2026 |