How it works

Apple Pay provides an easy, secure, and private way to pay for physical goods and services such as groceries, clothing, tickets, and reservations in your iOS apps. By simply using Touch ID, users can quickly and securely provide all their payment and shipping information to check out with a single touch.

Judopay’s iOS framework enables you to utilize Apple Pay within your iOS app. We provide the payment processing services that facilitate Apple Pay’s wallet solution. Apple Pay handles the secure storage of the device owner’s payment and shipping information, while Judopay processes the payments that Apple Pay initiates.

Note: It is important to understand the difference between Apple Pay and In-App Purchase. Use Apple Pay to sell physical goods and services. Use In-App Purchase to sell virtual goods such as premium content for your app, and subscriptions for digital content.


Requirements

Currently, Apple Pay can be used for physical goods and services using the following:

  • Devices: iPhone 6, iPhone 6 Plus, iPad Air 2, iPad mini 3 or newer
  • Operating System: iOS 8.1 or newer
  • Xcode: 6.1 or newer

User experience and interface

For consumers, the Apple Pay experience starts with registering payment and shipping information into the Wallet app on their Apple devices. Once registered, consumers can pay simply and securely by using Touch ID to authenticate a transaction.

Each transaction processed through Apple Pay is assigned a one-time payment number as well as a dynamic security code. This information is encrypted and used in place of credit or debit card details.

Apple Pay offers consumers an exceptional level of ease, security and privacy. For businesses, Apple Pay functions the same as any other secure debit or credit card payment processed with Judopay.

Effective implementations of Apple Pay can radically improve your payment process by allowing for a smoother ‘guest checkout’, while still capturing all the relevant information needed to fulfil a purchase (such as shipping information).

The Apple Pay button

Apple Pay allows the user to bypass the standard checkout flow and complete their payment with speed:

Apple Pay User experience and UI - Judo Payments

While integrating Apple Pay, you’ll need to consider when you want to introduce the Apple Pay button, such as on a product listing page for a single item, within a basket page of multiple items, or in both of these scenarios.

The Apple Pay button indicates that users can make a purchase from their immediate context (i.e. the particular page they’re browsing). When users tap the Apple Pay button, the payment sheet should immediately be invoked to begin the checkout process. For more information on the Apple Pay button, see Apple’s guidance of the PKPaymentButton Class Reference.

The payment sheet

Before a user submits an order and initiates the payment, Apple Pay will display a payment sheet containing the contact, shipping and payment information relevant to the checkout being used.

Although users can make changes within the payment sheet - such as selecting a different shipping method - they shouldn’t have to make changes or enter additional information. When a user sees the payment sheet, they should be able to immediately authorize and complete their payment.

Customizing the payment sheet

You can customize the information displayed on the Apple Pay payment sheet depending on the information you require in order to complete the transaction and fulfill the order. When customizing the payment sheet, there are a few things to keep in mind:

  • Make sure to display only the necessary information - Users may get concerned or confused if the Apple Pay sheet displays extraneous information. For example, requesting a shipping address is perfectly acceptable for mail order companies where there is a valid need for this information, but if this information isn’t required for fulfilment of the order you shouldn’t request it.
  • Let users choose their delivery method within the payment sheet - Users can select a delivery method from a list that you specify within the Apple Pay payment sheet. To specify a shipping method, you’ll need to use a label, a cost, and an optional second line for providing a delivery estimate.
  • Use line items for recurring payments and for charges that are added to the merchandise being purchased - A line item will consist of a label and a cost. It conveys additional information about the breakdown of charges in the user’s purchase. Use line items to:
    1. Indicate that a user is authorizing a recurring payment with a line item like ‘Monthly subscription £19.99’
    2. Notify the user of extra charges, for example: ‘Gift Wrap £5.00’ or ‘Tax £4.53’
    3. Show a coupon or discount that has a negative cost, such as ‘Friday Discount -£2.00’
  • Create line item labels that can display on a single line - Where possible we recommend using concise and readily understandable labels.
  • Provide a business name after ‘PAY’ on the same line as the total - This will help reassure users their payment is going where they expect it to.
  • Communicate possible additional costs if applicable - Users can authorize Apple Pay payments for services without knowing the total amount, such as a taxi journey. It’s important to clearly explain within the payment sheet that there may be additional costs. Equally, if you are pre-authorizing funds to collect later, this too should be represented within the payments sheet.

If you have any questions on your Apple Pay integration, contact one of our payment experts for a consultation.


Testing best practices

There’s currently no available test environment for Apple Pay, which means you’ll need to complete your testing stories within the production environment.

We strongly recommend testing Apple Pay through each of these scenarios before you release the app:

  • Unsupported device: Test Apple Pay using a non-supported device in order to verify that the whole recognition workflow works as expected.
  • Card not supported: Test Apple Pay using a card issued by a bank not supporting Apple Pay, or use test cards provided on our Dashboard, to validate the error returned and the expected behaviour.
  • Payment cancelled: cancel a transaction in process and see the results in the app and in your Dashboard history.
  • Poor / loss of connection: While a transaction is being processed, disconnect internet connection in order to see if the app is responding as desired.

Interested?

If you are interested in Apple Pay and want to start testing it within your project, visit our Getting started guide.