ShaunSocial docs ShaunSocial mobile app guide
Version 1.5.6
  • 1.5.6 (this version)

ShaunSocial mobile app guide 1.5.6 / In-app purchases

App Store (iOS)

AdminDeveloper

This page takes you from nothing to members buying eWallet credits in your iOS app through the App Store: the Paid Apps agreement, the in-app purchases and their review screenshots, the key your site needs to check every purchase, refund notices, sandbox test accounts, the AdminCP, testing and refunds, purchases and revenue, the first submission and what to do when a purchase does not work. Read In-app purchases first: it explains how buying credits works and what to prepare for both stores. Each section says who does it: Admin for the site owner, who also owns the Google Play and App Store accounts, and Developer for the person who builds and tests the app.

iOS: the Paid Apps agreement#

Admin

Last updated: 2026-11-19 · v1.5.6

Read from the code; store steps not run

The app's behaviour on this page was read from the code of the ShaunSocial app 1.5.6. The steps in App Store Connect were not run for this guide, and those consoles rename their menus from time to time: look for the same words if a menu is named a little differently. The official help pages are listed at the end (Official store help pages).

In App Store Connect open Business. The Paid Apps agreement must be Active, with your bank account and tax forms filled in. Until it is, the App Store returns no products and the app shows "Product unavailable".

iOS: create the in-app purchases in App Store Connect#

Admin

Last updated: 2026-11-19 · v1.5.6

  1. Open Apps → your app → Monetization → In-App Purchases and click +.
  2. Choose the type Consumable, enter a reference name (for example "100 credits") and the Product ID you planned, for example wallet_credit_100, then Create.
  3. Fill in the availability, the price, an App Store localization for every language of your app (display name and description) and the review screenshot (see Review screenshots).

    What you should see: the status becomes Ready to Submit.

The display name may have up to 35 characters and the description up to 55; count before saving, longer languages run out quickly. Your first in-app purchases are reviewed together with an app version (see Submit the first version with in-app purchases). Changes can take up to an hour to reach the test environment.

iOS: review screenshots#

Developer

Last updated: 2026-11-19 · v1.5.6

Every in-app purchase needs its own screenshot under Review Information → Screenshot. Apple asks for "a screenshot of the In-App Purchase that clearly shows the item or service being offered". Only the reviewers see it. A good choice is Apple's own payment sheet, because it shows the product's name and price exactly as the store sells them. Nothing is charged: a TestFlight build buys in the test environment.

  1. Check first: the in-app purchase has an App Store localization, the deposit package on the site the build uses carries the same Apple product Id, and an hour has passed since the last product change.
  2. On a real iPhone, install the TestFlight build and sign in as described in Sandbox test accounts. Use a neutral Apple account: its e-mail address shows on the sheet.
  3. Open the app, sign in as a member, open the wallet → Add fund, choose a package and tap Proceed to add ….
  4. When Apple's payment sheet has finished sliding up (product name, price, account and a test notice), take the screenshot with the side button and volume up. Then cancel, or buy: it is free and credits the test member.
  5. Repeat for every package, one screenshot per in-app purchase.
  6. Move the original files to your computer with AirDrop or a cable. Do not send them through a chat app: they shrink the picture, and App Store Connect then answers "The dimensions of one or more screenshots are wrong."
  7. Upload each screenshot to its own in-app purchase; naming the files after the packages avoids mix-ups.

Accepted iPhone portrait sizes include 1320 × 2868, 1290 × 2796, 1284 × 2778 and 1242 × 2688 pixels. If a screenshot has the right shape but a smaller size, enlarge it without stretching or cropping. Without a real iPhone, a screenshot of the Add fund to wallet screen with the package selected also shows the item being offered.

iOS: the In-App Purchase key#

Admin

Last updated: 2026-11-19 · v1.5.6

  1. In App Store Connect open Users and Access → Integrations → In-App Purchase → Generate In-App Purchase Key, give it a name and click Generate.
  2. Download the .p8 file. Apple lets you download it only once: keep it somewhere safe and private.
  3. Note the key's Key ID and the Issuer ID shown on the same page.
Use the In-App Purchase key

Not the push notification (APNs) key and not an App Store Connect API key: with those, Apple refuses every check.

iOS: refund notices (App Store Server Notifications)#

Admin

Last updated: 2026-11-19 · v1.5.6

