#anilnepal1111
heady dust
elfin sequoia
Hi there, can you share with me the invoice ID?
serene dove
Here is the request log: req_Nx8rMVXKR89yAl
Or this intent: pi_3N5Lr9Bc1vngakCU1J4zRa9c
elfin sequoia
Thanks for the ID. This error code is what the card issuer choose to return to Stripe, you can ask the customer to update a new payment method, or contact their issuer.
serene dove
This is not the only one customer who is having this issue. There are a lot of them
Also this request: req_u5Ud9al5TMmNO6. The card was expired but was being charged till last week and stopped this week saying the customer entered invalid card number.
There are others too, if you would like to check them, I can provide other request logs as well.
elfin sequoia
Card decline is a common scenario that your integration should handle, you can refer to this page (https://stripe.com/docs/declines/codes) for the list of codes and learn how to handle them.
serene dove
Thank you Jack for the response. I have handled the declines both during token creation and charging a customer and tested and everything looks good.
Actually, the integration is not an issue here since the subscriptions are created using API integration. The issue is that a lot of our subscriptions are failing and if we speak to the customers they claim the card to be working everywhere else except for us.
elfin sequoia
This is really up to the card issuer and we don't have details on how they process the payments. It's possible that for the same card details, the issuer may approve in one payment, and decline in another.
serene dove
Thank you for that.
Also, if you may clarify, I have been seeing some of the error logs with error code "invalid_expiry_month/year" and a format like below:
{
"card": {
"number": "*********9072",
"exp_month": "32",
"cvc": "",
"exp_year": "2002"
}
}
Most of them have "exp_month" to be 32, 52, 62, 82 and "exp_year" to be 2002.
Is it due to card decline while attaching the source to the customer?
elfin sequoia
The given expiry_month/year is not invalid, and that's why you get the error.
serene dove
Well, that is something weird since there is not just one transaction with such exp_month/exp_year. There are more of them. Something to doubt of is not everyone would enter expiry year 2002 or expiry month ending with 2 as mentioned above.
elfin sequoia
Can you send me one of the these request IDs?
serene dove
Yes please. Here are some of those requests: req_EaV8BaYI2WSaAz, req_dW3YN9kNgVq8O3, req_WastiVBhfWt20D
elfin sequoia
Ok, looks like you are collecting the card details from user directly and use the details to create a token?
serene dove
Yes
elfin sequoia
Are the card details entered by your customer?
serene dove
Yes.., they checkout using custom checkout from the website
elfin sequoia
OK. Since the card details provided by the customer is invalid, this is a human error and not something your application can prevend.
serene dove
Okay sounds good, since every such response body look the same, thought the error could be getting triggered by something else.
elfin sequoia
Are you asking your customer to enter card details for every renewing payment?
serene dove
If the users are logged in, I am showing them the default card, if any, from Stripe and checking out through that. Else, they are entering card during checkout
serene dove
Are you asking your customer to enter card details for every renewing payment?
For subscriptions, the customers don't enter card details for each recurring payment
Stripe is handling the recurring payments for subscriptions and we are only creating the subscription from our end
elfin sequoia
OK. This flow looks good to me.
serene dove
The only concern with us these days is the increasing failed invoices due to the card decline issue
Also, there is one customer: cus_JlTnfQjXuA8zgl who has an existing subscription but the card has expired on January but was being charged upon till last Friday.
elfin sequoia
Again it's really up to the card issuer, it's possible that the payment can be successful despite the card expiration.