#okays-invoice
1 messages ยท Page 1 of 1 (latest)
Thank you in advance!
Hey, taking over here!
However the event data shows that it was paid in 2019, but the finalized_at date for the invoice was last week
What makes you think it was paid in 2019?
This is the associated Payment Intent for the Invoice (in_1EDhqPFgJ7FCi1F2elOdim1o): https://dashboard.stripe.com/payments/pi_1EDhqPFgJ7FCi1F20jFzeOja
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
As you can see, payment only succeeded on 7/8/22
When the Invoice is generated, an associated Payment Intent is also created to facilitate payment. That's not indicative of an actual payment though (a PI is a state machine to track status of payment attempts)
In this case, the disparity in dates is because the Invoice was never marked void. This means it can in theory be paid at any point by the customer
Hi! I must have misread - I'd swapped finalized_at and paid_at
Are you saying that the customer has manually found the old invoice and paid it?
(is there a way to check that)
Also - the payment ID associated with the webhook is pi_1EDhqPFgJ7FCi1F20jFzeOja - the dashboard is saying that the payment succeeded on March 14 2019
Yep
Where does it say that? I just showed you the same Payment Intent where it says otherwise
Check the paid_at field on the Invoice, too: 2022-07-07 21:30:24
If you want an invoice to become terminal (and cannot be paid), you need to void it: https://stripe.com/docs/invoicing/overview#void
Otherwise if the user still has the link for the HIP (via an email), then they'll be able to make payment
Ah, here. Yeah this is wrong (and not sure why)
Let me double check on this
Actually, I think you're right. Looks like it was paid back in 2019
And I have no idea why the events are only just being created and send now ~3 years later
Is it just on this invoice, or are there other examples?
My only guess is that the invoice reconciliation didn't fire initially (i.e. marking it as paid), but no idea why its just happened now
Yeah looks like there was some inconsistent data between invoices/payments that was never reconciled, so we ran a job to fix that state
This is the only case of it happening. I only caught it because of my badly programmed application haha
I'd deleted customer data when they cancelled subscriptions so when the payment came in it alerted me it couldn't find a relevant subscription.
So I can safely ignore this webhook, right?
Yes, its safe to disregard
Great, thanks for your help
np! sorry for the time travelling webhook event
โ๏ธ
sorry for the time travelling webhook event
we could always blame it on Marvel/DC heroes/villains messing with space-time continuum ๐