skilld
All skills
raintree-technology avatar

/hig-technologies

@5aac106
by Raintree Technologyraintree-technology/hig-doctor140 stars
9

Apple HIG guidance for Apple technology integrations: Siri, Apple Pay, HealthKit, HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple, SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps, Mac Catalyst, and more. Use when asked about: "Siri integration", "Apple Pay", "HealthKit", "HomeKit", "ARKit", "augmented reality", "machine learning", "generative AI", "iCloud sync", "Sign in with Apple", "SharePlay", "CarPlay", "in-app purchase", "NFC", "VoiceOver", "Maps", "Mac Catalyst". Also use when the user says "how do I integrate Siri," "what are the Apple Pay guidelines," "how should my AR experience work," "how do I use Sign in with Apple," or asks about any Apple framework or service integration. Cross-references: hig-inputs for input methods, hig-components-system for widgets.

Ask your Agent

Use this Skill: https://skilld.dev/gh/raintree-technology/hig-doctor/hig-technologies

This session only. Nothing lands on disk.

referencestap-to-pay-on-iphone.md

≈1.2k tokens on demand. Your agent reads this file only when SKILL.md points to it.

<!-- hig-doctor:attribution -->

Source: Apple Inc. Canonical content at https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone. This file is a structured index of that content, snapshot 2025-02-02. Apple HIG text and imagery are © Apple Inc.; this repository provides organization and cross-referencing for AI agent consumption only.

Tap to Pay on iPhone

Enabling Tap to Pay on iPhone

Help merchants accept Tap to Pay on iPhone terms and conditions before they begin interacting with their customers.

Present Tap to Pay on iPhone terms and conditions only to an administrative user.

If necessary, help merchants make sure their device is up to date.

Educating merchants

Provide a tutorial that describes the supported payment types and shows how to use Tap to Pay on iPhone to accept each type.

  • Including it in a Learn More option in your in-app messaging

  • Automatically presenting it after merchants accept the Tap to Pay on iPhone terms and conditions

  • Automatically presenting it to new users of your app

  • Making it easy to find in a consistent place like your app’s help content or settings area

  • Launch a checkout flow for each type of payment

  • Help a customer position their contactless card or digital wallet on the merchant’s device for payment

  • Handle PIN entry for a card, including accessibility mode

Checking out

  • Offer payment options in addition to Tap to Pay on iPhone, as necessary

  • Respond quickly if a merchant initiates checkout before enabling Tap to Pay on iPhone

  • Help merchants perform checkout even if device configuration is still in progress

  • Present pre-payment actions that affect the final total before checkout completes

Provide Tap to Pay on iPhone as a checkout option whether the feature is enabled or not.

Avoid making merchants wait to use Tap to Pay on iPhone.

Make sure the Tap to Pay on iPhone checkout option is available even if configuration is continuing in the background.

If your app supports multiple payment-acceptance methods, make the Tap to Pay on iPhone button easy to find.

Make it easy for merchants to switch between Tap to Pay on iPhone and the hardware accessories you support.

Design your Tap to Pay on iPhone button to match the other buttons in your app.

Determine the final amount that customers need to pay before merchants initiate the Tap to Pay on iPhone experience.

If you support pre-payment options in your checkout flow, display them before the Tap to Pay on iPhone screen.

Displaying results

Start processing a transaction as soon as possible.

Display a progress indicator while payment is authorizing before you show your transaction result screen.

Clearly display the result of a transaction, whether it’s declined or successful.

Help merchants complete the checkout flow when a payment can’t complete with Tap to Pay on iPhone.

  • Present a new screen or reuse your checkout screen, letting merchants accept an alternate form of payment, like cash

  • Support checkout with a different method, like external hardware or a payment link

  • Relaunch Tap to Pay on iPhone, if a customer has another card they want to try

  • Some regions require Strong Customer Authentication (SCA) support, which means that although the payment card might not require a card PIN during a tap, the bank that issues the card can request a PIN after receiving the transaction processing request. In this scenario, your app may need to display the PIN entry screen instead of the transaction result.

  • In some regions your app may need to meet additional requirements to address the limitations of some cards, such as those in Offline PIN markets. Some PSPs support additional PIN fallback functionality to collect partial data from a tap, letting merchants continue the payment with another method such as a payment link.

If the system returns an error that the merchant must address, display a clear description of the problem and recommend an appropriate resolution.

Make it easy for merchants to get help with issues they can’t resolve.

Additional interactions

Use a generic label in a button that opens the Tap to Pay on iPhone screen to read a payment card when there’s no transaction amount.

If your app supports an independent loyalty card transaction, distinguish this flow from a payment-acceptance flow that uses Tap to Pay on iPhone.

<!-- hig-doctor:canonical-footer -->

For the complete guidance, including worked examples and illustrations, see the canonical page: https://developer.apple.com/design/human-interface-guidelines/tap-to-pay-on-iphone

Source: SKILL.md on GitHub

Third-party checks

No alerts16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill is a documentation resource providing guidance based on Apple's Human Interface Guidelines. It contains only markdown reference files and does not include any executable code or risky behaviors.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 5aac106. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 weeks ago.

Activeupdated 7 months ago

Capability

version
1.0.0

README badge

README badge for raintree-technology/hig-doctor/hig-technologies