#laxmanpula-reports

1 messages · Page 1 of 1 (latest)

tender verge
#

With newer standard connect accounts I believe you are correct that you'd get the reporting.report_type.updated event on your platform webhook to be notified of data availability but this wouldn't apply for older standard accounts that are not managed by a single platform

marsh sigil
#

we have created these accounts using api in last october. never used OAUth to setup.

#

I am assuming it is newer. is there a flag or setting I can verify these standard connect accounts that are controlled by a single platform?

tender verge
#

I can check one really quickly for you right now if you want - I believe that since you're not using oauth and following the flow where you create the account on their behalf you should be good to go, but I can double check

marsh sigil
#

sure.. what details you need to verify?

tender verge
#

just an account ID would be fine

#

(of the connect account)

marsh sigil
#

acct_1JnTEQQxmEUZXvBM

tender verge
#

Yeah, I can see it's set up to be controlled by a single platform so you should be fine

marsh sigil
#

Thank you for the confirmation.

#

if the events comes on platform webhook end point, how to identify the event is for connect or platform? also if I have multiple connect accounts for the platform account?

tender verge
#

For the reporting.report_type.updated event it would JUST be coming in for your platform - we wouldn't specify a connect account. We'd notify you that data is available for connected_account_payout_reconciliation.itemized.4 is available for you as a platform which should represent ALL your connect accounts. You can pass a specific connect account ID as a run parameter when you actually run the report

marsh sigil
#

ok. if we have more than one connect account?

#

do we need to RunReport for each connect account?

#

do we get the connected_account_payout_reconciliation.itemized.4 event only after data is available for all of its connected accounts?

tender verge
#

If you want the data for ALL your connected accounts you could just not specify a connect account ID when you run the report and it should give you back the data on all of your accounts. You'd specify a connect account ID only if you want information on one account. If you'd want to generate separate reports for each connect account then yes, you'd have to generate a run for each account ID.

#

do we get the connected_account_payout_reconciliation.itemized.4 event only after data is available for all of its connected accounts?

Yes, I believe this is the case

marsh sigil
#

thank you. Karbi.

#

One more question, How to not to receive connected transaction on platform account?

#

I mean when I dont pass connected account.. I would like to receive only platform transactions?

#

or is there a way we can identify whether it is a connected transaction and its connected account id from report?

tender verge
#

Is there a particular report type you're asking this for specifically? That may help me narrow down the answer

marsh sigil
#

yes. connected_account_payout_reconciliation.itemized.4 ---- for connected accounts

#

payout_reconciliation.itemized.4 -- Platfoem account

tender verge
#

For connected_account_payout_reconciliation.itemized.4 you'd ONLY get transactions associated with connect accounts. For payout_reconciliation.itemized.4 I believe connect-related lines would have connected_account_id populated, so you'd just check that

marsh sigil
#

got it. thank you.

#

I appreciate your help and quick response, Karbi.