Hi everyone,
We're using OneAll's social login widget for user authentication on a B2B platform, and we also collect business registration info (tax ID, company name) during the signup flow for business accounts.
Right now we're just storing whatever the user types without any validation against an external registry. This obviously isn't ideal — we've had a few signups with clearly fake or mismatched business data.
Has anyone integrated a secondary verification step after OneAll's social login completes, where you cross-check the submitted business name or tax ID against a government or third-party registry API before fully activating the account?
For context on what I mean by this kind of lookup, here's an example of a public business-name verification tool for a specific country (Peru) that shows the kind of data fields I'd want to cross-reference — company name, tax status, registration condition, etc: esta página
Curious if anyone's built something similar on top of OneAll's auth flow, or if there's a recommended pattern for chaining a verification API call right after the OAuth callback. Would appreciate any pointers on architecture or gotchas before we build this ourselves.
Thanks!
Please sign in to your OneAll account to ask a new question or to contribute to the discussions.
Please click on the link below to connect to the forum with your OneAll account.