Analysis and solutions for common rejection reasons of financial apps

The APP review here refers to the AppStore review.

First of all, we need to know that the Apple review team (App Store Review) is based on two review standards, one is the App Store Review Guidelines (Guideline for short), and the other is the Apple Developer Program License Agreement (PLA for short).

The full text of Guideline and PLA in Chinese and English is here. If you are interested, you can take a look.

App Store Review Guidelines - English.

App Store Review Guidelines - Chinese.

Apple Developer Program License Agreement - English.

Apple Developer Program License Agreement - Chinese. The translation is a bit rough, but thanks to the author anyway.

Apple has been increasingly strict in reviewing apps since 2017, and the review is based on domestic policies. For example, the country's financial supervision has become increasingly strict, and the review of financial apps has begun to tighten.

For financial apps (mainly referring to Internet financial apps), there are several common reasons for app review rejection.

• PLA 1.2 No loan qualifications and rejected
• PLA 3.2(f) Dishonesty or Fraudulent Rejection
• Guideline 2.1 -Performance – App Completeness
• Guideline 2.3.10 – Performance – Accurate MetadataAccurate metadata rejected
• Guideline 4.2 -Design – Minimum Functionality Minimum functional requirements were rejected
• Guideline 4.3 -Design – Spam apps rejected

Let’s analyze them one by one.

1. PLA 1.2: No loan qualifications and rejected

Reason for rejection

PLA 1.2 Apple Developer Program License Agreement 1.2

The seller and company names associated with your app do not reflect the financial institute in the app or its metadata, as required by section 1.2 of the Apple Developer Program License Agreement.

The app's developer name and company name do not match the financial institution in the app or app metadata, in violation of Section 1.2 of the Apple Developer Program License Agreement.

Next Steps

Your app must be published under a seller name and company name that reflects the financial institution name. If you have developed this app onbehalf of a client, please advise your client to add you to the developmentteam of their Apple Developer account.

Your app must be published under a developer name and company name that reflects the "Financial Institution Name". If you develop these apps on behalf of a client, please advise your client to add you to their Apple developer account.

Analysis of rejection reasons

1. The company entity of the app does not have the qualifications to provide financial services;
2. Financial apps can only be uploaded to the developer account of the app company, and cannot be uploaded to the developer account of an individual or a commissioned company;
3. The app name does not reflect the company brand;
4. The app name does not correspond to the company name, and there is no brand attribution or relevance;

How to deal with it

1. Prove that your company is qualified to provide financial services.

If the app does provide financial services, and the app's corporate entity is qualified to provide financial services, it can send proof of funds (such as a business license) to Apple's review team.

If the app provides financial services but does not have the relevant qualifications, the app needs to be submitted under the account of a qualified company entity.

If the app does not provide financial services, but Apple mistakenly thinks it is, the app can explain its business model to Apple and provide relevant proof, such as a p2p model or a loan assistance model.

2. If the application is submitted by a personal developer account, upgrade the personal developer account to an enterprise developer account before submitting;

3. If other developer accounts (such as outsourcing) develop for you, follow Apple's requirements and add other development accounts to your Apple developer account (in "Users and Roles-Add iTunes Connect User");

4. Modify the app name to make it relevant to the company brand. If the company is "Mashang Consumer Finance Co., Ltd.", the app name can be changed to "Mashangdai" and resubmitted;

5. Submit a "Software Copyright Registration Certificate" or "Trademark Certificate" to prove to Apple the association between the product name and the company;

6. Explain the operating entity of the app function, technical support website, etc. to the Apple review team to prove the relationship between the app and the company;

For example, in the “About Us” section of your app, introduce the company in both Chinese and English, and introduce the products that belong to the company.

For example, a technical support website further introduces the company and explains that the products belong to the company.

II. PLA 3.2(f) Dishonesty or Fraudulent Application Rejection

Reason for rejection

We have determined that your Apple Developer Program membersh ip , or another membership associated with your developer account, has been used fordishonest or fraudulent activity. This is prohibited by Section 3.2(f) of theApple Developer Program License Agreement:

We have determined that your Apple Developer Program membership or another membership associated with your developer account (two or more membership accounts for the same developer) has been used for dishonest or fraudulent activity. Section 3.2(f) of the Apple Developer Program License Agreement prohibits this behavior:

“You will not, directly or indirectly, commit any act intended to interfere with the Apple Software or Services, the intent of this Agreement, or Apple's business practices including, but not limited to, taking actions that may hinder the performance or intended use of the App Store, B2B Program, or the Program. ”

“You may not take any action, directly or indirectly, that is intended to interfere with the Apple Software or Services, the intent of this Agreement, or Apple’s business practices, including, without limitation, taking actions that could hinder the performance or intended use of the App Store, the B2B Program, or the Program.”

As a result of this activity, you are no longer able to submit updates.

Due to this activity, you will no longer be able to submit/update apps.

Continuing to engage in dishonest or fraudulent acts may result in the removal of your apps from the App Store and termination of your Apple Developer Program membership and all associated memberships.

