subscription-use-cases VS stripe-node

Imagine a scenario where your customer creates a new subscription and you’re listening for the following webhook events:

Subscriptions

Integrating a subscription service, for that I have decided to choose Stripe. Mainly because they have a lot of cool developer resources. Thankfully I have found a Github tutorial by Stripe,HERE, on how to create a subscription on the frontend and the backend.

Just curious, but is there a way to setup automatic monthly billing at your company? Like through Paypal or Stripe (or for hosting, WHMCS or Clientexec)? Your clients could set up their billing info and completely forget about it so that they never have to worry about making monthly payments on time. The hosting providers I work with always have an automatic system I rely on.

I'm looking into https://github.com/stripe-samples/subscription-use-cases thanks for suggesting stripe.

I want to build a product with metered billing, very similar to the example project here: https://github.com/stripe-samples/subscription-use-cases/tree/master/usage-based-subscriptions

Try this sample: https://github.com/stripe-samples/subscription-use-cases/tree/master/fixed-price-subscriptions. You host the pricing page. The user’s selection takes them to Checkout.

You can store payment details without an invoice. See https://stripe.com/docs/billing.

I'm talking about configuring it for subscriptions ... like this : https://github.com/stripe-samples/subscription-use-cases/tree/master/fixed-price-subscriptions/server/php-slim

Next, we will enable checkout and payment processing through Stripe. First, install the Stripe clients with the following command:

Head to Stripe and register if you haven't already. We can use the Stripe API in Test Mode to build the e-commerce app. You can add a bank account and get verified later when you're ready to start collecting real payments.

Stripe published its 2023 annual letter last week. Much like the previous edition it was filled with a lot of interesting nuggets. Stripe has a strong history of being fairly transparent with its practices. These range from engineering challenges through its blogs as well as thought leadership in the financial and entrepreneurship space. I personally like the writing style of this letter as it doesn’t seem corporate or stuffy. Instead it is filled with humorous anecdotes, quirky observations and intelligent historical narratives which make it a compelling read. You can read the letter here → Stripe Annual Letter: 2023

Stripe – payments

Imagine you want to create an API endpoint that allows users to register in your backend, while simultaneously making a payment towards Stripe. This could be for something that's a subscription-based service, where you charge people for access to something.

Our app – Upollo – connects with your app event data (like Segment) and payment data (like Stripe) to analyze your users and instantly figure out if someone is an important player in your industry. We also help you convert more users, reduce churn, and expand single seats to teams within a company. We're SOC 2 certified and we take data security very seriously.

That's cool - my page is still under development. But have you tried running it on something like https://stripe.com/ to see if the generates interesting results. Could share results here? DMing you also

Stripe is a great example of this as their margins on the side are visible with a faint line. All content is inside this except for some images and decorations.