#leah_connect-embedded
late forgeBOT
👋 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/1278458256846622836
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- leahhannahceramics_connect-payouts-accounts, 2 days ago, 22 messages
- leah_sandbox-dashboardbug, 5 days ago, 10 messages
gray lynx
Is this using a Connect embedded component?
If so, which one specifically? Can you point to the Stripe docs?
gray lynx
Do you have an Account Session object ID I can look at to confirm that this parameter was set?
wicked trench
Account ID: acct_1PFr2GjPoo3PsuORf
Request ID: req_wxWBm5vgN3N25R
Account Session Request ID: req_umXVRh1CnvCZrk
gray lynx
I think the issue in the request that errored out is different. It's saying that the ephemeral key you passed in doesn't have permissions to create the Refund, but the Refund itself might be a red herring. I would hone in on fixing the permissions of the ephemeral key first, then move on to testing to see if the refund button is still showing up.
wicked trench
Thanks for sharing. Do you have any pointers to address the issue with the key?
My goal is for the refund functionality not to show on this component.
any reasons why the refund button is showing at all?
gray lynx
I'm not sure about why the button shows to be honest, but we won't be able to debug until the ephemeral key issue is resolved anyway
wicked trench
is there any steps you'd recommend taking to help debug this issue?
gray lynx
Do you know where in your code you're instantiating/setting the ephemeral key?
wicked trench
Taking a look!
late forgeBOT
dapper pumice
leah_connect-embedded
wicked trench
I tried my best but this key is set the account object is created
I am unsure how relevant it is in this case since the front end of the component is showing a button that shouldn't show
dapper pumice
What does "I tried my best" means? Sorry I'm confused by your ask
I'm trying to grasp the backlog but not yet fully understanding what you are asking and what you see
wicked trench
Thanks for jumping in
I am using this component to manage disputes
I set the refund_management to FALSE but the component shows a refund button
I think this is a bug
is there anything needed from to help debug this?
dapper pumice
Give me a few minutes to try to reproduce. To be clear what you do is create a Destination Charge with a Test card for inquiries to trigger a dispute?
wicked trench
correct!
dapper pumice
okay working a reproduction, I'll be back soon
dapper pumice
yeah right now I'm struggling to get the component to render anything :p but working on it!
can you share your client-side code?
wicked trench
$components = [
'payment_details' => [
'enabled' => TRUE,
'features' => [
'capture_payments' => FALSE,
'destination_on_behalf_of_charge_management' => TRUE,
'dispute_management' => TRUE,
'refund_management' => FALSE,
],
],
onShowPaymentDetailsComponent(invoicePayment) {
const paymentIntentId = invoicePayment.dispute_payment_id;
const stripeConnectInstance = loadConnectAndInitialize({
publishableKey: this.stripe_connect_key,
fetchClientSecret: () => this.fetchClientSecret(invoicePayment),
});
const paymentDetails = stripeConnectInstance.create('payment-details');
paymentDetails.setPayment(paymentIntentId);
paymentDetails.setOnClose(() => {
paymentDetails.remove();
});
this.$refs.payment_details_component_container.appendChild(paymentDetails);
},
this may be easier to replicate with the guidance on the Stripe doc?
https://docs.stripe.com/connect/supported-embedded-components/payment-details
dapper pumice
yeahhhh our docs sometimes are the weirdest
paymentDetails.setPayment(paymentIntentId); what's the value here? The PaymentIntent id in the platform? Or are you passing the py_12345 from the connected account?
yeah okay you have to pass the py_12345. This is... so strange that we did that but oh well
I can reproduce the bug so looks like a real bug to me. I clearly pass refund_management: false and still it shows
wicked trench
Thanks for reproducing - what are the next steps in this case?
dapper pumice
I'd recommend contacting our support team at https://support.stripe.com/contact and providing the same details. You can mention this Discord thread https://discord.com/channels/841573134531821608/1278458256846622836 and they can report the bug to the product team.
I'll also proactively flag internally so we can look into what's causing this
wicked trench
Thanks I really appreciate your help!
dapper pumice
sure, sorry for the hassle, took a while to grasp this was likely on our end and not a bug in your code.
Also I hadn't built a demo for that component yet so now I have one 🙂