#Lucas974
1 messages · Page 1 of 1 (latest)
Hello! Have you taken a look at any of our docs yet? I'd recommend starting here: https://stripe.com/docs/webhooks/quickstart?lang=node
That's right - the stripe cli + stripe listen command is more of a tool to use while testing.
ok
is there a way to use a shell script to record this email address in a mongodb database?
instead of using node ... or smething else
like a shell script using curl... or the stripe cli itself perhaps ?
Personally I wouldn't recommend doing that - I don't think you'd be able to do signature verification with a shell script
I was looking for a KISS stack but yes you re certainly right
Can I ask you for an advice?
Feel free to ask!
I wish to create a simple saas, with the following features:
- passwordless
- oneshot payment
- provide invoice for client
Knowing a bit of javascript. What do you advice me to create the backend keeping things "simple as possible" ? I'm not talking you about the design or the frontend part, just the logic part.
Really the first question is how do you want to be collecting payment
using Stripe
I'd suggest starting by reading through our docs on how to collect payment (here https://stripe.com/docs/payments/accept-a-payment) - there's a few different options you can look into (CHeckout, Payment Element, Payment Link)
and depending on what you choose there, that'll influence the rest of your logic (as an example, with Checkout you don't need to be creating Subscriptions/Invoices directly)
I just need this:
- oneshot payment
- provide invoice for client
Clients, will connect to the website after payment using a magic link to download the digital product.
And auth: passwordless
Knowing these things... no way to advice me about the backend and the stripe feature or option I need?
That's why I linked you to the accept a payment docs - that's what I'd recommed as the starting part for one-short payment and providing an invoice
There's multiple ways of doing this, so it's best for you to read through your options and pick which one will work best for you and your integration
For auth I don't have any specific recommendations