#unknown-user
1 messages ยท Page 1 of 1 (latest)
I can supply invoice ids if that would be interesting.
in_0LkUwpo2ZNzxqgUA3IY7cAo3
in_0LkUx0o2ZNzxqgUAHATTwUs7
Thanks, let me take a look
hrm, looking around it looks like it may have happened again for
in_0LkUs4o2ZNzxqgUAShWUSCjJ
in_0LkUrso2ZNzxqgUASdSI4Aiv
Hi there ๐ taking over for @silk gyro
Give me a few minutes to get caught up.
This looks like the refund for the second set
in_0LkUsQo2ZNzxqgUAYU8WE2Pw
How long have these been happening? Was it just today?
I think we've got three reports of it, and all within our sandbox while doing some QA testing. I believe that all were within a fairly short timeframe.
I don't know of a mechanism within our codebase that would trigger the refunds that seem to have happened - which is what led me to be suspicious that perhaps some Stripe queue somewhere had a hiccup and corrected itself.
It looks like there was an glitch that caused the Invoice Payment Page to not load properly earlier today from 0706 - 1708 UTC, so I believe it was that as the times fit
Ok, that's good news. So I'm going to close this out for the time being as being a Stripe glitch. Does that sounds correct to you?
I would say go ahead and close it out as a Stripe-side error in this case