What is Stripe?
Who uses Stripe?
Stripe Integrations
Here are some stack decisions, common use cases and reviews by companies and developers who chose Stripe in their tech stack.
Stripe is used as one of our payment-gateways included in our shop-solution. We only use the credit-card features of it and don't accept any bitcoins (yet).
We've been using Stripe for a while to charge our customers (mostly for the ads you see on StackShare), but we only recently realized that you can actually invoice and charge customers all through Stripe's UI 😱
You just need a customer's email address, then you add them as a customer and create a new invoice and send it to the customer- all via the Stripe dashboard. The customer then gets an email with a link to the pay the invoice (via credit card, ACH, or wire transfer). Once the customer clicks the link in the email to pay they're taken to a page hosted at pay.stripe.com where they can download a PDF of the invoice and pay via credit card, or ACH/wire transfer.
Nevermind the fact that we built an entire Rails app to do all this 😒 We'll be sunsetting our payments app soon. I wish someone had told us about these features sooner! I doubt they had this when we first built the app but we could have stopped using/maintaining the app a while ago. Stripe is amazing. That is all.
#invoicing #payments
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 :-)
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
I am building a platform for a health provider using Vue.js with Cloud Firestore and Cloud Functions for Firebase. Some of the app features are: Video chat, Chat 1 to 1 Payment - using Stripe Mange clients - CRM
I am debating whether to stay with Cloud Firestore and Cloud Functions for Firebase as my backend (using ExpressJS) I built it in a way that will be easy to change to Rest API with other DB, but not sure if I want to keep using Firestore
Blog Posts
Stripe's Features
- Full-stack payments- You don’t need a merchant account or gateway. Stripe handles everything, including storing cards, subscriptions, and direct payouts to your bank account. Stripe.js lets you build your own payment forms while still avoiding PCI requirements.
- An API that gets out of your way- It’s so easy, we’ve embedded a bunch of examples right here. Copy some of these requests into your terminal and check out what happens. With wrappers in Ruby, PHP, Python and more, you can get started in minutes.
- Pricing like it should be- 2.9% + 30 cents per successful charge. No setup fees, no monthly fees, no card storage fees, no hidden costs: you only get charged when you earn money.
- We’re developers too- Our team is full of developers and entrepreneurs who have been there and seen the problems in this industry firsthand.
- Used by thousands of sites & apps- Stripe powers commerce for thousands of sites across the web. Our users include large companies, rapidly-growing start-ups, side projects, and everything in between.
