I'm approaching completion of my chrome extension and need to explore monthly subscription options. What is the best approach to doing this?
As #Deliaz stated, Chrome Web Store Payments supports both monthly and yearly subscription models. As with one-time Chrome Web Store payments, you have the option of providing a free trial.
For details about app payment options, you may check the Charging for your app documentation in the Overview.
Unfortunately the top-voted answer on this mentions Chrome Web Store Payments which was shut down by Google on February 1, 2021.
The only other thing I know like Chrome Web Store payments to monetize your extension is ExtensionPay. It's open source and works on all browsers, not just Chrome, which is nice.
Otherwise, you'll need to build an authentication system and sync it with your extension. Then you'll need to use a way of taking payments like Stripe or Paddle or Paypal or something and sync that with your user's extension.
Related
I have an app with Free, Premium and Gold subscription plan. Based on the plan user can access features like filters, messages, likes.
Now, I'm planning to have an web app only for payments using stripe. So, users will directed to web app to pay payments.
Will apple allow this approach or will they insist to use in-app purchase?
I'm little confused here. Need your suggestion here?
This is a question for Apple Review team, you should reach out to them directly and clarify. Stripe doesn't replace in-app purchases and you need to use Apple's API to perform in-app purchases. See here for details
I'm trying to upload and publish a chrome extension I've made with a simple one-time payment. I've found this article which makes me think I should just have pricing options on the upload page. I've hooked up my merchant account and set a valid payment method, as well as verified it but I still don't get any pricing options--when I load the page, the pricing options appear for a moment and are then replaced with just the distribution region checkboxes. Any ideas for solving this?
I think this is the same issue with this
Chrome Web Store payments - We are disabling the ability to create new paid items or add payments to existing items. This includes extensions, themes, apps, and in-app purchases.
TL;DR If this question doesn't make sense, please check the following video explanation: https://www.youtube.com/watch?v=9o2KhiBf1lY
I created a Chrome extension and followed the directions here: https://developer.chrome.com/webstore/one_time_payments
In the drop-down, I changed it to a subscription system with a free trial.
And my Chrome extension successfully uses the License API to check the payment status.
But now I'm wondering:
Where do my users go to pay for the full version?
How long is the free trial configured for?
You might be thinking that I have to use the Payments API, but the documentation says:
If the trial is expired, you can direct the user to the web store listing to purchase the item.
Why does it say to direct the user to web store? If I go there, it just says to install the chrome extension, there's no option to pay for it.
And how can it know when the free trial has expired? I never configured a value for it and there's no "free trial duration" specified in the docs.
Meanwhile, the Payments API makes it clear that it's for in-app purchases with SKUs. If this is the only way to accept payment, what's the purpose of that pricing configuration that I set up above?
Thank you for your help.
You have all the answers in the documentation. Read it carefully.
You decide the length of the trial period. In your extension's code, when you check the user's license, it will reveal when your extension was first installed. Compare that with the current date to determine if the user is still within the trial period or not.
The trial and the paid extension are the same, both installed from Chrome's Web Store. If the purchase button doesn't appear to you may be because you are the developer.
In the documentation you have sample code to request the license and check the trial period.
I currently have a Website Payments Standard checkout process for purchasing recurring payments. WPS just use some inputs hidden to send all information to PayPal.
But it's very insecure because if you know HTML, you can change these inputs hidden at browser's developer tool and change the prices.
I chose WPS because it's simplest than the Express Checkout, and you don't need a API integration.
So, someone had the same problem? There is a security way to use WPS?
How are you using WPS? With the PayPal buttons? If so, you can create encrypted buttons when you log into your PayPal account. If you are using something else, let me know and I can look into it.
My client is using moneris as our payment gateway for a new subscription based website that I am working on.
I will be using the language PHP
I've looked through their documentation for PHP api and am comfortable with how it works, it seems very straight forward.
One thing was missing in the documentation for me though. There is mention of how to start a recurring payment, how to update a recurring payment, but no mention of how to query a recurring payment?
Some payment gateways allow you to have a POST back URL of sorts that get updates on recurring billing status. This does not seem to be possible with moneris.
How do I go about automatting the process of tracking recurring payments with Moneris? I'd like for my customers to log in and be able to view their transaction history on my site.
This information will also make it easier for me to know when to close accounts. Ie. when a payment fails to go through, or a credit card expires? I don't want for my cleint(owner of website) to have to keep track of the recurring payments and cancel accounts manually?
I got an answer from Moneris:
Hi David, We currently do not have a reporting API or any way of
posting the information from our recurring payments back to your
server. It is something that has been mentioned previously and is
being looked into. We do not have a current ETA on such a solution.