2. Add apps and connect stores
Add Cafe Bazaar, Myket, independent, and PWA apps to an InAppify project
Each InAppify app represents one distributable build. If you publish the same product through Cafe Bazaar, Myket, independently, or as a PWA, create a separate app for each distribution method because their connection details and purchase-validation flows differ.
Before you start
Prepare the following information:
- the Android Package Name or iOS Bundle ID;
- an internal name that identifies the app in InAppify;
- for Cafe Bazaar and Myket, the RSA key and API key belonging to that exact store app;
- the app return URL or payment result page when direct payments are used.
The Package Name, RSA key, and API key must all belong to the same app in the same store. Do not copy credentials from another app.
Add a Cafe Bazaar app
1. Open the apps page
Select the project, then open Apps → Configuration from the sidebar and choose Add app configuration.
2. Select Cafe Bazaar
Under Iranian stores, choose Create a new Cafe Bazaar app.
3. Enter the app details
In the Cafe Bazaar form:
- Enter the Package Name exactly as registered in Cafe Bazaar.
- Add an Internal name that identifies this app in InAppify.
- Enter its Display name.
- Retrieve the App key and Public app key from the Bazaar dashboard as described below.
4. Retrieve the Bazaar RSA key
Sign in to the Cafe Bazaar developer dashboard and open:
Apps → Your app → In-app billing → Settings
Copy the complete RSA or billing public key shown there and paste it into InAppify's App key field.
5. Retrieve the Bazaar Pishkhan API key
In the Bazaar dashboard, open:
Apps → Your app → Pishkhan API
Create or copy the API key or token scoped to that app and paste it into InAppify's Public app key field. InAppify uses it for server-to-server communication with Bazaar and purchase validation.
In InAppify, App key stores the Bazaar RSA key, while Public app key stores the Bazaar Pishkhan API credential.
6. Save the app
Review the payment return settings and save the app. InAppify then generates the SDK connection key for this app; the SDK key is different from the Bazaar RSA and API keys.
Add a Myket app
- In InAppify, open Apps → Configuration and choose Add app configuration.
- Select Create a new Myket app.
- Enter the Package Name exactly as registered in Myket.
- Sign in to the Myket developer dashboard and select the matching app.
- Retrieve that app's in-app billing RSA key and enter it in InAppify's App key field.
- Retrieve the purchase-validation API key or token for that app and enter it in Public app key.
- Complete the internal name, display name, and payment return settings, then save the app.
Bazaar and Myket credentials are not interchangeable. Even when both builds use the same Package Name, create a separate InAppify app for each store and use that store's own credentials.
Add an independent app
Use an independent app for a build that is not distributed through Cafe Bazaar or Myket and whose publishing and payments you manage directly.
- Open Apps → Configuration → Add app configuration.
- Under Independent apps, choose Create a new Android app or Create a new iOS app.
- Enter the Package Name for Android or Bundle ID for iOS.
- Complete the internal name and display name.
- Select the payment return method: the InAppify result page or a custom app return address.
- For a custom return, enter a valid Deep Link or Callback URL.
- Save the app.
The screenshots show an independent Android app. Follow the same process for an independent iOS app, but enter the iOS Bundle ID instead of an Android Package Name.
An independent app does not require a store RSA key or Bazaar/Myket API credential because no store purchase validation is performed.
Add a PWA app
Use PWA configuration for a web application where customers complete purchases directly through your website.
1. Open web configuration
Select the project and open Apps → Configuration. Under Web configuration (PWA), choose Add web configuration.
2. Create the web application
Select Create a new web application.
3. Enter the PWA details
In the web app form:
- Enter an Internal name that identifies the app in the dashboard.
- Enter its Display name, which is used in customer-facing areas.
- Optionally enter a Support email. InAppify uses the account email when this field is empty.
- Under Download links, add the URLs where customers can access or download the app.
- In PWA origin, enter only the protocol and domain, for example
https://app.example.com. - Save the app.
The origin must not contain a path, query string, or fragment. Values such as https://app.example.com/payment-result or https://app.example.com?source=pwa are invalid; enter only https://app.example.com.
Key differences
| InAppify field | Source | Purpose |
|---|---|---|
| App key | The same app's in-app billing RSA key in Bazaar or Myket | Verifies store purchase signatures |
| Public app key | Bazaar Pishkhan API or the app API in Myket | Lets the InAppify server query and validate store purchases |
| InAppify SDK key | Generated after app creation in InAppify | Connects the application to the InAppify SDK |
Never expose store API tokens or server secrets inside the application, a public file, or a source repository.
Completion check
- A separate InAppify app exists for each store or distribution method.
- The Package Name or Bundle ID matches the real build.
- The Bazaar app uses the RSA key from In-app billing → Settings and the API key from Pishkhan API.
- The Myket app uses credentials belonging to that exact Myket app.
- The independent app's payment return route has been verified.
- The PWA has a valid origin and the required download links.
- The SDK connection key is available in the dashboard.