#smokey_best-practices
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1336000564689113160
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
I'm also wondering what are the benefits on using webhooks via stripe hosted form vs controlling everything myself in the app
Hi there 👋 what problems are you running into so far?
Our guides for building Subscription integrations starts here:
https://docs.stripe.com/subscriptions
Do you have a sense of how you want to save payment methods from the customers yet for the pay-as-you-go option? We recently changed our guides for those so they no longer group several integration paths to accomplish this in the same doc. I'd like to link you to the right one.
Our guide for putting a hold on a payment (separating the confirmation from the capture), can be found here:
https://docs.stripe.com/payments/place-a-hold-on-a-payment-method
Webhook endpoints serve a different purpose than using a Stripe-hosted checkout experience, so those two options aren't really comparable as they're addressing different needs. I'm also not sure what you mean by "controlling everything myself in the app" in that context.
Well I was building this in the past (around 12 months ago) and was speaking to someone from this Discord, and they let me know my flow was wrong.. I'm not sure if you can see my chat history...
I think previously; I did something like this:
User signs up and enters their domain, and whether they want to PAYG or Subscribe.
If PAYG, I created a new customer and attached their card. I think I ended up charging them like £0.99 and refunding - this was to validate their card.
If subscribe, I created a new subscription and charged them.
I can't remember what issue I ran into exactly, but before I give it another go, I just wanted to know if I'm thinking about this wrong
By "controlling everything myself in the app", I mean not using Stripe hosted forms, and instead using something like PaymentElement
If PAYG, I created a new customer and attached their card. I think I ended up charging them like £0.99 and refunding - this was to validate their card.
I'd recommend not doing this, the card networks aren't fans of that.
You should use Setup Intents for setting up cards for future usage, and you don't need to charge them.
OK, understood. I won't do that again
Okay, so Payment Element vs Checkout Session is a reaonsable comparison to make. The former is better for embedding into your site, the latter is better if you're fine with directing your customers to us and allowing us to control the checkout UI.
Webhooks are for receiving Events after a payment (usually). They're best suited for triggering downstream processes, like order fulfillment.
OK got it. I'll give everything a think over before implementing it. Thanks for your help Toby.