Hi team,
I’m implementing the Payouts API at the moment so we can reconcile these in our finance system.
For each Payout in the API, we get:
id
in the form po_33d35fca-59c7-42d9-a8ef-e22f03bbe450
end_to_end_id
in the form: T3ATS9XG370XV39
However, when I look at the list of Transfers in the dashboard it has:
- a
Transfer #
in the form: 3Z6F9NZJJSRX1DKBQNQZQJX8V7EX
Ideally we would store the Transfer # in the finance system as a narration that our Finance team can use to reference what is in the interface.
Can you help me understand how I can go about giving them a useful narration in this instance?
Unfortunately, the ID
that’s returned by the API isn’t an ID that can be used to reference the transfer in the Seller Dashboard.
Hi! I find myself doing something quite similar and since this post is 6 years old, is there any update on this topic?
I need to find which transaction (order or payment) is related to a payout.
Thanks!!
Unfortunately, there isn’t any update on this and if you’d like to get all payments associated to an payout you’ll need to use our APIs to do so.
Thank you so much Bryan!
Right now my logic is as follows:
- list_locations to retrieve a list of all available locations for each account.
- list_payouts using the retrieved locations and the pagination cursor to fetch all payouts.
Which endpoint should I use now to relate these payouts to their corresponding transactions?
Thanks!!
You’ll then take the payout_id
and call ListPayoutEntries for each payout to get all the transactions for each payout.
Thank you!! That’s just what I needed!