Please see the Codeless IAP Manual, now live on the Unity Documentation site. Overview What is Codeless IAP?
Codeless IAP is the easiest way to integrate in-app purchases in your Unity app. This allows you to use Unity’s GUI and avoid directly using the Unity IAP API for a basic IAP integration.
How do I use Codeless IAP?
Add IAP Buttons to your app and define your products in the IAP Catalog. When players run your game, the Unity Purchasing system is configured based on the products you entered in the catalog. When a player taps or clicks on an IAP Button, it initiates a purchase of the associated product.
Screenshots
Inspector for a Button decorated with the Codeless IAP component
IAP Catalog editor for defining and exporting Products
(edit: link to Unity Documentation site for additional details, truncate this post to ‘overview’ only)
We do not currently have any support for that, but we are always interested in collecting feedback about which features are important to put on our roadmap. Would you mind sharing a little about your workflow and why you want to set up different ids for different APKs?
If you want to try to work around the lack of support right now, you could try working with multiple catalog files. The catalog is currently serialized as JSON and saved inside the plugin directory, in Assets/Plugins/UnityPurchasing/Resources/IAPProductCatalog.json. You could copy that file or create multiple product catalogs. You could then set up your build process to change which catalog file is included in your APK, or you could include all the catalogs and change IAPButton.cs to load from a different path at runtime.
Hi! Thanks for support. My english is terrable … so …
we have a few apk’s in google play for different publishers.
e.t.c amazon does not allow multiple using iap bundle in one account.
that’s why our iap bundles contains apk bundle name
for example if apk bundle named
com.company.game1 and com.company.game2
iap bundles named com.company.game1.gold_100 and com.company.game2.gold_100
for example 3 similar apps for different publishers
Thank you for sharing your feedback. For your situation it sounds like Codeless IAP does not provide all the functionality you need, so you should continue to use the regular API. The existing API is not going away, and we expect many developers will choose not to use the Codeless IAP tools.
This is great! Are you planning to add a service to handle cross-platform UserIds so that purchases can be used in different platforms for the same gamer? (I’m referring about the logic even if we have to use our own backend) Example: say you have an iPhone, an Android-based tablet and a PC with steam installed, and the game is available for all those stores and platforms and we want to share your IAPs among those three platforms/devices.
Does this replace the current IAP Service, is it better than the current IAP Service or is it just an alternative for people who don’t have much coding knowledge?
Codeless IAP does not replace the existing service—it is built on top of the existing service and intended to help developers who have less coding experience get started with IAP integration.
Hi, I don’t use the unity GUI, I use NGUI instead. Is it still possible to use the code less IAP with NGUI?
Also you say you don’t implement non consumable restoration on apples App Store, Apple will reject any app that doesn’t allow you to restore purchases. How do you solve this problem?
Hi, just read the announcement of the release Unity 5.5, which also mentions Codeless IAP. Does this means that Codeless IAP is only included in unity and 5.5? Or is it available for previous versions as well?
Just got to do my first successful device on iOS from 5.4.3, super happy to finally make it work.
However I have a huge request, that it think would be super helpful for others as well. I noticed that when I create the IAP button, it comes automatically with a text component. Could it be possible to post a script that fetches the name and price in local currency of the IAP and set that as the text component?
Also a restore purchase script to drop on a button for restore purchase would also be very much appreciated.
I agree with Baroni, use the regular API to make sure Apple won’t reject your App…
Even better, use Baroni’s Asset for IAP, this will save you countless hours of your time trying to reinvent the wheel…
You can use it with Unity IAP wich is free and worked perfect for me. It also supports other Billing Plugins…
I implemented this Asset in just a few hours, don’t mess with IAP yourself just to save a few bucks if you don’t know exactly what you are doing, using a professional Asset like Simple IAP System will guarantee satisfied costumers…
I know you can use the regular API, but my point is whats the point of touting a code less IAP implementation if it can’t create an IAP solution that will pass basic Apple guidelines. Currently if you use this IAP method you will get rejected by apple because they insist on a restore purchases option. This Code less option is basically useless, so why are Unity suggesting it’s a solution to the IAP problem?