#deadend_api

1 messages · Page 1 of 1 (latest)

rich tigerBOT
#

👋 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/1334817235075858543

📝 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.

tiny spindle
#

Backend code

$account_session = $this->stripeClient->accountSessions->create([
'account' => $connectedAccountId,
'components' => [
'payment_details' => [
'enabled' => true,
'features' => [
'refund_management' => false,
'dispute_management' => true,
'destination_on_behalf_of_charge_management' => true,
'capture_payments' => false,
],
],
],
]);

thorn moat
#

What is the payment ID that doesn't show in the embedded component?

tiny spindle
#

pi_3QkkYTKksUCRFF3L1dRFR0Wn

#

Its in the platform account

thorn moat
#

Taking a look

tiny spindle
#

But I want to create an embedded component to view the payment details for the connected account

#

THanks

thorn moat
#

What is the connectedAccountId value in this context?

tiny spindle
#

acct_1PDgkL4EZVGMfX0x

thorn moat
#

Is thais the right ID? req_dl2e3Mw9JOjOYV. It 404s here

tiny spindle
#

When I try opening it from the payments embedded component its working fine

image.png
thorn moat
#

OK, it's because I think you're using the wrong ID:

For destination charges and separate charges and transfers, the PaymentIntent doesn’t exist on the connected account. Instead, pass the associated charge ID that belongs to the connected account.

Payment details

Show details of a given payment and allow users to manage disputes and perform refunds.

tiny spindle
#

I am doing that on the frontend.

I am passing in pi_3QkkYTKksUCRFF3L1dRFR0Wn

thorn moat
#

Yeah but in this context the component is initialised on the connected account – that ID doesn't exist there (it's a destination charge, so it's on the platform)

#

There'll be a py_xxx object you need to use, hang on

tiny spindle
#

oh okay.

The embedded component needs to be initialized with the connected account id right?

So in the backend I am initializing with the connected account.

thorn moat
#

Try with py_1QkkYW4EZVGMfX0xijIWhTiO

tiny spindle
#

okay

#

This worked

thorn moat
tiny spindle
#

Is this covered anywhere in the doc.

I am just lost between using pi_ and ch_

thorn moat
#

Yep, the funds flow is outlined here

Essentially the pi_xxx exists on the platform. As you're authenticated as the connected account, when you create the Account Session and init the component, it (correctly) 404s

Create destination charges

Create charges on your platform account, collect fees, and immediately transfer the remaining funds to your connected accounts.

#

In your setup, you need that py_xxx ID on the far right of that diagram for this component

tiny spindle
#

Got it Thanks.

thorn moat
tiny spindle
#

Thanks alot. This helps.

thorn moat
#

of course np