Recurly vs WePay: 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 WePay? The easiest way to accept payments. WePay helps people sell tickets to events, send invoices, sell items online, and accept donations online. WePay also provides an API that allows developers to access its payments platform.
Recurly and WePay belong to "Payment Services" category of the tech stack.
Some of the features offered by Recurly are:
- Subscription Plans
- Account Dashboard
- Dunning Management
On the other hand, WePay provides the following key features:
- Online Invoicing- Send custom, professional invoices to your customers. Customers receive an email and can pay online.
- Itemization- Get paid for all your work. Itemize your invoices so customers know exactly what they're paying for.
- Recurring Invoices- Save time by sending recurring invoices online. Automatically send invoices weekly, monthly, quarterly, or annually.
What is Recurly?
What is WePay?
Need advice about which tool to choose?Ask the StackShare community!
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 WePay?
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.