apple-design-commerce
Design Apple Pay checkout, in-app purchases and subscriptions, Wallet passes, or Tap to Pay on iPhone merchant experiences using Apple’s commerce HIG guidance.
SKILL.mdskills/design/apple-design-commerce/SKILL.md
GitHubApple Commerce and Wallet UX
Apply the skill
Identify the transaction type, customer or merchant role, supported regions, and the existing payment mechanism. Read the applicable commerce reference. Treat the distinction between payment products as a design starting point; verify current App Store and payment rules for the actual distribution context before making eligibility claims.
Make the item, total price, recurrence, trial conversion, and fulfillment understandable before commitment. Design pending, success, failure, cancellation, recovery, and restoration or management states where applicable. Preserve system confirmation surfaces and accurate branding.
For passes, specify issuance, addition, update, expiration, and access. For merchant acceptance, design preparation and recovery without making a customer wait through avoidable setup. A prototype must not perform a live payment or change a subscription.
Topic references
Select the topic that matches the design decision; do not load this entire list by default.
Source use
These references are original operational summaries of Apple’s public HIG, checked on 2026-09-08. They are guidance for design decisions, not a reproduced manual or a guarantee of App Store acceptance.
Read only the topic references relevant to the current task. Each links to the full official page. Consult that page for exact specifications, platform exceptions, assets, and version-sensitive behavior; use current official developer documentation for APIs and availability. If live documentation is unavailable, state the snapshot date and identify assumptions instead of inventing current requirements.
The user’s product goals, selected framework, and authorized scope remain controlling. Distinguish a source recommendation from a hard platform requirement and from your own proposed implementation.