#ninjaparade

1 messages · Page 1 of 1 (latest)

marsh lilyBOT
pine oyster
#

Hmmm, I'm not seeing anything on my end. Do you have some example charges?

visual rose
#

oh man do I ever

#

its insane

#

what would be the best way to share this?

#

just a charge_id?

pine oyster
#

Yeah, 3 or 4 charge IDs should suffice for now

visual rose
#

OK thanks

#

one second

pine oyster
#

When did this start? Is it ongoing?

visual rose
#

its been a while, we only caught it cause MMR Dropped like 50K

#

ch_3MjBC4KwzIfDusYv0TnAGdgP

#

this one, the customers card is valid until 2024/02, reports that its the wrong number now

#

in_1MjAF9KwzIfDusYvG1vrCz28 that's the invoice number of that helps

#

one thing I am curious about, is why a new payment intent was created? is that normal?

#

another charge ch_3Mldu6KwzIfDusYv1cPOD9LT

#

the card is valid until 2025

#

NSF sorry missed that

#

sorry use this

#

ch_3MldsmKwzIfDusYv0nfh9rcj

pine oyster
#

Digging now

visual rose
#

can you tell me if creating a new pi to charge an invoice when the card is defaulted on teh customer is a new thing? I dont think I've seen this before?

#

I think I found it

#

the cards aren't set up for off session use

pine oyster
visual rose
#

thats true but why would this fail then

pine oyster
#

That's what I'm digging into now

#

How many payments are failing roughly?

visual rose
#

dose this not look like the invoice is being paid by the default card and not being provided the pi as the source

#

dude hard to say its been a since the start of march but I can look now

#

btw that payment intent you linked was from 2022

#

this is the failed intent

#

would this not appear to be around how the original tonkenization of the card was done?

pine oyster
#

Looking at this with a colleague, will circle back with an update shortly

visual rose
#

❤️

pine oyster
#

Okay, so after looking at this, we aren't seeing anything specific on our end that we can easily diagnose. It could be an error on Stripe's end.

I'm going to grab see if I can get this escalated to some folks on our specialist team who will be able to dig into it with engineers that know that problem-space a bit better. Will circle back to confirm here shortly

visual rose
#

ok we had the same thing happen and they said it would be escalated but its been 24 hours

pine oyster
#

I understand. It's possible that it is already being worked on, but my extra bump will make sure you actually get a response from someone

visual rose
#

sorry I mean we spoke to support, they said it was sstrange and they were going to escalate

#

ok man but this is super super odd to me

pine oyster
#

yeah, it's strange for sure. It's might be that that person was issued a virtual card, then paid something and immediately disabled it afterward, though I'm not an expert in that side of things. You should be getting a response via email from someone here shortly

visual rose
#

okay great, one last thing to run past you

# 

Checkout Sessions no longer return the setup_intent property in subscription mode.```
#

could this be an API version? I know with other things on stripe subs that can't change after its created, but could the subscriptions be the issue now if they were made with an older version of the API and we're now using a newer version?

pine oyster
#

Possibly? It's hard to say at the moment. Even if that was the case, I don't think you should be getting the error "Your card number is incorrect."

visual rose
#

100% it seems like a very generic error rather than a real one, because the card is on file, its been used, so it should not be an incorrect number error, it should be something about the card being blocked no?

#

just grasping at straws tbh but it doesn't seem like its teh actual cause of it to me, its something else going on