Recurly vs Zuora: What are the differences?
What is Recurly? Subscription Billing. Zen Simplicity. Recurly is the leading pay-as-you-go recurring billing service because setup is easy, integrations are quick, and our service grows with the needs of your business.
What is Zuora? Billing, Commerce & Finance to Power your Subscription Business. Zuora gives you the enterprise-class, cloud-based tools you need to launch and scale any subscription service, quickly and affordably. Design your pricing and packaging, start taking quotes and placing orders, automate your billing and payments, and keep tabs on your financials.
Recurly and Zuora can be categorized as "Payment Services" tools.
Some of the features offered by Recurly are:
- Subscription Plans
- Account Dashboard
- Dunning Management
On the other hand, Zuora provides the following key features:
- Plan-Based Product Catalog
- Subscription Order Life Cycle
- Powerful Recurring Billing & Rating Engine
What is Recurly?
What is Zuora?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Zuora?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Recurly?
What are the cons of using Zuora?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Running a subscription service with just direct calls to Stripe or similar payment gateways is possible but also needs dedicated person(s) for decent amount of development and maintenance.
Plus features like updating card details, invoice history - all these can be built. Again, more dev work and resources.
Use of subscription platform like Chargebee or Recurly is definitely a great help here.
Chargebee offered a simple pay-as-you-go transparent pricing and almost trivial signup process.
Overall I've enjoyed working with Recurly, however, their XML only API response produced some headaches/delays in a Node-based (Meteor) project. Conversion of the XML worked, but the way responses were formed wasn't always consistent (e.g. for error handling) resulting in a lot of extra work.
The product is pretty good, but this XML issue along with improved API documentation would make it great.