-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to accept on-session payments with saved payment method. #318
Comments
You can simply call const { error, paymentIntent } = await confirmPayment(clientSecret, {
type: 'Card',
paymentMethodId,
}); You can see an example of this here: https://github.com/stripe/stripe-react-native/blob/master/example/src/screens/CVCReCollectionScreen.tsx#L74-L80 Note that if you're not recollecting the cvc, you can just leave out the cvc param as shown above. |
Thank you so much for the prompt reply. Actually I already tried using My import statement.
Please advice how should we import the |
@benipuri it looks like for a direct function export we've named the method |
Thank you for the quick clarification. |
Hi, I am migrating my App from Charges API to PaymentIntents and I think I am missing something very basic here but Is there any documentation about how to accept on-session payments with saved cards/payment methods. I checked Stripe's documentation about saving and reusing a payment method but it only explains about off-session payments and steps one should follow to start a recovery flow in case the off-session payment gets declined.
In my use case, and I think this is a very common use case, customer adds a card and pay for their order. I am saving this card for future use with setup_future_usage : on-session. Everything working perfectly fine when I try to add a new card and pay. The payment is processed perfectly, the authentication screen pops up wherever required, the payment method gets saved to the customer and so on.. But I can't understand how should I use this saved payment method later.
Any help will be highly appreciated.
The text was updated successfully, but these errors were encountered: