#uzelac
1 messages · Page 1 of 1 (latest)
That's not really what a Setup Intent is for. Instead you want to look at auth and capture: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
Ok testing to see if this works for my usecase. Will update you. What I'm trying to replicate is a Cameo style payment system. Where a user can pay another user for a response. And if the response if given they will be charged, if they dont then the payment will be canceled and never captured. Does this paradigm work for the link above?
Yep, exactly!
A Setup Intent is used to collect and save payment details, there's no actual payment involved. 2 different concepts
Understood. Also is there a way to automatically cancel a payment intent? Say after 7 days
Well authorisations/hold can generally only exist for ~7 days before they're automatically released anyway and then the Payment Intent is cancelled automatically yes
And do I need to pay any refund or cancellation fees when this occurs?
Nope, this is all detailed at the link above
Hmm, I seem to get this when trying to capture. Do I need to update that payment intent I'm trying to capture with a payment method?
Yes, you will need to collect payment details before you can capture the payment
Just to be clear, we need to create a payment intent then create a payment method to attach to the payment intent then capture the original payment intent
Is there a way to skip creating a payment method and do that directly when the payment intent is created?
Yes. I'd recommend starting here for a complete payment flow: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
Then you can adapt for auth and capture once that is established