I’m developing an app for Google Chrome and I would like to know how I can charge for it.
The problem is that I live on Brazil and on this link it tells that it doesn’t support the Chrome Web Store Payments. There is other way I can charge for that without the Chrome web store payment?
https://developers.google.com/chrome/web-store/docs/pricing#seller
My initial idea is to create a hosted app that is free (but limited) and the customer pays and can use it fully. Or the other idea is to give 30 days to try and the costumer need to pay only onetime if he likes it and can use it fully.
Do you guys know how to do that living in a country not supported by Chrome Web Store Payments?
Did you notice the text on https://developers.google.com/chrome/web-store/docs/pricing#seller which says "In the future, we expect to support sales to the following additional regions: Argentina, Brazil, India, Mexico, and Poland. Buyers in unsupported regions might be able to purchase apps, but they can't pay in their local currency and might have to pay international transaction fees."? Not sure if that means it would work for you or not.
Otherwise I'm pretty sure you're allowed to use other payment processors other than Chrome Web Store Payments (see https://ssl.gstatic.com/chrome/webstore/intl/en/dev_tos_text.html and https://ssl.gstatic.com/chrome/webstore/intl/en/program_policies.html), so you might see if other services like PayPal, Amazon payments, etc. are a better option for you.
Related
Hope everyone is well.
I have read the Chrome Web Store Developer Agreement which I believe has provided clarity on the matter, but just wanted to check with others who may have been down the same route...
Am I correct in thinking if building a paid Chrome Extension that you don't have to accept payment via the Chrome Web Store payment processing?
I ask, not because I want to avoid their 5% fee, but rather, I was looking at using a 'Merchant of Record' such as Paddle, 2Checkout or Fastspring as these services not only act as a payment processor but also obviously act as a reseller and in doing so take on all liability in regards charging, collecting and remitting the necessary sales tax, VAT & GST, therefore making things much easier for me in that regard.
I would greatly appreciate if anybody had any experience with this and could confirm this is possible as I currently believe it is.
Many thanks in advance.
I have a chrome extension that im looking to monetize with subscription and free trial.
I have followed all the guide detailed here: https://developer.chrome.com/webstore/one_time_payments
Everything works, its all good, just now I need to know how to actually trigger the payment flow when a user decides they want to pay for my extension.
I can see that there is a "buy.js" for in-app purchases but im not sure how you are supposed to do it for one-time payments.
The only way I can see of doing it is by opening a new tab to my chrome store page and then somehow educating the user that they need to press the orange button...
Theres got to be a better way of doing it than that tho, surely??
If you want your extension to be paid using Chrome Web Store Payments, you have to follow Chrome Web Store Payments rules, which include fixed price tiers and the fact that payment must be initiated by Chrome Web Store. The in-app purchases work differently.
So yes, your users will have to subscribe using the orange button in your extension's Chrome Web Store entry. Usually they need not to be "educated" to do that: after all, that is the page they installed your extension from, and the orange button was already there.
Depending on which kind of free trial experience you offer, you can display relevant reminders to your users.
For example, if your free trial limits some functionality of the extension, you can prompt the users to subscribe when they try to use one of the premium functions, and/or display a Subscribe button in a visible part of your extension that links to your Chrome Web Store entry.
If your free trial is time-limited, you can display a counter of how many free-trial days your users have remaining, and the Subscribe button mentioned above. When the trial period is over you can automatically alert the users and open the Chrome Web Store entry of your extension. This latter approach (time limited free trial period) is the one I am currently using in my extensions and so far I've had no problems with the users or confusion on their part.
I'm making a desktop app for a company, and they would like to get it featured in the windows app store for Windows 10 users.
The app will likely only work on desktop computers, it's not designed for mobile. What it does is perform lookups on lists of cell phone numbers, and outputs a spreadsheet with carrier info, and it requires a credit for each cell phone number looked up. The credits are bought in bulk through the company's sales team, there is no automated method to purchase them.
Because there is no automated system, it would be difficult to set up in-app purchases, also if Microsoft takes a cut of in-app payments then it wouldn't be feasible due to the tiny profit margin of the credits. But according to this (section 10.8.1), if the app consumes anything that has to be purchased then it needs to use the in-app purchasing api.
Does anyone know if there's some way around this? Or if it only applies to regular apps and not desktop only ones, which I understand are a different type of listing?
I realise I can get a developer account and go through this with them but I don't really want to spend this company's money on the dev account if Microsoft are just going to say no.
Thanks :)
That section of the policy refers to payments taken within the application.
It doesn't sound like what your application will do though. Your application is allowing the allocation (spending) of credits bought separately.
It's a small distinction but an important one. You may have seen other applications work around such limitations by requiring the user to go to a website to buy something and then return to the app to use it.
When submitting the app there is a declaration for "This app allows users to make purchases, but does not use the Windows Store commerce system." You can read more about this declaration at https://msdn.microsoft.com/en-us/library/windows/apps/mt148523.aspx but this shouldn't apply to your scenario.
There are potential legal implications here and if the company has any concerns about entering a legal agreement with Microsoft regarding financial matters then they should seek appropriate legal council. Having a developer ask other developers about legal matters is likely only suggest asking a lawyer.
I am testing my in-app purchases, I uploaded my app to the windows store as beta and made an in-app product.
I tried it out and noticed a bug, I want to reset the in app purchase(it is hide ads) but I am not sure how to do this.
I want it so it is like the user account that bought the in-app never actually bought it.
I am going to assume that you are talking about a durable in app purchase, since consumable purchases can be bought as many times as one wants.
Once a durable purchase is made, it is permanent to the account. A user could call customer service to have this reversed, but it is not common (I have done this).
However it is unlikely that a rep would reverse a free in app purchase for a beta app to assist in testing.
If you would like to test your app without having to deal with those issues, Microsoft has provided guidance in how to test in app purchases.
So far as i know, if someone bought something through store, he cannot actually get the money back. If you're releasing app, you should pre-test it to be 100% sure it's working. If you're not sure how is the in-app purchase working, there is a plenty of forum threads about how to do this efficiently. Long story short, if someone already bought this in-app feature, either you cannot block it to him or refund his money.
I'd recommend testing In App Purchases through the emulator. Every time you restart the emulator it's like booting up a fresh device, so you'll be able to purchase IAPs again.
I am developing an windows phone 8 application and want to maintain two versions of my app - free and paid. So that my app appear in both free and paid app sections.
Since these two applications will have different Product IDs, is it possible to buy paid app from inside the free app.
I know that if we use Trial API of WindowsPhone, we can purchase paid version from app itself and can unlock the features using IsTrial of LicenseInformation. But in this case your app doesn't appear in free section.
I want to allow user to buy paid app from free version say by clicking BUYNOW button in app and get the free version replaced by paid one automatically.
This is the exact scenario that Microsoft wants to avoid. They don't want to see duplicate apps in the market because it destroys the consistent user experience. Instead, you need to either use the Trial Library or release it for free and put an in app purchase to remove ads or add functionality.
Your only option is to maintain 2 apps one that limits functionality using IsTrial and the other with an in app purchase.
Some people have suggested this isn't allowed, but I've yet to find anything in the requirements documentation that says you can't do this. There's also quite a lot of examples of apps already in the store doing this.