#cisox-expiry-element

1 messages · Page 1 of 1 (latest)

opaque crown
#

HI there 👋 I don't believe I've heard of this happening before, do you have IDs from associated objects (such as the Payment/Setup Intent ID) that we could take a closer look at?

fresh flax
#

Yep, sure do. One sec

#

I have the request log itself if that's what you're looking for. It includes the customer update request for source with both the customer id and token.

rotund mantle
#

sure that's what we'd need

fresh flax
#

We think it was an issue with the expiration date but if you can tell anything else from that request that would have caused the issue vs us updating it directly in Stripe, that would be helpful

rotund mantle
#

They entered a future expiration date as expected, we got it, just here the bank says "I am sorry but this card is expired and I can't let you use it" usually because they lost the card and got it renewed

#

So this is just a "normal" decline and they need to talk to their bank

fresh flax
#

They talked to their bank which indicated no issue on their end. It eventually worked when we entered it directly into Stripe. Was that just a timing thing then?

rotund mantle
#

Likely!

fresh flax
#

I believe our support person who handled this case tried entering the info into our normal UI and when that failed tried Stripe. I'll let him know it may have been a timing issue.

rotund mantle
#

banks sometimes are just finicky, when you add it in the Dashboard it uses "MOTO" and so the banks validate this differently

#

but it's really not an API bug or anything, just the bank sometimes saying no and other times yes with the same data