Closed rvullriede closed 9 years ago
Hello @rvullriede,
To support Open Billing API, you must implement all methods described in the first doc. There is no any alternative, just different names for the same API.
I am not sure that I got the question. You can directly email me akarimova@onepf.org to discuss the questions. I am also interested in new stores. It is not only just a package of stores that use the same API but something more valuable. Thank you in advance.
Hi,
After digging more through the repository and source code it's clear now. The disconnect on my side was that I assumed you also propose a Open Billing API on the server side that supports the Native Appstore Billing API on the client side.
Ticket can be closed, Thanks!
Hi,
I'm trying to understand what exactly a new app store has to do to support OpenIAB.
OpenIAB also provides an open in-app billing API that stores could implement to support all the built APK files using this library. I've read https://github.com/onepf/OpenIAB/blob/master/OpenIAB_in_Appstore_Implementation.md and that part is clear to me.
However, your page https://github.com/onepf/OpenIAB/wiki/OpenIAB also mentioned a Open Billing API: "OpenIAB also provides an open in-app billing API that stores could implement to support all the built APK files using this library. "
If I understand that correctly implementing this API is a an alternative approach to the one suggested in OpenIAB_in_Appstore_Implementation.md . As long as the API follows the specification it is directly supported by OpenIAB and an app store does not have to implement all the bindings (IOpenAppstore.aidl).
Is that correct? If so, where do I find the specification of this API?