#nickdnk

1 messages ยท Page 1 of 1 (latest)

trim inletBOT
hoary pendant
#

That's a PaymentAttempt obj

pastel pagoda
#

I've not seen this before

#

Shows up in an error log

hoary pendant
pastel pagoda
#

Hmm. See req_xefa2HzRbi1Gmm

#

Seems to be coming from a client, which indicates the Stripe client SDK

#

yeah it's stripeJS

#

Why would this be happening?

hoary pendant
#

unsure, when exactly are you seeing this? Can you share the relevant code?

pastel pagoda
#

Hold on

#

I genuinely don't know

#

It's a direct-to-stripe request from stripe.js

#

so I can't trace from where it's coming

hoary pendant
#

No worries, taking a look

#

The endpoint is /pi_3NqfqQIRviNLId5i0TOSIzXd/source_cancel so seems like 3DS/Redirect related

pastel pagoda
#

yeah that doesn't really help me

#

๐Ÿ˜„

#

I only use PaymentMethods in the Stripe JS library

#

Never sources

hoary pendant
#

yeah it's not on your end, these requests are made by Stripe.js when 3DS is prompted (the whole redirecting to issuer site for auth and back)

pastel pagoda
#

Okay

#

Something worth investigating perhaps since it shows up as an error on my end

hoary pendant
#

yup, looking into it

dire aspen
#

it's an internal object. It relates to Sources only because we used to implement 3D Secure as using Source objects internally, and recently we're migrating that to PaymentAttempts as another internal system.

The URL /source_cancel is what happens when you click the little "x" on the 3D Secure popup from stripe.js, and I think a few other contexts.

Ultimately these are all internal details that don't really matter. Was there a merchant-facing problem you're seeing?

pastel pagoda
#

Alright. No, I don't think it caused any real problem, I was just wondering since we usually don't have errors in the API log except for some I expect and code around.

dire aspen
#

yeah ultimately our various hosted surfaces and libraries make various internal API calls, unfortunately a lot of them can leak through various logs

#

looking at that PaymentIntent and that error, what actually happened is an error in the 3D Secure protocol, looks like a timeout on the challenge

pastel pagoda
#

Okay

#

No problem then

dire aspen
#

it's hard to say more than that but I see that basically the customer had a few retries on that PaymentIntent and eventually made their payment

#

probably they had some problem doing 3DS with their bank initially

pastel pagoda
#

All good