subscription-use-cases VS datasette-stripe

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

If you want to analyse your payment failures with SQL you could use https://table.dog to download them into a SQLite database.

https://table.dog is a CLI that downloads your Stripe account to a SQLite db.

Would appreciate it if you could test it out if you are interested.

https://table.dog (a CLI to download Stripe to SQLite).

I considered Node.js, C#.

I went with Rust for a few reasons:

- Easy to build small portable binaries (as a primary language feature).

- The type checker ensures type consistency when writing out to SQL tables (SQLite is loosely typed). Code that reads from the SQLite database implicitly benefits from Rusts strong type checks.

- Macros to convert structs to SQL insert/updates.

- Reduce the chance of errors at runtime.

- Leverage as much as SQLite's write throughput as possible.

- When converting Stripes Open API JSON spec into Rust code (using another Node.js program), the Rust type checker ensures I have a well formed HTTP client - the strict compiler makes it a good target for generated programs. Read more about this idea at (https://willcrichton.net/notes/rust-the-new-llvm/).

This is a CLI written in Rust to download your Stripe account to a local SQLite database.

It is intended to enable using SQL queries over your data.

There is also a template for fly.io and Datasette to give you a Sigma like web UI:

https://github.com/tabledog/datasette-stripe