#arditron
dull mapleBOT
analog elk
Hello
When you say "checkout session" you mean Stripe Checkout, correct?
Not your own custom flow
hybrid mango
Yes, created using SessionCreateParams.
analog elk
Gotcha
The only way this is possible is using custom Radar Rules in that case
Otherwise, you could use something like geolocation before redirecting to Checkout
But that won't be perfect
hybrid mango
Yeah, ok. Just to clarify, If I create a checkout session using SDK with mode for "subscription", with a recurring "Price", I can create a recurring subscription, right?
analog elk
Yep
hybrid mango
But then wouldn't there be a fee (based on the card) and then 0.5% of the subscription cost on top of it?
I was wondering if I should collect the payment method using "setup" mode and manage subscription fee collection by using my own logic or use Stripe's subscription mode.
If it is a domestic card, then 1.75% + $0.30 + 0.5% of the amount or just 1.75% + $0.30 only? [In case of a subscription]
analog elk
Yes there is a fee for using Stripe Billing. I believe it is 1.75% + $0.30 + 0.5% of the amount but honestly I know next to nothing about our Pricing/fees as we only focus on the API here. If you have questions about Pricing you are going to want to reach out to our Support team via https://support.stripe.com/contact/login to discuss with them.
hybrid mango
No, that's all good. I was just confirming that the 0.5% of the amount is on top of the card fee. That's all good.
analog elk
If you are going to run your own recurring payments, you still might as well use payment mode to take the first payment
You can save the card when doing that
And then have your own recurring logic for renewals
hybrid mango
Yes, but if a customer is using 3DS card, they would need bank verification to complete the process. So while we setup the checkout session using SDK, with "setup" mode, is it possible to mention not to allow 3DS cards?
analog elk
Both payment and setup will optimize the card for off-session re-use in the future.
(With payment mode you need to pass payment_intent_data.setup_future_usage: off_session)
So if 3DS is required it will be completed at time of Checkout. Then for future recurring payments we will apply for an exemption for 3DS as the card was already set up. However it is always possible that an issuer requires 3DS anyway and you need to bring your custome back on-session in that case.
hybrid mango
OK. Would it be possible to know whether the issuer requires 3DS all the time after the first payment from the PaymentMethods?
analog elk
No that's impossible to know and not really a thing. Most issuers have their own fraud models that dictate when they force 3DS or not.
I'm not aware of any that really force it on every transaction (though it is possible)
It would really hurt their conversion on recurring payments so I doubt any do that
hybrid mango
Understood. So my best bet here is to use the "Payment" mode, collect the first payment, and then use the payment method to run my own schedules if I don't want to pay 0.5% or use Stripe's billing and pay 0.5%.
analog elk
Yeah pretty much
You also won't get access to Invoices if you use your own logic
Don't know if you care about that
hybrid mango
yeah right, I know that. thanks. Just one more doubt - when we create checkout session with "Payment" mode, would the PaymentMethod created be a "default" payment method of the customer?
analog elk
There is no such thing really unless you are using Subscriptions/Invoices.
When you create/confirm a PaymentIntent directly you always pass the payment_method paramter with the PaymentMethod ID
So you would basically track this "default" on your end if you want a Customer to have a default