Zoho Subscriptions

Really easy to set up, and integrated with the merchant processing of my choice. When we first switched over Zoho subscriptions were the only tool that could email multiple reminders to the clients prior to the billing renewal which I feel is great for subscription services.

The customer portal on the backend allows for customers to change their credit card information without me or one of my team members to have to do it manually. Super time saver.

It also notifies my team when a payment doesn't go through for whatever reason and can automatically retry the card again.

When we first started, it gave up to $50k worth of transactions as a free trial. Meaning you don't have to pay for a subscription until you reach 50k worth of transactions or a certain number of clients. Really cool.

The only thing I didn't like was that I couldn't do a one time payment easily. Sometimes we have one time jobs such as web development or consulting, and it makes it kind of hard to use just this one system. We had to also get Zoho invoice to complement what we were doing. So unless you are doing just recurring subscriptions you'll need to get an invoicing tool as well.
Als ran into problems with the customer portal, but most of my clients didn't wnat to log in so it wasn't that big of a deal.

Whilst working this was the ideal cost effective solution,

Zoho support is disgraceful. Irrespective of the situation and the urgency of a particular matter when speaking to someone you get the same generic response of we will get someone from technical support to look into it and contact you" the minimum this will take is 2 weeks. Even when they respond, their response either bares not resemblance to the matter you raised, or its someone else's fault.

Pricing structure
API integrations
Webhook announcements
Clean and intuitive admin panel
Robust reporting
Subscriber export
Subscription pricing flexibility with coupons and addons

The non-API deployment is a bit limited in terms of collecting any customer information that's not part of the default data. We didn't have the budget to do a full API deployment, but we were able to come up with some workarounds to collect info in fields not specifically designed for that information. When we did go with the full API deployment, it was pretty easy to transition our hacked-together data collection into the new custom fields.

It's quite easy to setup, far easier than other solutions. Nearly everything can be done 'no-code', where you can easily create subscriptions and start accepting payments easily. API is quite easy to use, if you need it.

It's extremely limited in what it can do, and the interface is a little clunky. I constantly experienced bugs when integrating it with Zapier, often times having to reach out to support in order to deploy a fix. You cannot do multi-lingual checkouts, which can be a huge issue in certain regions. The customer portal that they provide is also quite lacking in visual appeal.