#kan-ghetto_api
sacred mothBOT
👋 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/1497225190671650867
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
pallid bay
Hi there! Looking into this now
unkempt pecan
Thank you! I can provide more details if needed
pallid bay
You mentioned you tried using the payment id, that works. Can you provide that payment id here?
unkempt pecan
yes give me a second
py_1TPjWDLI0Nx1nST2XaLWDvxW
This works: {stripeConnectInstance && <ConnectComponentsProvider connectInstance={stripeConnectInstance}> {stripeModalVisible && <ConnectPaymentDetails payment={"py_1TPjWDLI0Nx1nST2XaLWDvxW"} onClose={() => setStripeModalVisible(false)} />} </ConnectComponentsProvider>}
Sadly the payment id will not be returned, i checked your whole JSON Response, for Webhook: "checkout.session.completed" and order creation endpoint
pallid bay
Yeah, it looks like this issue stems from the Destination charge that was created from this request:
https://dashboard.stripe.com/acct_1RtVWJLI0N9fs5iQ/test/logs/req_yaADT2lMjZa8WL
py_1TPjWDLI0Nx1nST2XaLWDvxW lives on acct_1TMbwELI0Nx1nST2 (the destination account)
https://dashboard.stripe.com/acct_1TMbwELI0Nx1nST2/test/payments/py_1TPjWDLI0Nx1nST2XaLWDvxW
pi_3TPjW9LI0N9fs5iQ0k8EguUF lives on acct_1RtVWJLI0N9fs5iQ
https://dashboard.stripe.com/acct_1RtVWJLI0N9fs5iQ/test/payments/pi_3TPjW9LI0N9fs5iQ0k8EguUF
The limitations of destination accounts for this embedded component is noted here
https://docs.stripe.com/connect/supported-embedded-components/payment-details?lang=node&client=react
By default, the embedded components offer limited information for destination charges and separate charges and transfers. They don’t provide access to customer information, payment methods, and some charge amount details. The destination_on_behalf_of_charge_management feature allows a connected account to perform refunds, manage disputes, and see additional information for destination charges, including customer information, payment methods, and fees.
This should be the workaround:
https://docs.stripe.com/connect/supported-embedded-components/payment-details#allow-your-connected-accounts-to-manage-destination-charges
When you set the destination_on_behalf_of_charge_management feature to true, your connected accounts can use the payments component to view and manage destination charges that have the on_behalf_of attribute. If you also turn on the dispute_management feature, your connected accounts can participate directly in handling their disputes.
Enabling the destination_on_behalf_of_charge_management feature has the following limitations:
You can’t filter by charge status or payment methods.
You can’t export certain data columns.
unkempt pecan
Tried it with "pi_3TPjwDLI0N9fs5iQ1vC3OeYY", still does not work
Maybe, if its easier, is there an endpoint where i can pull the payment id if i enter the "cs_test_a1svWnjx8zJLlCG3PnKuwVBUKrBrjGUZikSQr3PDtUFnTb3GJQ2993boL7" and/or customer account id? Thats also fine.
pallid bay
Okay, you should also be able to get the py_1TPjWDLI0Nx1nST2XaLWDvxW Charge ID (which lives on the destination account) from the pi_3TPjW9LI0N9fs5iQ0k8EguUF PaymentIntent ID (which lives on the platform).
If you call GET /v1/payment_intents/pi_xxx?expand[]=latest_charge.transfer, then you can use response.latest_charge.transfer.destination_payment to get the py_xxx ID to use in the embedded component.
Alternatively, you can listen to the charge.succeeded webhook and expand transfer.destination_payment to get the py_xxx programmatically.
unkempt pecan
perfect, let me give it a try. thank you
Works!
Thank you. Its crazy how you got such a good support -- on discord -- so fast. I hope they pay you good! Thank you so much.
pallid bay
No problem, happy to help!