App Store and PayPal revenue

Updated 2026-08-04

This is the app developer who also does client work — mobile subscriptions through Apple, and consulting or one-off invoices collected through PayPal.

It's a common and financially sensible combination: the client work funds the product while the product's recurring revenue grows.

Two streams with opposite characters

App Store subscriptions are small, numerous, recurring and slow-growing. Predictable.

PayPal consulting income is large, lumpy, unpredictable and finite. A single invoice can exceed a month of subscription revenue.

The temptation is to look at total income and feel fine. The risk is that consulting revenue masks a product that isn't actually growing — you feel successful right up until the client work stops.

Keep them separate deliberately

The useful framing:

• True MRR — product revenue only. The number that tells you whether the business is becoming self-sustaining.
• Today's cash — everything, including invoices. The number that tells you whether you can pay rent.

Consulting income should generally stay out of MRR unless it's a genuine recurring retainer. See does one-off revenue count towards MRR?.

What each side contributes

Current state: the PayPal half works today. The App Store integration authenticates and validates credentials but does not yet report sales.

Which means, honestly, that this particular pairing is the least complete of the five-platform set right now. If both halves are what you need, wait for the App Store reporting pipeline.

Setting up

App Store Connect needs an issuer ID, key ID and .p8 file. PayPal needs a REST app client ID and secret scoped to reporting.