karen_code | Stripe Developers | Page 1

split mistBOT Oct 18, 2024, 10:01 AM

#

👋 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/1296775266718453782

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

faint obsidian Oct 18, 2024, 10:05 AM

#

The PaymentIntent can't be confirmed unless you say do so.

#

Could you please share more details about how currentyl the PaymentMethod is automatically confirmed ?

ruby basin Oct 18, 2024, 10:07 AM

#

Thank you, when the payment intent is created the buyer can pay for it, I would like to "block" the payment intent so even though is created they buyer can not pay yet.

faint obsidian Oct 18, 2024, 10:10 AM

#

How the buyer is paying it ?

#

Can you share more details ?

ruby basin Oct 18, 2024, 10:14 AM

#

We have a redirect page for payment created with Stripe elements and the payment is confirmed using publishable keys.

#

If a Payment Intent Id exists, and the frontend has the publishable key, nothing is preventing the payment.

#

I would like to set a flag or something on the payment intent itself like "requires_action", that we can set true/false to block or unblock the confirmation.

#

Does something like this exist?

faint obsidian Oct 18, 2024, 10:24 AM

#

You need to implement the block in your frontend

#

or example before clicking the submit button you make a call to your backend and verify if it can be proceeded

#

Or you can refactor your integration to a two step confirmation flow:
https://docs.stripe.com/payments/build-a-two-step-confirmation

#

You first collect the PaymentMethod

#

and then confirm the Payment on the Server

#

So before you confirm the payment on the server you make you check and block the payment if needed

ruby basin Oct 18, 2024, 10:37 AM

#

https://docs.stripe.com/api/payment_intents/create#create_payment_intent-confirmation_method Can I update the confirmation method from manual to automatic to achieve a similar effect?

faint obsidian Oct 18, 2024, 10:38 AM

#

Yes with the two step confirmation flow you can use the automatic confirmation_method

ruby basin Oct 18, 2024, 10:39 AM

#

Ummm, I don't see this field available in the update call: https://docs.stripe.com/api/payment_intents/update

faint obsidian Oct 18, 2024, 10:42 AM

#

You simply need to omit/remove that parameter when creating the PaymentIntent

split mistBOT Oct 18, 2024, 10:54 AM

#

ruby basin Oct 18, 2024, 10:58 AM

#

Let say that implementing the two-steps flow is not feasible for the product, can a PaymentIntent be created in "draft" mode or this is completely not possible?

queen condor Oct 18, 2024, 11:00 AM

#

There's no 'draft' status for an intent. The requires_payment_method status, which is what will be returned on creation, is as close to as 'draft' as you'll get

#karen_code