In-App Payments in Australia: Cards, PayTo and Store Rules

Quick answer: If your app sells digital content or features used inside the app, Apple and Google generally require their own in-app purchase systems. If it sells physical goods or real-world services, you take payment through your own processor, using cards, Apple Pay, Google Pay or PayTo. Federal Court orders against Apple, set to apply from March 2027, are loosening those rules for Australian users, so check the current guidelines before you design checkout.

Two questions decide how an Australian app collects money: what exactly is the customer paying for, and where will they use it? Answer those first and the choice between Apple's in-app purchase, a card form, Apple Pay and PayTo mostly makes itself. The business model behind the app, whether subscriptions, one-off purchases or ads, is a separate decision covered in our guide to app monetisation models.

When must you use Apple and Google in-app purchase?

When the purchase unlocks something digital that is used inside the app. Apple's App Review Guidelines (section 3.1) and Google Play's payments policy both work on this principle, with specific exceptions.

Store billing comes with a commission, commonly 15% for smaller developers enrolled in Apple's and Google's small business programmes and up to 30% otherwise. Using your own processor for digital content where store billing is required is a frequent rejection reason, which our app store submission checklist covers.

When can you take cards, Apple Pay or Google Pay directly?

Whenever the customer is paying for physical goods or a service delivered in the real world. Here you integrate a processor such as Stripe, Square, Tyro or Adyen, and the app stores take no commission.

Good practice for app checkout:

• Offer Apple Pay and Google Pay first. Customers confirm with Face ID or a fingerprint instead of typing card numbers, which suits small screens.
• Use the processor's native SDK so card details go straight to the processor and never touch your servers. That keeps your security obligations under the card industry's PCI DSS standard much lighter.
• Support saved cards properly, with the customer's agreement, for repeat orders and bookings.
• Handle authentication challenges gracefully, since banks may ask customers to approve some card-not-present payments.
• Test refunds and partial refunds, not only payments.

What is PayTo, and when does it beat cards or direct debit?

PayTo lets a customer approve a payment agreement inside their own banking app, after which you can collect payments directly from their bank account. It is run by Australian Payments Plus on the New Payments Platform, and payments settle in near real time. Customers can see, pause or cancel agreements in their banking app.

PayTo is strongest where payments recur or vary: memberships, childcare and tuition fees, service plans, utilities and instalments. It can also suit larger one-off payments where card fees hurt. Australian Payments Plus expects PayTo to take over much of what direct debit forms used to do.

Its limits are practical: the customer must switch to their banking app to approve, not every bank account is PayTo-enabled yet, and your processor must support it. Keep cards as a fallback.

How do subscriptions and recurring billing work across these options?

The route depends on what the subscription delivers.

• Digital subscriptions used in the app generally run through the stores' subscription systems. The store handles renewals, cancellations and receipts; your server listens to the stores' notifications to grant or remove access.
• Real-world services, such as a weekly cleaning plan or a gym membership, are simpler as card-on-file billing through your processor or as a PayTo agreement. Both allow variable amounts within agreed limits and let you control retries.
• Mixed models, such as a membership bought on your website and used in the app, need care. Check what the current guidelines allow you to say inside the app about buying elsewhere.

Whichever route you take, plan reconciliation. Processor payouts arrive net of fees, refunds and disputes, and should map cleanly into Xero or MYOB so your bookkeeper is not untangling them each month. Our comparison of subscription billing providers covers billing logic in more depth.

What could change after the Epic court cases in Australia?

Quite a lot for apps sold to Australians, although the details are still settling. In August 2025, the Federal Court of Australia found that Apple and Google had misused their market power, in breach of the Competition and Consumer Act, including through restrictions on in-app payments. In October 2026, the court made remedies orders against Apple that, as reported, apply from 1 March 2027 to the Australian App Store. They require Apple to allow alternative payment methods and alternative app marketplaces for Australian users.

What that means for app owners:

• Check the current guidelines for Australia before designing checkout for digital content, because options that were prohibited may now be allowed.
• Do not assume zero fees. How Apple implements the orders, including any commission on outside payments, will decide the real economics. Appeals may also change the picture.
• Watch Google separately. Its obligations follow from the same litigation but on their own timetable, so confirm Google Play's current Australian policy.
• Build a swappable payment layer. Keep payment logic behind one internal interface so you can switch between store billing and your own processor by country without rewriting the app.

Which provider should handle payments in your app?

Choose on how well the provider fits your app and your accounts, not only on the per-transaction fee. Questions to ask:

• [ ] Are the iOS, Android and cross-platform SDKs (Flutter, React Native) mature and well documented?
• [ ] Are Apple Pay, Google Pay and PayTo supported in the same integration?
• [ ] How quickly do payouts reach your Australian bank account?
• [ ] Does it reconcile cleanly with Xero or MYOB?
• [ ] How are disputes, refunds and fraud screening handled?
• [ ] Are webhooks reliable and signed, with good retry behaviour?
• [ ] Can it handle other currencies if you expand to the UK or US?
• [ ] What does support look like when payments fail on a Friday night?

A cheaper rate is a false saving if reconciliation eats your bookkeeper's week. For build budgets, our Australian app cost guide puts simple-to-mid cross-platform apps at $40k–150k, with payment complexity one of the factors that moves the figure.

Frequently asked questions

Do I have to use Apple in-app purchase in my app?

Only for digital content or features used inside the app, and even then the March 2027 orders may give Australian users alternatives. Physical goods and real-world services must use your own payment processor, not Apple's in-app purchase.

Can I use Stripe in an iPhone app?

Yes, for physical goods and real-world services such as bookings, deliveries and tickets, including Apple Pay through Stripe. For digital content unlocked in the app, Apple's in-app purchase has generally been required, though the Australian court orders may widen the options for Australian users.

What is PayTo, and how is it different from direct debit?

PayTo lets customers approve a payment agreement in their banking app instead of filling in a direct debit form with their BSB and account number. Payments settle in near real time, failures show up quickly, and customers can see, pause or cancel the agreement themselves.

Does PayTo work with every Australian bank?

Not every bank and account yet. Major banks support it, but some smaller institutions and some account types do not. Check your provider's eligibility checks and keep card payments as a fallback.

Are app store payment rules changing in Australia?

Yes. Following the Federal Court's 2025 findings, orders made against Apple in October 2026 require it to allow alternative payment methods for Australian users from March 2027. Google's position is following its own course, so check both stores' current Australian policies before you build.

Plan payments before you design screens

We build apps for Australian businesses with payment flows that fit both the store rules and your accounting. See how we approach mobile app development, or book a free call and we will map the right payment route for your app.