Braintree vs Recurly: What are the differences?
Braintree: Accept payments in your app or website today. Braintree replaces traditional payment gateways and merchant accounts. From one touch payments, to mobile SDKs and international sales, we provide everything you need to start accepting payments today; 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.
Braintree and Recurly can be categorized as "Payment Services" tools.
Some of the features offered by Braintree are:
- Simple pricing with no minimums- Pay only for what you use, with no minimum monthly volume, at the simple US pricing rate of 2.9% + $.30 per transaction.
- An API developers love- Integrate your app with our API over a cup of coffee.
- We support your business model- Subscriptions or one-off, mobile or web, local or global, our platform adapts.
On the other hand, Recurly provides the following key features:
- Subscription Plans
- Account Dashboard
- Dunning Management
"Well-designed api" is the top reason why over 22 developers like Braintree, while over 17 developers mention "Recurring billing" as the leading cause for choosing Recurly.
According to the StackShare community, Braintree has a broader approval, being mentioned in 162 company stacks & 33 developers stacks; compared to Recurly, which is listed in 39 company stacks and 7 developer stacks.
Dear StackShare Community,
I am seeking inspiration on creating a billing & subscription stack and came across this wonderful website and community.
From what I understood so far, I need something like Stripe or Braintree to collect payments without dealing with PCI compliance or setting up merchant accounts, etc... Additionally, services like Chargebee, Recurly, Chargify, etc. are said to make life easier when dealing with recurring billing.
Stated below, I've tried to give you some context on what I want to achieve. I am very curious about your ideas and how you'd configure an optimal stack.
Project context (very high level):
Loyalty program for local merchants (stores, restaurants,...).
Customers support their community and merchants by shopping local.
Merchants grant points to customers based on a customer's value spent in a store, restaurant, etc.
Customers can redeem their points at any participating merchant.
Billing / Subscription scenarios to be considered:
(affecting merchants only)
One-time setup fee
What: Merchant pays a setup fee by signing up for the service
Where: Order placed on the website
Monthly retainer fee
What: Merchant pays a monthly recurring retainer for the service.
Where: Order placed on the website
Manually initiated payment
What: Merchant initiates a payment to top up his virtual points wallet. E.g. pays 100 USD to top up 100000 points which then can be used by the merchant for granting points to customers.
Why: Points issued to members need to be paid for by the merchant. We first considered billing the merchants post-ante, e.g. monthly based on the points they've granted to their customers in the last 30 days, but this seems too risky: If they can't / won't pay we'd still have to pay out points to the customers (technically to the merchants where the customers redeem their points). Thus, the pragmatic idea to reduce risk by having the merchants to pre-pay for their points by topping up their balance.
Where: Web application (with the merchant logged in)
Nice to have: Opt-in for automatically initiated top-ups if a merchant's balance falls below a certain amount.
What: After every transaction (setup, retainer, top-up,...), we need to automatically issue and send (E-Mail) an invoice to the merchant.
Nice to have: Customer portal with all their invoices.
Other potentially relevant parameters
Currency: Only Euro
Country: Only Germany (so far)
Tax: Only one tax rate
Payment for setup & retainer: Credit Card; ideally SEPA Direct Debit (but that still causes headache due to the SEPA regulatory and risk of chargebacks still after weeks), PayPal?
Payment for top-up: Same as above plus any other that makes sense (Klarna, Sofort, PayPal...)
Again, thank you very much for sharing your ideas and thoughts! I'd highly appreciate any input :-)
Stripe was made with developers in mind first so the extensibility of it is great! This makes it very easy for us to integrate and automate as much as we need with its APIs and SDK. It allows a lot of customization of exactly what we need to build our applications. They also manage all of our customers from a tax and accounting perspective which makes it easy from a business standpoint.
What is Braintree?
What is Recurly?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Recurly?
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
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.
I had the opportunity to integrate Braintree as a new gateway on a project I worked on last year (RoR project), the change from PayPal to Braintree was smooth and now it's really easy to maintain. The documentation for the API was super easy to follow. Really enjoyed using Braintree.
Braintree handles recurring credit card and Paypal payments for healthchecks.io. We liked the extensive developer documentation, the language-specific libraries and the friendly, timely communication from Braintree.
Gotta take the money, might as well take it in style and on all devices without too much headache. Oh and we use the fraud prevention tools.
Braintree is effectively the only good billing PaaS for Eastern European companies.