#dilk-errors
1 messages · Page 1 of 1 (latest)
@lunar wing yes, declines codes are part of errors that are specifically related to a failed charge where e.g. the bank declined the payment, error codes are more general.
Under what circumstances are these two types of returns? Because sometimes one of them is null
decline codes are returned when there's a decline(like charging a card where the bank declines the payment, can be tested with the cards at https://stripe.com/docs/testing#cards-responses ))
What is the difference between these two?
do you know what a credit card decline is?
I'm not sure how else I can describe this otherwise. If the error is a decline, then there can be a decline code( the code the bank returned as the reason for declining the payment). If the error is not a decline, and is an error for some other reason(like a malformed API request or an internal Stripe error or a network error), it won't have a decline code.
i don't know
then I'd read https://stripe.com/docs/declines/ in detail
Therefore, if the issuing bank refuses, it will return the decline code, otherwise it will return the error code?
However, when I was testing, I deliberately filled in the wrong verification code when performing 3ds, and then executed the Stripe.onPaymentResult() method. Later, I got the error code in the onSuccess() callback, and the decline code was a null value.
yep that is not a decline, so that seems normal
as in, failing 3D Secure is not a decline, it's a failed authentication
a decline can be tested using the test cards for it as I mentioned above
The decline code is returned because of the bank’s error, so doesn’t 3ds belong to the issuing bank?
it does, but it's a different concept basically. Declines are for a card 'authorisation' failing. 3D Secure is a separate layer called "authentication" and is different
Sorry, I still don't understand it very well. Is it true that the bank error returns the decline code, and the error code is returned due to stripe or network errors?
yes