#jkas-source-status
1 messages · Page 1 of 1 (latest)
Hello 👋
Just so that I am on the same page, Are you asking about the legacy sources API? If so, the source object status should be able to reflect its current status
https://stripe.com/docs/api/sources/object#source_object-status
We have to use sources because Stripe hasn't moved ApplePay and GooglePay over to methods yet.
It's not really legacy since it's our only option.
Anyway
I'm looking at source events, including the deleting of one, and the status doesn't ever change.
The new PaymentMethods API does support ApplePay/Google Pay
Can you look at the Events with me for src_1CbclDEkTO8kaKcKe3p9vB11?
Can you share the event ID you're looking at?
That's the source ID
This will give you a better idea of what I'm talking about
It's all the events I want to discuss
Ok, here's one: evt_1MjAYpEkTO8kaKcKfqulMr9L
It's a customer.source.deleted event
But the payload shows this:
Shouldn't the status or usage change?
afaik, yeah the status should change to consumed
The API ref seems to suggest the same.
https://stripe.com/docs/api/sources/detach
Taking a look now..
Right, so I'm wondering why we're not seeing that happen.
We're ending up with lots of errors attempting to use consumed sources.
Hmm feels like a bug, asking a colleague to take a look too in case I missed something..
If I retrieve the source now, I can see that it's marked as consumed. So I guess we might have to make an additional request to Stripe to confirm it's status, rather than relying on the event payload.
Yeah that should be a valid workaround for now..
Ok, thanks for your help!
NP! Happy to help