CalebR-Connect-Reports | Stripe Developers | Page 1

buoyant kayak Feb 22, 2022, 6:40 PM

#

Hi there! Give me one sec

#

Do you have a request ID when you try to run the report while setting the connected account but it errors?

#

Ah, actually.

#

You want to look at the Connect specific reports: https://stripe.com/docs/reports/report-types#connect

#

For instance you probably want one of the connected_account_payouts.itemized.x reports

#

Have you tried those?

void goblet Feb 22, 2022, 6:57 PM

#

Ah, that is helpful. Let me see if that gives the correct information

void goblet Feb 22, 2022, 7:21 PM

#

So that finds the payouts, however, the payment_intent_id column is coming back empty.

buoyant kayak Feb 22, 2022, 7:24 PM

#

Ah you are likely using Transfers (either through destination charges or Separate Charges and Transfers, which means that the payments on the Connected Accounts will not be PaymentIntent objects, but payment objects instead (py_xxxxx).

#

These payment objects are the result of a transfer on the Connected Account

#

And are the same as Charge objects

void goblet Feb 22, 2022, 7:25 PM

#

Yes, we are using destination charges

buoyant kayak Feb 22, 2022, 7:25 PM

#

So you want the charge_id column

#

Instead of payment_intent_id

void goblet Feb 22, 2022, 7:26 PM

#

Okay, but is there a way to connect the charge_id back to the payment intent that originated it?

#

When I try to retrieve a charge via the API, I get a 404.

buoyant kayak Feb 22, 2022, 7:27 PM

#

Are you passing the Connect Account header?

#

That charge lives on the Connected Account

#

Yes you can trace back to the original PaymentIntent, give me a sec to write out the steps to do that.

void goblet Feb 22, 2022, 7:31 PM

#

Is there documentation on how to specify the Connected account? I'm using the Ruby API client

buoyant kayak Feb 22, 2022, 7:32 PM

#

Yep, take a look at: https://stripe.com/docs/connect/authentication

Making API calls for connected accounts

Learn how to add the right information to your API calls so you can make calls for your connected accounts.

#

To trace backwards from the payment on the Connected Account, you want to look at the source_transfer property: https://stripe.com/docs/api/charges/object#charge_object-source_transfer which will give you the transfer ID. From there you can utilize the source_transaction property (https://stripe.com/docs/api/transfers/object#transfer_object-source_transaction) which will give you the original charge that created the transfer. And from there you can access the PaymentIntent.

#

You can use expand to limit the amount of API calls necessary here: https://stripe.com/docs/api/expanding_objects

void goblet Feb 22, 2022, 7:39 PM

#

Okay, that did it. Is there any way to do that connection with a report, or are we just going to have to backtrack through the API for every transaction?

buoyant kayak Feb 22, 2022, 7:41 PM

#

If I remember correctly you can only get the source ID (the transfer) from the Payout Recon Report and then you do need to backtrack from there. I would test this though with the columns in the payout reconciliation reports, I haven't played with these reports in a while.

void goblet Feb 22, 2022, 7:43 PM

#

Okay, thanks. This was quite helpful.

#CalebR-Connect-Reports