#mesudev_api
quasi coveBOT
đ 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/1228427331203498065
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
gray ploverBOT
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.
- mesudev_twint-beta, 4 days ago, 6 messages
glad junco
Flutter Stripe is a 3rd party library, so we aren't familiar with it in here and can't support it
faint sphinx
Then let me rephrase the question, as the flutter community package builds on top of your native iOS and Android SDKs. In these, is it possible to save payment methods in the explained way, without immediately needing to relate them to a payment?
glad junco
Yep the guide you linked has tutorials for how to do this in ios, android, and react native
Just have to click the buttons at the top
faint sphinx
ok great thanks!
glad junco
No problem
faint sphinx
then I suppose the community package must offer a way to do so too but we'll see; you don't know by coincidence about the best possible channel for their support? As I see that Stripe is the main sponsor of that community SDK ?
glad junco
Not sure honestly. I'd check their docs if they have some first
Maybe create an issue on their github repo if there's no luck
Likely, it'll be pretty much the same as their accept a payment flow
The main difference is you use a setupintent instead of a payment intent
faint sphinx
Cheers
wait so this means the method used to confirm a setup intent for card storage + the one used to confirm a setup intent for a payment intent, that's the same endpoint on your end?
glad junco
It's not, no
I just mean from the front-end it's mostly the same
You call different endpoints for confirming a setupintent and confirming a payment intent
faint sphinx
Hmm then it's maybe the easiest that I setup my own input fields for the card data, and forward the data directly to the according stripe endpoint used to confirm the setup intent when storing a card? Or does the stripe-js package used when doing so use some kind of additional authentication like a CSRF-Token or whatever that is built-in in the js sdk ?
with that approach, I would remain PCI-compliant, correct ?
glad junco
Hmm then it's maybe the easiest that I setup my own input fields for the card data, and forward the data directly to the according stripe endpoint used to confirm the setup intent when storing a card?
You would need to maintain pci compliance on your end if you were to do it this way
The mobile payment element is used/recommended so that you don't have to worry about these things
faint sphinx
and same goes for the flutter_stripe package then I guess? Meaning the PCI-Compliance already starts at the way how the text input is handled?
and not only to which server the data is sent?
glad junco
Correct
Flutter stripe, as far as i know is a wrapper on our native sdks
So it would use the mobile payment element
faint sphinx
understood