Apple Pay – Technical Requirements

In a previous post, I talked about the advantages of enabling Apple Pay in your App (especially if you are a retailer).

I also differentiated between Apple Pay within apps and in-app purchases. To recap, the benefits of implementing  Apple Pay within apps as a payment option are:

  • Ease of use as there is no requirement to fill in Credit/Debit card and contact information
  • Security of payment using Touch ID on iPhone6 and above
  • Privacy as card details are not shared with merchants

Now that we know what the benefits are to users, how can Merchants and App Developers optimise their Apps to enable Apple Pay? Thought you’d never ask.

The Apple Pay architecture is a very interesting one. In order to implement it in your App, you will need:

1.Merchant Identifier: A merchant ID and matching certificate need to be at the Dev Portal. These are used to encrypt payment data and ensure security. The format for this is a reverse DNS format (i.e. merchant.*)

  1. Payment Process: In order to process payments, there are a host of payment platform options depending on your location that you can use. They decrypt the payments on your behalf. Here is a list of payment processors.

However, you can choose to decrypt the payment yourself but this is recommended if you already have an existing payment infrastructure.

The payment flow is quite the straightforward process:


It really is easy to implement but you also need to consider your existing payment options and how you will like to measure the benefits.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s