Continued dishonest behavior or fraudulent conduct may result in removal of your apps from the App Store and termination of your Apple Developer Program membership and all related memberships.

Analysis of rejection reasons

1. First, Apple reviewers have determined that your Apple Developer Program membership account has been used for dishonest or fraudulent activities;
2. Or your member account has not violated any rules, but other developer accounts associated with your account have violated any rules and have been discovered by Apple reviewers;
3. Your actions violate Section 3.2(f) of the Apple Developer Program License Agreement;
4. Due to these violations, Apple’s penalty to you is “prohibiting you from continuing to submit/update the app”;
5. If you continue to engage in these violations, Apple may remove your app from the shelves , suspend your developer account, and terminate your Apple Developer Program membership;

Apple mentions 3.2(f) here:

“You may not take any action, directly or indirectly, that is intended to interfere with the Apple Software or Services, the intent of this Agreement, or Apple’s business practices, including, without limitation, taking actions that could hinder the performance or intended use of the App Store, the B2B Program, or the Program.”

But there are no detailed examples for these. The author further checked the PLA3.2(f) in Apple's official document and found that these are all violations of 3.2(f):

• Submit false reviews for your App or any third-party App;
• Choose a name similar to that of a third-party app to confuse users;
• Taking over other applications' names to prevent legitimate third parties from using them;

You can check your developer account or vest package account to see that it is likely that one or more of the following items have been violated;

How to deal with it

PLA3.2(f) is a very severe penalty from Apple. The app can no longer be corrected through updates and submitted for review again. Its severity is second only to account deregistration. In response to this situation, you can work on the following aspects.

• If there is any behavior of swiping rankings or swiping comments, stop it;
• If a fake account with information connection or transfer relationship with this developer account is swiping rankings or comments, it will be stopped immediately;
• It is best not to update the vest package that has information association or transfer relationship with this developer account, and the update will be rejected;
• Do not create a placeholder application. If you have already created one, rename it.
• Do not buy an Apple developer account on Taobao or other trading platforms;
• If you want to create a new alias package for review, reapply for a new account that has no information associated with the existing account. The “no information association” here includes but is not limited to:

Email account domain, account owner, IP address, Mac address, Dun & Bradstreet contact/contact information/office address, payment credit card account, invoice header, etc.

• After stopping all possible violations, appeal to the Apple App Review Board;

3. Guideline 2.1 -Performance – App Completeness

Reason for rejection

We discovered one or more bugs inyour app when reviewed on both iPhone and iPad running iOS 10.3.3 on Wi-Fi connected to an IPv6 network.

We found one or more bugs in your app on Wi-Fi over IPv6 networks, on iPhone and iPad running iOS 10.3.3.

Specifically, we were unable to make a loan application.

Specifically, we were unable to apply for a loan.

Please see attached screenshots for details.

See attached screenshot for details.

Next Steps

To resolve this issue, please run your app on a device to identify any issues, then revise and resubmit your app for review.

To fix this, please run your app on a device to identify any issues, make corrections, and submit it for review again.

Analysis of rejection reasons

Because of the bug, the reviewer was unable to perform core functions (applying for a loan), interrupting the review process.

We later analyzed and found that we actually did not have any bugs, but the Apple review team found it difficult to understand the logic and interaction and thought it was a bug, which led to rejection.

How to deal with it

• Ensure that the submitted product is bug-free, especially that the bugs cannot affect the operation and use of core functions.
• The account provided to the Apple review team must be able to experience core functions. For example, a loan app needs to be able to submit a loan application.
• The logic and interaction of product functions should follow a logic that ordinary people can understand and accept, and should not be obscure and difficult to understand.

Guideline 2.3.10 – Performance – Accurate Metadata Accurate metadata is rejected

Reason for rejection

We noticed that your app or its metadata includes irrelevant third-party platform information.

We noticed that your app or its metadata contained irrelevant third-party platform information.

Referencing third-party platforms in your app or its metadata is not permitted on the App Store unless there is specific interactive functionality.

References to third-party platforms or their metadata are not permitted on the App Store unless there is specific interactive functionality.

Please see attached screenshots for details.

Please see the attached screenshot for details.

Next Steps

To resolve this issue, please remove all instances of this information from your app and its metadata, including the app description, What's New info, previews, and screenshots.

To resolve this issue, remove all of this information from your app and its metadata, including the app description, updates, previews, and screenshots.

Analysis of rejection reasons

The reason is that in our app preview, there is a page showing functions that the APP submitted for review does not have, and the Apple review team will think that this is something from a third-party platform.

Data from third-party platforms, including third-party company names, company logos, etc., cannot appear in your app (including About Us, Agreement, etc.). Third-party company names, company logos, and functional points that the app does not have cannot appear in the app description, latest updates, previews, or screenshots.

Of course, it’s best not to have Apple products appear in your app or app description, latest updates, previews, or screenshots.

How to deal with it

Strictly follow the instructions given by Apple. Before review, check whether there are any third-party elements in the application, application comprehensive information, and application version information.

5. Guideline 4.2 -Design – Minimum Functionality The minimum functional requirement was rejected

