#sg-pushpaveni_api

1 messages ยท Page 1 of 1 (latest)

solar yarrowBOT
#

๐Ÿ‘‹ 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/1318114042665107456

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

thick jacinth
#

kindly let me know what type of 3d secure flow this payment intent pi_3QUZhYJTd5VGe2wm0wSA3zpW gone through

#

this payment call responsed with --- "status":"requires_action"

frail mural
#

Hi there, I checked this paymentIntent and its status is succeeded

#

You should setup a webhook endpoint to listen to payment events like payment_intent.succeeded and payment_intent.requires_ation

#

So that your application can still be notified about the payment status if your frontend app failed to receive status due to network problem.

thick jacinth
#

payment_intent.succeeded and payment_intent.requires_ation these are handled in our code.

but this payment response was not happened as other payment flows with 3DS

#

jsut wanted to know, whether the user had taken so much time to complete the 3DS verification

frail mural
#

No, I don't see you've set up any webhook endpoints yet.

thick jacinth
#

you mean the webhook for credit card payment also???

#

during the checkout flow, we are creating the order based on the responses from the API calls on the payment success, otherwise the order wont be created.....

#

we have confirmed the webhooks for ACH payments, not for the Credit card payment, isn;t it????

frail mural
thick jacinth
#

var service = new PaymentIntentService();
var paymentIntent = service.Get(
authorizationInformation.Paymentintentid
);

            if (paymentIntent.Status != "succeeded")
            {
                var confirmedIntent = service.Confirm(authorizationInformation.Paymentintentid, options);
                return confirmedIntent;
            }

we are handling the requires_action with the above code, it is working for most of the users, but only for only few users, this is not working....
it would be great to know the cause of the missing payment status only for those few users.....
it is related to 3ds only...
is there any other ways to handle the requires_action flow so that we can be sure that the payment status will be received in all the ways...

frail mural
#

No I don't think this is the right way to handle payements with requires_action status. You can't handle 3DS from backend, you need to bring your customer to your frontend page where you can call stripe.confirmCardpayment to start the 3DS flow.

thick jacinth
#

But then it is working fine for most of the user payments with "status":"requires_action"
only for few users, the bove code flow is not working

kindly share your thoughts on it

thick jacinth
frail mural
thick jacinth
#

Im cheking on it

#

this is what we have implemented in our application

#

return url is mandatory for this one???
we are missing that return url....
But Im still surprised, for some users with status = requries_action, the payment flow succedded with this implementation itself.

#

I would like to understand the payment flow for the already shared paymentIntent, something is different from other ones....

  • what type of 3ds was done the user?
  • did the user have taken so much time to compelte the 3ds ---> which is leading to some issue?
frail mural
#

that part of the document that you are reading now is about payment confirmation. After confirmation, if the payment status becoes requires_action, you still need to bring your customer back to the frontend to start the 3DS authentication flow.

thick jacinth
#

it is handled with the below code

stripe.handleCardPayment(
clientSecret
).then(function (result) {
if (result.error) {
} else {}
})

#

I would like to understand the cause of the missing payment flow for some users and handle that in our end

That is why Im asking so many questions and sharing the code snippets also for your reference

#

kindly help me to resovle it in our end

frail mural
#

What do you mean by "missing payment flow for some users " ?

thick jacinth
#

if there is an option to have a call with screen sharing with voice, then it is easy to share with you

frail mural
#

I can only support you through chats

thick jacinth
frail mural
#

What's payment intent ID?

thick jacinth
#

pi_3QUZhYJTd5VGe2wm0wSA3zpW
this is the one which I have shared already

frail mural
#

No, this payment is already succeeded

thick jacinth
frail mural
#

We discussed about this, and the solution that I recommended is to set up a webhook endpoint so that your application is still able to notfied about payment status when your frontend is unable to.

#

Did you get a chance to go though the docs that I shared earlier?

thick jacinth
#

Im going through it, but I have to completely understand it

#

and have to check how to implement it in our application.....

frail mural
#

You can pass the docs to your engineers and feel free to come back again if they have any questions regarding the webhook implementation.

thick jacinth
#

I will check it out, but the thing is that the 3DS flow is working for most of the users ...
it is surprising for me, how it is working with the current implementation itself....

thick jacinth
frail mural
#

Ok, so here's what happened. You confirmed the payment from frontend, and Stripe.js automatically trigger 3DS flow when 3DS was requested. However, your frontend didn't receive the response and therefore it "stuck" in the requires_action status.

#

Actually the 3DS was succeeded, payment went through, but your application doesn't have webhook endpoint that listesn to payment related events and therefore unable to get notified about the latest payment status.

thick jacinth
#

thanks for clarifying, I will go thorough all the references you have shared...

#

thanks for the support from your end ๐Ÿ™‚

frail mural
#

No problem! Happy to help.

solar yarrowBOT
compact otter
#

๐Ÿ‘‹ taking over for my colleague. Let me know if there's any follow-up Qs I can answer!