#dupont-connect-checkout

1 messages ยท Page 1 of 1 (latest)

sonic arch
#

Hiya ๐Ÿ‘‹ do you have the request ID from when you tried to create the checkout session?

plush holly
#

I can recreate one

#

req_f4Xdh84eKY2zdW

sonic arch
#

Thanks, taking a look!

sonic arch
#

Thanks for your patience. Looking at the request it seems like you're combining direct and destination charge parameters, so it's not clear what is attempting to be accomplished. Do you know the type of charge you're intending to create?

plush holly
#

For a 100$ price for example, I want that the connected account receive 80$ and 20$ as fees for the platform

#

It is better for us if the subscription charges do not appear in our platform balance, its seems to be direct charge that we need ?

#

But even without transfer_data, which means "destination charge", I got the same error ?

sonic arch
#

When looking at the request I saw that the price object existed on the account that you had specified as the destination. With destination charges the platform is the system-of-record, and therefore any relevant objects need to exist on that account.

plush holly
#

Yes, but I'm purpose, is to try to start the subscription on the connected account

#

On a new request, I have removed the transfer_data option, but I still got the same error

#

req_0TLff4VeWOd07X

sonic arch
#

Ah, if you want to do it on the connected account then you will need to create a direct charge by specifying the connected account in the stripe_account parameter.

plush holly
#

It's already done ๐Ÿ˜ฆ

sonic arch
#

I would suggest double checking the key that you used when initializing stripe, and the value that you're passing for stripe_account. I can't disclose account IDs in this forum so I can't give specifics, but I don't think they're set to what you're intending to set them as.

plush holly
#

Holy shit it's a typo on the connect_id

#

Sorry

sonic arch
#

No worries, we've all been there. Glad we were able to get to the bottom of it!