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.
Related
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'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.
Is it possible to customize gmail landing page ? I am thinking of using gmail for business to manage my emails and wondering if one can include a link on his business website which directs to their work email account (gmail one) webpage featuring their business logo on it.
If not Google, does anybody provide such flexibility ?
Sounds like you want google for work:
https://www.google.com/work/
"With the exception of Google Apps Vault, all are included in the basic plan, which costs $5 per user per month or $50 per user per year. A premium package, Drive for Work, includes Google Apps Vault plus unlimited storage is available for $10 per user per month."
You will be able to customize the theme with logos of your choice.
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.
Anyone know how to get the merchant key for goole wallet?
Support indicates I should have an integration menu in settings but the menu is not showing up
http://support.google.com/checkout/sell/bin/answer.py?hl=en&answer=42963
Thanks
David.
AFAIK, merchant key is only relevant to "legacy" Google Checkout - re: your account must be for Google Wallet for Web sites (products/services sold at your web site).
The merchant key referenced in the support link you have, is used (only for) that specific API.
The Google Wallet integration settings page is at https://checkout.google.com/inapp/merchant/settings.html .
For some reason, this page is not accessible from anywhere within the Google Wallet merchant interface.