fbcosta

[inland ermine]

Hi! Let me help you with this.

[sour steeple]

hi vanya, thanks!

btw you can ignore the PIN part of the question since all cards details are collected online

[inland ermine]

Yes, Setup Intent is designed to ensure the card can be charged later. However, there is never 100% guarantee the bank will not decide to request authorization again.
You can use off_session parameter when charging a set up card on the backend: https://stripe.com/docs/payments/save-and-reuse?platform=web#charge-saved-payment-method

[sour steeple]

ok thanks. Is there a limit to the number of times the card can be charged before authorization is required once again? or a maximum time period?

[still brook]

👋 taking over for my colleague. Let me catch up.

[still brook]

unfortunately this is upon the issuing bank discretion and we don't really have control over it

[sour steeple]

sure, but do you have any guidance based on experience?

[still brook]

it really differs per issuing bank and per card type

you shouldn't really rely on time frames but instead just reactively ask for authorization when the PI is in requires_action status

[sour steeple]

Ah so does the bank pre-emptively notify Stripe when additional authorization would be required for future charging of the card? or does this status only update when an unsuccessful attempt to charge the card is made?

[still brook]

does this status only update when an unsuccessful attempt to charge the card is made
in this case the PI will fail and the status will change to requires_action which should trigger the flow of getting your customer back to your portal to authorize the payment

regardless of when this should happen in time (maybe twice a day in a row and then none for a year or once a week or whatever)

you shouldn't depend on any timeframe

[sour steeple]

yes I get that, but is there a way to detect that the payment will require auth before actually attempting to charge the card?

[still brook]

no not really

[sour steeple]

Ok thanks for your help

could you direct me to the documentation for the requires_actions status?

is there a way to differentiate between a PI failure due to a lack of funds vs auth required?

[still brook]

https://stripe.com/docs/js/payment_intents/handle_next_action

[sour steeple]

that link leads to a 'Page not found"

[still brook]

are you signed in to your account?

[sour steeple]

and last question: can the same payment intent be used for several charges?

[sour steeple]

yes

[sour steeple]

e.g. we capture the card details once and then it is used for several bids on different items

[still brook]

do you mean capture small chunks of the initial amount?

[sour steeple]

no I mean several distinct charges that are linked to the same card

[still brook]

Oh no you'd have to create new Payment Intents each time but you can save the card details I'll send you the docs for that

https://stripe.com/docs/payments/save-during-payment

https://stripe.com/docs/payments/save-during-payment?platform=web#save-payment-details-for-future-use

[sour steeple]

yes but we wouldn't need to ask for the card details again right? a new PI would be created automatically on the backend when a new bid is placed?

[still brook]

automatically? I'm not sure I understand what you mean about this

If you're creating the PI then sure

[sour steeple]

desired flow would be:

• we collect user's card details when they place their first bid
• they place other bids on other items WITHOUT needing to add any more card details
• when the bids are accepted, we charge the same card

[still brook]

this is the flow I shared earlier

[sour steeple]

ok cool

[still brook]

in a couple of words:
1- you create a PI with setup_future_usage: 'off_session'
2- you collect the payment details
3- in the next PI you use off_session: true to indicate that you're doing this obo your customer