#Venkatesh Thirupathi
sour granite
soft flame
The "Setup Future Usage" column on the tables in this section will tell you if a PM of that type can be saved or not https://stripe.com/docs/payments/payment-methods/integration-options#additional-api-supportability
Tough interestingly, it lists iDEAL as being able to be saved https://stripe.com/docs/payments/payment-methods/integration-options#additional-api-bank-redirects
I will check in to if the doc got that wrong or not and will get back to you
potent orchid
sure, thanks
soft flame
Hey @potent orchid huge apologies for the delay in this thread. The server got busy and I accidentally dropped off here.
It looks like iDEAL can be saved so the doc is accurate. Our processes for saving iDEAL PaymentMethods creates a SEPA PaymentMethod that is the one to be reused. https://stripe.com/docs/payments/ideal/save-during-payment
Can you send me the ID of the request where you got this error message (req_123)?
soft flame
Were you following a specific doc when doing that flow? I see just before that you created the iDEAL PM directly but that isn't how iDEAL PMs are typically saved as far as I know.
Basically, if you are taking a payment upfront and using it later, you follow this doc to take an iDEAL payment and then save the SEPA PaymentMethod https://stripe.com/docs/payments/ideal/save-during-payment
potent orchid
im invoking this api request using postman
soft flame
If you are just setting up for a future usage, you would want to just save a SEPA PaymentMethod