Payments and subscriptions

In-app subscriptions and payments across every store

We set up in-app subscriptions and payments for phone, TV and web apps: App Store, Google Play, Amazon and Roku billing, and Stripe on the web. One backend keeps every purchase in step, so people get what they paid for on each device the store rules allow.

Platforms

Billing on every platform.

Each store has its own billing system and rules about when it must be used. We set up each one and connect them to your accounts.

App Store

Subscriptions, free trials and one-off purchases on iPhone, iPad and Apple TV, with server notifications for renewals and refunds.

Tech used: StoreKit 2, App Store Server API

Google Play

Subscriptions and in-app products on Android phones, tablets, Android TV and Google TV, verified on your server.

Tech used: Google Play Billing, real-time developer notifications

Amazon Appstore

In-app purchasing for Fire TV and Fire tablets, following Amazon’s own billing rules and review.

Tech used: Amazon In-App Purchasing

Roku

Subscriptions and purchases in Roku channels, with the sign-up flow Roku certification expects.

Tech used: Roku Pay, BrightScript

Web payments

Checkout, subscriptions, invoices and a customer billing portal on your website.

Tech used: Stripe, Next.js

One set of entitlements

A backend that records every purchase from every store, so access is the same wherever someone signs in.

Tech used: Python and Django, PostgreSQL

Getting it right

What good app payments need.

Payment bugs cost money and trust. These are the things we plan for from the first design.

Store rules followed

Each store says when its billing must be used. We follow those rules, so the app is not rejected or removed.

Verified on the server

Purchases are checked with the store on your backend, not just trusted from the device.

Renewals and refunds handled

Store notifications update access when a subscription renews, lapses, is refunded or changes plan.

Clear prices and trials

People see the price, the trial and what it covers before they pay, with no surprises.

Tested end to end

Sandbox purchases, renewals and cancellations tested on every platform before launch.

Proof

Built by the team behind Ohm.

Ohm sells per-device licences with a 7-day free trial, both on its own website and through the app stores. We built and run its billing and licence system ourselves, so your payments get the same care and the same lessons.

Ohm

A premium IPTV player for the playlists you already have. Ohm plays your own sources; it never supplies channels.

Visit the Ohm website (opens in a new tab)
Process

How a payments project runs.

  1. 01

    Discover

    Platforms, products, prices, trials and budget agreed in a fixed-price proposal.
  2. 02

    Design

    Paywalls, purchase and account screens designed and agreed before code.
  3. 03

    Build

    Store billing, Stripe and your backend connected and tested in each sandbox.
  4. 04

    Launch

    Products set up in each store, review answers and a careful first release.
  5. 05

    Look after

    Updates for store rule changes, new products and help with billing questions.
FAQ

Payments and subscriptions questions.

Something else? Contact the App29 team.

How much does it cost to add payments to an app?

It depends on how many stores and platforms you sell on, the products and trials you offer and whether you already have a backend. After a short discovery call we send a fixed-price proposal with the scope written out, so you know the cost before work starts.

Do I have to use App Store and Google Play billing?

For digital content and features sold inside an app, the stores usually require their own billing, and the rules differ by store and country. Physical goods and services are generally paid for another way. We check the current rules for your app during discovery.

Can a subscription bought on one device work on another?

Yes, where the store rules allow. Every purchase is recorded on your backend against the person’s account, so signing in on another device gives the same access.

Can you take payments on our website as well?

Yes. We use Stripe for checkout, subscriptions and invoices on the web, connected to the same accounts as your apps.

How are refunds handled?

The store refunds purchases made through it under its own rules, and tells your backend so access changes. Website purchases are refunded through Stripe under your own refund policy.

Can you add subscriptions to an existing app?

Yes. We review how the app and backend work today, then add billing, entitlements and the purchase screens without disrupting current users.

Do I own the code and designs?

Yes. Once the project is paid in full, you own the code, designs and everything we built for you. We hand over the repositories, store accounts and documentation.

Adding payments to your app?

Tell us where you sell and what you want to charge for. We will reply with questions and a fixed-price proposal.

Start a payments project