Taxes and Commissions
How RevenueCat estimates taxes and commissions for transactions
RevenueCat can optionally report revenue after store commissions, or after taxes and commissions through various features like integrations, webhooks, and our Revenue chart; but there's some context you should be aware of when using RevenueCat's tax estimation to see your net revenue from a transaction.
How we estimate commissions
The factors we take into account to accurately estimate commissions vary by store, as each store has its own rates and policies for determining the percentage they take on a given transaction.
App Store
To determine the commission of a given transaction, we look at the original purchase date of the transaction, your presence in the App Store Small Business Program, and your Apple Alternative EU Terms Addendum dates, when applicable.
For more information, see the App Store Small Business Program and Apple Alternative EU Terms Addendum guides.
Google Play Store
To determine the commission of a given transaction, we look at the original purchase date of the transaction, the year-to-date sales for your application, and whether the transaction is a subscription renewal or a one-time purchase. This reflects Google’s reduced service fee of 15% on the first $1M in sales for a given app in a calendar year.
For more information on Google’s reduced service fee for the first $1M in sales, click here. Where Google’s 2026 fee structure has taken effect, we also take into account when the Customer first installed your app. See Google Play service fee changes in 2026.
Amazon Appstore
We apply a 30% store commission to all transactions from the Amazon Appstore.
Stripe
Stripe’s API provides the necessary details to calculate the various fees which might be charged in a transaction, and we sum these fees to calculate the commission charged by Stripe for a given transaction.
Google Play service fee changes in 2026
Google is replacing its single service fee with a service fee plus a 5% billing fee during 2026. RevenueCat doesn’t support Google’s alternative billing options, so the 5% billing fee always applies to the transactions we process.
The new structure takes effect region by region:
| Region | Effective date |
|---|---|
| EEA, UK, United States | June 30, 2026 |
| Australia, Japan | September 30, 2026 |
| South Korea | December 31, 2026 |
| Rest of world | September 30, 2027 |
Once it’s live in a Customer’s region, we deduct:
| Transaction | Service fee | Billing fee | Total |
|---|---|---|---|
| Subscriptions | 10% | 5% | 15% |
| One-time purchases, first $1M in the calendar year | 10% | 5% | 15% |
| One-time purchases above $1M, existing install | 25% | 5% | 30% |
| One-time purchases above $1M, new install | 20% | 5% | 25% |
Only the last row changes from the previous rates. Above the $1M threshold, we now deduct 25% instead of 30% when the Customer installed your app on or after the effective date for their region.
Google counts an install as new when the Customer first installed your app on or after that date. For apps not originally installed from Google Play, the first update from Google Play counts instead.
RevenueCat uses the earliest interaction we’ve recorded for a Customer as a proxy for their install date. If you adopted RevenueCat after your app shipped, we may treat some long-standing Customers as new installs.
Enrolling in Google’s Apps Experience Program or Games Level Up Program reduces these rates further. See Apps Experience and Games Level Up Programs.
For Google’s full description, see Understanding lower service fees.
How we estimate taxes
Transaction country identification
In order to calculate an accurate tax rate for each store, we need to know the country that the transaction occurs in and the applicable taxes for the store in that country.
In some cases (for example, USD or EUR transactions on the Google Play Store), we may have to estimate the country based on the customer's IP address, but in the vast majority of the cases the store country of a transaction is deterministic and known by RevenueCat, especially for transactions occurring in 2024 or later.
We do not take your location as a developer into account when estimating taxes to be withheld, though some stores & countries may withhold differently on transactions in the country you're operating in.
Calculating taxes for the mobile stores
The App Store, Google Play Store, and Amazon Appstore stores appear to charge both Value-Added Tax (VAT) and the digital services taxes (DST) that have been put in place by several countries. However, they do not apply identical tax rates for each country, so we:
- Find the proceeds quoted by the store for a given price in a given country
- Use that to determine the tax rate being charged to yield proceeds
To then calculate the portion of a given transaction that was deducted for taxes, we:
- Use the found tax rate to determine what was deducted from the customer price due to taxes:
price / (1 + [tax rate]) = [amount deducted for taxes] - Divide the amount deducted due to taxes from the customer price to get the
tax_percentagethat's provided in events, used to calculate Charts, etc:[amount deducted for taxes] / price = tax_percentage
Previously, we calculated taxes deducted from App Store transactions after commission had been deducted. In June 2024 we updated this behavior to deduct taxes first to better match Apple's behavior. Though the yielded Proceeds are not affected by this ordering, the portion deducted for taxes and commission respectively are changed by this. The Revenue chart and Scheduled Data Exports have been updated to reflect this improved definition, but please keep in mind that prior events dispatched by RevenueCat will still contain the old values.
Calculating taxes for Stripe
If you have enabled Stripe Tax in your Stripe developer account, we will retrieve the precise tax amounts directly from your Stripe invoices, making estimation unnecessary.
To learn more about enabling Stripe Tax in your Stripe developer account, click here.
Keep in mind that not all stores handle VAT the same way. Apple applies VAT to the post-commission revenue from a transaction, while Google applies VAT to the full amount, yielding different tax percentages (e.g. different values for the tax_percentage field).
How to report revenue after commissions and/or taxes in RevenueCat
Revenue chart
Our Revenue chart offers the following measures to understand your net revenue:
- Revenue (net of taxes): Revenue generated in a given period (as defined above), minus our estimate of revenue deducted from the stores for taxes (e.g. VAT, DST, etc).
- Proceeds: Revenue generated in a given period (as defined above), minus our estimate of revenue deducted from the stores for taxes and commission.
Integrations
For integrations which report revenue you’ll see the option to select a Sales reporting mode for the integration. Selecting either “Revenue after store commission” or “Revenue after store commission and taxes” will apply the respective calculations to your data so that your sales are reported in a format that is most appropriate for your use case.
To learn more about using integrations through RevenueCat, click here.
Webhooks
In our webhooks you will find a tax_percentage and commission_percentage field, which specify what percentage of your gross revenue (price and price_in_purchased_currency fields) we estimate to be deducted from your proceeds as taxes and commission. For example, you could calculate your proceeds in USD from the webhook payload as price * (1 - tax_percentage - commission_percentage).
To learn more about using our webhooks, click here.
Scheduled Data Exports
Our Scheduled Data Exports offer the same two fields, tax_percentage and commission_percentage, which can be use for estimating proceeds in the same manner through these exports.
To learn more about using our Scheduled Data Exports, click here.