What this case covers
Author Agan's mini program, developed under an individual entity, already charged fees and had existing users. Due to three rejection opinions, the author decided to migrate to a corporate entity. The article covers the complete process of entity change, name and abbreviation, privacy guidelines, AI category, virtual payment, and dual-platform real-device payment.
Questions it answers
- What did each of the three rejection opinions block?
- Can existing users and data be preserved after entity change?
- Why does the AI category require materials to correspond to online calls?
- Why can Android payment succeed while iPhone still fails?
- Why can merchants not proactively initiate Apple refunds?
Our observations
- The limitations of an individual entity are not at the code level, but in qualifications and payment capability.
- AI category review looks at whether materials can prove a real invocation relationship.
- Payment acceptance must be verified separately by device, account status, and first purchase.
From the author
Code can solve pages and authorization flows, and the backend can supplement privacy guidelines and category materials. When the entity does not have the corresponding qualification, it cannot be submitted even after both sides are changed.