Use when accepting ANY real-world payment — Apple Pay, Wallet passes, Tap to Pay, Orders in Wallet. NOT in-app purchase / digital content (use axiom-integration). Covers entitlements, certs, signing, App Review payment rules.
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Medium
Suggest reviewing before use
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.
Use this skill when you encounter:
com.apple.developer.proximity-reader.payment.acceptance).well-known/apple-developer-merchantid-domain-association.txt)| Issue | Correct Skill | Why NOT axiom-payments |
|---|---|---|
| In-app purchase, subscriptions for digital content | axiom-integration | StoreKit 2 / digital goods boundary; see axiom-integration (skills/in-app-purchases.md) |
| 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 |
| Symptom / Task | Reference |
|---|---|
| Should this be Apple Pay or IAP? | See skills/apple-pay-vs-iap.md |
| Selling physical goods, services, or donations | See skills/apple-pay-vs-iap.md |
| App was rejected for using IAP for physical goods | See skills/apple-pay-vs-iap.md |
| Native Apple Pay (iOS / iPadOS / macOS / Catalyst / visionOS / watchOS) | See skills/apple-pay.md |
| PassKit / PKPaymentRequest API surface | See skills/apple-pay-ref.md |
| Apple Pay on the web (Apple Pay JS or Payment Request API) | See skills/apple-pay-web.md |
| Web ApplePaySession / Payment Request API surface | See skills/apple-pay-web-ref.md |
| Domain verification, merchant identity cert, third-party browser support | See skills/apple-pay-web.md |
| Tap to Pay on iPhone (ProximityReader) | See skills/tap-to-pay.md |
| ProximityReader / PaymentCardReader API surface | See skills/tap-to-pay-ref.md |
| Tap to Pay entitlement stuck in "Submitted" | See skills/tap-to-pay.md |
| Wallet passes (boarding, event ticket, coupon, loyalty, store card) | See skills/wallet-passes.md |
| pass.json schema, semantic tags, barcodes, NFC payloads | See skills/wallet-passes-ref.md |
Poster generic style, featured actions, new barcode types OS27 | See skills/wallet-passes-ref.md |
| Pass Designer app, Pass Builder server package | See skills/wallet-passes-ref.md |
Customer engagement on a paired device (CustomerEngagementSession) OS27 | See skills/tap-to-pay-ref.md |
| Pass signing, manifest hashing, PKCS #7 | See skills/wallet-passes.md |
| Pass updates not arriving (web service / APNs) | See skills/wallet-passes.md |
| Orders in Wallet, signed order packages, fulfillment status | See skills/wallet-orders.md |
| Issuer / bank card provisioning extensions | See skills/wallet-extensions-ref.md |
| "No payment sheet appears" / merchant validation 503 / pass won't import | See skills/payments-diag.md |
| Sandbox testing failures, prod-vs-sandbox cert mismatch | See skills/payments-diag.md |
| Apple Pay button vs Apple Pay Mark confusion | See skills/apple-pay.md |
| App Review rejection for Apple Pay / Wallet / Tap to Pay | See skills/payments-diag.md |
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:
axiom-integration/skills/in-app-purchases.md instead.skills/apple-pay-vs-iap.mdskills/apple-pay.md + skills/apple-pay-ref.mdskills/apple-pay-web.md + skills/apple-pay-web-ref.mdskills/tap-to-pay.md + skills/tap-to-pay-ref.mdskills/wallet-passes.md + skills/wallet-passes-ref.mdskills/wallet-orders.mdskills/wallet-extensions-ref.mdskills/payments-diag.mdApple Pay vs IAP boundary (the most common cross-suite question):
skills/apple-pay-vs-iap.md)skills/in-app-purchases.md)skills/apple-pay-vs-iap.md then skills/payments-diag.mdPayments + App Review rejection:
skills/payments-diag.md) for the root cause; also invoke axiom-shipping (skills/app-store-diag.md) for appeal workflowPayments + cert management:
.p12 mechanics → also invoke axiom-security (skills/keychain-ref.md)skills/tap-to-pay.md); generic managed-capability mental model → axiom-security (skills/code-signing.md)Payments + Xcode capability / provisioning:
Payments + HIG:
skills/hig.md)Payments + Catalyst / macOS:
skills/apple-pay.md Catalyst section)Payments + Apple Watch:
skills/apple-pay-ref.md watchOS section)| 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 paymentSession. Server-only call using two-way TLS with the merchant identity cert. Calling from the browser leaks the cert. |
| "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. |
This suite intentionally does not cover:
axiom-integration/skills/in-app-purchases.md and axiom-integration/skills/storekit-ref.md. The boundary rule lives in skills/apple-pay-vs-iap.md.MobileDocumentReader) — uses ProximityReader but for identity verification, not payment. Brief cross-ref appears in skills/tap-to-pay-ref.md; identity-verification UX as a whole is axiom-integration territory if it lands anywhere.User: "Should I use Apple Pay or IAP for my hotel-booking app?"
→ See skills/apple-pay-vs-iap.md
User: "How do I set up Apple Pay in my iOS app?"
→ See skills/apple-pay.md
User: "What's the structure of PKPaymentRequest?"
→ See skills/apple-pay-ref.md
User: "Apple Pay on my website doesn't show the button in Chrome"
→ See skills/apple-pay-web.md
User: "Domain verification keeps failing"
→ See skills/payments-diag.md
User: "I want to add Tap to Pay on iPhone to my point-of-sale app"
→ See skills/tap-to-pay.md
User: "My Tap to Pay entitlement has been Submitted for two weeks"
→ See skills/tap-to-pay.md and skills/payments-diag.md
User: "How do I build a Wallet pass for my event tickets?"
→ See skills/wallet-passes.md
User: "My .pkpass file won't import — Wallet says invalid"
→ See skills/payments-diag.md
User: "I want order tracking to appear in Wallet after Apple Pay checkout"
→ See skills/wallet-orders.md
User: "App Review rejected my app for using IAP for restaurant delivery"
→ See skills/apple-pay-vs-iap.md then skills/payments-diag.md
User: "How does Apple Pay differ from In-App Purchase?"
→ See skills/apple-pay-vs-iap.md
User: "Implementing card provisioning for our bank's iOS app"
→ See skills/wallet-extensions-ref.md
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
ea3be7c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.