#josha_code
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1286055373215629332
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Correct. Specifically, a card-type PaymentMethod.
Sure, you would use a SetupIntent with Payment Sheet in that case: https://docs.stripe.com/payments/save-and-reuse?platform=ios&mobile-ui=payment-element
Ok, thanks. I'll give this a shot.
While I have you, do you know if this will require any backend changes, if we were already doing same with the Card Element UI framework?
Yeah likely some minor tweaks
You need to return the Customer ID here to the frontend
I'm still refamiliarizing myself with our existing implementation but, off the cuff, it seems like the SetupIntent is a new step here, maybe?
Potentially -- it really depends on what you were doing before.
It is entirely possible that previously you were just collecting a Token or PaymentMethod on your frontend and passing that to your backend and then handling stuff there.
As opposed to calling your backend to help handle stuff on your frontend (this flow)
Ok... I'll dig into this and report back here if I encounter any hangups. Thanks for the info.
๐
Does a SetupIntent have a unique, standardized prefix, like other API objects? (e.g. cus_, ephKey_, etc)
Looks like maybe seti_
Operational question: Can other users add comments to this Discord thread? Perhaps it'd be helpful for my backend colleague to drop in here with questions about the same topic.