Skip to content
cccskills
FreePublished on GitHub

external-purchases

US web checkout via the StoreKit External Purchase Link entitlement — currently 0% Apple commission (litigation ongoing), how to ship it safely, and how to architect for a commission flip so a future ruling is a config change, not a rewrite. Use when adding external purchase links, weighing web checkout vs IAP, or planning US-storefront pricing strategy.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md4.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

External Purchases (US Web Checkout)

On the US storefront, apps may link out to a web checkout for digital goods using the StoreKit External Purchase Link entitlement — and as of mid-2026, court orders have Apple's commission on those purchases at 0%, with the fee case still moving through district court. This is the largest indie revenue unlock of the era, and it is reversible by a ruling — so the engineering rule is: ship it now, architect it so a commission can be flipped on later.

Verify current state before relying on this: the entitlement terms, the commission rate, and the litigation status have each changed more than once. Treat every number here as "true as of 2026-07, re-check."

When This Skill Activates

  • "Add a web checkout / Stripe / external purchase link" for digital goods
  • Deciding IAP vs web checkout for a US-heavy revenue base
  • The store-growth audit flags P8.4
  • Reviewing an app whose external links might be non-compliant (wrong storefront, no entitlement)

The rules of the road

  • US storefront only — elsewhere Guideline 3.1.1 still applies (EU/JP/KR have separate entitlements/terms; don't extrapolate from the US).
  • Entitlement required: com.apple.developer.storekit.external-purchase-link + matching Info.plist declaration — a bare Link("Buy", …) without it is still a rejection (see app-store/rejection-handler §3.1.1).
  • Present the link per the entitlement's UI terms (StoreKit's ExternalPurchaseLink / disclosure sheet where required). Don't dark-pattern the IAP option away if you keep both.
  • Purchases made on the web are your customer relationship — payment processor, refunds, taxes; Apple's merchant-of-record role no longer applies.

Architecture: the commission flip

Design so that a future "Apple takes N% of external purchases initiated in-app" ruling changes a config value, not your codebase:

  • ✅ Route every in-app-initiated web checkout through one link-out service that stamps the session (source=app, timestamp, storefront) — web-organic checkouts stay unstamped. If a commission returns, it applies to a knowable, logged subset.
  • ✅ Keep a single CommissionPolicy (remote-configurable): rate, applies_to, effective_date. Report/accrue against it from day one — at 0% it's just a counter.
  • ✅ Log day-one analytics: link taps → checkout starts → completions, vs the IAP funnel. The conversion drop through a web checkout (Apple's sheet, Safari hop, payment form) is real; whether 0% beats IAP's frictionless 85–70% is an empirical per-app question.
  • ❌ Scattering openURL("https://…/buy") calls through features — un-auditable, un-flippable.
  • ❌ Ripping out StoreKit. Keep IAP as a fallback path (non-US storefronts still need it, and some US users convert better in-sheet).

Decision sketch

SituationLean
Subscriptions, US-heavy, ARPU high enough to absorb processor fees + your own supportWeb checkout for new subs; keep IAP for the rest of world
Impulse-priced consumables/unlocksIAP — checkout friction eats more than 15–30% commission
Existing subscriber base on IAPDon't force-migrate; offer web at renewal decision points
B2B/prosumer, invoicing needsWeb checkout regardless of commission math

Output Format

Status: entitlement present? · storefront scope correct (US-only gating)? ·
link-out service centralized? · CommissionPolicy flippable? · funnel analytics live?
Verdict + the one next step.

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Run a structured accessibility audit on an iOS/macOS app — automated XCUITest audits, Accessibility Inspector, manual VoiceOver/Dynamic Type passes, and App Store Accessibility Nutrition Label evaluation. Use before release, when preparing Nutrition Label declarations, or for EU Accessibility Act compliance.

The English summary is being prepared. Showing the original description.

rshankras/claude-code-apple-skills814Updated Jul 24, 2026

Generate accessibility infrastructure for VoiceOver, Dynamic Type, and accessibility features. Use when improving app accessibility, adding accessibility labels and hints, or auditing compliance.

The English summary is being prepared. Showing the original description.

rshankras/claude-code-apple-skills814Updated Jul 24, 2026

Generates an Apple-compliant account deletion flow with multi-step confirmation UI, optional data export, configurable grace period, Keychain cleanup, and server-side deletion request. Use when user needs account deletion, right-to-delete, or Apple App Review compliance for account removal.

The English summary is being prepared. Showing the original description.

rshankras/claude-code-apple-skills814Updated Jul 24, 2026

Privacy-preserving ad measurement with AdAttributionKit (SKAdNetwork's successor) — install and re-engagement attribution, conversion-value strategy under crowd anonymity, and end-to-end postback testing. Use when running paid acquisition beyond Apple Ads, measuring re-engagement campaigns, designing conversion values, or migrating from SKAdNetwork.

The English summary is being prepared. Showing the original description.

rshankras/claude-code-apple-skills814Updated Jul 24, 2026

AlarmKit integration for scheduling alarms and timers with custom UI, Live Activities, and snooze support. Use when implementing alarm or timer features in iOS 26+ apps.

The English summary is being prepared. Showing the original description.

rshankras/claude-code-apple-skills814Updated Jul 24, 2026

Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.

The English summary is being prepared. Showing the original description.

rshankras/claude-code-apple-skills814Updated Jul 24, 2026

See all skills by rshankras

Report a problem with this skill