#Faisal Rana (hehim)

1 messages · Page 1 of 1 (latest)

woven swiftBOT
austere halo
#

hi two shoes.. thanks for joining me.

#

please message me back when you get a chance, I know you must be busy yourself.

verbal talon
#

Taking a look now

#

The transition to requires_capture will only happen once a valid Payment Method has been attached to a Customer Payment Intent or a Customer and confirmed.

austere halo
#

oh okay, so I have to use a setupIntent flow? My goal was to not store any client credit card information... what I would like to do is do an authorization hold, and then capture.

#

i did follow the quickstart guide..

#

i have pretty much the exact same code

#

any chance we could do a voice call/screenshare so its easier for you to see?

verbal talon
#

so I have to use a setupIntent flow? My goal was to not store any client credit card information... what I would like to do is do an authorization hold, and then capture.
Setup Intents are required for auth and capture. You wouldn't be storing this information on your end. The card details would be submitted directly from the client to Stripe and you would get back a Payment Method (with an ID to use for making charges)

verbal talon
verbal talon
#

Additionally, if you must follow the docs you linked, you'll want to make sure you heed this:

Before continuing to capture, attach a payment method with card details to the PaymentIntent, and authorize the card by confirming the PaymentIntent. You can do this by setting the payment_method and confirm fields on the PaymentIntent.
which means you'll need to create a payment method, attach the newly created Payment Method to the Payment Intent, and then auth the card using the Payment Intent