#schavan

1 messages · Page 1 of 1 (latest)

sly harnessBOT
brittle thunder
edgy prism
#

Request Log: req_BBgBjfWXVKwTRP

brittle thunder
#

You're setting setup_future_usage to on_session here
Is that intended? Is your customer around to complete the payment?

edgy prism
#

But same transaction we did on 23rd Jan 2023 that time it was working without passing CustomerId and using same input parameter for PaymentIntent creation. this is log for successfull transaction on 23rd Jan: https://dashboard.stripe.com/test/logs/req_KOD1sURJDtuBsa

Our question is, it was working on 23rd Jan 2023 and what happened now, why its not working for same inputs. Also other 3ds Cards are working fine with same inputs.

brittle thunder
#

No, I was just asking if you passing the parameter in was intended and not a misunderstanding.
I don't think that's what's affecting this.

edgy prism
#

Yes we are adding this for future use.

brittle thunder
#

Gotcha, okay!

edgy prism
#

But in both transaction same card was in use i.e 4000000000003063

brittle thunder
#

The fingerprints are different on both the payment method so I'm 99.9% sure these aren't same cards. Maybe there was a typo in the middle

#

if these are the same cards then the fingerprints should be the same

edgy prism
brittle thunder
#

The dashboard only shows last 4. Its possible that something was missed in the other 12 numbers.
Can you try creating a new payment method and use that payment method in a PaymentIntent to see if that helps?

edgy prism
#

ok will try

#

Sorry missed to inform this we are already using this flow: first creating paymentMethod with 4000000000003063 card and using that PaymentMethodId in Paymentintent as input, but it is failing.

brittle thunder
#

Ah okay!

edgy prism
brittle thunder
#

Oh, good point..

brittle thunder
#

Sorry for the delay here

#

Server is running quite busy today

#

Quick question, why exactly are you creating a PaymentMethod by calling the API directly and setting up a PaymentMethod for future use later on?

An easier approach here would be to use a SetupIntent, no?