because you need to have an API component by thunkable not just one you come with app will be rejected.
@Mikas_3D Hi, what do you meant API component by Thunkable?
- How would google know if an API in my app is implemented by me or Thunkable?
- I’m using an api to add items to a virtual basket, which then get added to a web basket in webview, the user pays there. As it’s a physical-item shop, not an in-app feature, I don’t think there should be any issues, have you experience of this?
(Payment is done on the web, not via mobile SDK functionality)
Any experience you have is appreciated!
About the Payments policy
Apps that employ in-store or in-app purchases must comply with the following guidelines:
- In-store purchases: Developers charging for apps and downloads from Google Play must use Google Play’s payment system.
- Developers offering products within a game downloaded on Google Play or providing access to game content must use Google Play In-app Billing as the method of payment.
- Developers offering products within another category of app downloaded on Google Play must use Google Play In-app Billing as the method of payment, except for the following cases:
- Payment is solely for physical products
- Payment is for digital content that may be consumed outside of the app itself (e.g. songs that can be played on other music players).
- In-app virtual currencies must only be used within the app or game title for which they were purchased.
- Developers must not mislead users about the apps they are selling nor about any in-app services, goods, content, or functionality offered for purchase. If your product description on Google Play refers to in-app features that may require a specific or additional charge, your description must clearly notify users that payment is required to access those features.
This what i got from google
My payment is solely for physical products
Also, I’m not technically doing in-app purchases, the payment is done on the web, the in-app payment SDK is not used (because it obviously doesn’t exist at the moment).
Hi @domhnallohanlon and all others,
I got this notice from google saying that from november 1st, 2020, a new billing policy will be activated in play store:
Anything to do here in thunkable for me as a developer?
Read the policy and see if it applies to you.
If it does, make the required changes.
Hi @domhnallohanlon. I was very interested to find this thread in the community and I see that In App payments is coming soon. Any idea when and can I ask does in app payment mean support only for that? In app payments incur high charges from google/apple while payment for physical goods or services such as tuition appear exempt, Will the proposed tools handle both types of payment?
We need this feature to bring ourselves up a level and offer tiered subscriptions and in app content
Seems like a huge task. Is it possible? If so, Will it happen before June? Before December?
It’s something we’re working on at the moment - it is a pretty big task, particularly navigating the subtle policy differences between App Store and Play Store, but we’ll get there @jared!
That really is great news @domhnallohanlon!
This is dope. I’d love to beta test if and whenever possible!
Thanks for getting back to me!
Will it only be In App purchases or will it also handle sale of real goods and services like tuition? As I mentioned earlier in this thread, these are exempt from the high charges levied by Apple and Google.