Rejection Decoder
Home / Guidelines / 3.1.2

Guideline 3.1.2 rejection: Subscriptions

What it means, why it happens, and how developers get through it.

Subject line you may see: Guideline 3.1.2 - Business - Payments - Subscriptions

In one line: The paywall or listing does not clearly show what subscribers get and the required subscription information.
Usual next move: Fix, new build, then replySomething in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify.Based on how this guideline is usually resolved, not a prediction for your app.
Paste your rejection to check
On this page: CausesFixReplyReal casesQuestions

Common real causes

How to fix it

  1. Make the billed price the most prominent price
  2. Show title, length, price per period, and what is included
  3. Working Terms and Privacy links on the paywall
  4. Terms of Use link in the App Store description or a custom EULA

What to put in your reply

Thank them and name Guideline 3.1.2.
Say exactly what changed, and in which version and build.
Give a numbered path the reviewer can follow.
Attach proof: screenshots or a screen recording.

The full fill-in-the-blanks reply for 3.1.2 is in the Rescue Kit.

Real cases: others who got 3.1.2

2 public cases: 1 pending, 1 outcome unknown. Outcomes are what the developer posted.

Outcome unknownX · @techback2 · Aug 28, 2026

Paywall rejected: free trial more prominent than the billed amount

Outcome after resubmitting unknown.

PendingX · @Ivan_Borovets · Oct 25, 2026

Rejected for a Terms of Use link missing from the description

Still in the queue after 10 days, as stated. Guideline not named in the post; 3.1.2 is our reading.

Questions developers ask about 3.1.2

What does a Guideline 3.1.2 rejection mean?

The paywall or listing does not clearly show what subscribers get and the required subscription information.

Why do apps get rejected under Guideline 3.1.2?

The most common real causes: free trial more prominent than the billed price; missing Terms of Use link in the description; no clear list of what is included; broken Terms or Privacy links.

How do I fix a Guideline 3.1.2 rejection?

1. Make the billed price the most prominent price. 2. Show title, length, price per period, and what is included. 3. Working Terms and Privacy links on the paywall. 4. Terms of Use link in the App Store description or a custom EULA.

Do I need a new build for Guideline 3.1.2?

Fix, new build, then reply. Something in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify. This is how the guideline is usually resolved, not a prediction for your app.

How should I reply to App Review about Guideline 3.1.2?

Reply in App Store Connect. Thank the reviewer and name Guideline 3.1.2, say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.

Stuck on 3.1.2?

Do it yourself, faster

App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.

Get the kit, $12

Have it written for you

Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.

AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.

Reply service, $29

Related rejections

3.1.1 In-App Purchase required2.1(a) App Completeness2.1(b) In-app purchases not found2.5.2 Downloading or executing code

Source: Apple's App Review Guidelines, section 3.1.2, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.