User1-incomplete-pi

[lucid fog]

Hey there!

Generally they're safe ignore. The reason they're marked 'incomplete' is that you can attempt to confirm/pay them at a later tine. They don't 'expire'

If it's an issue, you could cancel them manually after a certain period: https://stripe.com/docs/api/payment_intents/cancel

[silver steppe]

but cancel its not really required right?

[lucid fog]

It's not required, nope!

But they don't expire naturally, so if they become an issue some merchants prefer to cancel them after a certain period

[silver steppe]

and one more doubt. i am using tokenization process also.
i am using setup_future-usage and off-session for to save the card.
then i will use list_payment-method to list the cards.then i will use the payment_id with confirm=true to complete the payment.

but when some type of cards always required to authentication then how we will use saved card.it results error when try to do payment_intent apis.
so how we will manage this? any advice?

[hearty ridge]

if that happens you have to contact the customer to come back and authenticate again

https://stripe.com/docs/payments/save-during-payment-cards-only?platform=web#web-create-payment-intent-off-session talks about the process there

[silver steppe]

for example this type of cards always required authentication. so i think saved card process is not possible for this kind of cards right? or any solution there?

because first time they complete authentication then we will list the cards.but now we using payment_method(which is already authenticated) but this type of cards again required authentication.

i saw this in the test flow. but i dont think its often happening in livemode

[hearty ridge]

what type of card is it exactly? do you have an example?

an example of a failed PaymentIntent pi_xxx that required authentication would help

[silver steppe]

4000002760003184

pi_3Kt9uiLtXp80ejoe0dTitPOF

[hearty ridge]

looking

but yeah, as you say, that's a card that requires authentication on every payment.

most cards in reality don't work that way, try using the 3155 card instead(https://stripe.com/docs/testing#authentication-and-setup), with that one only the initial payment requires authentication and subsequent ones can succeed without needing authentication again as they get exemptions

either way you need to be able to handle both outcomes

[silver steppe]

if i need to handle this how it would be?because if we already have payment_method i will make a payment_intent request with required params. in this case the status will show requires_action but how we can setup authentication.

if we use stripe js payment elements confirm_payment_methodwill automatcally redirect to authentication page. but we did not enter the card details again since we already have payment_method

[formal mulch]

Hi taking over for karllekko as they have to step out

If you just want to have the customer authenticate again without entering payment details (because you already have a PaymentMethod), you can do this

stripe.confirmCardPayment(intent.client_secret, {
  payment_method: intent.last_payment_error.payment_method.id
}).then(function(result) {
  if (result.error) {
    // Show error to your customer
    console.log(result.error.message);
  } else {
    if (result.paymentIntent.status === 'succeeded') {
      // The payment is complete!
    }
  }
});```