Apple tells your site about refunds by sending a notice to an address on your site.

  1. In App Store Connect open Apps → your app → App Information → App Store Server Notifications.
  2. Under Production Server URL click Set Up URL, enter https://example.com/api/wallet/apple_notification with your own domain (and the folder, if your site is installed in one), and choose Version 2.
  3. Under Sandbox Server URL enter the same address, also Version 2, so refunds of test purchases reach your site too.

While your site is in maintenance mode (see Switch on maintenance mode), it refuses these notices like any other app request; Apple tries again later. What your site does with a refund is in Refunds and other events.

iOS: sandbox test accounts#

AdminDeveloper

Last updated: 2026-11-19 · v1.5.6

Builds run from Xcode and TestFlight builds always buy in Apple's test environment (the sandbox): nothing is charged. A sandbox account is only needed for clean, repeatable tests.

Create a sandbox account (Admin)#

  1. In App Store Connect open Users and Access → Sandbox and click + (the first time: Create Test Accounts).
  2. Enter a name, an e-mail address, a strong password and the App Store country or region (it sets the price currency), then Create.

The e-mail address must never have been used for an Apple account. Apple sends no confirmation e-mail, so the mailbox does not have to exist. Name, e-mail and password cannot be changed later, and a sandbox account works only for the apps of the team that created it.

On an iPhone with a TestFlight build (Developer)#

The quick way needs no sandbox account: install from TestFlight and buy while signed in with your normal Apple account. The purchase still runs in the sandbox and is free. With a sandbox account instead:

  1. Install the build from TestFlight with your normal Apple account.
  2. Turn on Developer Mode: Settings → Privacy & Security → Developer Mode, restart, then confirm with your passcode. The switch appears only after the iPhone has been connected to a Mac with Xcode once.
  3. Settings → your name → Media & Purchases → Sign Out (only the store account signs out, iCloud stays).
  4. Settings → Developer → Sandbox Apple Account → Sign In with the sandbox account.
  5. Open the app → wallet → Add fund: the payment sheet now uses the sandbox account.

With a build run from Xcode (Developer)#

Start a purchase and sign in with the sandbox account when the sheet asks. The sheet shows [Environment: Sandbox]. From then on the account is under Settings → Developer → Sandbox Apple Account, where Manage also clears the purchase history. Never sign in to iCloud or the App Store app itself with a sandbox account.

iOS: fill in the AdminCP#

Admin

Last updated: 2026-11-19 · v1.5.6

What each field means is explained in the ShaunSocial guide; here is what to put in them:

FieldWhereWhat to enter
Apple bundle idGeneral Configuration → General Settings (see Package name and bundle ID)your app's bundle ID, exactly as App Store Connect shows it
Issuer ID, Key ID, key content (.p8)General Configuration → In-App Purchase (see The In-App Purchase settings)from The In-App Purchase key; for the key content, open the .p8 file in a text editor and paste all of it, including the BEGIN and END lines
App Store environmentthe same partleave it on Production: it also checks TestFlight and App Review purchases
Answer App Store consumption requeststhe same partoff, unless your terms record the customer's consent
Apple product Ideach deposit package (see Deposit packages)the App Store product ID of that package; the package must be active

The bundle ID is in the General Settings part, not in the In-App Purchase part. While it or one of the key fields is empty, every iOS purchase is refused with "Apple in-app purchase is not available right now." The Apple shared secret field is not used for in-app purchases.

iOS: test a purchase and a refund#

AdminDeveloper

Last updated: 2026-11-19 · v1.5.6

  1. With a build from Xcode or TestFlight, signed in as in Sandbox test accounts, buy the smallest package.

    What you should see: "Your wallet has been topped up.", and the balance goes up once.

  2. Buy something that costs more than the balance, choose Top up … and pay.

    What you should see: after the top-up, the item is bought without asking again.

  3. Refund the sandbox purchase in one of the ways Apple's page Testing In-App Purchases with sandbox describes (see Official store help pages).

    What you should see: Apple sends the refund notice to your site and the credits are taken back (see Refunds and other events).

iOS: purchases and revenue in App Store Connect#

Admin

Last updated: 2026-11-19 · v1.5.6

Unlike Google Play, App Store Connect has no list of single orders and no refund button. You see totals in Sales and Trends and the money in Payments and Financial Reports; a single purchase is checked through the buyer's receipt.

Check whether a member paid#

  1. Ask the member for the Order ID in Apple's e-mail "Your receipt from Apple" (or from reportaproblem.apple.com). The receipt shows the date, product and amount: that alone proves the member was charged.
  2. Check the member's balance in the AdminCP. Charged but not credited: see When an iOS purchase does not work; the app tries again by itself.

