louis_api

[rocky nymph]

👋 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/1283065507871850539

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[dusky plaza]

Hello

[elfin rune]

hi there, can you share an example object ID, and explain what you are trying to do?

And where are you seeing these payatt_123 object ids?

[dusky plaza]

I'm trying to find out why we have 20% failed payments instead of the regular ~4%. For that I looked at the "payment analysis" dashboard, under "failed payments" and downloaded the export.
In this export are 19 columns.
When filtering for outcome_type=authentication_failed and transaction_initiator=(empty) I see that all the values of the column "id" start with payatt. For example payatt_3Pwr9XKjQ6ckdFHB0opjixfo
I wonder what are those payments, in which case we have those

[hard coral]

Hi 👋 jumping in as my teammate needed to step away. Those are payment attempt objects that aren't exposed via the API.

[dusky plaza]

Hi, thank you. Are those retried with an exponential back off if unsuccessfull?

They're all marked is_final_attempt=true

And if not retried, can we manually retry them?
I heard from Stripe support that there was an incident with 3D secure that was resolved today. This looks to have greatly impacted our payments and I would like to make sure those are not lost.

[hard coral]

Um, I don't think the question really makes sense. Each one is an individual attempt to process a payment as far as I understand. My teammates and I in this forum aren't familiar with the output of the reports you're running or how to interpret them (we specialize in helping developers work with our API), so our colleagues on our Support team may be able to share more insight on what you're seeing.

You can't interact with payment attempt objects

[dusky plaza]

Ok I see, I'm at lost since they don't know lot about those payment attempts too

[hard coral]

I am a bit too, I'm not sure why those are being shown to you.

Taking a step back, lets set aside the existence of those payment attempt objects, what is your goal here? Maybe I can at least point you in the right direction if I can't provide more insight.

[dusky plaza]

I'm trying to find out if we have another problem aside from the 3D secure (I assume global) issue that may explain this 4% -> 20% failed payment rate

But thay may be because of failed renewals of last year since we have promotions at this time of year

[hard coral]

Gotcha. For checking the trend of authorization rates for your account, I would suggest reaching out to our Support team again, they're better suited to assist with that:
https://support.stripe.com/?contact=true

If you want to try to look at this from the API, I'd suggest trying to list all of your Charge objects from the time period you're investigating, and look specifically for ones that have a status of failed. Then try to gain insight on why they failed from the failure_code , failure_message , and outcome hash on those objects.