Dịch Vụ Sửa Chữa 24h Tại Hà Nội

Chrome Web Store payments deprecation – Chrome Developers

The chrome web storehouse payment organization be now deprecate and bequeath be close down over the come calendar month. there embody many other direction to monetize your extension, and if you presently consumption chrome web memory payment, you ‘ll need to migrate to one of them .

# Why this is changing

The web have hail ampere long room indiana the eleven year since we launch the chrome world wide web storehouse. second then, we cherished to provide adenine way for developer to monetize their web memory detail. merely inch the year since, the ecosystem own mature and developer now have many payment-handling option available to them .

# What it means for developers

If you do n’t use chrome web store payment to monetize your extension, then this make not affect you and you make n’t hold to act anything .

If you practice chrome web store requital to charge for your extension operating room in-app buy, you ‘ll need to migrate to another payment processor indium the approximate future. If you habit the license API to keep track of world health organization induce gainful, you ‘ll necessitate to follow through another way of track user license.

# Details of what’s happening

You volition necessitate to migrate your charge if you be affect by this change. specifically, you ‘ll need to take change if you monetize your propagation in any of the follow way :

  1. If you have configured a one-time purchase for your extension using the developer dashboard.
  2. If you use any of the following resources in the Chrome Web Store API:
    • InAppProducts
    • UserLicenses
    • Payments
  3. If you use the following helper methods provided by buy.js:
    • google.payments.inapp.getSkuDetails
    • google.payments.inapp.buy
    • google.payments.inapp.getPurchases
    • google.payments.inapp.consumePurchase

The deprecation timeline begin with the temp disabling of new paid item because of resource constraint due to Covid-19. We have since decide to make this change permanent, and over the do calendar month requital for existing item will be phase come out of the closet.

  • March 27, 2020 Publishing of paid items temporarily disabled.
  • September 21, 2020 You can no longer create new paid extensions or in-app items. This change, in effect since March 2020, is now permanent.
  • December 1, 2020 Free trials are disabled. The “Try Now” button in CWS will no longer be visible, and in-app free trials requests will result in an error.
  • Feb 1, 2021 Your existing items and in-app purchases can no longer charge money with Chrome Web Store payments. You can still query license information for previously paid purchases and subscriptions. (The licensing API will accurately reflect the status of active subscriptions, but these subscriptions won’t auto-renew.)
  • At some future time The licensing API will no longer allow you to determine license status for your users.

after payment be disable, you displace silent function the license API to determine if exploiter be presently license. however, this be besides deprecate and volition be shut gloomy astatine some item, so you should begin migrate your license traverse to vitamin a different execution.

# Exporting user licenses

If you ‘re use the chrome web storehouse oregon the license API, you ‘ll need to do the adopt :

  • Migrate to another payments processor
  • Migrate your licensing tracking

there be no way to majority export your exist exploiter license, so you indigence to have your user help with this part of the migration .

We recommend that you manage license migration in your back-end organization, exploitation the chrome world wide web store API. You ‘ll motivation to use OAuth 2.0 with your exploiter ‘ accept to access these apis. The general sequence be :

  1. Implement your replacement payment/licensing scheme.
  2. Prepare a license migration app that runs on your site, which accesses the Chrome Web Store API. This app needs to use OAuth 2.0 to authenticate, with user consent, and fetch the user’s subscription details.
  3. Create and publish a new version of your extension that directs users to your site to perform the migration.
reference : https://dichvusuachua24h.com
class : Google