Archeden ART
Everything needed to answer the rejection under Guidelines 4.3 and 4.2.6: whether a new build is required, what the app has to change first, every paid flow a reviewer can reach on iOS, and the nine answers written to match the build you upload.
Verdict
The nine written answers cannot clear this rejection on their own. Apple allows a same-build resubmission when the problem is only the wording of metadata, but the payment statement on file does not match what a reviewer can reach inside the iOS app. That is treated as a problem with the app, so the build has to change first and the answers have to describe the build you upload.
What is only metadata
Payment approach
Apple in-app purchase is the right model for digital sales under Guideline 3.1.1, and it is not implementable on the current architecture. Archeden ART is a packaged web app running on Base44. That runtime has no StoreKit, so there is no product catalogue, no purchase sheet, no transaction result to read, and no receipt to trust.
What exists today and must not be presented as IAP: One function accepts a transaction identifier from the client and switches an account on. It does not verify anything with Apple, so any signed-in caller can send a well-formed number and become entitled. It is a placeholder, not an in-app purchase implementation, and it is not wired to a StoreKit purchase anywhere in the app.
The three routes
01
What this build does now that every digital path is closed. No subscription, purchase or tip is offered on iOS, and access to digital content is free there. Fastest route back to review, and it is the only one available without leaving this platform. The cost is no digital revenue from iOS users.
02
A real in-app purchase implementation: products in App Store Connect, purchase and restore flows, server-side signed-transaction verification, and App Store Server Notifications updating entitlements. It keeps this web app as the backend, but it is a second app to build and maintain, and it cannot reuse the packaged build.
03
Answer Apple without resubmitting until either route above is finished, so the reply and the build agree whenever the next review starts.
The Guideline 3.1.1 reply kept in this app’s public files states that the iOS build has no checkout, no tipping and no purchase path at all. That was not true of the build under review, and a reply that contradicts the binary is how a wording problem becomes a second rejection.
Delete that file, or mark it void, before opening App Store Connect. Nothing in this packet repeats its claims, and none of the nine answers assert that the payment model already complies with 3.1.1.
If the recording still shows a checkout sheet for digital content, it demonstrates the problem rather than resolving it. Re-cut it on the new build.
Payment surface audit
Apple’s rule applies to digital content unlocked inside the app. Tickets to a real concert, merchandise that ships, and a booking for a venue are ordinary commerce and may stay. Anything digital must not be sold on iOS in this build.
Membership subscription
Paywall, subscription gate · Digital
On iOS the gate grants access and renders no plan, no price and no button.
One-time purchase of a creator’s work
Buy dialog on a media item · Digital
The dialog returns nothing on iOS, so neither price nor button reaches the screen.
Tips to a creator
Tip dialog · Digital
Returns nothing on iOS, and the card form never mounts.
Subscription management
Subscription management screen · Digital
The billing portal is closed on iOS, so a subscription cannot be started or changed there.
Paid mashup commission
Mashup dashboard · Digital
A paid commission of digital work started a web checkout inside the iOS app. Closed in this pass.
Ad campaign purchase
Advertiser payment step · Digital
Promoting your own content inside the app is a digital service and ran a web checkout on iOS. Closed in this pass.
Web tip landing page
Web tip page · Digital
A web_checkout=1 parameter used to turn the iOS gate off, so a link carrying it rendered a card form on a phone. The parameter no longer affects the gate, and the tip page shows a plain notice on iOS. Closed in this pass.
Event and concert tickets
Event details, concert info · Real world
Admission to a real-world event, paid outside Apple’s rules for digital content. Say so in the notes so the reviewer expects a checkout.
Merchandise
Event details · Real world
Physical goods shipped to a buyer, paid by card as ordinary commerce.
Venue and performance bookings
Venue inquiry, booking payment · Real world
A service performed at a venue away from the app, not content unlocked inside it.
In the build
These change the app, so they need a new package uploaded before resubmitting.
Close the paid mashup commission on iOSDone
Digital work commissioned in the app no longer starts a checkout on iOS.
Close the ad campaign purchase on iOSDone
Promotion of content inside the app no longer starts a checkout on iOS.
Stop the web tip parameter disabling the iOS gateDone
The gate now depends on the device only, so no link can switch it off inside the iOS app, and the tip page shows a notice there instead of a card form.
Walk the reviewer path on a deviceOpen
Sign in, pass the age gate, open the globe, open a portfolio, follow, report a piece, block a user, then delete the account. Fix anything that dead-ends.
Cut the screen recording on the build you uploadOpen
On a physical device, showing the globe walkthrough and no checkout sheet for digital content.
Rebuild the iOS package and upload itOpen
The uploaded build has to contain the changes above, or the answers describe a different app.
In App Store Connect
These are edited in the submission itself and travel with the build above.
Replace answer 1 with the platform-specific wordingDone
It now states what the iOS build does and does not sell, instead of claiming paid features are present in every build.
Void the old Guideline 3.1.1 replyDone
Marked void in the public files, so it can no longer be sent by mistake. Delete it outright if you prefer.
Make the age rating agree with the buildOpen
The rating, the audience description in answer 2 and the gating in the build must say the same thing.
Fill in the demo account and its lifetimeOpen
A working sign-in that stays active through review, in the App Review notes.
Replace the example device list with the real oneOpen
Only the devices and OS versions the build was actually opened on.
Describe the testing honestly in the notesOpen
The same informal testing as answer 4, not a TestFlight programme.
Decisions only you can make
Three groups. The first is already in the app. The other two cannot be closed by changing code, so treat them as your own to-do list before you answer Apple.
Checked against this codebase. No action needed from you.
No digital purchase path on iOS:
Membership, one-time purchases, tips, the billing portal, paid mashups and ad campaigns render no price, no button and no link on iOS.
A URL cannot reopen the iOS gate:
The gate reads the device only, so no link or parameter can bring a checkout back on a phone.
Mature content filtered where the data is read:
Age gating runs inside the media query on the public discovery, portfolio and following surfaces, so a flagged item cannot arrive beyond the first page.
Age assurance at first sign-in:
Date of birth is collected once. Under 13 loses the social features; under 17 loses mature content.
Reporting, blocking and account deletion:
Each exists and is reachable, so moderation is not a dead end for a reviewer.
Real-world iOS payments kept:
Tickets, merchandise and venue or performance bookings still check out on iOS, as ordinary commerce.
Facts about your account and your testing. None of them can be read from the code.
Names and scope of the other apps on your account:
One sentence per app for answers 5 and 6, plus whether any first-party code or asset is shared with them for answer 7.
Two or three real beta observations:
The comment a tester made and the change it produced in the build you upload, for answer 4 and notes section 2b.
The demo account:
An email and password that work, with content already loaded, kept active for the whole review.
The devices and OS versions you actually tested on:
The example list in the notes is not a record and has to be replaced or deleted.
None of this happens by editing the app.
Rebuild and upload the iOS package:
The uploaded build has to contain the closed payment paths above, or the answers describe a different app.
Set the age rating and make it agree:
The rating, the audience description in answer 2 and the gating in the build must say the same thing.
App Privacy answers and the privacy policy URL:
Tracking is No, and the policy URL goes in the app metadata.
Record the screen recording on that build:
On a physical device, walking the reviewer path, with no checkout sheet for digital content in it.
Send the nine answers and the review notes:
Only once the amber blocks are replaced and the statements match the build that is waiting for review.
The nine answers
Text in amber is a fact only you can confirm. Amber notes under an answer are evidence gaps for you, never part of the copied text. Copy an answer once its amber blocks have been replaced.
Evidence gap, not for submission
Apple asked for before-and-after examples and none are in this file yet. You confirmed you can supply them: add them above, then send the answer. Do not reconstruct examples you cannot point at directly, because the notes section 2b has to carry the same ones.
Reviewer walkthrough
Only send these steps once each one has been walked on the build you upload. If a step dead-ends, fix it or drop the step, because a note the app contradicts is worse than no note.
Sign in with the demo account
Expected: The globe loads as the home screen. No subscription prompt appears.
Complete the age gate if it appears
Expected: Date of birth is requested once at first sign-in. Under 13 loses the social features; under 17 loses mature content.
Select a country, then a state or county on the globe
Expected: Artists and work anchored to that place are listed, not a global feed.
Open an artist from that list
Expected: Portfolio opens with follow and report actions. On iOS there is no price and no purchase button on digital work.
Publish a piece of your own from the workspace menu
Expected: The upload completes and the work appears in your portfolio.
Report a piece of content, then block a user
Expected: Both complete and are findable again, so moderation is not a dead end.
Delete the account from the account settings
Expected: Deletion runs and the session ends.
Check the only paid flows left on iOS
Expected: Event and concert tickets, merchandise, and venue or performance bookings. These are real-world goods and services, not digital content.
Never say this
Each of these would misdescribe the app, and a reply that contradicts the build is how a wording problem becomes a second rejection.
These live in the App Review Information notes, not in the nine answers.