If you’re looking to get into the app business, or if you’re already in it, but are just now considering adding a payment option for your app, you must be in search of a provider for such services. In-app payments are generally outsourced to established services that take care of the payment part and instate your app with the capability of accepting payments. There are several solutions for such a necessity, but in this article we are only going to talk about two of them, which are considered by many to be the best available. These are Stripe and Braintree. By the end of this article, you should have a better understanding of what it is both of these solutions offer, as well as develop an opinion on your owned. Let’s get into the details and see which might better serve your app requirements and needs:

The price of getting paid
The two services offer similar and yet slightly different solutions for pricing. Starting with Stripe, you have a flat fee that is charged for each successful card transaction. This fee is 2.9% in addition to 30 cents. Other than this, you are not required to pay any other type of regular fees.

Braintree offers a very similar deal, although there’s a very important difference. The flat fee they require is the same, 30 cents and 2.9% for each successful card charging. There is, however an important detail in the fact that with Braintree, this flat fee only comes into practice after your first $50000. This would estimate the money you end up saving to about $2000.

In the case of chargebacks, both will tax you $15 for every incident that occurs.

Who do you call?
When it comes to support, we have two different stories. Stripe will respond to your queries in about a day and a half from when you send it. Additionally, there is no option for telephonic contact. Your only bet is to use Stripe’s online form to send out a query.

Braintree approach customer support differently. From the moment you send out an inquiry, you can expect a response in the next 6 hours, which is drastically better than what Stripe offers. You can contact Braintree telephonically but their regular means of communication is email.

Who can use it?
Currently, both solutions come with a simplified and user friendly approach. This means that mobile app developers will find it easy to work with either of them. However, it is noteworthy that Stripe was first to adopt this model as Braintree joined up later, coming from a full-stack approach.

Accepted currencies
Both come with numerous accepted currencies under their belt, but as far as the most popular currency options go, both platforms are able to handle Euro, USD and GBP. It is also a very good thing that these currencies are supported everywhere, meaning that either Stripe or Braintree can accommodate your currency requirements wherever you are.

In terms of actual countries in which you can use these services with various currencies, there is a big difference in Braintree’s favor. Braintree feature a far more extensive list of supported countries. Among the top countries which you would expect to see on the list, you can also count the likes of Malta, San Marino or Liechtenstein.

Stripe seems to be going after a smaller, more coy group of supported customers, featuring countries such as Mexico or Japan. You can also count on the leading countries to feature on Braintree’s list as well.

Mobile SDKs
When it comes to mobile SDKs Stripe will offer you support for iOS 5 and everything released at a later date as far as Apple’s platform goes. For Android, the required minimum version is Android 4, and everything higher is accepted. Stripe also pleases its customers through the fact that it reduces the stress of PCI compliance handling, so that card data may be sent to its servers and get converted to tokens which are server-side code changeable.

Braintree needs you to have at least iOS 7 to function, while Android API 15 will do just fine as well. Unfortunately for Braintree users, the platform does not benefit from the same server mitigation benefits as Stripe. Braintree relies on custom Drop-in integration to acquire PCI compliances.

Conclusion
Now that you’ve learned a bit about the two services, you might find it easier to determine which one would better serve the interests of your app, company, or otherwise payment acceptance service dependant endeavor.