wp-plugin-hostgator domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home4/scienrds/scienceandnerds/wp-includes/functions.php on line 6114ol-scrapes domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home4/scienrds/scienceandnerds/wp-includes/functions.php on line 6114Source:https:\/\/techcrunch.com\/2023\/04\/19\/google-play-store-billing-choice-uk\/<\/a><\/br> Google has proposed letting developers offering apps through its U.K. Play mobile app store to have the option to use alternative payment processors for in-app transactions, rather than being locked to its own billing system (GPB), following an antitrust intervention by the U.K.\u2019s Competition and Markets Authority (CMA).<\/p>\n \u201cGoogle\u2019s proposed commitments would give app developers the freedom to offer a different billing system of their choosing, known as \u2018Developer-only Billing\u2019 (DOB), or offer users a choice between an alternative billing system or Google Play\u2019s billing system, known as \u2018User Choice Billing\u2019 (UCB),\u201d the regulator explains in an update on the enforcement.<\/p>\n The CMA has opened a consultation<\/a> on Google\u2019s proposal which it says it\u2019s minded to accept \u2014 inviting developers and other interested stakeholders to respond by May 19. After considering responses it will take a decision on whether to accept the commitments and resolve the case.<\/p>\n Last summer<\/a>, the regulator concluded a year-long study of the mobile ecosystem which identified substantial concerns with the market power of the duopoly (Google with Android and Apple with iOS). At that time, in addition to opening certain other in-depth probes into aspects of the two tech giant\u2019s operations, it\u00a0announced it that was taking enforcement action<\/span> against Google in relation to its app store payment practices.\u00a0<\/span>The CMA\u2019s <\/span>concern here focused on conditions it sets on developers for in-app payments. So Google\u2019s proposal aims to settle those concerns.<\/p>\n In a blog post<\/a> detailing Google\u2019s offer, legal director, Oliver Bethell, writes:<\/p>\n Under the commitments, developers will be able to add an alternative in-app billing system, alongside Google Play\u2019s billing system, for their mobile and tablet users in the U.K. At checkout, users will be able to choose which billing system to use. These options will be presented in a neutral manner allowing users to make an informed and engaged choice.<\/p>\n<\/blockquote>\n \u201cDevelopers can alternatively choose to not offer Google Play billing at all when their users in the U.K. are paying for digital content and services,\u201d he adds.<\/p>\n In the blog post, the company also notes that its U.K. proposal would extend the choice of an alternative billing system that it already offers in the European Economic Area (EEA) \u2014 where Google has faced a number of antitrust enforcements over the past several years \u2014 and in other parts of the world; such as South Korea<\/a> where, back in 2021<\/a>, lawmakers intervened to force Google\u2019s hand on billing. India is another country where Google is gearing up to offer alternative billing<\/a> \u2014 after being slapped with a $162 million fine for antitrust practices last fall<\/a>.<\/p>\n For its U.K. offer, Google is proposing to reduce what it bills as the per transaction \u201cservice fee\u201d it charges developers for in-app digital sales \u2014 aka its cut\/commission (or the app store tax, as some critique such fees) \u2014 by 4% where a developer offers users a choice that includes GPB but the user selects alternative billing. But if developers opt not to offer Google\u2019s own payment processing system the proposed stick is a slightly lower reduction in Google\u2019s cut \u2014 reduced to 3% in that scenario, seemingly incentivizing developers to keep offerings users the option to select its own payment tech.<\/p>\n (NB: Google\u2019s baseline service fee for the Play Store starts at 15% for the first $1 million in revenue earned per year, rising to 30% for any annual earnings over that threshold \u2014 so, under the alt billing proposal, its fee would remain above 10% in almost all scenarios. For automatically recurring subscriptions Google\u2019s standard cut is 15%. Although it says some types of media content apps may attract a fee that\u2019s lower than 15% under its Play Media Experience Program.)<\/p>\n Here it seems to be offering a blend of what it has already rolled out elsewhere \u2014 with developers in South Korea and India getting a 4% fee reduction when using alternative billing, while devs in the EEA were given a 3% reduction last summer<\/a>.<\/p>\n \u201cFor both options, developers are still required to meet appropriate user protection requirements, and service fees and conditions will continue to apply in order to support our investments in Android and Play,\u201d Google adds.<\/p>\n It also wants to be able to phase in the proposed commitments, arguing this will allow time \u201cfor the necessary changes to be made\u201d to its systems \u2014 initially making them available to developers of non-gaming apps; and then bringing them to gaming apps \u201cno later than October 2023\u201d.<\/p>\n Whether Google gets its way will be up to the CMA which will decide whether to accept the proposal \u2014 and that may depend on the kind of feedback it gets.<\/p>\n The regulators says it\u2019s especially keen on feedback about Google\u2019s suggested service fee reduction (\u201cunder each of UCB and DOB); as well as additional elements including\u00a0the proposed process for reporting in-app purchase-related turnover to Google (either manually or using APIs) for the service fee to be calculated; the use of information screens and, for UCB, a billing choice screen; and the process it\u2019s proposing for monitoring Google\u2019s compliance with the commitments, especially a commitment it has made not to retaliate against app developers choosing to use UCB or DOB.<\/p>\n \u201cBased on the information the CMA has received to date, and for the reasons set out below, the CMA provisionally considers the Proposed Commitments to be appropriate to address the particular Competition Concerns resulting from the Conduct that the CMA has investigated in this case,\u201d the regulator writes in the Executive Summary of its Notice of Intent<\/a> to accept the commitments \u201cThose app developers opting to use an alternative billing system will have the possibility of establishing direct relationships with customers and overseeing their own transactions. They may also be able to offer pricing deals which are different to prices where GPB is used. Moreover, third party payment processors will be able to offer their services to potential app developer customers for in-app purchases of digital content or services within an app distributed on Google Play, allowing app developers to benefit from increased choice and competition,\u201d the CMA also suggests.<\/p>\n<\/p><\/div>\n <\/br><\/br><\/br><\/p>\n
\nGoogle offers billing choice for UK Play Store devs in bid to settle antitrust probe<\/br>
\n2023-04-19 22:14:27<\/br><\/p>\n\n
\u201cBoth DOB and UCB would allow app developers the opportunity to use billing systems of their choosing (and DOB would allow them to choose not to offer GPB at all), breaking the link that the GPB requirement currently creates between access to Google Play and the use of Google\u2019s proprietary billing system for in-app sales of access to digital content or services.\u201d<\/p>\n