Apple Pay with Salesforce Commerce Cloud: 5 learnings
Finally! Apple Pay is live in The Netherlands. It was a long wait since the initial release date of October 2014. The adoption curve in other countries look promising, resulting in high expectations for The Netherlands. Apple chose to launch Apple Pay in The Netherlands with launching partners, Omoda was one of them and decided to make Apple Pay directly available on every channel, supporting all shipping methods. A big challenge with short timelines. Are you planning to launch Apple Pay on Salesforce Commerce Cloud as well? Here are a few learnings.
#1 Flattening Shipping Methods
You probably support more than one shipping method and even shipping options such as timeframes in your current check-out. For Omoda, it was key to support all shipping methods at go-live, because they didn’t want to offer less service to customers using Apple Pay. Why was this a challenge? Apple Pay only supports showing a flat list of shipping methods. So we had to “flattening” the shipping options for Same Day delivery, Home delivery including, Pick-up in Store and Pick-up Points. The sum of all options would easily hit a list of 50 shipping options shown in a flat list. Therefore we chose to show the first 3 options of each shipping method. And yes, for pick-up points and pick-up in store the 3 nearest locations are shown based on the shipping address given by the user via Apple Pay (!)
#2 Supporting Maestro
Salesforce supports Apple Pay already a few years out of the box in Commerce Cloud. There are a few limitations for the European market though. Especially and essential for The Netherlands: there is no support for Maestro cards. Why? Salesforce only supports Apple Pay version 1 until now and you need at least to support version 4 to support Maestro following this overview with supported networks per Apple Pay version. We solved this with a workaround, resulting that Omoda is the first supporting Maestro payments via Apple Pay via Salesforce Commerce Cloud.
#3 Splitting street name and house number
Apple does not return the street name and house number in separate fields, instead, you will get this as one field: “street”. If you need to have this split - like Omoda - for back-end systems or fulfillment, you will need to do some extra work. Omoda supports splitting Dutch, Belgium and German addresses and if we don’t recognize the address and splitting doesn’t succeed: we process the address via an address validation service and split the address after that. In addition: we automatically correct the address when incorrectly entered and splitting couldn’t be done based on the user given input.
#4 Payment Service Provider
Apple Pay is just “facilitating” the transaction, you need a Payment Service Provider supporting Apple Pay to proces the actual transaction. Personally I highly prefer to work with Adyen in general and also for Apple Pay they proved to be one of the best partners to get Apple Pay smoothly integrated into Salesforce Commerce Cloud. Buckaroo and Mollie announced their support to Apple Pay as well.
#5 Apple Pay cannot be enabled per locale
A short one, but important to know: in Salesforce Commerce Cloud you can only enable Apple Pay per site. Not per locale. So if you have one site, for multiple European countries and you just want to support for instance The Netherlands, you will need to make a customization for this. Fortunately this was not needed for Omoda.
Do you have questions on Omoda’s integration of Apple Pay? Contact us.
Ewoud Frielink, June 16, 2019
Omoda brengt jou: Apple Pay (+video)