#mnguyen-issuing-authorization
1 messages · Page 1 of 1 (latest)
Even if there are not Issuing specific breaking changes, your SDK is likely pinned to your previous default API version
DId you make a corresponding upgrade to your SDK and modify your webhook endpoint API version?
or, conversely, keep the the endpoint locked ot the old version to maintain your current SDK version?
correct. we upgraded the sdk first. and then migrated webhooks to new api and then flipped the switch to the platform account to match.
I'm inferring that you're having issues with the auth request webhooks, since you didnt share specific about how these issues are arising
not so much the auth request webhook since those events are coming in properly and we are respondig properly, it's the subsequent workflows that happen in stripe that seem to be different and not happening as before.
after we give the ok on the auth request, we are expecting issuing_authorizatio.updated event and subsequent issuing_transaction.created event which are not happening anymore
both we confirmed we are listening for
Can you share some specific example authorization IDs?
mnguyen-issuing-authorization
here's one evt_1O7jq0PDVDJTnrXClPPrJTQi
sorry that was event id. here's the auth id
iauth_1O7JEXPJDAKxiTtzYf7c8vxl
@sweet orbit do you have an example of the other behaviour so that I can compare?
so after the auth request comes in, we reply back with 200 ok response, which would then generate an issuing_authorization.updated event followed by an issuing_transaction.created event. I can give you an eventid prior to upgrading if that provides any useful info
I don't think API versions would have anything to do with this right now.
What I want is to see a real Issuing Authorization with the behaviour you expect so that I can compare the two
any insight to what happens to the platform account if you do bump up the api version?
I'm really sorry, I don't get what that sentence could mean on its own
ok, one sec let me pull an auth request from yesterday that works properly
iauth_1O6ylaPNj1GxER9h3fEvbMAT
Okay so when I look at that one, the issuing_authorization.updated Event happened more than 24 hours later.
Is it possible you're being confused and mixing things up here?
Like my understanding is that you get issuing_authorization.request for you to approve/decline an Issuing Authorization. If you approve you then get issuing_authorization.created to reflect it's created as pending, and later, something will trigger the Issuing Transaction (that something can be many things like payment settlement, partial capture, etc.) right?
hmm, interesting, don't know if we ever paid attention to when it clears. let me double check some old ones to see how far apart they normally happen.
ok, looking at our history of records, it does reflect a day before the trasnaaction gets generated. we do see those events starting to come in for ones done from yesterday so it seems like all is in order. will continue to monitor. thanks for the troubleshooting possbilities.