Hi enrique,
we use such accounts as well, generated by the (main) managed playstore account but i can only see apps provided by our MDM and not any other app. So nothing able to be purchased there so i wonder how they get the possibility on your end to purchase apps using that account.
What kind of enrollment you use (BYOD, COPE, COBO)?
We use COBO, our users are not able to buy more apps. but they can make in app purchases.
They can add their personal credit or debit card, complete the transaction.
This is problematic in several ways
If we as an organization buy premium features for some app and this is the only method it would be problematic to enter the payment method for each managed account. (fortunately this is not our case).
We as an organization loose control of the features offered in the app.
Complicates support for the app offered.
If the user leaves the organization, What happens to the content payed and associated with the managed account?
Hmm, never tried that to be honest.
But as the payment is linked to the account used and this is a generic account, you will loose the payed (functions and apps) when doing a reinstallation or playstore reassignment as a new generic account is used then.
I think you may need to talk to the app provider to pay for the app in a different way and provide for example a license key or so via managed app config or so to the relevant devices.
That's the way we handled it yet with payed/licensed apps.
Please do not do this, reach out to the developer(s) of the app(s) you want to pay for to work out a licencing agreement.
This shouldn't be supported and that it's been possible to add payment methods appears to be an oversight on Google's part.
@Lizzie fyi is the team aware of this?
Because then (if a company SIM is used for example) employees could charge their company on their own... That shouldn't be possible or done.
As Jason already said, this should always go through licensing between the app provider and the company which wants to use the app.
