#girotto_best-practices

1 messages ¡ Page 1 of 1 (latest)

gritty gateBOT
#

👋 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/1233387120207466530

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

mossy graniteBOT
lost dove
#

Hi, let me help you with this.

#

That's similar to how Stripe was working before. Currently, the recommended flow is to create an object called PaymentIntent on the backend (or SetupIntent if you're saving the payment method for later), and provide it to the frontend component (Payment Element, Mobile Payment Element, etc.), which will take care of sending the sensitive credit card data without you ever needing to interact with it. I don't know exactly how stripe-flutter does it, since it's not one of our official SDKs, but perhaps you could get an intuition for it by looking at our React Native flow: https://docs.stripe.com/payments/accept-a-payment?platform=react-native

static light
#

Thanks for the help @lost dove ! As far as I understood, the PaymentIntent is tied to a specific charge, isn't it? Our goal is to create something that can be reused. The flow in our app is: the user register its CC information in the wallet and we use this CC every order the customer does.

lost dove
mossy graniteBOT