#ang3lkar_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ 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.
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.
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",
],
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
no, in the second PaymentIntent you shared (pi_3RsLaVJrE1Xw3Ytg1HlRyipb), the user paid with a card
if I press "pay" here, i am paying with "link", correct?
even like this, I still get "card" as a payment method, example: https://dashboard.stripe.com/test/workbench/logs/req_eWTQKEzCEZE1cj
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.
if it's just for testing, you could set payment_method_types: ["card", "link"] when creating the Checkout Session.
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
this was the checkout session in our production account: https://dashboard.stripe.com/payments/pi_3RsLDhJrE1Xw3Ytg07joimmG
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
it seems to have similar payload
looks at the API response from Stripe, and the payment_method_types, to see if Link was available as a payment method or not.
indeed
this could change based on your Dashboard settings
we have received
"payment_method_types": [
"card",
"link",
],
if you don't want Link, you could disable it in your Stripe Dashboard
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
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?
sure
this is the production case: https://dashboard.stripe.com/payments/pi_3RsLDhJrE1Xw3Ytg07joimmG
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
this is a test case: https://dashboard.stripe.com/test/payments/pi_3RsMmMJrE1Xw3Ytg193bRi38
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
thanks, having a look
๐ 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
basically if you visit https://dashboard.stripe.com/acct_1PnfZvJrE1Xw3Ytg/settings/payment_methods/pmc_1Pt4woJrE1Xw3YtgtY6fOirK you can see that in livemode Link is off (in passthrough mode) whereas in testmode https://dashboard-admin.stripe.com/acct_1PnfZvJrE1Xw3Ytg/test/settings/payment_methods/pmc_1Pt4viJrE1Xw3YtggiEP0ptL it's enabled
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
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
how can we do that? because clicking "Pay" in this screenshot gets the first case (link+card) #1401891580205334529 message
would you mind sharing the PaymentIntent IDs of the 2 link payments in this screenshot
https://dashboard.stripe.com/payments/pi_3RsLaVJrE1Xw3Ytg1HlRyipb (link+card)
https://dashboard.stripe.com/payments/pi_3RsLDhJrE1Xw3Ytg07joimmG (link)
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
and you want to be able to reproduce only link in test mode?
exactly
can you try to use payment method types and specifically pass link https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_method_types ?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
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.
Hi, from looking at this request, https://dashboard.stripe.com/test/logs/req_c74zR9a1rmt9Ii to create the Checkout Session you passed setup_future_usage: "on_session"
However, link does not support future on session payments.