Reason for rejection

We found that the usefulness of your app is limited by the minimal amount of content or features it includes.

We've found that your app's usefulness is limited by overly simplistic content or features.

Next Steps

We encourage you to review your app concept and incorporate different content and features that are incompliance with the App Store Review Guidelines.

We encourage you to review your app concepts and consider different content and features to comply with the App Store Review Guidelines.

Analysis of rejection reasons

Simply put, your app's functions are too simple, it does not meet the standards of an app, and is not eligible to be submitted to the appstore.

By further looking at Apple's official Guideline 4.2, the content is as follows:

An app should contain functionality, content, and UI, not just a repackaged website. If your app doesn't have any useful value, isn't innovative, or doesn't really feel like an app, then it doesn't belong in the App Store. If the app doesn't provide lasting entertainment value, or is simply creepy, it won't be approved. If your app is just a song or a movie, you should submit it to the iTunes Store. If your app is just a book or game guide, you should submit it to the iBooks Store.

4.2.1 Apps should use APIs and frameworks to achieve their intended purposes and describe the integration details in the app description. For example, the HomeKit framework should provide home automation services, while HealthKit should be used for health and fitness purposes and integrated into the Health app.

4.2.2 Except for directory apps, apps should not be used solely for marketing materials, advertisements, web clippings, content aggregation, or collection of links.

4.2.3 The App should be able to work independently without installing other apps.

4.2.4 Apple Watch apps that resemble watch faces may be confusing because users may assume that these apps work with various device features such as swipe, notifications, and third-party widgets. It's a good idea to use creative ways of representing time as an app interface (for example, a tide clock for surfers), but if your app looks too much like a watch face, we may reject it.

4.2.5 Apps that are primarily used as iCloud and iCloud Drive file managers need to include additional app functionality in order to be approved.

4.2.6 Apps created using commercial templates or app generation services will be rejected.

How to deal with it

Apple's review guidelines make it very clear that all you have to do is be a good citizen, follow Apple's standards, and submit valuable, compliant apps. At the same time, please note:

• Avoid overly simple features;
• Simple information aggregation and link aggregation apps will not be rejected;
• You do not need to submit applications created using commercial templates;

6. Guideline 4.3 - Design – Spam applications are rejected

Reason for rejection

Your app duplicates the content and functionality of apps submitted to the App Store, which is considered a form of spam.

Your app copies content and functionality from other apps submitted to the App Store, which is considered spam.

Apps that simply duplicate content or functionality create clutter, diminish the overall experience for the end user, and reduce the ability of developers to market their apps.

Apps that simply duplicate content or functionality create confusion, degrade the overall experience for end users, and reduce the developer's ability to market their app.

You will experience a delayedreview process if you deliberately disregard the App Store Review Guidelines, ignore previous rejection feed back in future app submissions, or use your app to mislead or deceive users.

If you intentionally disregard the App Store Review Guidelines, ignore rejection feedback in subsequent app submissions, or use your app to mislead or deceive users, you will experience a delayed review process.

Additional Information

We want to provide a safe experience for users to get apps and a great opportunity for all developers to be successful.

We want to provide a safe experience for users who get our apps, while giving all developers an opportunity to succeed.

Deliberate disregard of the AppStore Review Guidelines and attempts to deceive users or undermine the review process is a direct violation of section 3.2(f) of the Apple Developer ProgramLicense Agreement. Continuing to violate the Terms & Conditions of the Apple Developer Program will result in the termination of your account, as wellas any related or linked accounts, and the removal of all your associated appsfrom the App Store.

Willful disregard of the App Store Review Guidelines and attempts to deceive users or subvert the review process is a direct violation of Section 3.2(f) of the Apple Developer Program License Agreement. Continued violation of the terms of the Apple Developer Program will result in the termination of your account and your associated accounts, and removal of all of your associated apps from the App Store.

Analysis of rejection reasons

1. Your app is defined as a junk app if its functions are the same as others, or it is the same as your own approved package, or even has the same code.
2. Duplicate apps or simply copied apps are very harmful to users and developers, and undermine the health of the app store ecosystem;
3. If you ignore Apple's warnings and continue to violate the rules, your app review will be delayed;
4. If you further try to deceive users or undermine the review process, you will be subject to more severe penalties, such as account bans and app deletions. This is very serious;

How to deal with it

1. You should attach importance to the idea that your application should be valuable, less plagiarized or not plagiarized, and if the functions are similar, there should be differences;
2. Please do not upload the same app under multiple accounts;
3. If there are similarities with other products, you can create a product-focused attribute classification that is different from the original product by modifying the product classification, product distribution area, etc.
4. If you are making a vest package, the functions need to be more differentiated to reduce the amount of identical code. Apple may conduct machine-based scans of the code;

For industries and applications that are sensitive to regulation, Apple's review is more stringent. It is recommended that everyone compile an app review checklist, including detailed inspection items such as developer account application, app design, app development, app information and version information description. Before review, check and confirm each one to improve the app review pass rate.

This analysis and summary ends here for now. We will update it later with more ways in which financial apps are rejected.