#newtreyes
proven totem
Hello! If you mean a specific Payment Method object, no, a Payment Method can only be associated with a single Customer. If you mean a generic payment method, like a card for example, that one card can be represented by several different Payment Method objects, and those objects can be attached to several different Customers.
What are you really trying to do? 🙂
worthy mirage
Well, here's the thing
We are using this endpoint to find out what's the setup intent for a specific payment method: https://stripe.com/docs/api/setup_intents/list
What we are seeing is that a single payment method can return a list of setup intents and they are not from the same customer.
proven totem
When you say "same customer" do you mean a human being or do you mean a Stripe Customer object?
worthy mirage
Stripe customer object
proven totem
Can you give me the ID of one of the Payment Methods which are showing multiple Setup Intents for different Customers?
proven totem
Looking, hang on...
worthy mirage
Thank you, Sir
proven totem
So it looks like what's happened here is that a legacy Bank Account object (the ba_ ID you provided) was used to create several different Payment Method objects (pm_) and then those different Payment Method objects were set up with several different Setup Intents. No customer was set on the Setup Intents, so there was no conflict there.
Unfortunately this happened so long ago that the API request logs are no longer available, so it's hard to say exactly what happened.
But that's why you're getting the unexpected results.
The unique Payment Method objects used with these Setup Intents also don't seem to be associated with a Customer.
But the original ba_ object is.
Does that help?
worthy mirage
Give me a min to digest
proven totem
Although... hm. This is getting stranger the more I look at it. 😅
proven totem
Yeah, okay, something is amiss here.
The Payment Methods used with the Setup Intents are for ACSS accounts, but the legacy Bank Account is a US account.
Do you have a request ID for one of your list requests? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
If you're using the Dashboard to find the request ID make sure you adjust the filters to show GET requests.
proven totem
Yep, thanks! We're investigating, hang on.
worthy mirage
Thank you, Sir
proven totem
Do you know if this worked as expected before, or is this something new you're trying for the first time?
wintry ironBOT
worthy mirage
Do you know if this worked as expected before,
We've seen this issue way more frequently lately
but we didn't know if it was very specific to a connected account
this something new you're trying for the first time?
No. We have had this in place for a while but these errors happened recently
proven totem
To clarify, are the errors only when you use a legacy ba_ object as the Payment Method, or does it matter?
proven totem
Also wondering if legacy objects specifically worked before?
worthy mirage
Not sure
proven totem
We're wondering if this is something specific to legacy objects or if things like pm_ are impacted as well. So far we haven't been able to reproduce on a different account, but we're still investigating.
worthy mirage
Thank you
proven totem
Okay, looks like a bug on our end. We're looking into it and will hopefully have it fixed soon, but I can't give you an ETA or anything like that.
proven totem
If I had one I would share it, but we just don't know yet unfortunately.
worthy mirage
Got you
proven totem
The only workaround I can think to suggest is to filter by Customer instead, then find the relevant Setup Intent in the results.
proven totem
Sorry I don't have better news, but thank you for flagging and providing the information so we can get to work on fixing this one!