#clashroyaleofficial

1 messages · Page 1 of 1 (latest)

autumn galeBOT
#

Hello! We'll be with you shortly. 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.

tribal oyster
#

I will provide some images to clarify how my app works on the user end

cosmic swan
#

Hi 👋 it's not necessarily a bad practice to keep creating Payment Intents, as long as your code is ready to parse through and ignore any incomplete ones and you don't mind seeing those in your dashboard.

You can also look at our flow where creating a Payment Intent is the last thing you do:
https://docs.stripe.com/payments/accept-a-payment-deferred?platform=web

Collect payment details before creating an Intent

Build an integration where you can render the Payment Element prior to creating a PaymentIntent or SetupIntent.

tribal oyster
#

Ok cool thank you! I will probably do that then. I'm only worried about overflowing with paymentIntents, but if you think that shouldn't cause any problems then I'm good to go

#

this is the UI flow

cosmic swan
#

👍 yup, it's technically not a concern, but we heard complaints in the past about those cluttering the dashboard views which is why I wanted to warn about that.