#santicarmo31
1 messages · Page 1 of 1 (latest)
- Is there any way to get the SetupIntent or a list of it created by the Stripe iOS SDK
No, typically to do something like this, you would reach out to your server which would make the list SetupIntents call and return that info to your client. That being said, usually the iOS SDK doesn't have much use for SetupIntents outside of confirming them which you already seem to be doing. Which brings us to- How do you use the SetupIntent created by the Stripe iOS SDK
This depends on what you are trying to do. Are you trying to charge the existing card? Present a list of saved cards to your user? Something else?- Can you remove/delete a created SetupIntent if so, how do you do it?
You can cancel SetupIntents that have not been confirmed but you cannot fully delete them. Can you tell me more about why you are looking to delete them?
I'm building an add card on file feature, where we collect user payment methods, and later we list those methods and charge to one of those.
We want to collect the Payment method details using the Stripe Terminal Readers.
So typically in the SDK you would either show the user our CustomerSheet
https://stripe.com/docs/elements/customer-sheet?platform=ios
Or you would list out saved payment methods on your server and then send info to your app so it can display them
https://stripe.com/docs/api/payment_methods/list#list_payment_methods-customer
Will you be charging when the user is away from your app, when they click on some kind of buy button, or both?
Happy to send docs on how to charge saved payment methods for either situation
both please.
Just to confirm. When saving the SetupIntent using "x" customerId, if i list the paymentMethods for "x" customerId then I'll get the paymentMethod saved in the SetupIntent, right?
No rush with it @queen python .
Final question, If I'm already using STPPaymentCardTextField is there any way to use the Stripe Terminal readers to collect the card details ? Or the only way is using the SetupIntent approach
To be clear, you are saying that you want to collect some cards via users inputting the card in to your app and some users putting their card in to one of your termingals? If so, then yes you can do that, we don't restrict you to just card present or card-not-present flows
I want to know if the only way for collecting the cards using the terminals is by using the SetupIntent approach. If there are other what would it be?
Also I have one half of the docs I mentioned, here is how to charge a payment method on your server after saving it. You could do this both for when the user is present and is not present on your app but I think there is a way to do the payment while the user is on your app with the iOS SDK as well https://stripe.com/docs/payments/save-and-reuse?platform=ios&ui=payment-sheet#charge-saved-payment-method
Yes, using SetupIntents would be the best way to save cards through terminal
Thank you @queen python
And for later payments in your app, you can use the payment sheet if it makes sense for you. It will display saved payment methods for customers if you provide their ID and an ephemeral key https://stripe.com/docs/payments/accept-a-payment?platform=ios&ui=payment-sheet
Got it, thanks!
Is it necessary to attach a Customer to a SetupIntent ? Can't I use
curl -G https://api.stripe.com/v1/setup_intents \
-u sk_test_LDGrFyACdIKYxGRktJ4HM2Xn: \
-d limit=3
To list all the setup_intents and then filter them by the id's to get the payment methods I'm interested on ?
👋 stepping in as Pompey needed to step away
You want to associate a SetupIntent to a Customer if you want to make the PaymentMethod re-usable. Otherwise it would only be set up for single-use without a Customer.
single-use means that i can only charge once?
I'm planning to create a SetupIntent without a customer but associating the SetupIntent ids with an specific order, so later i can get the Intent's for that order.
Is there any doc about it?
https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements discusses how Customers are used for future payments
That's it, thanks!