Sandbox and TestFlight purchases are never charged and never appear in sales or financial reports.

Refunds are decided by Apple

You cannot refund an App Store purchase yourself. The member asks Apple at reportaproblem.apple.com or through Apple Support. When Apple approves, it sends a refund notice to your site and the credits are taken back.

Revenue and payouts#

  • Sales and Trends has next-day figures, including in-app purchases. Proceeds there are not final.
  • Payments and Financial Reports has the final payments, by Apple's fiscal months (not calendar months).
  • Apple pays within 45 days of the end of the fiscal month, to the bank account under Business, once your balance reaches the minimum payment for your country; until then it is carried forward.

iOS: submit the first version with in-app purchases#

AdminDeveloper

Last updated: 2026-11-19 · v1.5.6

Your first in-app purchases cannot be submitted on their own: they go to review in the same submission as an app version. Later packages can be submitted alone once the first ones are approved.

  1. Live site ready (Admin): the AdminCP fields are filled in on the live site (see Fill in the AdminCP), App Store environment is Production, Accept sandbox and test store purchases is on (reviewers pay with sandbox accounts), the refund notice address is set (see Refund notices), and allow_url_fopen is on (see Before you start).
  2. One real test against the live site (Developer): install the TestFlight build that uses the live site, buy the smallest package and check that the balance goes up. Do not submit before this works: a reviewer who cannot top up rejects the build.
  3. Every package is Ready to Submit (Admin): price, availability, localizations in every app language and the review screenshot.
  4. On the version page (Distribution → iOS App → the version), in In-App Purchases and Subscriptions, click Select In-App Purchases or Subscriptions, tick every package and click Done.
  5. Select the build and fill in What's New in This Version for every language of the version (switch the language at the top right of the page). An empty language gives "What's New in This Version – This field is required".
  6. In App Review Information → Notes, give a demo member account and where to find the purchase, for example: "Wallet top-up via In-App Purchase: sign in with the demo account → Menu → the wallet row under the name → Add fund → choose a package."
  7. Click Add for Review, then Submit to App Review. The version and the packages move to Waiting for Review together.

On Google Play, products need no separate review: once your app is published on the production track, the active products can be bought.

When an iOS purchase does not work#

AdminDeveloper

Last updated: 2026-11-19 · v1.5.6

As on Android, a payment your site could not credit shows "Your payment was received but has not been added to your wallet yet. It will be retried automatically." with your site's reason on a second line, and the app sends it again by itself; nobody needs to pay twice.

What you seeLikely cause
"Product unavailable" / "This package is not available in the store."the Paid Apps agreement is not active, the product is not Ready to Submit, its ID differs from the package's Apple product Id, or the change has not reached the sandbox yet (up to an hour)
Second line "Apple in-app purchase is not available right now."Apple bundle id, the Issuer ID, the Key ID or the key content is empty in the AdminCP
Second line "The purchase could not be verified with the App Store. Please try again."your site could not ask Apple, or Apple refused. In the system log, the line Apple IAP transaction lookup failed says why: "no suitable wrapper could be found" means allow_url_fopen is off (see Before you start); status 401 means a wrong key, Key ID or Issuer ID (or the wrong kind of key), or a wrong server clock
Second line "The apple bundle id is not correct."Apple bundle id in the AdminCP is not the bundle ID of the app that made the purchase
Second line "The package not found."no active deposit package has this product ID; the root admin account gets a notification naming the product. Activate or correct the package and the app's next try credits the purchase
"Test purchases are not accepted."Accept sandbox and test store purchases is off (see After the stores approve your app)
A member says they paid, but App Store Connect shows no saleSales and Trends is next-day data and lists no single orders; ask for the Order ID and check the balance (see Purchases and revenue)
"The dimensions of one or more screenshots are wrong."the review screenshot is not an accepted size, usually because a chat app shrank it (see Review screenshots)

The system log is at AdminCP → System Setting → System Log (see System log).

Official store help pages#

AdminDeveloper

Last updated: 2026-11-19 · v1.5.6

App Store Connect:

Change log#

Last updated: 2026-11-19 · v1.5.6

Date (GMT+7)SectionWhat changed
2026-11-19allFirst version for the ShaunSocial app 1.5.6. The app's behaviour was read from the 1.5.6 code; the steps in the store consoles were not run for this guide.
2026-11-19allSplit by platform: Android and iOS have their own pages.