#benbartling-customer-payment-method
eager horizon
Do you have an example request id (req_123) or customer id (cus_123) I can look at?
eager horizon
perfect looking
huh that's weird, I didn't know we had this limitation, it feels off. Let me reproduce first but looks like we expect you to set the customer before SetupIntent creation
strange flower
Ok, thanks for looking into it.
It does feel off to me as well. This limitation does not exist for PaymentIntent, which makes it even more odd.
eager horizon
yeah unfortunately looks like a real validation we've added when we built that API. I don't fully grasp why though so I'll be raising this internally, but for now your best bet is to create the customer upfront
strange flower
Ok, thanks for the update. What happens when you raise it internally? Can this result in the validation getting changed?
Can I stay in the loop on this?
eager horizon
it might though it's unlikely in this specific case