#VoodooPrawn
1 messages · Page 1 of 1 (latest)
The list call can let you list out an array of payment intents filtered by certain factors https://stripe.com/docs/api/payment_intents/list
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Also our search API which can filter on more things but keep in mind its data can be ~1 minute out of date https://stripe.com/docs/api/payment_intents/search
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
my problem is, I only have an array of pi_ ids our side
at the moment, I'm pulling payments that are 1 month either side of the date range I'm looking at (which almost certainly contains ALL of the payments I need). But it takes a long time to pull out that volume of payments 100 at a time using the list endpoint
is it possible to filter on connected Stripe account ID?
that would do the trick
the context is I'm trying to make a report for a specific connected account. It gets a little complicated because we have UK clients using destination charges and non-UK clients using direct charges
and I have a table full of payments with their pi_ in Stripe (either the pi_ of the PI in the platform account if it's destination or the PI in the connected account if direct). I need to grab all payments within a date range for a single connected account
The direct charges you can definitely filter that easily on. You can make the normal list call but include the account's ID in the Stripe-Account header https://stripe.com/docs/api/connected_accounts
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Looking in to if this is possible for destination charges
Not immediatley seeing an easy way to do that. You can use the search API to filter on metadata, so as a workaround you can pass in the account's ID as metadata and search on that. Otherwise I think I will need to put in a feature request to add filtering like that
Interesting, thanks for your help