#daniele-de-benedetto_api
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/1326465741687488533
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
That PM is created without a customer, so it's an one-time used object. You seem to used an old JS method to collect it via https://dashboard.stripe.com/test/logs/req_Gb7NIodoqqYDqS
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
i'm using the embedded form creating a checkout session marked with offsession and the customer in the checkout session is specified
i have a radar rule that prevent the payment if the card is prepaid but i want to collect the payment method because i have a recurring behaviour and can be helpful to have the card collected
Hmm can you share the Doc you are following, and the embedded Checkout Session Id?
cs_test_a1BzyrFPysTWx5Hu7X8PXCmTIv7hL12GPXdwxPNk85UG0sOFScBwTzcvew
and then once blocked i was using the attach api https://docs.stripe.com/api/payment_methods/attach?lang=cli
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Okie, when you create the Checkout Session, can you specify this parameter? https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
It should automatically attach the PM after the session is paid
is already setted, the problem here is that i don't want to let the user pay, but i want to collect the 'blocked' payment method for future usage
Hmm when the payment was unsucessful, the PM became orphaned and can't be attached again
but the user have completed the 3ds and the checkout session is for the customer, there is no way ? so you are saying that to attach the pm the payment must succed right ?
there is no way to attach a payment method on a blocked payment ?
Yes I think so. Could you try SetupIntent instead? (change the Checkout Session mode from payment to setup). Would you have an attached Payment Method by the time the SetupIntent is confirmed?
uhm it's trange because i have the custome ron a checkout flow, so you are suggesting to first setup an intent and then create a checkout session?
Yeah can you try it? I think radar won't interfer with the SetupIntent so you will have an attached Payment Method
interfet, i need to made a customer rule to avoid the setup intent
it work but is aweful for the user....
he need to perform two flow, first setup and then pay, it look strange...
You can show them the Setup, and then (seamlessly) let them Pay by calling Create Payment Intent with confirm = true
They still see 1 flow
ok but i need to build a custom checkout with payment elements i cannot use the embedded form
there is no way to maintain the checkout session in payment mode and attach the method to the customer, you are collecting the payment method and i have the session associated to the customer.. it's strange that i cannot combine the two thing
Hi! I'm taking over from my colleague. Please, give me a moment to catch up.
You can use payment_intent_data.setup_future_usage to be able to use the PaymentMethod used during session for future payments: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage
i was using, but it apply only to succeded payment
here i have a block by radar
but i want to save every payment method also the blocked ones
i have already explain it to your collegue
Why would you want to save the blocked ones?
because i have a model in which i bill my customer later in the fure like a recurring plan, so for the first payment i want to acquire debit and credit to be more sure to acquire founds on next billings, but if i'm able to acquire also the prepaid and virtual in the meantime i have more option to bill them in case of future dunning
no metter why, the docs says that with the off session parameter i can reuse the payment method, but if i have radar it's not true
but if i have radar it's not true
Could you please elaborate on this part?
i have a checkout session with setup future usage off session, the user insert a prepaid card, radar block it, the charge failed, but the payment method exists on stripe, the customer is specified in the checkout flow but i cannot attach the payment method to the customer
if i remove radar and for example i perform a capture_method: 'manual' the payment method was attached and then i can refound but doing this bring me to totally remove radar, because is useless, block the unwanted cards but don't let me acquire the information, is a losso of data nd functionality
This sounds like a bad user experience. A customer gets their card authorization blocked and then sees the same card saved on their account? This sounds like something they wouldn't expect.
I would suggest separating these 2 flows. In the payment flow you only allow selected cards with Radar. And then, on the side, you allow them to save any card with a Checkout Session in mode=setup.
yes ok, but two flow for making a simply attach is strange
but if it is the only way ok
You can still attach the cards used for payment, but only the successful ones, i.e. not blocked by Radar.
ok thank you