How to explain the paywall in Review Notes
When reviewers hit a paywall, notes must spell out how a demo account reaches purchased or unlocked state. “Full feature access” alone leaves them on the payment screen.
Goee · Apple listing · Google listing · Guide library · Telegram @hagee66
Reviewers do not have your member password and are not required to pay for your app. Notes should let a stranger follow text past the paywall.
At least four lines in the notes
- Which demo account to use and whether subscription or IAP is already enabled on it.
- If purchase is required, where Sandbox or test billing lives on this build. Do not cite expired promo prices.
- Where verification codes go and whether they expire during review. See demo accounts must not expire.
- What they should see right after login to prove they are past the paywall.
Sentences that do not work
“Please experience full features” or “check the member center” are not paths. When the reviewer is stuck on a price screen, those lines are empty.
Goee can draft this block from your build. You keep your developer account; we join as invited members only—no passwords or signing keys. Approval is decided by Apple and Google; Goee does not promise approval and does not publish pricing on the site.
FAQ
Q: Can we give reviewers one universal password?
A: Do not use a real production user password. Use a review-only account with fixed entitlements that will not expire during review, and state what it can see in the notes.
Q: Account deletion is only behind the paywall—what now?
A: Put paywall steps and the delete-account tap path in the same note. See account deletion requirements.