Choose a payment path and finish store agreements

Check which payment rules apply to your offer, finish the store agreements, and test purchases and restores.

By The Draftbit team · Updated
Sources checked

This guide is for Paid apps and apps selling subscriptions, digital features, physical products, or services.

You know what you want to sell, but you’re not sure which payment setup the stores allow. The answer depends on what people buy and where. Digital access, physical goods, and qualifying services can have different rules, and those rules can vary by storefront.

Write down what people buy, where they use it, which countries you’ll serve, and whether the app sends them elsewhere to pay. Include subscriptions sold on your website.

Check the rules for your product and storefronts

Start with the store’s default rules for digital goods and services. Compare your offer with the documented exceptions for physical goods and qualifying services.

Before adding external purchase links or alternative billing, check every intended storefront. Permission in one region doesn’t establish permission everywhere. Google programs can also require enrollment.

Only then choose the payment implementation. A working card form tells you that the payment works, but doesn’t establish that the store allows that purchase route.

Complete agreements and configure products

For Apple paid apps or in-app purchases, the Account Holder needs to accept the Paid Apps Agreement and finish the required banking and tax setup. Missing commercial setup can also prevent purchase testing.

Create the store products your build expects and check that the identifiers match. In the appropriate test environment, verify purchases, restores, and the access each purchase grants.

Give reviewers access and instructions for paid features. Keep the listing and subscription terms consistent with the actual offer.

On Apple, configuring a product doesn’t submit it. Follow the first-purchase review steps to include the app version, purchase items, and any required subscription group in the intended submission.

If purchases or submission are blocked

Work out whether the issue is an agreement, a product setting, broken app behavior, or a policy rejection. The Account Holder must resolve agreement tasks; another build won’t accept the contract.

Before changing the payment route after a rejection, reread the official payment rules. You’re ready when the route is supported in your chosen storefronts, required agreements are active, and testing confirms that the app grants and restores the correct access.

If Apple cites 3.1.2, compare the paywall with the actual subscription offer. If reviewers can’t reach the paid experience, check their access instructions.

Messages this guide can help with

Stripe allowed; in-app purchase; Paid Apps Agreement; banking tax information; subscriptions

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Next for Apple App StoreConnect your iOS bundle ID, signing, and app recordNext for Google PlayClear sensitive permissions and unexpected declarations