axiom-payments
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseReal-World Payments (Apple Pay / Wallet / Tap to Pay)
现实场景支付(Apple Pay / Wallet / Tap to Pay)
You MUST use this skill when accepting ANY real-world payment — physical goods, services, donations, ticketing, loyalty cards, contactless card-present, or post-purchase order tracking. NOT for in-app purchase or digital content.
当你处理任何现实场景支付时必须使用本技能——包括实体商品、服务、捐赠、票务、会员卡、非接触式刷卡支付,或售后订单追踪。不适用于应用内购买或数字内容。
When to Use
适用场景
Use this skill when you encounter:
- Adding Apple Pay to an iOS / iPadOS / macOS / Catalyst / visionOS / watchOS app
- Adding Apple Pay to a website (Apple Pay JS or W3C Payment Request API)
- Building Wallet passes (boarding passes, event tickets, coupons, loyalty cards, store cards)
- Accepting contactless card payments on iPhone (Tap to Pay on iPhone / ProximityReader)
- Surfacing post-purchase order tracking in Wallet (Orders in Wallet, FinanceKitUI add-order helpers)
- Issuer or bank card provisioning into Wallet (issuer extensions)
- Apple Pay merchant ID, processing certificate, or merchant identity certificate setup
- Pass Type ID or Order Type ID certificates and PKCS #7 signing chains
- Tap to Pay managed entitlement ()
com.apple.developer.proximity-reader.payment.acceptance - App Review rejections that mention payments, IAP, Apple Pay, Wallet, or Acceptable Use Guidelines
- Domain verification for Apple Pay on the web ()
.well-known/apple-developer-merchantid-domain-association.txt - Sandbox testing with Apple Pay sandbox cards or sandbox tester accounts
遇到以下情况时使用本技能:
- 在iOS / iPadOS / macOS / Catalyst / visionOS / watchOS应用中添加Apple Pay
- 在网站中添加Apple Pay(使用Apple Pay JS或W3C Payment Request API)
- 开发Wallet凭证(登机牌、活动门票、优惠券、会员卡、储值卡)
- 在iPhone上接受非接触式刷卡支付(Tap to Pay on iPhone / ProximityReader)
- 在Wallet中展示售后订单追踪信息(Orders in Wallet、FinanceKitUI添加订单工具)
- 将发卡机构或银行卡添加至Wallet(发卡扩展)
- Apple Pay商户ID、处理证书或商户身份证书的设置
- Pass Type ID或Order Type ID证书及PKCS #7签名链
- Tap to Pay托管权限()
com.apple.developer.proximity-reader.payment.acceptance - App Review因支付、IAP、Apple Pay、Wallet或可接受使用准则相关原因驳回应用
- Apple Pay网页版的域名验证()
.well-known/apple-developer-merchantid-domain-association.txt - 使用Apple Pay沙盒卡片或沙盒测试账户进行沙盒测试
When NOT to Use
不适用场景
| Issue | Correct Skill | Why NOT axiom-payments |
|---|---|---|
| In-app purchase, subscriptions for digital content | axiom-integration | StoreKit 2 / digital goods boundary; see |
| Generic NFC tag reads (Core NFC, non-Wallet) | axiom-integration | Different framework; PassKit NFC is Wallet-specific |
| Code signing / provisioning fundamentals | axiom-security | Code signing is generic; payment certs are added to that flow |
| App Store rejection workflow & appeals | axiom-shipping | Rejection workflow lives there; payment-specific rejection patterns route from there into here |
| HIG cross-cutting design guidance | axiom-design | Apple Pay / Wallet HIG specifics live here, but design overview lives in axiom-design |
| Consumer banking surface (FinanceKit) | Out of scope | This suite uses FinanceKitUI only for Orders. Account aggregation / transaction queries are not covered. |
| PKSecureElementPass, transit cards, car keys | Out of scope | Issuer-controlled, not relevant to merchant developers |
| 问题场景 | 正确技能 | 为何不使用axiom-payments |
|---|---|---|
| 应用内购买、数字内容订阅 | axiom-integration | 属于StoreKit 2/数字商品范畴;详见 |
| 通用NFC标签读取(Core NFC,非Wallet相关) | axiom-integration | 属于不同框架;PassKit NFC是Wallet专属功能 |
| 代码签名/配置基础 | axiom-security | 代码签名是通用操作;支付证书是在此流程之上的额外配置 |
| App Store驳回流程与申诉 | axiom-shipping | 驳回流程归属于该技能;支付相关驳回模式会从该技能跳转至本技能 |
| HIG跨领域设计指南 | axiom-design | Apple Pay/Wallet的HIG细节在此,但设计概述归属于axiom-design |
| 消费者银行界面(FinanceKit) | 超出范围 | 本套件仅将FinanceKitUI用于订单功能。账户聚合/交易查询不在涵盖范围内 |
| PKSecureElementPass、交通卡、车钥匙 | 超出范围 | 由发卡机构控制,与商户开发者无关 |
Quick Reference
快速参考
| Symptom / Task | Reference |
|---|---|
| Should this be Apple Pay or IAP? | See |
| Selling physical goods, services, or donations | See |
| App was rejected for using IAP for physical goods | See |
| Native Apple Pay (iOS / iPadOS / macOS / Catalyst / visionOS / watchOS) | See |
| PassKit / PKPaymentRequest API surface | See |
| Apple Pay on the web (Apple Pay JS or Payment Request API) | See |
| Web ApplePaySession / Payment Request API surface | See |
| Domain verification, merchant identity cert, third-party browser support | See |
| Tap to Pay on iPhone (ProximityReader) | See |
| ProximityReader / PaymentCardReader API surface | See |
| Tap to Pay entitlement stuck in "Submitted" | See |
| Wallet passes (boarding, event ticket, coupon, loyalty, store card) | See |
| pass.json schema, semantic tags, barcodes, NFC payloads | See |
| Pass signing, manifest hashing, PKCS #7 | See |
| Pass updates not arriving (web service / APNs) | See |
| Orders in Wallet, signed order packages, fulfillment status | See |
| Issuer / bank card provisioning extensions | See |
| "No payment sheet appears" / merchant validation 503 / pass won't import | See |
| Sandbox testing failures, prod-vs-sandbox cert mismatch | See |
| Apple Pay button vs Apple Pay Mark confusion | See |
| App Review rejection for Apple Pay / Wallet / Tap to Pay | See |
| 问题/任务 | 参考文档 |
|---|---|
| 应该使用Apple Pay还是IAP? | 详见 |
| 销售实体商品、服务或接受捐赠 | 详见 |
| 应用因使用IAP销售实体商品被驳回 | 详见 |
| 原生Apple Pay(iOS / iPadOS / macOS / Catalyst / visionOS / watchOS) | 详见 |
| PassKit / PKPaymentRequest API接口 | 详见 |
| Apple Pay网页版(Apple Pay JS或Payment Request API) | 详见 |
| 网页版ApplePaySession / Payment Request API接口 | 详见 |
| 域名验证、商户身份证书、第三方浏览器支持 | 详见 |
| Tap to Pay on iPhone(ProximityReader) | 详见 |
| ProximityReader / PaymentCardReader API接口 | 详见 |
| Tap to Pay权限一直处于“已提交”状态 | 详见 |
| Wallet凭证(登机牌、活动门票、优惠券、会员卡、储值卡) | 详见 |
| pass.json schema、语义标签、条形码、NFC payloads | 详见 |
| 凭证签名、清单哈希、PKCS #7 | 详见 |
| 凭证更新未送达(Web服务/APNs) | 详见 |
| Wallet订单、签名订单包、履约状态 | 详见 |
| 发卡机构/银行卡添加扩展 | 详见 |
| “支付面板未显示”/商户验证503错误/凭证无法导入 | 详见 |
| 沙盒测试失败、生产与沙盒证书不匹配 | 详见 |
| Apple Pay按钮与Apple Pay标识混淆 | 详见 |
| App Review因Apple Pay/Wallet/Tap to Pay驳回应用 | 详见 |
Decision Tree
决策树
dot
digraph payments {
"Payments question?" [shape=diamond];
"Apple Pay or IAP?" [shape=diamond];
"Where is the surface?" [shape=diamond];
"What kind of pass?" [shape=diamond];
"Something not working?" [shape=diamond];
"skills/apple-pay-vs-iap.md" [shape=box];
"skills/apple-pay.md" [shape=box];
"skills/apple-pay-web.md" [shape=box];
"skills/tap-to-pay.md" [shape=box];
"skills/wallet-passes.md" [shape=box];
"skills/wallet-orders.md" [shape=box];
"skills/wallet-extensions-ref.md" [shape=box];
"skills/payments-diag.md" [shape=box];
"axiom-integration\n/in-app-purchases.md" [shape=box];
"Payments question?" -> "Apple Pay or IAP?";
"Apple Pay or IAP?" -> "skills/apple-pay-vs-iap.md" [label="boundary unclear"];
"Apple Pay or IAP?" -> "axiom-integration\n/in-app-purchases.md" [label="digital content /\nsubscription for digital"];
"Apple Pay or IAP?" -> "Where is the surface?" [label="real-world payment"];
"Where is the surface?" -> "skills/apple-pay.md" [label="native app"];
"Where is the surface?" -> "skills/apple-pay-web.md" [label="website"];
"Where is the surface?" -> "skills/tap-to-pay.md" [label="contactless on iPhone"];
"Where is the surface?" -> "What kind of pass?" [label="pass / order"];
"Where is the surface?" -> "skills/wallet-extensions-ref.md" [label="card provisioning\n(issuer / bank)"];
"What kind of pass?" -> "skills/wallet-passes.md" [label="boarding / ticket /\ncoupon / loyalty"];
"What kind of pass?" -> "skills/wallet-orders.md" [label="post-purchase\norder tracking"];
"Payments question?" -> "Something not working?";
"Something not working?" -> "skills/payments-diag.md" [label="yes"];
}Simplified routing:
- Is this a digital good or subscription for digital content? → Use instead.
axiom-integration/skills/in-app-purchases.md - Selling physical goods / services / donations, or unsure? →
skills/apple-pay-vs-iap.md - Native Apple Pay (iOS / iPadOS / macOS / Catalyst / visionOS / watchOS)? → +
skills/apple-pay.mdskills/apple-pay-ref.md - Apple Pay on the web? → +
skills/apple-pay-web.mdskills/apple-pay-web-ref.md - Tap to Pay on iPhone (ProximityReader)? → +
skills/tap-to-pay.mdskills/tap-to-pay-ref.md - Wallet passes (ticket / coupon / loyalty / store card)? → +
skills/wallet-passes.mdskills/wallet-passes-ref.md - Orders in Wallet (post-purchase tracking)? →
skills/wallet-orders.md - Issuer / bank card provisioning? →
skills/wallet-extensions-ref.md - Something not working (no sheet / merchant validation fails / pass won't import / Tap to Pay never enables)? →
skills/payments-diag.md
dot
digraph payments {
"Payments question?" [shape=diamond];
"Apple Pay or IAP?" [shape=diamond];
"Where is the surface?" [shape=diamond];
"What kind of pass?" [shape=diamond];
"Something not working?" [shape=diamond];
"skills/apple-pay-vs-iap.md" [shape=box];
"skills/apple-pay.md" [shape=box];
"skills/apple-pay-web.md" [shape=box];
"skills/tap-to-pay.md" [shape=box];
"skills/wallet-passes.md" [shape=box];
"skills/wallet-orders.md" [shape=box];
"skills/wallet-extensions-ref.md" [shape=box];
"skills/payments-diag.md" [shape=box];
"axiom-integration\n/in-app-purchases.md" [shape=box];
"Payments question?" -> "Apple Pay or IAP?";
"Apple Pay or IAP?" -> "skills/apple-pay-vs-iap.md" [label="boundary unclear"];
"Apple Pay or IAP?" -> "axiom-integration\n/in-app-purchases.md" [label="digital content /\nsubscription for digital"];
"Apple Pay or IAP?" -> "Where is the surface?" [label="real-world payment"];
"Where is the surface?" -> "skills/apple-pay.md" [label="native app"];
"Where is the surface?" -> "skills/apple-pay-web.md" [label="website"];
"Where is the surface?" -> "skills/tap-to-pay.md" [label="contactless on iPhone"];
"Where is the surface?" -> "What kind of pass?" [label="pass / order"];
"Where is the surface?" -> "skills/wallet-extensions-ref.md" [label="card provisioning\n(issuer / bank)"];
"What kind of pass?" -> "skills/wallet-passes.md" [label="boarding / ticket /\ncoupon / loyalty"];
"What kind of pass?" -> "skills/wallet-orders.md" [label="post-purchase\norder tracking"];
"Payments question?" -> "Something not working?";
"Something not working?" -> "skills/payments-diag.md" [label="yes"];
}简化路由指引:
- 是否为数字商品或数字内容订阅?→ 请改用
axiom-integration/skills/in-app-purchases.md - 销售实体商品/服务/捐赠,或不确定?→
skills/apple-pay-vs-iap.md - 原生Apple Pay(iOS / iPadOS / macOS / Catalyst / visionOS / watchOS)?→ +
skills/apple-pay.mdskills/apple-pay-ref.md - Apple Pay网页版?→ +
skills/apple-pay-web.mdskills/apple-pay-web-ref.md - Tap to Pay on iPhone(ProximityReader)?→ +
skills/tap-to-pay.mdskills/tap-to-pay-ref.md - Wallet凭证(门票/优惠券/会员卡/储值卡)?→ +
skills/wallet-passes.mdskills/wallet-passes-ref.md - Wallet订单(售后追踪)?→
skills/wallet-orders.md - 发卡机构/银行卡添加?→
skills/wallet-extensions-ref.md - 功能异常(支付面板未显示/商户验证失败/凭证无法导入/Tap to Pay无法启用)?→
skills/payments-diag.md
Cross-Suite Routing
跨套件路由指引
Apple Pay vs IAP boundary (the most common cross-suite question):
- Selling physical goods, services, or donations → stay here ()
skills/apple-pay-vs-iap.md - Selling digital content, premium app features, subscriptions for digital content → use axiom-integration ()
skills/in-app-purchases.md - App was rejected for using the wrong one → then
skills/apple-pay-vs-iap.mdskills/payments-diag.md
Payments + App Review rejection:
- Rejection cites Section 3.1 / 3.2 / Apple Pay AUG → stay here () for the root cause; also invoke axiom-shipping (
skills/payments-diag.md) for appeal workflowskills/app-store-diag.md
Payments + cert management:
- Merchant Identity Certificate, Pass Type ID Certificate, Order Type ID Certificate, Payment Processing Certificate — operational discipline → stay here
- Generic Keychain export / mechanics → also invoke axiom-security (
.p12)skills/keychain-ref.md - Tap to Pay managed entitlement → stay here (); generic managed-capability mental model → axiom-security (
skills/tap-to-pay.md)skills/code-signing.md
Payments + Xcode capability / provisioning:
- Apple Pay capability checkbox in Xcode, merchant ID selection, Tap to Pay entitlement plumbing in the provisioning profile → also invoke axiom-build for capability/profile mechanics; payment-specific guidance stays here
Payments + HIG:
- Apple Pay button vs Apple Pay Mark, Wallet pass design specs, Tap to Pay button label → stay here
- Cross-cutting design context → also invoke axiom-design ()
skills/hig.md
Payments + Catalyst / macOS:
- Apple Pay on Mac and Catalyst (window requirement, web security model, static merchant validation URL) → stay here (Catalyst section)
skills/apple-pay.md - Generic Catalyst patterns → axiom-macos
Payments + Apple Watch:
- WKInterfacePaymentButton, watchOS payment delegate flow → stay here (watchOS section)
skills/apple-pay-ref.md - Generic watchOS patterns → axiom-watchos
Apple Pay与IAP的边界(最常见的跨套件问题):
- 销售实体商品、服务或接受捐赠 → 继续使用本套件()
skills/apple-pay-vs-iap.md - 销售数字内容、应用高级功能、数字内容订阅 → 使用axiom-integration()
skills/in-app-purchases.md - 应用因使用错误支付方式被驳回 → 先查看,再查看
skills/apple-pay-vs-iap.mdskills/payments-diag.md
支付+App Review驳回:
- 驳回理由涉及第3.1/3.2条/Apple Pay可接受使用准则 → 继续使用本套件()排查根本原因;同时调用axiom-shipping(
skills/payments-diag.md)处理申诉流程skills/app-store-diag.md
支付+证书管理:
- 商户身份证书、Pass Type ID证书、Order Type ID证书、支付处理证书的操作规范 → 继续使用本套件
- 通用Keychain导出/操作机制 → 同时调用axiom-security(
.p12)skills/keychain-ref.md - Tap to Pay托管权限 → 继续使用本套件();通用托管能力相关概念请查看axiom-security(
skills/tap-to-pay.md)skills/code-signing.md
支付+Xcode功能/配置:
- Xcode中的Apple Pay功能勾选框、商户ID选择、配置文件中的Tap to Pay权限设置 → 同时调用axiom-build处理功能/配置机制;支付相关指引继续使用本套件
支付+HIG:
- Apple Pay按钮与Apple Pay标识、Wallet凭证设计规范、Tap to Pay按钮标签 → 继续使用本套件
- 跨领域设计背景 → 同时调用axiom-design()
skills/hig.md
支付+Catalyst/macOS:
- Mac与Catalyst上的Apple Pay(窗口要求、网页安全模型、静态商户验证URL) → 继续使用本套件(的Catalyst章节)
skills/apple-pay.md - 通用Catalyst模式 → 查看axiom-macos
支付+Apple Watch:
- WKInterfacePaymentButton、watchOS支付委托流程 → 继续使用本套件(的watchOS章节)
skills/apple-pay-ref.md - 通用watchOS模式 → 查看axiom-watchos
Anti-Rationalization
常见误区纠正
| Thought | Reality |
|---|---|
| "We sell physical stuff but we'll use IAP — easier integration" | Guaranteed App Review rejection (Section 3.1.1 / 3.1.3(e)). Use Apple Pay for physical goods, services, donations. |
| "Our app is digital content, we'll use Apple Pay because IAP fees are higher" | Guaranteed App Review rejection. Digital content + subscriptions for digital content must use IAP. |
| "I'll just embed our PSP's raw card form on the web — it's faster" | Acceptable Use Guidelines violate parity rule. If you accept any other payment method on the web, you must offer Apple Pay at least as prominently. |
| "Tap to Pay just needs a capability checkbox like other features" | Tap to Pay uses a managed entitlement requested via a separate form. The Xcode capability flow doesn't apply. Two-step request (dev → distribution); rejection or "Submitted" stalls add 1–4 weeks per loop. |
| "We'll roll our own pass signing — it's just zip + sign" | PKCS #7 detached signature, manifest hashing, WWDR Intermediate cert, S/MIME signing-time, PEM/DER format gotchas — most signing failures originate from rolled-from-scratch implementations. Use a server library. |
| "The Apple Pay Mark is just a button graphic" | The Mark is "Apple Pay accepted" signage — never tappable. The Button is API-provided and initiates payment. Using the Mark as a button is an HIG violation and a known conversion killer. |
| "Production cards will work the same as sandbox cards" | Sandbox transactions decline pre-fulfillment by design. Production transactions need production keys + activated certs. Test on real devices with real cards before launch. |
| "Apple Pay merchant ID expires every year" | Merchant IDs never expire. Payment Processing Certificates expire after 25 months. These are different things. |
| "I can call merchant validation from the browser" | The browser must never call |
| "FinanceKit will let our app see the user's bank transactions" | Out of scope for this suite. FinanceKit consumer banking surface is not covered. We use FinanceKitUI only for the order-add helpers. |
| 错误想法 | 实际情况 |
|---|---|
| "我们销售实体商品,但用IAP更易集成" | 必然会被App Review驳回(第3.1.1/3.1.3(e)条)。实体商品、服务、捐赠请使用Apple Pay。 |
| "我们的应用是数字内容,用Apple Pay是因为IAP手续费更高" | 必然会被App Review驳回。数字内容+数字内容订阅必须使用IAP。 |
| "我直接在网页上嵌入支付服务商的原生卡片表单——这样更快" | 违反可接受使用准则的对等规则。如果网页接受其他支付方式,必须至少同等突出地提供Apple Pay选项。 |
| "Tap to Pay和其他功能一样只需勾选功能框" | Tap to Pay需通过单独表单申请托管权限。Xcode功能流程不适用此操作。需分两步申请(开发者→分发);驳回或“已提交”状态的停滞每次循环会增加1-4周时间。 |
| "我们自己实现凭证签名——只是压缩+签名而已" | PKCS #7分离签名、清单哈希、WWDR中级证书、S/MIME签名时间、PEM/DER格式陷阱——大多数签名失败源于从零开始的自定义实现。请使用服务器库。 |
| "Apple Pay标识只是个按钮图标" | 标识是“接受Apple Pay”的标识——绝不可点击。按钮是由API提供的,用于发起支付。将标识用作按钮违反HIG规范,且会严重影响转化率。 |
| "生产环境卡片和沙盒卡片表现一致" | 沙盒交易默认在履约前拒绝。生产环境交易需要生产密钥+激活的证书。上线前请用真实设备和真实卡片测试。 |
| "Apple Pay商户ID每年过期" | 商户ID永不过期。支付处理证书有效期为25个月。二者是不同的事物。 |
| "我可以从浏览器调用商户验证" | 浏览器绝不能调用 |
| "FinanceKit能让我们的应用查看用户的银行交易" | 超出本套件范围。FinanceKit消费者银行界面不在涵盖范围内。我们仅将FinanceKitUI用于添加订单的工具。 |
Out of Scope
不涵盖范围
This suite intentionally does not cover:
- In-App Purchase (StoreKit 2) — Use and
axiom-integration/skills/in-app-purchases.md. The boundary rule lives inaxiom-integration/skills/storekit-ref.md.skills/apple-pay-vs-iap.md - FinanceKit consumer banking (account aggregation, transaction queries) — not covered. We only use FinanceKitUI for order-add buttons.
- PKSecureElementPass, transit cards, car keys — issuer-controlled Wallet surfaces, not merchant-developer territory.
- Tap to Present ID () — uses ProximityReader but for identity verification, not payment. Brief cross-ref appears in
MobileDocumentReader; identity-verification UX as a whole is axiom-integration territory if it lands anywhere.skills/tap-to-pay-ref.md - Generic NFC reads (Core NFC) — different framework. PassKit NFC is Wallet-specific (loyalty / contactless ticket / boarding).
本套件明确不涵盖以下内容:
- 应用内购买(StoreKit 2)——请使用和
axiom-integration/skills/in-app-purchases.md。边界规则详见axiom-integration/skills/storekit-ref.md。skills/apple-pay-vs-iap.md - FinanceKit消费者银行功能(账户聚合、交易查询)——不涵盖。我们仅将FinanceKitUI用于添加订单按钮。
- PKSecureElementPass、交通卡、车钥匙——由发卡机构控制的Wallet界面,不属于商户开发者范畴。
- Tap to Present ID()——使用ProximityReader但用于身份验证,而非支付。
MobileDocumentReader中有简要交叉引用;身份验证整体UX若有归属则属于axiom-integration范畴。skills/tap-to-pay-ref.md - 通用NFC读取(Core NFC)——属于不同框架。PassKit NFC是Wallet专属功能(会员卡/非接触式门票/登机牌)。
Example Invocations
调用示例
User: "Should I use Apple Pay or IAP for my hotel-booking app?"
→ See
skills/apple-pay-vs-iap.mdUser: "How do I set up Apple Pay in my iOS app?"
→ See
skills/apple-pay.mdUser: "What's the structure of PKPaymentRequest?"
→ See
skills/apple-pay-ref.mdUser: "Apple Pay on my website doesn't show the button in Chrome"
→ See
skills/apple-pay-web.mdUser: "Domain verification keeps failing"
→ See
skills/payments-diag.mdUser: "I want to add Tap to Pay on iPhone to my point-of-sale app"
→ See
skills/tap-to-pay.mdUser: "My Tap to Pay entitlement has been Submitted for two weeks"
→ See and
skills/tap-to-pay.mdskills/payments-diag.mdUser: "How do I build a Wallet pass for my event tickets?"
→ See
skills/wallet-passes.mdUser: "My .pkpass file won't import — Wallet says invalid"
→ See
skills/payments-diag.mdUser: "I want order tracking to appear in Wallet after Apple Pay checkout"
→ See
skills/wallet-orders.mdUser: "App Review rejected my app for using IAP for restaurant delivery"
→ See then
skills/apple-pay-vs-iap.mdskills/payments-diag.mdUser: "How does Apple Pay differ from In-App Purchase?"
→ See
skills/apple-pay-vs-iap.mdUser: "Implementing card provisioning for our bank's iOS app"
→ See
skills/wallet-extensions-ref.md用户:"我的酒店预订应用应该用Apple Pay还是IAP?"
→ 详见
skills/apple-pay-vs-iap.md用户:"如何在我的iOS应用中设置Apple Pay?"
→ 详见
skills/apple-pay.md用户:"PKPaymentRequest的结构是什么?"
→ 详见
skills/apple-pay-ref.md用户:"我的网站上的Apple Pay在Chrome中不显示按钮"
→ 详见
skills/apple-pay-web.md用户:"域名验证一直失败"
→ 详见
skills/payments-diag.md用户:"我想在我的POS应用中添加Tap to Pay on iPhone"
→ 详见
skills/tap-to-pay.md用户:"我的Tap to Pay权限已提交两周"
→ 详见和
skills/tap-to-pay.mdskills/payments-diag.md用户:"如何为我的活动门票开发Wallet凭证?"
→ 详见
skills/wallet-passes.md用户:"我的.pkpass文件无法导入——Wallet提示无效"
→ 详见
skills/payments-diag.md用户:"我想在Apple Pay结账后在Wallet中显示订单追踪"
→ 详见
skills/wallet-orders.md用户:"App Review因我用IAP处理餐厅配送驳回了我的应用"
→ 先查看,再查看
skills/apple-pay-vs-iap.mdskills/payments-diag.md用户:"Apple Pay和应用内购买有什么区别?"
→ 详见
skills/apple-pay-vs-iap.md用户:"为我们银行的iOS应用实现卡片添加功能"
→ 详见
skills/wallet-extensions-ref.mdResources
参考资源
WWDC: 2020-10662, 2021-10092, 2022-10041, 2023-10114, 2024-10108
Tech Talks: 111381 (Apple Pay on the Web), 110336 (Implementing Apple Pay Orders)
MIG: Apple Pay Merchant Integration Guide (2026 edition) — operational spine, cited throughout this suite
Docs: /passkit, /applepayontheweb, /proximityreader, /walletpasses, /design/human-interface-guidelines/apple-pay, /design/human-interface-guidelines/wallet, /apple-pay/acceptable-use-guidelines-for-websites
App Review: Section 3.1 (In-App Purchase), Section 3.1.3(e) (Goods and Services Outside of the App), Section 3.2 (Other Business Model Issues), Section 4.9 (Apple Pay)
Skills: axiom-integration (in-app-purchases, storekit-ref), axiom-shipping (app-store-diag, app-review-guidelines), axiom-security (keychain-ref, code-signing), axiom-design (hig, hig-ref), axiom-macos
WWDC:2020-10662, 2021-10092, 2022-10041, 2023-10114, 2024-10108
Tech Talks:111381(Apple Pay网页版), 110336(实现Apple Pay订单)
MIG:Apple Pay Merchant Integration Guide(2026版)——操作核心文档,本套件全程引用
官方文档:/passkit, /applepayontheweb, /proximityreader, /walletpasses, /design/human-interface-guidelines/apple-pay, /design/human-interface-guidelines/wallet, /apple-pay/acceptable-use-guidelines-for-websites
App Review规则:第3.1条(应用内购买)、第3.1.3(e)条(应用外商品与服务)、第3.2条(其他商业模式问题)、第4.9条(Apple Pay)
相关技能:axiom-integration(in-app-purchases, storekit-ref)、axiom-shipping(app-store-diag, app-review-guidelines)、axiom-security(keychain-ref, code-signing)、axiom-design(hig, hig-ref)、axiom-macos