#eric_unexpected
elder forumBOT
đ 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/1239862891968987256
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
timber snow
Here is an example of a request that does display Link as as payment method: req_lSix7nAH9y6qu4
That is using the exact same frontend and backend, the only difference is the Stripe account associated with the two requests
twin laurelBOT
long bluff
What integration option are you following ?
https://docs.stripe.com/payments/link/payment-element-link#integration-options
timber snow
The second which is successful for req_lSix7nAH9y6qu4
elder forumBOT
long bluff
The second which is successful for req_lSix7nAH9y6qu4
What you mean exactly by successful? did you tried to enter the customer email in Stripe Element ?
Do you have a hosted link to your Element integration that we can check ?
torpid ginkgo
@timber snow I'm taking over for my colleague. I will get back to you once you reply to my colleague's questions
timber snow
Apologies I had a meeting. By successful I mean I can see the intent returning Link as a payment option and I am given this option as a customer when trying to pay
Currently we are only enabling Link on our internal test server which won't be accessible to you I'm afraid. I am happy to send across anything you might find relevant though if it helps
torpid ginkgo
I'm looking into it
thanks for the info
would you mind sharing a screen recording?
timber snow
No problem
So here I am creating a payment intent initially against the stripe account that displays Link and then against the one that doesn't. It's worth noting the one that successfully works is for a US based Stripe account and we are charging in dollars. Other than that though there is no difference in the way we are creating the intent or in the UI we use
The first intent created corresponds to this req id: req_7mnhWWunmos2Xd
And the second to this: req_C8tqD4Rmw6Mppt
torpid ginkgo
the problem is in the difference of LINK configuration between the two accounts
timber snow
Okay that's good to know. What is the issue in their configuration? I must have missed something
elder forumBOT
halcyon pecan
Can I reproduce this somewhere?
timber snow
Not currently I'm afraid we want to test Link on our internal test server so this won't be live. I am happy to try and pull out anything meaningful for you. I think I just need a better understanding of the decision rules around displayhing Link and maybe some clarification on @torpid ginkgo's message. I'm curious in how the configuratoin of these accounts (when in Test mode) differ and how that is affecting displaying Link
halcyon pecan
Link is subject to a lot of treatments/experiments that determine if/when it should show, so likelihood is that differs between the two accounts you're testing on
timber snow
So is this out of my hands? I have reached out to the development team about this before and was given a similar answer. If that's the case I'm happy to just leave this for now
halcyon pecan
This is the account that it's not showing on, right? acct_1KIxL1FaN5iJ7I36
halcyon pecan
So is this out of my hands? I have reached out to the development team about thi...
Generally yes, you can request to be exempt from treatments if you prefer via https://support.stripe.com/contact/email?topic=api_integration
Trying to confirm that is the case
timber snow
How can I find the account ID, sorry. Is it visible in the dashboard or in the log calls for creating intents?
halcyon pecan
Yeah I think it's specifically disabled on your GB account
timber snow
Yes account id is: acct_1KIxL1FaN5iJ7I36
And the one it works on: acct_1NBF05Jq68BMMr0v
halcyon pecan
Yep, it's disabled currently
As I said, if you want to opt out of that and have Link on that account you can email us: https://support.stripe.com/contact/email?topic=api_integration
timber snow
That's very helpful thanks. I was unsure why this was the case. I'll reach out around this then
halcyon pecan
No problem, glad I could help!
timber snow
Whilst i have you and no problem if you'd rather I raise this as a separate ticket I am seeing some strange behaviour with account id: acct_1KIxL1FaN5iJ7I36 where despite getting a valid intent back our same UI is not recognising it properly. Again, same FE and BE integration. I don't suppose you can check if there's anything on your end that might be causing that?
This is what we see:
halcyon pecan
where despite getting a valid intent back our same UI is not recognising it properly
What does this mean exactly?
timber snow
The log: req_EfCQmXT1myq5o3
So typically we retrieve our intent back and then display the PaymentElement but for this account specifically it hangs and renders a second spinner. I can investigate our side and see if there's anything amiss but just wondered if this was down to something on your end as again it is consistent on our other Stripe accounts
halcyon pecan
Hmm, no errors there. When you click that 'continue to payment' button in your UI and the modal opens, what code are you calling?
Are there any errors in your browser console?
timber snow
No nothing. We get back a valid intent:
We are calling and establishing a payment intent with you which I can see in the logs and it all looks valid. We return what we need to then pass a secret to our elements
Okay that's fine. I thought I'd ask in case it was something similar
halcyon pecan
Yeah I'd guess this is some logic in your code that is failing for certain intents. Hard to say without code