Skip to main content

Tap to Pay

docs image

Tap to Pay

Pay in just one tap

Tap to Pay

Tap to Pay is an Apple-authorized payment solution. It offers a fast and convenient way of making payments through an iPhone, replacing bulky and/or stationed payment terminals. Customers can simply pay by tapping or hovering an NFC-enabled smartphone, payment card, or wearable device on an iPhone where the EVA Checkout App is installed and payment method enabled.

Tap to Pay available countries

A list of countries where Tap to Pay is currently available can be found on Apple's official page.

iOS 16.4

Only iPhones running on iOS version 16.4 or higher are able to use Tap to Pay.

Enabling Tap to Pay on EVA​

To start using Tap to Pay in your stores, configurations on both your Adyen and EVA accounts are required.

Configuration in Adyen​

Submit a request for Tap to Pay to be enabled in your Adyen environment. See Payment methods in Adyen for a glimpse of how this is done.

Unreferenced returns not supported via Tap to Pay

A referenced return is a refund that can be referenced to its original payment (time of order placement), and using Tap to Pay as your refund method requires this reference to be available. This means that payments not initially made via Tap to Pay are not possible to refund via Tap to Pay.

Configuration in EVA​

Follow the below steps to configure Tap to Pay as a payment method and payment type via Admin Suites Payment methods chapter.

Step 1: Create a new payment method

  • Name: AdyenPosSdk
  • Code: ADYEN_POSSDK

Step 2: Create the payment type

  • Name: Adyen - TapToPay
  • Code: ADYEN_POSSDK_TAPTOPAY

Step 3: Add the following two settings and their respective values obtained from Adyen:

  • Adyen:Possdk:BaseUrl
  • Adyen:Possdk:Apikey

Step 4: Ensure that the BackendID of your type store organization unit in EVA where Tap to Pay is being enabled, matches with what's specified in your Adyen account.

Steps for matching IDs
When you import your OU information from an external system, the **BackendID** that gets listed in your OU's [Basic information](/documentation/documentation/organizations/creating-ous#basic-information) won't necessarily match the ID listed in Adyen. You can work around this by adding it in a custom field, as described here below: - Create a custom field in your ***Organizations*** chapter. - Type *Line* - Name it *Adyen Store ID* for example, for extra clarity - Add the right **Organization unit set** - Visible by *Employee* and *API* type - Editable by *Employee* - Required *No* - Now go the OU you want to enable Tap to Pay for and add a new custom field in its ***Custom fields*** tab. - Select the *AdyenStoreID* and add the store's **BackendID** as it's known by in Adyen - Lastly: fill the value of the `AdyenStoreCustomField` setting with the **BackendID** of your custom field (*AdyenStoreID*)
Partial payments and refunds

When App:TapToPay:AllowPartialPayment is set to true, orders can be partially paid and refunded using Tap to Pay.

Security & PCI​

Tap to Pay iOS complies with the following:

  • Security / PCI: Tap to Pay on iPhone is built in compliance with PCI CPOC / CPOC + PIN (this certification process was undertaken by Apple itself).

  • Payments processing / EMV: The supported Apple devices are compliant with relevant network requirements (Level 1 / L1). The kernels are an integrated part of the distribution on each iOS version, so Apple is also responsible for the Level 2 / L2 certification, while Adyen is responsible for conducting and completing the Level 3 / L3 certification for each payment method that is offered. Adyen's Tap to Pay on iPhone solution is currently EMV certified for Visa, Mastercard, Amex, and Discover in the US markets.

  • PCI requirements from merchants: Merchants are required to complete the SAQ B-IP, requirement 9.9 which refers to the Physical security of the devices. This control requires that personnel who interact with card-present devices on a day-to-day basis, be trained on awareness aspects of attempted tampering or replacement of devices. Furthermore, requirement 12 of the SAQ B-IP will also be required.

note

Requirement 12 (part of PCI requirements from merchants) is an interim solution until the SAQ MPOC is finalized by the PCI SSC. Once the SAQ MPOC has been released, and the MPOC certification has been scoped by the recognized lab, this requirement will be re-assessed.