#leahhannahceramics_unexpected
spring socketBOT
👋 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/1268714395941474305
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
hardy wigeon
Hello
can you share the example Payment Intent ID?
torpid wolf
pi_3Pj3DjPwykGTMq6421MCy9RR
hardy wigeon
Hmm looks like the dispute was closed already?
using this request: https://dashboard.stripe.com/test/logs/req_haia1RchIUfwYO
torpid wolf
Oh I resolved it via the dashboard - should I open a new one?
hardy wigeon
Yup
and are you enabling destination_on_behalf_of_charge_management when you create the element?
https://docs.stripe.com/connect/supported-embedded-components/payment-details#:~:text=For destination charges with,enabling the corresponding features.
and you also need to turn on dispute_management
https://docs.stripe.com/connect/supported-embedded-components/payment-details#allow-your-connected-accounts-to-manage-destination-charges
torpid wolf
yes i have both set to TRUE
hardy wigeon
Can you share the code you're using for this?
torpid wolf
[
'account' => '{{CONNECTED_ACCOUNT_ID}}',
'components' => ['payment_details' => [
'enabled' => true,
'features' => [
'capture_payments' => false,
'destination_on_behalf_of_charge_management' => true,
'dispute_management' => true,
'refund_management' => false,
]
]],
]
hardy wigeon
client-side code too
torpid wolf
const stripeConnectInstance = loadConnectAndInitialize({
publishableKey: this.stripe_connect_key,
fetchClientSecret: this.fetchClientSecret,
});
const paymentDetails = stripeConnectInstance.create('payment-details');
paymentDetails.setPayment(invoicePayment.stripe_payment_id);
paymentDetails.setOnClose(() => {
paymentDetails.remove();
});
container.appendChild(paymentDetails);
hardy wigeon
Thanks, give me a moment
spring socketBOT
hardy wigeon
I was able to reproduce the issue I think..
are you seeing any failed network requests in your console?
hardy wigeon
It could be a bug. We're checking with our product team about this
torpid wolf
Thanks I really appreciate it
hardy wigeon
Ah I think I figured it out
You also need to set
enabled: true,
features: {
refund_management: true,
dispute_management: true,
capture_payments: true,
destination_on_behalf_of_charge_management: true,
},
},```when you create the account session
torpid wolf
ohh - even if I'm not using the payments embedded component in the front end?
hardy wigeon
Yeah I think the permissions that are granted for payment component is what you'd need to respond to disputes
I know it feels wrong.. We've reported this internally to see what can we do about this
but for now, you'd need to enable payments component too
hardy wigeon
NP! 🙂 Happy to help