I am a Ruby on Rails and React.js developer with ten years of experience, allowing me to build robust and groundbreaking digital products for Fintech and eCommerce clients. I have actively introduced company-wide coding best practices throughout my career as a Ruby on Rails Tech Leader. 

Mateusz Wieczorek

Wondering how to choose a Ruby on Rails development company? Read the post to find out how to successfully outsource your RoR project.

Outsourcing RoR | How To Choose A Ruby On Rails Development Company?

No matter what type of platform you own: eCommerce, eLearning or a booking one, your main concern will always be to ensure that your customers are safe and you provide them with an easy-to-use payment system.

The provider you choose has to satisfy the needs of your business as well as the requirements of your customers.

Over [21% of customers](https://www.google.com/url?q=https://baymard.com/lists/cart-abandonment-rate&sa=D&ust=1591985041593000&usg=AFQjCNGN1dBpeELBtJn_Lu2ebCf7_6Zxzg) tend to abandon websites that have a long checkout process and 17% because the website was not secure.

![](https://s3.amazonaws.com/a.storyblok.com/f/86602/800x480/24df8194a2/reasons-for-abandoment-during-checkout.png)

Integrating a payment gateway into your store will give your website security and improve the overall user experience.

If you are looking for more information on payment gateways and how to implement payment gateway into your system, keep on reading.

## What is a payment gateway?

A payment gateway is a solution that connects your bank account with a merchandising platform to which you wish to transfer money. It creates a secure tunnel between online retailers and buyers.

Most of eCommerce service providers create a website with payment options as it is a fundamental feature offered to their clients. It allows us to make purchases anywhere in the world while ensuring maximum data security.

Payment gateways are virtual terminals equivalent to physical point-of-sale terminals.

## How does a payment gateway work?

![](https://s3.amazonaws.com/a.storyblok.com/f/86602/800x533/5dfbc061da/payment-gateway.jpg)

**A payment gateway is an important broker between customers and merchants**. It is dealing with payment processing and authorizing. Payment gateways deliver an encryption method to sensitive data like credit card numbers. The data is encoded giving you a guarantee that it is sent securely between the online store and the customer.

Here is a basic flow of the transaction:

1. a customer finishes an order by clicking a submit button or its equivalent
2. the customer is redirected to a payment gateway allowing him/her to choose credit card payments or to be redirected to a bank website. The transaction is transferred to the issuing bank or another page like 3Dsecure to authenticate the transaction
3. if the authentication is successful the bank checks if the customer has enough funds on his/her account to make a response to the payment gateway that the transaction is a success or not
4. when the response from the bank is ready, it goes to the merchant. If the answer is negative, the merchant will display a notification about an error to the user. If it is positive, the merchant seeks the transaction from the bank
5. in the end, the bank settles the payment with the payment gateway, which settles the money with the merchant

The key points that any payment gateway provided are authorization, settlement and reporting.

## How does a payment gateway keep information secure?

Security is crucial in the eCommerce world. Customers want to keep their credit card information and payment information safe. Data security in online payments or eCommerce can be ensured by using technologies like:

* **TLS encryption -** payment gateways use SSL certificates. An easy way to check if our payment gateway uses a secured protocol is to check its URL. If it is https we can assume that we are secure
* **PCI-DSS Compliance -** the Payment Card Industry Data Security Standard was established to provide secure payment solutions by forcing companies to use Firewalls on their internal networks and encrypt the cardholder data while denying to store this data on disks or paper
* **Tokenization -** a way of substitution the real card numbers with randomly generated ones that are useless to hackers
* **Two-factor authentication -** an extra layer of security that is used to confirm the user’s identity by sending a message to a registered mobile number

## Benefits of using a payment gateway

Payment gateways have lots of benefits, that is why they are so popular in the eCommerce world. Let’s present some of them:

* **Security:** payment gateways secure transactions by protecting and encrypting sensitive data
* **Sales boost:** they help you expand your business by reaching to customers from all over the world
* **Time saving:** transactions are much quicker than standard manual processing via bank
* **Everyday at any time:** payment gateways work 24/7
* **Security, once more:** thanks to payment gateways you can avoid suspicious transactions by blocking transactions from certain countries or IP addresses
* **Marketing:** they have a positive impact on marketing since you can create affiliate program with rewards with referral commission from other sites

## Payment gateway transaction types

Payment gateway providers support many types of transactions. The most common ones are:

* **payment/sale/debit -** the most standard transaction. The payment gateway asks the bank about the authorization of transactions. If it is a successful settlement of the transaction will be accomplished by the end of a working day
* **authorization -** a payment gateway blocks demanded amount of money on the buyer’s account for the future settlement transaction. The period during which the money is blocked depends on the card system and the issuing bank but it usually takes from 3 to 7 days
* **capture -** this kind of transaction takes place when the merchant wants to charge the amount of money that was previously blocked by an authorization transaction. To capture a transaction means to send it for settlement
* **void -** if the transaction is not settled it allows to immediately unlock the previously blocked transaction on the user’s account without the need to wait for the blocking time to expire
* **refund -** a kind of transaction that gives the merchant an opportunity to cancel the transaction when the buyer had been already charged. It sends the money back to the client’s bank account
* **chargeback -** an operation when a customer appeals to the bank about the charges on their bill. A customer can appeal in cases when the item was not received, due to technical problems, unauthorized card usage or in the case of a friendly-fraud situation
* **credit -** a transaction similar to a refund. It can only proceed in the case when the previous transaction successfully incomed to the buyer’s account. The merchant can credit user’s credit card exceeding the amount of money from the previous successful transaction

<Baner name={software-development} />

## Payment gateway types

There are two types of payment gateways: **hosted and non-hosted**. In a hosted payment gateway after clicking the purchase button the customer is redirected to the payment service provider page.

In non-hosted payment gateways the user enters the debit or credit card details directly on the checkout page of the store owner.

Here are the most popular payment gateway providers:

HOSTED PAYMENT GATEWAYS

* [PayPal](https://www.paypal.com/pl/home)
* [Amazon Pay](https://pay.amazon.com/)
* [Stripe](https://stripe.com/)
* [SagePay](https://www.sagepay.co.uk/)

NON HOSTED PAYMENT GATEWAYS

* [Authorize.net](https://www.authorize.net/)
* [BrainTree](https://www.braintreepayments.com/)
* [PayPal Pro](https://www.paypal.com/us/webapps/mpp/referral/paypal-payments-pro)
* [PayU](https://poland.payu.com/)
* [Adyen](https://www.adyen.com/pl_PL/;jsessionid=FC0CF6768B912CDADC0019BBB84A4BE3)
* [FirstData](https://www.firstdata.com/pl_pl/home.html)
* [MongoPay](https://www.mangopay.com/)
* [SagePay Direct](https://www.sagepay.co.uk/support/find-an-integration-document/direct-integration-documents)

### Costs of using payment gateways

The overall costs of using a payment gateway services depends on your overall turnover. However, you should keep in mind that the transaction fee starts from about 2,9% up to 3,5% plus an additional $0,30 per each transaction.

Some of the payment gateways also have monthly fees as well as an installation fee, so take it into consideration when choosing a provider.

## How to integrate a payment gateway

Follow the steps to embed payment on website.

PayPal integration

1. create a [PayPal button](https://gist.github.com/Lkubok/5264856b3e6d639e9c025d0214cfcc9a#file-paypal1-txt)

   <Gist id="6485f4af4d7228dfff368efa8de7fc10" />
2. set up the [basic payment](https://gist.github.com/Lkubok/5264856b3e6d639e9c025d0214cfcc9a#file-paypal2-txt)

   <Gist id="3ad9034881cb8fa95f3ca23a95c1ed71" />
3. extend the basic payment with [additional parameters](https://gist.github.com/Lkubok/5264856b3e6d639e9c025d0214cfcc9a#file-paypal3-txt)

   <Gist id="a9e620d40d13768861fc6ff8a77bd62b" />
4. [execute](https://gist.github.com/Lkubok/5264856b3e6d639e9c025d0214cfcc9a#file-paypal4-txt) the payment

   <Gist id="9f5a15453d765f13964710c5846bf654" />

Amazon Pay integration

1. create an [Amazon Pay button](https://gist.github.com/Lkubok/f7ce0eedb2e8c779de0ace956494a388#file-amazon1-txt)

   <Gist id="9d14894606b86ec913207a5919734f95" />
2. add [Address Book and Wallet Widgets](https://gist.github.com/Lkubok/f7ce0eedb2e8c779de0ace956494a388#file-amazon2-txt) to your website

   <Gist id="62ffb6af65c31abafadb375ac312a7d2" />
3. [obtain buyer’s authorization](https://gist.github.com/Lkubok/f7ce0eedb2e8c779de0ace956494a388#file-amazon3-txt) for recurring payments

   <Gist id="c85976054c41fad9adbbb89609d6c240" />
4. [set a billing agreement details](https://gist.github.com/Lkubok/f7ce0eedb2e8c779de0ace956494a388#file-amazon4-txt) and confirm the agreement

   <Gist id="8448c5d2194facba04002be1eb400826" />
5. [validate](https://gist.github.com/Lkubok/f7ce0eedb2e8c779de0ace956494a388#file-amazon5-txt) the billing agreement

   <Gist id="bf0c48f589ba611ee8517c2caae053f7" />
6. [request authorization](https://gist.github.com/Lkubok/f7ce0eedb2e8c779de0ace956494a388#file-amazon6-txt)

   <Gist id="7bf28f1aeb608393d6e932d8f9453da5" />

Tada! Your payment gateway is ready!

## Conclusions

There are many ready-made solutions for payment gateways on the market. Choosing the right provider is a key decision for growing your business. Implementing a payment gateway into your website will deliver enhanced user experience and maximum security for your customers. Many of payment gateways are equipped with security measures like TLS encryption, two-factor authentication and are PCI-DSS compliant.

Integrating a payment gateway is not complicated and will definitely have a positive impact on your store.

If you are looking to create a website integrated with a payment gateway or need to add a gateway to your existing product, [contact our team of developers](https://selleo.com/ecommerce-development-company).

In this article, we'll show you how to integrate a payment gateway into a website. We'll also provide tips on which gateway to choose and make it work.

How To Integrate A Payment Gateway Into A Website

I'd like this to be a reasonably detailed overview of how does the upgrade process in Rails look like in general, but with a strong emphasis on **Rails 5.2 to 6 upgrade** part (RC1 being the latest release). I've already seen a number of great posts describing the list of changes that awaits us in **Rails 6**, so I will skip this entirely and will focus solely on the upgrade. Keep in mind that even though it's an overview, it is possible that when given a big enough application, the customization on your side may make using e.g. `rails app:update` impossible.

## Should I upgrade yet/things to consider

According to DHH, Rails 6 beta1 was already stable enough to run your projects on it. In fact, in his [Rails blog post](https://weblog.rubyonrails.org/2019/1/18/Rails-6-0-Action-Mailbox-Action-Text-Multiple-DBs-Parallel-Testing/) he writes that Basecamp has already been migrated.

> Basecamp is already running Rails 6.0.0.beta1 in production, and both Shopify and GitHub and surely others will follow close thereafter. This isn’t some rickety-shack release.
> *DHH*

BUT, since there's still no official release yet, you may find that some of the gems you use are not prepared for the upgrade yet. If the gem has Rails version restricted to 5 or lower (or any other dependency for that matter), you may possibly fall into a dependency hell right from the start. If you really don't want this in your life right now, it might be a better choice to wait until most of the gems' creators catch up. Keep in mind though that this might change quickly - I saw big progress in this aspect these past several weeks.

Another thing to consider is how strongly do you feel your app is covered with tests. **Having good tests is absolutely crucial for major upgrades**. You will change dozens of settings in the process, each of which may change the way the app is working. If you want to know which issue was caused by which change (and I think you want to), you might end up spending obscene amounts of time on manual testing. So if you app is lacking in that department,  try to fill in all the gaps of your test suite before progressing.

## How to upgrade to Rails 6?

### Step 1: Update Ruby to at least version 2.5

Depending on the size of your app and how big of an upgrade it is, during the **Ruby upgrade** you might encounter a whole bunch of errors or you may see none (OK, that's unlikely). Even when coming from relatively new Ruby versions, I advise you to make these changes incrementally. Ruby releases come in the following pattern: `ruby_{MAJOR}_{MINOR}_{TEENY}`. I don't think that upgrading by every TEENY version is needed, but incrementing by every other MINOR version (released each Christmas) is a good idea. At minimum, I would split the process into two parts, starting with the version in the middle (between your current and the destination one).

Run your tests after each iteration. Once you've got that working in test/development, repeat the same on the staging server, perform manual testing for any obvious problems and only then go with production. Depending on how much you trust your tests, you may want to give your app a few days before going further with the Rails upgrade.

### Step 2: Upgrade Rails to the latest version in 5.2 series (5.2.3 as of writing)

Before starting with **Rails 6 upgrade**, make sure you're on the latest available **Rails 5** version. If you're coming from versions earlier than 5, there are many articles touching the subject, including accounts from [Kickstarter](https://kickstarter.engineering/upgrading-kickstarter-to-rails-5-e8203f93df55), [Shopify](https://engineering.shopify.com/blogs/engineering/upgrading-shopify-to-rails-5-0) and [GitHub](https://github.blog/2018-09-28-upgrading-github-from-rails-3-2-to-5-2/).

### Step 3: Update the Gemfile with gem 'rails', github:  'rails/rails' and run bundle update rails

As already mentioned, this might be easier said than done. For mature applications, it is more than likely you will see a long, red list of unresolved dependencies. It *usually* isn't as bad as it looks - what you see is a result of the chain reaction which might have been caused by a mere single gem. The list is not displayed in any particular order (that I know of at least). You will get a bunch of `Bundler could not find compatible versions for gem XXX` errors, but usually, only a few of those include a conflicting gem. In my experience there are usually two kinds of culprits:

* rails related gems (`rails`. `railties`, `actionpack`, `activesupport` etc.) limited to versions < 6
* gems with an upgrade limited to minor versions by using the `\~>` operator   which is why I tend to look for these on the list first. In order to fix them, I usually have to manipulate a combination of project's `Gemfile` and `Gemfile.lock`, along with gems' `.gemspec`s and sometimes `Rakefile`s.   One of the projects I bundled (experimentally) for the needs of this article was `content-data-admin` from [alphagov](https://github.com/alphagov). In their case, the list had over 70 lines, but only one dependency was blocking the bundle from progressing (in that case it was `actionview` from the `govuk_publishing_components` gem (screenshot below).

![](https://s3.amazonaws.com/a.storyblok.com/f/86602/667x510/727dabd0d3/rails_6_1.png)

Whether the gem will work fine with the dependency unlocked is, of course, a different matter, but most of the gems should have no issues working with Rails 6 if they already worked with 5. With the previous versions (Rails 4 and 5) you could have used [Ready4Rails](http://www.ready4rails.net/) app to check whether the gem is ready to work with a particular Rails version - currently, there's no mention of **Rails 6**, but this might change by the time you read this.

Bumping the Rails version might fix the problem, although this comes with an obvious disadvantage of having to either fork each of these gems or finding someone who's already done it for you. I am not aware of any workarounds here, so bear that in mind before going further. In my biggest upgrade out of 231 gems I had bundled, 6 had to be forked and upgraded manually.

### Step 4: Run rails app:update from terminal

`rails app:update` leads you step by step by adding the new config settings to your app. It's an interactive process which is seemingly easy but can lead to some unexpected problems if enough caution is not taken. I recommend you to run the diff tool (`d`) for every suggested file change to be fully aware of the change extent.

![](https://s3.amazonaws.com/a.storyblok.com/f/86602/800x76/ecb381608c/rails_6_2.png)

I doubt you will want to overwrite some of the files it will suggest (e.g. routes or I18n files). You have two options here:

* Before choosing `y`/`n`, select (`m`) and merge the files with a tool of your choice
* Use `y` for every file, then using merge tool/IDE go file by file and see what changes were implemented. Combine the new settings with the old, custom ones.    Personally, I prefer the second approach - I get to decide in what order the files are updated, having better control and view of things overall. Note: both this and the next step can be tiresome. Give yourself a favor and approach each setting individually. It is extremely easy to miss/add/remove one little thing, which will eventually lead to hours of debugging that could have been otherwise avoided. If you get lost in what's new and what's old, [this site](http://railsdiff.org/)\* can be helpful. And since you're on it, check the [default configs](https://edgeguides.rubyonrails.org/configuring.html#results-of-load-defaults) from previous upgrades as well (if the project started before Rails 5), this is a good moment to have them set correctly.

As the comment on the main page states - the tool shows the difference between the newly generated application in different Rails versions. It *does not* show all the commits implemented between the versions internally.

### Step 5: Uncomment defaults in `new_framework_defaults_6_0.rb`

As of now (Rails 6.0 RC1), the comment at the top of the file is slightly misleading. It advises to "flip defaults", where in fact you should simply uncomment the flags. It goes back to **Rails 5.0**, where after updating from Rails 4.2 the flags were uncommented and set to `false` by default, and only then were supposed to be switched to `true`. This is not the case in **Rails 6** - here, the flags already have the correct values. The comment should be [fixed](https://github.com/rails/rails/pull/33584) in the final release though. All flags with their defaults are listed and described in the [Configuring Rails Applications](https://edgeguides.rubyonrails.org/configuring.html) guide, although the comments in the file are already descriptive and should be enough to let you make the right decision (to uncomment or not).

### Step 6: Add missing gems and bundle

Each major **Rails version** comes with a slightly different set of gems. Unfortunately, the `rails app:update` command will not help in that aspect, so without manual changes, the app may break without some dependencies in place. There are many ways you can approach this - using [RailsDiff](http://railsdiff.org/5.2.3/6.0.0.rc1)  is one of them (see: Gemfile).

### Step 7: Run migrations

[Should be required only if ActiveStorage is installed](https://github.com/rails/rails/pull/35620).
![](https://s3.amazonaws.com/a.storyblok.com/f/86602/1126x28/faff51db17/rails_6_3.png)

### Step 8: Go through [official upgrading Rails guide](https://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-5-2-to-rails-6-0) and [release notes](https://edgeguides.rubyonrails.org/6_0_release_notes.html)

Implement changes from the first link if needed. Skim through the second link to search for any potential breaking changes that might be specific to your app. If you have good test coverage, most of the problems will come up while running the test suite anyway.

### Step 9: Run the tests, suppress deprecations

Right after the bigger **update** (especially on legacy projects), deprecation warnings can take the majority of output you will get from the tests. My advice is to fix them as quickly as possible. You *could* hide them with `ActiveSupport::Deprecation.silenced = true`, but you will have to tackle the problem at some point anyway, so why not do this now? This part  isn't too hard and is very rewarding at the same time - making the output clean really feels like progress.

### Step 10: Run the tests, fix the failing ones

It's impossible to cover enough material here to be helpful to any significant number of readers. It seems that lots of people already started trying out **Rails 6 upgrade**, as most of the issues I encountered were already reported/asked about on boards. Some of them have been even [fixed](https://github.com/thoughtbot/shoulda-matchers/issues/1167) in the meantime, which is showing that the upgrade will get only easier as time passes.

### Step 11: Perform manual tests

As much as I'd love to believe that automatic testing is all we need, after getting all green, I like to open the page on the server and **check manually** if anything was overlooked.

### Step 12: Push to staging

Before going live, set up or use existing staging to test the app in an environment looking closer to production. If possible, get other people to test it with you.

### Step 13: Push to production

## Wrap up

The Rails 6 RC1 version isn't probably going to change much before the final release so now is a good time to seriously consider an upgrade. My feeling is that the procedure was much easier than for example from 4.2 to 5.0, especially if the app started on one of the 5.X versions. As always, having your dependencies up to date and good test coverage should very much ease the whole process.
First drafts of this article were written right after the Beta1 was released and in the span of the past weeks I can see the difference in community preparedness for making the leap. Hopefully, before you read this most of the problems will be already solved.

Need help with your Rails development? Contact our [expert team](https://selleo.com/ruby-on-rails-expert-developers-team). Want to read more? Check out other [related posts](https://selleo.com/blog/tag/ruby-on-rails).

This guide will show you how to upgrade to Rails 6. We'll cover the upgrade process in general and provide helpful tips to make your upgrade as smooth as possible.

How To Upgrade To Rails 6

\[TOC\]

## What is SaaS Subscription Management?

SaaS subscription management is, as the name suggests, the process of managing subscribers and their preferences. It refers to a broad range of subscription lifecycle operations including assigning credits or issuing refunds. Subscription management involves billing actions that cannot be scheduled, unlike recurring billing. Subscription management starts as soon as a customer signs up to your company’s services and ends whenever they leave or cancel the subscription.

Subscription managers can be both an external software and an integral part of your [payment gateway](https://selleo.com/blog/how-to-integrate-a-payment-gateway-into-a-website).

## What are the differences between Online subscription management and recurring billing?

As mentioned above, subscription management includes operations that cannot necessarily be automated.

Subscription management is an interaction between a business and its customers like changes to the subscription, customer communication and other customer-oriented tasks. Recurring billing, on the other hand, takes care of generating invoices and tracking payments. Subscription management and recurring billing work hand in hand and are often used interchangeably, although incorrectly.

## Benefits of SaaS subscription management

Subscription management has one definite advantage: it covers the entire customer lifecycle from start to finish. We can divide the subscription management benefits into three categories:

* sign-up - SaaS subscription management can be used to provide discounts for customers, free trials for the undecided visitors and trial extension.
* during subscription - when you gain a customer this is where subscription management starts to shine. From now on, it will cover upgrades and downgrades of the subscription plans as well as inform the customers about upcoming payments, updates and new features.
* after cancelling - when a customer leaves, you can still use subscription management to ask for feedback
* customer help - a SaaS subscription management platform provides a subscription experience history, you may access transaction history easily and make a refund, modify the plan or cancel it
* marketing data - the software will provide you with customer statistics, which is a great foundation for marketing planning, some of them also enable A/B testing
* time and money saving - subscription management software eliminates the need to outsource the management
* financial planning - subscription managers monitor revenue and visualize it so you can keep track of your income, find out which subscription generates the most income or plan your future spendings

There are many subscription management solutions that SaaS companies can choose from. Among the most popular we can distinguish **Stripe, BrainTree, Recurly, Chargebee, Sage, Zuora and Chargify**.

## Best subscription management software in 2020

### Stripe

![](https://s3.amazonaws.com/a.storyblok.com/f/86602/800x439/153cc9c470/stripe.png)

Source: [Stripe](https://stripe.com/en-pl/payments)

[Stripe](https://stripe.com/en-pl) is known for being extremely easy to use and to integrate. The system uses flexible APIs making it a great option for startups. It is a great example of a hybrid system equipped with a payment gateway, a subscription management platform and a merchant account. However, Stripe is a good base for billing but should be integrated with a subscription management platform with a greater range of features.

Developers tend to choose Stripe because it is developer-friendly with its easy setup process. The well-designed API and great documentation are what makes Stripe popular among companies like Kickstarter, Foursquare or Code School. What is more, it can be integrated with tools like Wufoo, Quaderno and Baremetrics.

### BrainTree

![](/uploads/braintree.png)

Source: [BrainTree](https://www.braintreepayments.com/products/braintree-direct)

[BrainTree](https://www.braintreepayments.com/) does not require implementation with a separate payment management system. It was created to provide a transparent system connecting multiple payment options. BrainTree works great across mobile and web platforms. It is an amazing option for both freelancers, small companies as well as large industries. What is more, Braintree has no minimum or monthly fees.

Braintree is a PayPal service so it is often chosen because of its well-designed API and the fact that it is developer friendly. Companies like Uber, Airbnb and Heroku use it in for their subscription management ventures.

### Recurly

![](/uploads/recurly.png)

Source: [Recurly](https://recurly.com/)

[Recurly](https://recurly.com/) is a great choice for SaaS companies that are freshly getting started with billing services. It can be used on top of payment gateway services. Recurly includes features like analytics and revenue recognition. It is often used together with Stripe.

This subscription management service is said to have a great recurring billing option and promoting simplicity. It works with multiple gateways and that is why Linkedin, Groupon and Twitch use it.

### Chargebee

![](https://s3.amazonaws.com/a.storyblok.com/f/86602/800x344/8d4adb0ba5/chargebee.png)

Source: [Chargebee](https://www.chargebee.com/)

[Chargebee](https://www.chargebee.com/) can handle all of the SaaS billing needs, which means billing, subscriptions, analytics etc. Thanks to the many options to customize the customer plans it is great for scaling. Chargebee has great, clear documentation which is appreciated by the users. However, with this solution, you will also need a payment gateway to process payments.

What is more, Chargebee is used by Soylent, Findify and Livestorm and can be easily integrated with MailChimp, Google Analytics and Salesforce Sales Cloud.

### Sage

![](https://s3.amazonaws.com/a.storyblok.com/f/86602/798x411/f0d22c8ab3/sage.png)

Source: [Sage](https://www.sageintacct.com/subscription-management-software)

[Sage](https://www.sageintacct.com/subscription-management-software) allows its clients to leverage comprehensive financial controls and streamline business processes. The system includes features like: subscription billing, accounting, inventory management, financial reporting or revenue recognition - all cloud-based.

Sage ensures financial control, security and compliance. It automates processes to reduce labor and save costs. It is the 3! rated revenue management software in customer satisfaction by G2.

### Zuora

![](https://s3.amazonaws.com/a.storyblok.com/f/86602/800x383/9616989529/zuora.png)

Source: [Zuora](https://www.zuora.com/)

[Zuora](https://www.zuora.com/products/) is an evangelist of the Subscription Economy. At the heart of Zuora is an enterprise platform Zuora Central which is a solution between CRM and ERP. Central orchestrates all subscription processes in real-time. Zuora’s applications handle subscription pricing, orders, quoting, billing and payments. It is used by companies like Tata Communications, Ustream or Box. Enterprise leaders use Zuora’s multi-tenant cloud platform Z-Central to scale, launch and monetize subscription services.

### Chargify

![](https://s3.amazonaws.com/a.storyblok.com/f/86602/800x352/13b1bfdf94/chargify.png)

Source: [Chargify](https://www.chargify.com/)

[Chargify](https://www.chargify.com/) was built having fast-growing B2B SaaS businesses in mind. It is a billing and revenue management platform and is a leader in recurring billing and subscription management. It enables businesses to optimize, create and adapt their offers as well as manage change over time. It is used by thousands of businesses helping them drive billions in annual revenue. Chargify removes billing bottlenecks providing you with flexibility and speed.

## Summary

Choosing the best subscription management solution is a hard decision to make. Apart from the obvious aspects about the usability of a given solution we can also take into consideration the popularity of said solutions. However, each of the platforms has its own unique features and will definitely help your business grow.

If you need help with integration of those platforms or an entire team of developers, contact our [experienced team of engineers](https://selleo.com/saas-development-company) that will help you accelerate your online business, retain customers and gain new ones.

There are many subscription management solutions that SaaS companies can choose from. Among the most popular we can distinguish: Stripe, BrainTree, Recurly, Chargebee and PayPal Subscriptions. 

Mateusz Wieczorek

Blog posts that I worked on

Outsourcing RoR | How To Choose A Ruby On Rails Development Company?

How To Integrate A Payment Gateway Into A Website

How To Upgrade To Rails 6

Your Guide To Subscription Management Solutions

Tell us about your project