#gecko - stripe hosted payment page
1 messages · Page 1 of 1 (latest)
Hello, our Checkout docs would be the best place to start for our low code solutions https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout
so I've been reading them
i see the demos, etc. looks like what I'm hunting for
before I go down the rabbit hole, I wanted to first check with the community and see if I'm looking at the correct way
I have a 3-tier payment for a single product, and some will likely want recurring (subscription) and others 1-time payment...but it's 1 product with good-better-best set of prices.
I don't really want to setup my own web pages to host all of it, so my thinking was something like this:
i notify the customer they need to make a payment, and give them a URL (to stripe)...they go there, make a payment, and I get a return message (event, webhook, notification, etc) which tells me some details about the transaction, so I can record just the minimum info in my database. (which discord user or server or whatever, but not the payment details)
so i was thinking about the stripe demo code on the subscription as my basis, and want to ensure I understand the comms mechanism between stripe and me, and if/what I should leverage on the sample code vs. customize. I don't think I need much.
Gotcha, that sounds like a plan. So the main question right now is how to receive that notification after the payment?
Happy to help with any part of that, just want to make sure I know what info you are looking for
so I assume that if I use that standard sample, I can login to my Stripe account, and setup some customized look and feel (payment methods, Icon for my business, etc).
Then i think I need to understand 2 things. First, I will have a URL that points to my storefront on Stripe.com, I'll need to understand the format I use to give my customers. (for example they will have an ID I want to pass through this URL and receive back, which identifies them)...
Second, there will be the notification. The docs talk about delayed payment timing, so use webhooks....wouldn't just listening for confirmed payments be ok?
(like I don't get why have an event listener, and a webhook....why not just listen for events, no matter when the payment finalizes?)
For tracking which customer you are dealing with in the first part, you will want to look at this doc if you have not already. https://stripe.com/docs/payments/checkout/custom-success-page#modify-success-url