#ang3lkar_unexpected

1 messages ยท Page 1 of 1 (latest)

strong fjordBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1401891580205334529

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

paper oriole
#

hi there!

#

I'm not sure I understand the question. this PaymentIntent was paid with a Link payment method, so it's expected that you don't see a card here.

pastel summit
#

in the second example, user also paid with link

#

but in the response, when capturing the payment, the value is different:

#
"payment_method_types": [
"card",
],
paper oriole
#

no, in the second PaymentIntent you shared (pi_3RsLaVJrE1Xw3Ytg1HlRyipb), the user paid with a card

pastel summit
#

if I press "pay" here, i am paying with "link", correct?

paper oriole
#

well, it depends. when you created that Checkout Session, you can see in the response payment_method_types: ["card" ]: https://dashboard.stripe.com/test/logs/req_c74zR9a1rmt9Ii
so users can only by card, but they could use Link to pre-fill their card. in the end you still get a card payment method.

pastel summit
#

how can I get a "Link" method then

#

I can't reproduce this scenario

paper oriole
#

if it's just for testing, you could set payment_method_types: ["card", "link"] when creating the Checkout Session.

pastel summit
#

however, this happened on our production account, not testing, and the payload we send when creating a checkout session did not change.

#

and we cannot reproduce this case in our test account

#

it seems to have similar payload

paper oriole
#

looks at the API response from Stripe, and the payment_method_types, to see if Link was available as a payment method or not.

pastel summit
#

indeed

paper oriole
#

this could change based on your Dashboard settings

pastel summit
#

we have received

"payment_method_types": [
  "card",  
  "link",
],
paper oriole
#

if you don't want Link, you could disable it in your Stripe Dashboard

pastel summit
#

the question remains, considering we have the same configuration between production and test, why in the production account we received "link", but not in test

#

they seem to behave differently

#

note: we have disabled "link" some minutes ago on production until we figure out why this happens

paper oriole
#

why in the production account we received "link", but not in test

#

you shared multiple IDs so far. can you share the 2 IDs you want me to look at?

pastel summit
#

sure

paper oriole
#

thanks, having a look

strong fjordBOT
storm cargo
#

๐Ÿ‘‹ taking over for my colleague. Let me catch up.

#

will be with you shortly

#

so basically you're using Link in PaymentMethod mode in Livemode and in Passthrough mode in Testmode

#
pastel summit
#

As I said, we just disabled that until we manage to reproduce the case and fix

#

the configurations were the same

#

and the question isn't if link is available or not. What we're trying to reproduce is having a payment with ONLY Link as a payment method

#

we want to reproduce the second case in screenshot

storm cargo
# pastel summit

would you mind sharing the PaymentIntent IDs of the 2 link payments in this screenshot

pastel summit
#
storm cargo
#

and you want to be able to reproduce only link in test mode?

pastel summit
#

exactly

storm cargo
pastel summit
#

i will, but primarily I would like to know why this happened in the first place.

#

in order to fix this case in our systems

#

and thanks for the assistance so far, Iโ€™m eager to see if we can get this completely resolved.

strong fjordBOT
jolly sapphire
pastel summit
#

yes, this seems to be the case

#

I have managed to reproduce by removing the setup_future_usage attribute

#

thanks for the support!