venkateshjsoft

[desert cargo]

You're passing confirm: true when creating the PaymentIntent
https://dashboard.stripe.com/test/logs/req_cqDdLnbNdZfwuu

You should only pass that parameter if you have a previously stored payment method and are trying to confirm the PaymentIntent server-side.

[lime crane]

We don't have frontend to confirm the payment at the moment. so I should make another stripe api call to confirm the payment?

[desert cargo]

I'm confused. If you don't have a frontend then how would you collect the payment method information?

[lime crane]

im sorry for the confusion, frontend is not ready. im a backend developer so im creating payment service which will be invoked from the frontend later.

is it possible to test the whole payment flow (create customer, create payment method, payment intent and confirm payment) from the server side

[desert cargo]

We usually recommend against creating a payment method by calling the PaymentMethods API directly but you could try that
https://stripe.com/docs/api/payment_methods/create

[lime crane]

is it possibel to confirmIdealPayment or any other payment methods from server side?

I have one api which is responsible for creating customer, create payment methods and create payment intent. since I was passing the parameter confirm = true. it was giving the error. HOw can I confirm the payment when the frontend is not ready

[desert cargo]

Once you create the payment method, you can pass it in and call the confirm PaymentIntent API endpoint
https://stripe.com/docs/api/payment_intents/confirm

[lime crane]

I did the same, but payment intent is not the final payment I guess. correct me if i am wrong

I believe we need to make another api call to stripe to confirm the payment

[desert cargo]

Not sure what you mean. You setting confirm: true is different than when you call /confirm endpoint with a payment_method parameter
https://stripe.com/docs/api/payment_intents/confirm#confirm_payment_intent-payment_method