App Store 3.1 rejection: Payments

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad apps charging for content, features, subscriptions, goods, or services.

A payment rejection starts with what the customer is buying. Apple’s 3.1 separates digital access, subscriptions, physical goods, and specific exceptions. We’d classify each product before replacing a checkout system.

Map the purchase to the rule

For each offer, write down what the person receives, where they use it, who supplies it, and the storefront involved. Digital functionality generally leads to 3.1.1; recurring access also needs 3.1.2. Physical goods and qualifying services are explained in 3.1.3.

External purchase links have regional and entitlement conditions. The presence of a web checkout in another app doesn’t establish that your app qualifies for the same arrangement.

Test the offer people actually see

Inspect the paywall, web links, store products, receipts, and access after payment. Change the payment route or offer according to the applicable rule, and make all descriptions agree.

Give Apple a reviewable purchase flow and explain any exception with the specific clause and evidence. Include the tested storefront and account conditions. Apple Pay and in-app purchase serve different purposes; sharing the Apple name doesn’t make them interchangeable.

Messages this guide can help with

App Store 3.1 rejection; app store 3.1 denial; Guideline 3.1; Payments

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit your iPhone or iPad app for review