Need advice about which tool to choose?Ask the StackShare community!
Braintree vs Midtrans: What are the differences?
Developers describe Braintree as "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. On the other hand, Midtrans is detailed as "Empowering commerce through technology". It has helped thousands of businesses in Indonesia with a secure and convenient online payment system. It is compatible with various APIs and plug-ins for an easy integration process.
Braintree and Midtrans can be primarily classified 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, Midtrans provides the following key features:
- Can be used on various platforms
- Ease of reconciliation
- There are 20 payment methods
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.
Pros of Braintree
- Well-designed api25
- Developer friendly18
- Easy setup17
- Reliable14
- Excellent documentation6
- Great support4
- Can use paypal and debit card3
- Test it without obligation, great SDK/API and prices2
- Great API, awesome docs1
Pros of Midtrans
Sign up to add or upvote prosMake informed product decisions
Cons of Braintree
- Lacking documentation for mobile integrations1