ali_paymentintent-twint

[wanton mirage]

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

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

[lean plaza]

For the first issue, that looks to be an inherent restriction on twint. It is a single use payment method, so we don't support saving it to customers for re-use https://docs.stripe.com/payments/twint

[worn heart]

okay understood

[lean plaza]

A requires_confirmation status means that the next step is confirming the intent. You have three options here:

1. Pass confirm: true when creating your payment intent, this will confirm the intent while it is being created
2. Confirm the intent client-side with a Stripe.js call to confirmPayment
3. Confirm the intent server-side with the same library that you used to create the intent

[worn heart]

okay after the confirmation od i get the next steps to redirect the customer so he can complete the payment ?

[lean plaza]

If you do the client-side confirmation Stripe should do that automatically. For the other ones you can either use Stripe.js's handleNextAction method or you can redirect to the URL in the intent's next_actions property yourself

[worn heart]

if i pass the confirm: true i get this error You cannot create a charge on a connected account without the card_payments capability enabled. as show in the request req_TxcnzCopXUOujP

[lean plaza]

Gotcha, finding a doc on that. Quick correction on my last message, it is next_action not next_actions https://docs.stripe.com/api/payment_intents/object#payment_intent_object-next_action-redirect_to_url-url

So basically when you create a connected account, you request certain capabilities for them and that generates different information that you need to collect from that user in order to enable them for that capability. https://docs.stripe.com/connect/account-capabilities
If you have already requested card_payments for that account, you should just need to run through connect onboarding
https://docs.stripe.com/connect/hosted-onboarding
Otherwise you will need to update the account and add card_payments to their capabilities and then complete onboarding again to collect the necessary info for that

[worn heart]

nice now it's enabled thank you for the help

one last question is there a way to add a webhook to the payment intent so when the payment is confirmed we get an update automatically ?

[lean plaza]

Yes there is! payment_intent.suceeded is the typical one to listen to for that

[worn heart]

is there a way to tell stripe to send a request to my webhook with the status updated
or i should get a cron running every minute to check if the status has changed for the payment intent ?

[lean plaza]

Yes, that is how our webhook events work. We send events to your endpoint when certain status changes happen on stripe objects. In this case, when they payment succeeds we send a payment_intent.succeeded event to your endpoints that are subscribed to that event.

[waxen canyon]

ali_paymentintent-twint

[worn heart]

where can i put that webhook ?

[waxen canyon]

@worn heart https://docs.stripe.com/webhooks I recommend carefully going through that doc and familiarizing yourself with it