#vilesa - Errors

1 messages · Page 1 of 1 (latest)

half raptor
#

Can you share a request ID that corresponds to these errors?

frank citrus
#

the /source_cancel errors?

half raptor
#

I can't help without more clear examples than just pictures.

#

If you can provide a request ID for a request that triggered an error then maybe I can help

frank citrus
#

hmmm.. your question is actually my question

i'm asking you to help me find a request ID, because I cannot do it myself because of a stripe UI issue

#

my question is: Can you point me to one of these "POST /v1/3ds2/authenticate" errors? because on stripe webUI it does not work

thanks!

half raptor
#

Unfortunately I cannot do that without a request ID to see what is going on

#

If you can see your logs (the screen shot you provided) you absolutely can get the request ID

#

It would really help

frank citrus
#

you are not reading my message properly

half raptor
#

Additionally, we do not expose any API that matches /v1/3ds/authenticate

frank citrus
#

"If you can see your logs" -> i'm telling you that I cannot see the logs. That's the issue

#

if /v1/3ds/authenticate is not one of your endpoints, why am I seeing it listed here ?

unknown.png
half raptor
#

Can you share the ID of this object? The payment intent in question? It will start pi_XXXXX

frank citrus
#

can you be more precise? the ID of which object?

half raptor
#

Payment Intent. The first error I see here is to /v1/payment_intents

frank citrus
#

the first error I see is /v1/3ds/authenticate, not /v1/payment_intents

#

why are you talking about /v1/payment_intents; I'm really not talking about that

half raptor
#

I'm reading from the bottom up because it's the first event in chronological order

#

And it's important for why the next errors happened

frank citrus
#

they are unrelated

#

here are my questions:

#
  1. why do I see /v1/3ds/authenticate here; if you say it's not one of stripe endpoints
half raptor
#

It's an internal endpoint that occurred as part of another request. I'm trying to find those requests in your logs

frank citrus
#

ok thanks

#
  1. if I click on "/v1/3ds/authenticate", i arrive on a page related to /source cancel queries. Why is that? Are they related? if yes, how?
half raptor
#

Source cancel queries are about canceling a Payment Method because of an authentication failure

#

These errors appear to be related to authentication failures with 3DS.

#

I'm trying to look at payment intents to se the flow

#

How are you integrating with Stripe?

frank citrus
#

thanks

#

from python SDK and iOS and android SDK

half raptor
#

Okay and you are using the Payment Sheet in Android and iOS?

frank citrus
#

what is the Payment Sheet?

half raptor
frank citrus
#

I don't have my mobile devs nearby, but I guess we use that, we have been processing millions of stripe payments in the last 4 years

#

for info i'm getting this:

#

white page - never had this before on stripe

#

--
would you know for example the reason for this request:
POST /v1/payment_intents/pi_3KjlmgGTsLVnzqGE3qP5NRpE/source_cancel

#

{
"error": {
"message": "La source spécifiée n'est pas valide.",
"type": "invalid_request_error"
}
}

#

although the pi_ in question: pi_3KjlmgGTsLVnzqGE3qP5NRpE

#

went thru successfully

half raptor
#

Perfect, thanks

frank citrus
#

Q: why is this pi_3KjlmgGTsLVnzqGE3qP5NRpE successful but this is called:
/v1/payment_intents/pi_3KjlmgGTsLVnzqGE3qP5NRpE/source_cancel

#

I need to run i will read you later

thanks for the help

honest vigil
#

Hello! I'm taking over and catching up now...

half raptor
#

Hi 👋
This took more investigation but we have some info:

  • The errors related to /v1/3ds2/authenticate/ - These represent errors in bank authentication. These requests are generated internally by Stripe and so they don't show up in your developer logs. I have made a request to ensure we only display errors that can be viewed in the logs.

  • The requests related to the Payment Intent pi_3KjlmgGTsLVnzqGE3qP5NRpE are strange. We see the request to /source_cancel and that is was unsuccessful (it did not cancel the source). 2 seconds later the same source was used to complete the payment in a request to /source_redirect_complete. I have asked internally for an explanation of this behavior as it is not what we expect.

I know that is less than ideal but I hope it does provide some additional insight into the behavior you are experiencing.

fierce locustBOT
#

This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact

Stripe: Help & Support

Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

lime basalt
#

@frank citrus Hi! I reopened this thread. What is your question?

frank citrus
#

hello!

your colleague mentionned (#959492893633048576 message) that something needs to be investigated on stripe side. Are you going to reach out to me once you have some answers?

#

also here is an example of a weird situation (that happens a lot to us):

#

pi_3KkXdSGTsLVnzqGE0S4LLv9P is 'payment_intent_authentication_failure'

although the end user was acknowledged by stripe in their 3DS flow:

unknown.png
#

is there an issue somewhere on stripe side?

#

why do we have so many payments in 'payment_intent_authentication_failure' although they seem to be succeeded on the user side

lime basalt
#

Are you going to reach out to me once you have some answers?
This is an internal investigation, so there's no easy way for you to be notified of this unfortunately.

#

pi_3KkXdSGTsLVnzqGE0S4LLv9P
Can you clarify what is the issue exactly? On our end it looks like you canceled the paymentintent's source a few seconds after creating it.

frank citrus
#

We are not the ones making this request: req_FEZzuRLakMLW5v
i believe that is part of your SDK

the issue is the following:

  • our end users go through the 3DS, they see a Auth confirmation from Stripe (see above screenshot)
  • however it seems there is a mechanism in Stripe SDK that make these /source_cancel requests
  • in the end the payment "fails" (payment_intent_authentication_failure), but we dont understand why: our user have successfully done the 3DS
#

-> so there is an issue in Stripe 3DS flow, where stripe cancels the payment for no reason

obsidian relic
#

Discord is not the right venue for this kind of deep multi day investigation into a livemode possible bug

frank citrus
#

ok sure I will do that

but given your team is already investigating this issue: #959492893633048576 message
can I get a ref ID of your side to link this?

obsidian relic
#

unfortunately not no

#

I can't find it myself and that person is in a different timezone so I can't ask. Sorry! If you write to support that's how you can have a 1-on-1 discussion and be updated on any progress

void cloak
#

Hi, an event was not created for several customers whose card card expires this month 4/22. 'customer.source.expiring'. The only explanation I can think of for why these events were not created is that I added the cards to these customers on March 31, the day before the event was to be created. Would this be the reason the event was not created on my account?

obsidian relic
#

@void cloak please don't ask that in this thread, you can ask in the main channel.

void cloak
#

oops sorry - didn't realize I was on a sub-channel or whatever this is

frank citrus
#

but if I reach out to support how to get them to link to that issue you are already investigating

#

what can I tell them

obsidian relic
#

mention that you were asking about this in Discord, share all the object IDs like pi_xxx etc , and the full context of what you're reporting, and feel free to mention people like Pompey/Snufkin by name in the ticket