#pavlos_91429
1 messages · Page 1 of 1 (latest)
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.
- pavlos_91429, 15 hours ago, 7 messages
- pavlos_91429, 1 day ago, 6 messages
- pavlos_91429, 2 days ago, 39 messages
- pavlos_91429, 5 days ago, 18 messages
- pavlos_91429, 5 days ago, 7 messages
- pavlos_91429, 6 days ago, 4 messages
and 3 more
Hi
Could you please summarize your latest follow up question ?
private _handleSubmit = async () => {
const { stripe, elements } = this.props;
if (elements == null || !stripe) {
return;
}
const { error: submitError } = await elements.submit();
if (submitError) {
emitToast({
content: submitError.message,
toastType: ToastTypeEnum.error
});
return;
}
const res = await axios.post("/investor/payment-methods/initiate-stripe"); // this is a call to my API that correctly returns a client secret
const { error } = await stripe.confirmSetup({
elements,
clientSecret: res.data.clientSecret,
confirmParams: {
return_url: `${process.env.DOMAIN_URL}/investor/stripe-pay-callback`
}
});
if (error) {
emitToast({
content: error.message,
toastType: ToastTypeEnum.error
});
}
Hello! Thanks for the response. Sure.
I am using payment elements to allow users to add payment methods, without them having to pay (saving the payment method for future use)
I had some trouble where the confirmSetup promise was not resolving.
This happened only when I added billingDetails: “never” was added as an argument to the PaymentElement component
Can you share the SetupIntentId ?
I shared two setup intent IDs in the previous thread, let me get those
seti_1Oeh5PJ54lNDIU9BqU9sbLA0
I see only the creation request
I see no confirmation request was made
For some reason the stripe.confirmSetup isn't called
Indeed, but the code does reach that line. Any idea if internally the Stripe library would not make that call for some reason??
No, that's not related to Stripe SDK