#newt-setupintent-3ds
1 messages ยท Page 1 of 1 (latest)
Yes
that's why we usually discourage doing SetupIntent right before a PaymentIntent
We are using Stripe Connect and we want to apply special discounts based on CC brand. So, we are using a setupintent for capturing the CC and a Payment intent with an special application fee based on CC brand for capturing the payment.
So, in our case, is there a way around using a SetupIntent right before a Payment Intent?
I don't get what you said, but let me reframe it
You can't use PaymentIntent, because you want to change the underlying amount after you know the card brand/whatever and before the real 3DS/confirmation
We can't use PaymentIntent, because we want to change the underlying application fee based on CC information.
So, we need the CC information before we can create / process the Payment Intent.
No worries
like is my summary your exact problem?
the same, but without the 3DS part
Does it require Payment Element?
I don't think so, though PaymentElement is drastically better so you should absolutely support it :p
We would love to
Like really it doesn't make sense if you don't use PaymentElement
but we had a problem with it
If you don't use PaymentElement all you have to do is first create the PaymentMethod
so there's no reason to do what you do in that world
Sorry, always so hard to do everything in parallel with little info
1/ If you use PaymentElement, you have absolutely no control over the payment method used for confirmation because Stripe collects it and confirms at the same time. That's where the beta I shared is useful
2/ If you do not use PaymentElement and use CardElement, beyond the fact that you shouldn't and PaymentElement is drastically better (but I'm biased), then you absolutely never need your SetupIntent -> PaymentIntent hack
All you have to do is
1/ Show card element client-side
2/ Create a card PaymentMethod: https://stripe.com/docs/js/payment_methods/create_payment_method
3/ Submit to your server, decide what to do based on that card and create/confirm a PaymentIntent with the right amount
And create payment method won't trigger 3DS?
no
Checking something on my side
What's the difference between confirm Card Setup and Create Payment Method?
Why do you need a setup intent if you can create the payment method directly? What will happen with CCs that require 3DS authentication when creating the payment method directly? Is that payment method still usable for capturing a payment intent?
And btw, I agree that payment element is awesome but we had an issue with it because it was forcing a full page refresh and we needed to use it within an iframe. The full page refresh caused issues with external processes that we had no control of.
I was looking into this now and seems like it was a problem with a full page redirect for us bank account payments. We were told there was no way of avoiding this. That's why we had to drop it
SetupIntents are used to save cards for later and do 3DS and all of that
here you're just using it wrong/misunderstood really
Probably. But we do want to be able to use them later on
but you can do this on PI ๐
1/ Create a PM
2/ Server-side check what you need
3/ Create a PI and confirm with that PM id and pass customer and setup_future_usage and that will automatically attach the PM for future payments
I would be more than glad to use it
If done like that, will we prevent double 3DS auths?