#nickdnk
1 messages ยท Page 1 of 1 (latest)
For reference, I've had a call with Stripe about this a month ago
So just checking if this has been resolved before I override the session
I was told there was a JIRA about this
So you may be able to find it there
I'm fairly certain it still wouldn't work because I haven't heard anything, so I'm just checking
I also don't really understand why Stripe considers the document invalid. It looks fine to me and it's not expired.
Not sure why that design decision was made specifically but I found the JIRA. It's a bit out of my expertise so trying to understand what current progress is.
Alright. To elaborate: It's a compliance and/or privacy issue where IP restrictions are required to access PII of sessions created more than 48 hours ago. I cannot use IP-filter in my archtecture because it's difficult to set up static IPs, so if I go into the dash and override the session after 48 hours have passed, my API cannot access the information to create the verified profile on our end
In the meeting I had, I was told you would investiate options to extend the window by another 48 hours if the session is overridden from the dashboard
So it's basically just a check-in on how that's going
Because I'm blocked at the moment from issuing these verified profiles
I see. I am not seeing any recent changes on your account that would reflect that a special exemption was granted for the override.
I do see that there have been many conversations around how we can best support the usecase and so on..
I believe you chatted with our product team directly the last time, if you still have that email thread handy then I'd recommend following up there as they should be able to tell exactly how far/close we are on the resolution
I already did, I just wanted to check in here to see if I could get an immediate update because these problems are piling up. But I'll wait for their response!
Thanks
Yeah sorry, like I mentioned there are tons of details here and I don't want to mislead you when I don't have the full context from product perspective
It's fine, I get it. Just checking if there had been any changes.
Because if not I won't override it as it breaks our integration
And I can't un-override it ๐
(because at that stage it's already gone wrong I mean)
I think I will just have to reject them and contact the users and ask them to redo it free of charge
Def understand. Sorry for the friction ๐
I'll work around it ๐