Lago is better in that they have have support for custom payment integrations [3].
[2] https://paystack.com/stripe/south-africa
[3] https://getlago.com/docs/integrations/payments/custom-paymen...
I think the offering is similar -- both manage entitlements and paywalls. And while we do have a proportion of users that use us for mobile apps we're pretty focused on SaaS / web.
I can imagine Adapty would go deeper on features like AB testing, paywall designing etc
Our users handle lower volume of subscriptions but require more flexibility and depth on the pricing models they want to support.
This means you don't need to store any additional IDs for billing -- just make calls to Autumn with your exiting auth uuids.
Past invoices: - We have a GET /customer method that returns all billing related information on a user. This includes their current plans, features and balances they have available, and can take in an expand?=invoices param that will return all past invoice data for you to display.
Users can also see invoice history in the Stripe billing portal mentioned above.
I've suffered so much with all the pricing changes I've been experimenting with (early stage solo founder). Till now had been chugging along doing it manually but I'm going to integrate autumn soon.