#inexorable-auths-duration

1 messages · Page 1 of 1 (latest)

tough eagle
#

hello, the 7 days is a network limit really. You could keep re-doing the auth every time it expires, every 7 days.

other than that, you can talk to Support again and ask if they have any special features available for you where you could potentially be allowed for larger authorization windows.

foggy iron
#

Am I right in assuming you mean by storing the card details (payment_intent_data.capture_method = manual) ... and then scheduling an automatic attempt (outside of Stripe) to re-auth for the same amount again via the original PaymentIntent (without the cardholder interaction)?

#

hehe.... sounds iffy... bad actors can just hire the equipment... wait 7 days... cancel the card and run 🙂

#

This feels like it's not achievable with Stripe. I'll go back to the drawing board and have a re-think.

#

Thank you for your time and help.

tough eagle
#

Am I right in assuming you mean by storing the card details (payment_intent_data.capture_method = manual) ... and then scheduling an automatic attempt (outside of Stripe) to re-auth for the same amount again via the original PaymentIntent (without the cardholder interaction)?
no

#

I meant

day 1 you use customer's card to create a $X authorization and save their card as pm_123

day 7 (when auth expires) but you still need the auth, you let the prev one expire and make a new one for $X

and all of these auths happen on Stripe, not outside of Stripe

#

to re-auth for the same amount again via the original PaymentIntent (without the cardholder interaction)?

it would be a new PaymentIntent, not the original, as that would end up being canceled due to auth expiry

but yes to "re-auth for the same amount again" and yes to "without the cardholder interaction"

#

I didn't say this is not achievable within Stripe, it is, just that card networks have particular restrictions

I also mentioned:

you can talk to Support again and ask if they have any special features available for you where you could potentially be allowed for larger authorization windows.

foggy iron
#

Thanks for the detailed explanation. I hope I didn't imply you said it wasn't possible - I meant the fact that the card requires re-auth in 7 days is a BIG floor in the hire / security deposit model. If the re-auth fails but the customer already has the goods, the purpose of a security deposit has failed. I also understand that's not necessarily a Stripe restriction.... but Stack Overflow articles are hinting at possible arrangement being able to be made via support as you've said.

#

My "rethink" was more about the big hole in the model - not a Stripe shortfall. I'm just struggling to find a better way. I'll follow your lead with support and see where it goes 👍

#

Thanks again for your time - much appreciated.

#

To clarify a point - when I said about scheduling a re-auth outside of Stripe - I meant scheduling an automated task outside of Stripe that would automaticlly post to the Stripe API to permorm the re-up. I assumed there was still no scheduling mechanism that would allow this in Stripe?

tough eagle
#

ah gotcha, thanks for clarifying, yes we're on the same page