Regional Requirements
When publishing your app in multiple regions include the following regional requirements:
LOCALIZATION STRING FOR TAP TO PAY ON IPHONE
| Region | Long Form | Short Form |
|---|---|---|
| US, UK, AUS | Tap to Pay on iPhone | Tap to Pay |
| FR | Tap to Pay sur iPhone | Tap to Pay |
| NL | Tap to Pay op iPhone | Tap to Pay |
| BR | Tap to Pay no iPhone | Tap to Pay |
| TW | iPhone卡緊收 | iPhone卡緊收 |
| UA | Tap to Pay на iPhone | Tap to Pay |
LOCAL REQUIREMENTS
| Requirement | Region |
|---|---|
| PIN Entry in Education | US (Debit), BR, UK, NL, FR, UA, AU |
| Fallback Payment Method | UK |
| Surcharging | BR, AU |
| IFR | FR |
PIN ENTRY IN EDUCATION
When a Customer is prompted to enter their card PIN under specific circumstances with Tap
to Pay on iPhone. In regions where PIN is a common part of the checkout experience you
must provide PIN entry and accessibility details in the merchant education.
FALLBACK PAYMENT METHOD
In regions where a significant number of cards cannot be used with contactless under
specific circumstances (e.g. Offline PIN markets), the app must support at least one (1)
accepted alternative payment method and fulfill the following requirements:
- All merchants must be set up with at least one (1) accepted alternative payment
method so that all transactions can be completed in person. Check with your PSP for accepted alternative payment methods. - Ensure the app provides a seamless transition between the Tap to Pay on iPhone UI
and the accepted alternative payment method provided for the merchant. - Provide details on the fallback mechanism as part of the merchant education.
SURCHARGING
If your PSP supports surcharges for payments your app must demonstrate the surcharges
to the paying customer. If your PSP supports a blended rate surcharge (same rate for all
cards) your final amount on the Tap to Pay on iPhone screen should reflect this. For
example if payment is $100 and surcharge is 2% then the paying customer should see $102
as the total amount on Tap to Pay on iPhone UI.
If your PSP supports varying surcharges per card brand your app should have a dedicated
screen prior to the Tap to Pay on iPhone UI that allows the customer to see and confirm the
surcharge amount. In this scenario the Tap to Pay on iPhone UI will display just the
purchase amount and the surcharge will be added post tap.
The receipt must provide details on the purchase amount and the surcharge. Important
Itemization is required on digital receipts to meet governance requirements in some regions.
IFR
In EU markets with a domestic payment network and if your PSP terminal profile supports it,
the app (or PSP SDK) must offer an optional method for the customer to select a preferred
card brand before tapping their card.
Updated 16 days ago