#sofi-kry_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/1342122943295258696
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- sofi-kry_docs, 1 hour ago, 9 messages
- sofi-kry_customer-sheet-selected-pm, 19 hours ago, 47 messages
The Stripe Mobile Element (PaymentSheet) handles this automatically
But in this case I'm not triggering the sheet because the payment method is already saved and selected by default
In our app we have the "manage cards" and pay flows separate. If there's no card saved, then "pay" triggers the paymentsheet where you can add a card and pay directly. If there's already a saved card and selected as default, then "pay" should trigger the payment without showing the sheet. Does that make sense?
Yes, let me check what the best flow here
Sorry for the late reply
This should be handled using flowController
Trying to find a good public reference for it
mm but we went through the "normal" payment sheet, and according to the flow controller documentation "Displays a sheet to collect payment details only. The button in the sheet says Continue and returns the customer to your app, where your own button completes the setup." So isn't this just another way to present the information?
For our scenario, we don't want to present any sheet.
The sheet will be presented just to confirm the PaymentIntent and handle any next actions for you
What if we don't want to present any sheet? It used to work like that before the migration
Is you want absolutly not to display the payment sheet
then try using the native call directly
ok I'll explore that