#padek

1 messages · Page 1 of 1 (latest)

rugged cliffBOT
dawn pecan
#

when a client register a card it creates a payment method on stripe
How are you creating a PaymentMethod? Are you using SetupIntents?

wooden sun
#

yes i use first stripe.PaymentMethod.create and then stripe.SetupIntent.create

dawn pecan
wooden sun
#

so the flow that i tried setting up is the following: client register a card (can be more than one) , makes an order and then select what card he wants to pay with and then we hold that amount for 3 days with a PaymentIntent with manual settings then on the third day we charge that same paymentIntent

#

and when we charging that payemtnIntent is when i have encounter that error warning

dawn pecan
#

Can you share the PaymentIntent ID?

wooden sun
#

give me one sec

wooden sun
dawn pecan
#

could you copy one of those IDs here, in text form?

wooden sun
#

ofc

#

pi_3NL9F7AbKEfBp830OGHSD6bQ
pi_3NL9DbAKEfBp83O0QDPSqLO

dawn pecan
#

Ahh, looks like they're both slightly off:
pi_3NL9F7AbKEfBp83O0GHSD6bQ
pi_3NL9DbAbKEfBp83O0QDPSqLO

for next time, you can also grab these from the URL after clicking into each payment

wooden sun
#

oh i apologize for that

dawn pecan
#

no problem!

#

Since you're essentially asking your customers to share their payment details now but plan to charge them later/at a later date, you should reorder your flow a bit: create the SetupIntent first, use the SetupIntent's client secret + Elements to collect the customer's payment details client side, then confirm the SetupIntent client side. This will create the PaymentMethod automatically and trigger any additional authentication if the customer's bank requires it

wooden sun
#

okay so when i first receive the clients card information y should create a setupintent

dawn pecan
#

yes, that's correct

wooden sun
#

okay let me give that a good read and think about it so i can understand but basically the only part im a little confused is if i create a setupIntent does that alone create a paymentMethod

dawn pecan