Alternatives to Ripple logo

Alternatives to Ripple

Stellar, Ethereum, Swift, Stripe, and PayPal are the most popular alternatives and competitors to Ripple.
20
19
+ 1
0

What is Ripple and what are its top alternatives?

It is an open source protocol which is designed to allow fast and cheap transactions.
Ripple is a tool in the Blockchain category of a tech stack.

Top Alternatives of Ripple

Ripple alternatives & related posts

Stellar logo

Stellar

2
11
0
2
11
+ 1
0
Fast database snapshot and restore tool for development
    Be the first to leave a pro
    Stellar logo
    Stellar
    VS
    Ripple logo
    Ripple
    Ethereum logo

    Ethereum

    227
    160
    1
    227
    160
    + 1
    1
    Open source platform to write and distribute decentralized applications
    Ethereum logo
    Ethereum
    VS
    Ripple logo
    Ripple
    Swift logo

    Swift

    8.3K
    6K
    1.1K
    8.3K
    6K
    + 1
    1.1K
    An innovative new programming language for Cocoa and Cocoa Touch.
    Swift logo
    Swift
    VS
    Ripple logo
    Ripple

    related Swift posts

    Shivam Bhargava
    Shivam Bhargava
    AVP - Business at VAYUZ Technologies Pvt. Ltd. | 20 upvotes 40K views

    Hi Community! Trust everyone is keeping safe. I am exploring the idea of building a #Neobank (App) with end-to-end banking capabilities. In the process of exploring this space, I have come across multiple Apps (N26, Revolut, Monese, etc) and explored their stacks in detail. The confusion remains to be the Backend Tech to be used?

    What would you go with considering all of the languages such as Node.js Java Rails Python are suggested by some person or the other. As a general trend, I have noticed the usage of Node with React on the front or Node with a combination of Kotlin and Swift. Please suggest what would be the right approach!

    See more
    Siddhant Sharma
    Siddhant Sharma
    Tech Connoisseur at Bigstep Technologies | 12 upvotes 499.5K views

    WordPress Magento PHP Java Swift JavaScript

    Back in the days, we started looking for a date on different matrimonial websites as there were no Dating Applications. We used to create different profiles. It all changed in 2012 when Tinder, an Online Dating application came into India Market.

    Tinder allowed us to communicate with our potential soul mates. That too without paying any extra money. I too got 4-6 matches in 6 years. It changed the life of many Millennials. Tinder created a revolution of its own. P.S. - I still don't have a date :(

    Posting my first article. Please have a look and do give feedback.

    Communication InAppChat Dating Matrimonial #messaging

    See more

    related Stripe posts

    Adrien Rey-Jarthon
    Adrien Rey-Jarthon
    Founder at updown.io | 13 upvotes 124.9K views
    Shared insights
    on
    StripeStripePayPalPayPalBitPayBitPay
    at

    To accept payments on updown.io, we first added support for Stripe which is by far the most popular payment gateway for startups and for a good reason. Their service is of awesome quality: the UI is gorgeous, the integration is easy, the documentation is great, the API is super stable and well thought. I can't recommend it enough.

    We then added support for PayPal which is pretty popular for people who have money on it and don't know where to spend it (it can make it feel like you're spending less when it comes from PayPal wallet), or for people who prefer not to enter a credit card on a new website. This was pretty well received and we're currently receiving about 25% of our purchases from PayPal. The documentation and integration is much more painful than with Stripe IMO, I can't recommend them for that, but not having it is basically dodging potential sales.

    Finally we more recently added support of BitPay for #Bitcoin and BitcoinCash payments, which was a pretty easy process but not worth the time in the end due to the low usage and the always changing conditions of the network: the transaction fees got huge after price raise and bitcoin because unusable for small payments, they then introduced support for BCH and a newer Bitcoin protocol for lower fees, but then you need a special wallet to pay and in the end it's too cumbersome, even for bitcoin users, to pay with it. I think unless you expect a bit number of payments using cryptocurrencies it's not worth implementing this solution, and better to accept them manually.

    See more
    Tom Klein
    Tom Klein
    CEO at Gentlent | 11 upvotes 254.8K views

    Google Analytics is a great tool to analyze your traffic. To debug our software and ask questions, we love to use Postman and Stack Overflow. Google Drive helps our team to share documents. We're able to build our great products through the APIs by Google Maps, CloudFlare, Stripe, PayPal, Twilio, Let's Encrypt, and TensorFlow.

    See more

    related PayPal posts

    Adrien Rey-Jarthon
    Adrien Rey-Jarthon
    Founder at updown.io | 13 upvotes 124.9K views
    Shared insights
    on
    StripeStripePayPalPayPalBitPayBitPay
    at

    To accept payments on updown.io, we first added support for Stripe which is by far the most popular payment gateway for startups and for a good reason. Their service is of awesome quality: the UI is gorgeous, the integration is easy, the documentation is great, the API is super stable and well thought. I can't recommend it enough.

    We then added support for PayPal which is pretty popular for people who have money on it and don't know where to spend it (it can make it feel like you're spending less when it comes from PayPal wallet), or for people who prefer not to enter a credit card on a new website. This was pretty well received and we're currently receiving about 25% of our purchases from PayPal. The documentation and integration is much more painful than with Stripe IMO, I can't recommend them for that, but not having it is basically dodging potential sales.

    Finally we more recently added support of BitPay for #Bitcoin and BitcoinCash payments, which was a pretty easy process but not worth the time in the end due to the low usage and the always changing conditions of the network: the transaction fees got huge after price raise and bitcoin because unusable for small payments, they then introduced support for BCH and a newer Bitcoin protocol for lower fees, but then you need a special wallet to pay and in the end it's too cumbersome, even for bitcoin users, to pay with it. I think unless you expect a bit number of payments using cryptocurrencies it's not worth implementing this solution, and better to accept them manually.

    See more
    Tom Klein
    Tom Klein
    CEO at Gentlent | 11 upvotes 254.8K views

    Google Analytics is a great tool to analyze your traffic. To debug our software and ask questions, we love to use Postman and Stack Overflow. Google Drive helps our team to share documents. We're able to build our great products through the APIs by Google Maps, CloudFlare, Stripe, PayPal, Twilio, Let's Encrypt, and TensorFlow.

    See more

    related Braintree posts

    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.

    Invoicing

    • 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 :-)

    See more
    Mark Catalano
    Mark Catalano
    Co-Founder at TakeShape | 1 upvotes 71.3K views

    Deciding what tools to use to set up selling from a JAMstack site. Stripe, PayPal, Braintree, @snipcart, @gumroad, @foxy, @memberful, Chargebee, Recurly.

    See more
    Adyen logo

    Adyen

    94
    124
    43
    94
    124
    + 1
    43
    One integration allows businesses to accept 250 payment methods, from wherever people pay
    Adyen logo
    Adyen
    VS
    Ripple logo
    Ripple

    related Adyen posts

    Gabriel Pa
    Gabriel Pa
    CEO at NaoLogic Inc | 1 upvotes 18.7K views

    Stripe is awesome and works great for subscription models but there's a problem: If you want to make money, you need to have multiple payment gateways. That's why we choose Chargebee .

    We can integrate with Adyen or SagePay for EU customers without needing to create a new integration

    See more

    related Recurly posts

    Ajit Parthan
    Ajit Parthan
    CTO at Shaw Academy | 5 upvotes 46.3K views

    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.

    #Paymentgatewayintegration

    See more

    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.

    Invoicing

    • 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 :-)

    See more