#chuckrevs_unexpected
jade haloBOT
👋 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/1317196007410237481
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
faint fossil
crude shale
Hey! Looking into this now.
faint fossil
hey, thanks!
i am also still looking at it and noticed one more thing that could be helpful. the status that appears on the index view "payments" component is not matching the status of the "payment details" when i click on an individual payment.
Specifically "partially refunded" in the index view is appearing as "succeeded" in the details view.
Likewise for "disputed"
Interestingly, when i click on a disputed payment (via the Disputes "tab") I do see the Payment Method Details as I would expect to. And I am presented with the "counter dispute" button.
jade haloBOT
tardy pasture
Hello
Taking over here..
Can you share the payment ID for which you're trying to see the details?
faint fossil
pi_3QKS9mFLSb2ZGk3809u0Vnth
tardy pasture
Hmm its a direct charge so the config you have should work as is 🤔
Can you share the exact code you're using to create the account session?
tardy pasture
Can you enable destination_on_behalf_of_charge_management feature too just to see if it makes any difference?
tardy pasture
You'd want to add that under payment_details feature.. Not payment feature
ah you added both nvm
faint fossil
yeah, just in case :)
tardy pasture
Is it just happening with this specific payment or all payments?
faint fossil
I have also tried removing the payment_details component entirely and just using Payments and it's not helped
this is happening with all payments
there are no connect.js errors, and just this one warning which is expected:
You may test your integration over HTTP. However, live integrations must use HTTPS.
tardy pasture
Hmm interesting..
Give me a few to look into this. I'll need to try and reproduce this which might take a bit
faint fossil
sure, thanks for your help
tardy pasture
still looking.. things are just running a tad bit busy
tardy pasture
okay so I asked a colleague to try it out too and they seem to be able to see the details -
https://asi-connect-elements.glitch.me/connect-elements
have you tried testing with a different account and see if that works?
also try changing the components hash to be something like:
components: {
account_onboarding: {
enabled: true
},
payment_details: {
enabled: true,
},
}
Ok, will try that. And report back
(I have tried using different connected accounts)
jade haloBOT
faint fossil
Ok, so I thought I had test with a different connected account but I must not have because other connected accounts are working as expected. i'm not sure what is special about the other account I was testing with 🤷♂️
naive pebble
Hey there 👋 jumping in as my teammate needed to step away. Just want to make sure I'm understanding correctly, the component behaves as expected for one account but not for another?
If so, can you share the ID of the Account where it works as expected? I'd like to compare it to the other Account associated with the intent you shared earlier.
faint fossil
this account works as expected: acct_1QBMfuFJlOgl29Tq
this is the account where it does not: acct_1QDROnFLSb2ZGk38
Unfortunately, I may need to sign off in a few minutes
naive pebble
Any chance you have a publicly accessible test site where we can take a closer look at what you're seeing?
faint fossil
the account is is borked is the one I test with locall, the ones on staging seem fine so even if i gave you access to our staging server it would all look good to you
naive pebble
Hmm, I wonder if testing locally is contributing to what you're seeing in any way.