Index of every page on this site: llms.txt
All skills
rshankras avatar

/external-purchases

@f958982
Run it yourself

US web checkout for digital goods — on the US storefront, buttons, external links and calls to action need no entitlement (Guideline 3.1.1(a)); 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.

Use this Skill: https://skilld.dev/gh/rshankras/claude-code-apple-skills/external-purchases

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈113 tokens for metadata: the name and description. ≈1.3k when used: this file.

Description uses 5.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈451 characters, or 5.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

External Purchases (US Web Checkout)

On the US storefront, apps may include buttons, external links, and other calls to action to a web checkout for digital goods, with no entitlement required (Guideline 3.1.1(a), as of the 2026-10-16 update). 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 guideline text, the commission rate, and the litigation status have each changed more than once. The commission figures and litigation notes come from court orders, not from the App Review Guidelines. 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 (links shown outside the US storefront without an entitlement)

The rules of the road

Guideline 3.1.1(a) splits the world into three cases:

Storefront External purchase buttons / links / calls to action
United States Allowed. No entitlement required.
Specific other regions (where Apple offers it) Allowed only with a StoreKit External Purchase Link Entitlement (or, where permitted, a Music Streaming Services Entitlement), linking to a permitted destination. Approved destinations vary by region and the entitlement is limited to certain platforms.
All other storefronts Prohibited. Apps and their metadata may not direct customers to purchasing mechanisms other than IAP.
  • Gate by storefront. A US-only checkout link must not appear on other storefronts. Read Storefront.current (StoreKit 2) and show the link only where it is allowed.
  • Outside the US, follow the entitlement's terms: the entitlement plus its Info.plist declaration, and the ExternalPurchaseLink / disclosure sheet where the entitlement requires it. Don't extrapolate US rules to EU, JP, KR, or other regions.
  • Don't dark-pattern the IAP option away if you keep both. Misleading marketing, scams, or fraud around external purchase links can get the app removed and you expelled from the Developer Program (3.1.1(a)).
  • 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

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

Output Format

Status: storefront gating correct (US: no entitlement needed; entitlement regions: entitlement +
permitted destination; elsewhere: no link)? ·
link-out service centralized? · CommissionPolicy flippable? · funnel analytics live?
Verdict + the one next step.

References

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts10d3 checks · Risk SAFE
  • Gen Agent Trust Hub10d

    This skill provides architectural guidance and compliance rules for implementing external web checkout links for digital goods on the US App Store. It is purely informational and contains no malicious code or instructions.

  • Socket11d

    No alerts

  • Snyk11d

    Risk: LOW · No issues

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

Last checked against GitHub last week.

Activeupdated 2 weeks ago
What it can do
Reads files Edits files
last_verified
2026-11-08
review_by
2027-06-22
All 5 allowed tools
ReadWriteEditGlobGrep

README badge

README badge for rshankras/claude-code-apple-skills/external-purchases