Skip to main content

In-app purchases: let members pay inside your mobile apps (In-app Billing)

Set up purchases and subscriptions inside your iOS and Android apps. Where In-app Billing settings are, what each field is for, and which product lists to fill in.

Written by Team

If your package includes mobile apps, members can pay for top-ups, memberships and services inside the iOS and Android apps. These payments go through the app stores, and Apple and Google keep their own fee. The settings live in the Apps section of your admin panel. For the big picture of apps, read Your dating platform on phones.

Where to find it

Open Dating channels → Apps. The page has these parts:

  • Application links: the links to your app in Google Play and the App Store, and the package name in Google Play.

  • In-app Billing settings: purchases and subscriptions inside the app.

  • Push notifications: notification settings.

The same parts are also available under Dating Funnels → Customize your service → System → Apps.

In-app Billing settings

The page has these lists and fields: Purchases, Subscriptions, Services, API Key, Client ID, Client Secret and a Refresh tokens link. The OAuth fields (Client ID and Client Secret) are not required.

Which product IDs to create

Create the product IDs (also called SKU) in the store, then add them to the matching list in the admin panel:

  • Top up the balance: the list of purchases, for adding money to the member's balance.

  • Membership: the list of subscriptions, linked to your membership groups in Access permissions.

  • Paid service: the list of services, for services of the tariff type.

Subscription renewals on Google Play

Renewals of Google subscriptions need a service key file kept on the server outside the site folder. It cannot be uploaded through the admin panel, so ask support to place it.

Related

  • Publishing the apps: see the articles on publishing iOS and Android apps in the Help Center.

  • Membership groups: Memberships.

  • Prices and what is included in your package: pricing page.

Did this answer your question?