REQUEST TO MICROSOFT CERTIFICATION TEAM - REF. PARTNER REQUEST TICKET ID 2004100040003081
Please explain why our submission received the failure notice 1100.1.4 shown below.
What should we change in our submission to clear this hurdle?
PLEASE NOTE:
Our offer is FREE and requires no purchase of a license or additional services.
Our service integrates with Outlook in M365. No additional services are required. We should not fail “1100.1.4 Additional Service or Account Disclosures”. If certification disagrees, please comment in the certification report so we understand how you arrive at this conclusion so that we can address the issue.
Failure Notice:
General Content
1100.1.4 Additional Service or Account Disclosures
Your offer contains features which are unlocked through the purchase of a license or additional services. If your product offers in-app purchases, you must select the "My product requires purchase of a service or offers additional in-app purchases" check box on the Product Setup tab when submitting your offer via Partner Center. Please update your offer as required and resubmit.
Thank you!
Dan
If a user has to pay to use the add-in at any point such as a free trial ending or to unlock additional functionality, that checkbox must be marked and that fact clearly disclaimed in the description of the offer. If this is not the case and the add-in is 100% free for users, you can mention that in the certification notes of the submission.
Related
Reason for rejection: Offer descriptions must notify users in the description of any extra charges to use advertised features or to activate additional features or content. Please update the description of the offer to include such information and re-submit your offer.
Should I include any extra additional information or documents regarding the charge disclosures for mu add-in or just text information is enough?
If there are any charges for a user at any point to use the add-in, this must be disclosed in the description.
If no payment is required at any point to use an add-in such as at the end of a free trial, for additional functionality etc. You can make this clear in the certification notes of a submission.
I am wondering whether it is possible to hide the email of the developer on the Chrome Webstore extension page.
I had the same issue and this was what I got from Chrome Web Store support.
In regards to the contact email address, it is a mandatory information to provide when you publish the chrome items and this requirement has been implemented on June 9th, 2020.
3.4 You Support Your Product. You agree to supply and maintain valid and accurate contact information that will be displayed in each product detail page on the Store and made available to users for customer support and legal purposes. For paid Products or in-app transactions, you must respond to customer support inquiries within three (3) business days, and within 24 hours to any support or Product concerns stated to be urgent by Google.
Failure to provide adequate support for your Products may result in low Product ratings, less prominent product exposure, or in some cases removal from the Web Store, such as if the extension no longer functions as described.
Having this said, there's no option to hide the contact email address from your listing page at the time but the Contact Email address doesn't have to be your personal email and you can change it anytime from the Developer Dashboard.
You can edit it at the [Account] --> [Profile] --> [Contact email address] in the Developer Dashboard (*Please see the attached screenshot image).
So I changed the contact email from my personal email to my work one and now my personal email is no longer exposed.
while reading through the online documentation I do not understand if:
there are some fees for commercial Apps published into GAM (or CWS) or the one time 5$ would suffice;
it is mandatory to have a Google Wallet account or not.
Thank you.
Before you publish your first item, you must pay a one-time US$5.00 developer registration fee. They charge this fee in order to verify developer accounts and better protect users against fraudulent activity.
The 5$ fee is just to verify the developer account.
Check this page for more details.
I believe all the payments to Google goes through Google wallet only. However, you have to provide your card information in Google wallet while you are paying.
Hope that helps!
We are upgrading our SagePay protocol from v2.23 to 3.0 to support surcharge fees. In v3.0 transaction registration post there are CreateToken and StoreToken which was not in the earlier version. What is the reason for create and store tokens? I went through the document but couldn't find a clue.
The link provided in the above post links to advice by one of our Sage Pay Partners so take a look at it.
Token allows shoppers the option of storing their card details (as a token) to their account on the payment page during their first purchase instead of having to set it up manually afterwards. Single click purchases for repeat customers will become much simpler and quicker to set up.
To view the Token Guide go to here, scroll to the bottom of the screen and select the Download the Documents option within your preferred method of integration (server, server inframe, direct). Within the guide it explains creating and storing a token.
If this is a service you would like enabled on your Sage Pay account our New Business team are available 0900-1800 on 0845 111 4466. Prices for Token are available via here. If you have any other questions, our 24/7 Support team can assist to on 0845 111 4455.
Sage Pay Support.
I believe this is related to their token system, allowing you to store and send card details as a token.
If you don't use their token system you don't need to worry about it.
Sage Pay have destroyed their content recently so it's hard to find anything, here's a quick article on their token system - http://www.metakinetic.com/blog/2013/09/sage-pays-token-system-and-advancements-in-payment-gateways/
I was wonder if it's possible to use PayPal mobile checkout directly in my wp7 app, as in-app payment gateway.
My concern it’s Microsoft marketplace application policy 2.1:
“Your application must be fully functional when acquired from Windows
Phone Marketplace (except for additional data as permitted below).
Unless you have a pre-existing billing relationship with the user,
your application may not require the user to provide payment
information,within the application experience, to activate, unlock, or
extend usage of the application. “
Does this means I’m not allowed to use PayPal to make in-app purchasing?
Thank you,
Alex
I think this policy only applies to your app. If you want to use PayPal
to activate, unlock, or extend usage of the application
than it's not allowed. If you want to do other things which require PayPal the policy allows you to do so.
The marketplace requirement menas that you must have that "pre-existing billing relationship with the user". It doesn't put any restriction on how you bill your users. You could, therefore use PayPal or any ither method available to you.
This requirement is partly to enforce the prevention of apps which have no functionality when downloaded from the marketplace, without paying for the content.
I would suggest contacting app hub support to further discuss your specific requirements if you need to or to confirm the exact meaning around what qualifies as a "pre-existing billing relationship".
You can use Paypal. If you study the clause carefully, it states "Unless you have a pre-existing billing relationship with the user, your application may not require the user to provide payment information,within the application experience, to activate, unlock, or extend usage of the application."
f you do not have a pre-existing billing relationship with new users, all they need to do is to complete the payment information outside the app, for example get redirected to an external browser (Paypal) to input their details.
Hope this helps.