#lafafm-stripejs

1 messages · Page 1 of 1 (latest)

soft turret
#

@crude ocean depends what kind of error it is, since e.g. if the error is from an attempt to confirm a PaymentIntent failing, that is an API call and appears in your logs as normal. But no direct logs for stripe.js itself at least, you might want to make sure you catch and log all exceptions in your own monitoring/use tools like e.g. Sentry, etc.

If you have more context on what exactly these errors might be, happy to try to help

crude ocean
#

As for ApplePay complain - customer says he got process failure

GPay - There was an error processing your order

#

Haven't seen any of those before, so not sure where to dig in

#

Also, maybe there's some possibility to filter out error logs here dashboard.stripe.com/logs by the name on card?

E.g. most of error bodies for payment_intents / etc. have payment_method.name param

soft turret
#

I'd maybe try to find the IDs of the Payment/SetupIntents involved in those customer's check out attempts(you might need to consult your system's logs or add this kind of information if you don't have it) and from there you can look at them in the Stripe dashboard to find any related API errors. You might also ask the customer for more information like the device they were using or the brand of the card etc

soft turret
#

the log filtering is fairly basic, the main thing is to know the ID of the API objects involved in the failed attempt from your monitoring and then you/we can look for possible errors

crude ocean
#

Ok, thank you

Will search for it then

#

Btw @soft turret

What Error param filter stands for?

Can I use it to reduce logs scope somehow?

soft turret
#

you can but I haven't used this much myself actually

#

I don't think it helps unless you already know what you're looking for , like you've found one example of a failed request and are looking for others