Show HN: Crosspay – We built cross-platform subs because Apple rejected our app

1 points by pcvetkovski 2 days ago

Hey HN,

We built Crosspay (by Maxint) because we were forced to. Here's the story:

Our app, Maxint, started on iOS/Android using RevenueCat for IAPs. We expanded to the Web, integrating Stripe, and later migrated to Adapty hoping for easier management. Everything seemed okay until we tried listing our MacOS app on the App Store.

Apple's requirement for native MacOS App Store in-app purchases became a hard blocker. The tools we used (and others we looked at) couldn't unify subscriptions across iOS (App Store), Android (Google Play), Web (Stripe), and MacOS (App Store) under a single user entitlement. Apple kept rejecting our app.

Faced with maintaining fragmented subscription logic or building our own unifier, we built Crosspay. It's designed to handle purchases from any of these platforms and sync the user's subscription status so they buy once and get access everywhere (iOS, Android, Web, MacOS, Linux and Windows).

It tackles the developer headache of reconciling disparate systems and the user frustration of multiple subs.

Try Crosspay on Maxint https://maxint.com/

Did you run into this MacOS IAP issue? We're keen to hear your thoughts, questions, and feedback!