#citruslime.benk - request options
shadow trout
Just to clarify, you are using this: https://stripe.com/docs/connect/destination-charges#settlement-merchant
?
mint vessel
That's correct.
So I'll elaborate.
We have a dashboard for each of our retailers, so we want to get all payment intents for a particular stripe account (unique to each retailer).
The reason why we want to use list all async is because we are concatenating the payment intent with dbo records for our ecommerce system, so we need to transform your models into another model.
The only problem is that the list all method isn't returning any data when we add the param.
shadow trout
So that param is the stripe account header
mint vessel
Correct.
shadow trout
That is used to find payment intent objects stored on the account
When you use destination charges, payment intents are stored on the platform
So it's expected nothing will be returned there
mint vessel
Ok, that's understandable.
In that case, how would we be expected to filter the payment intents by the destination account?
shadow trout
You would have to filter in your own code. You could inspect the transfer_data: https://stripe.com/docs/api/payment_intents/object#payment_intent_object-transfer_data-destination
mint vessel
So this presents a problem, since we have ...
Currently it takes an absolute age to load all of this data and filter it in code?
I can't see how this could be considered a tenable solution?
Are there literally no other alternatives?
shadow trout
The reason why we want to use list all async is because we are concatenating the payment intent with dbo records for our ecommerce system, so we need to transform your models into another model.
Going forward I recommend doing this operation and storing the Payment Intent data in your database on payment success so that you won't have to query the Stripe API to load the dashboard. Unfortunately there's not a simple way to do this with existing results if you're using destination charges
mint vessel
If that is the case, I can't see this being a tenable. We're going to need to discuss this internally.
Can we petition to have the transfer destination as a permitted search query field?