Home/For partners
For business & platforms

Satisfy the filing. Shed the liability.

Federal law makes you collect the SSN. It never made you keep it. Embed Othentity and your platform holds a scoped token where the raw identifier used to sit — while we resolve and transmit to the IRS and SSA inside a layer you never touch.

Request a sandbox key See the architecture
Raw SSNs you store
Zero
Integration surface
One API
Agency channels
IRS · SSA
The swap, in one line. Replace your SSN field with the Othentity consent button. The customer authorizes once; you receive an opaque token like idv_a7f3…c21e and store that everywhere a Social Security Number used to live.
Before Othentity SSN in 4+ systems
After Othentity Token only
Who embeds Othentity

Built for any platform that has to collect a tax identifier.

If your product asks a worker, contractor, or customer for an SSN, ITIN, or EIN to file with an agency, Othentity drops into that exact moment.

Payroll platforms

File W-2s and quarterly returns by token. Your payroll DB never holds the worker's SSN again.

HR & onboarding

Replace the SSN step in new-hire onboarding with a single authorization the employee controls.

Contractor marketplaces

Collect 1099 authority for thousands of contractors without becoming the custodian of their identifiers.

Staffing agencies

Onboard temp and placement workers at volume, with consent and audit attached to every record.

Benefits administration

Verify identity for enrollment and file required returns without expanding your PII footprint.

Accounting software

Render filled W-2 / 1099 PDFs by token reference — no raw identifiers ever enter your codebase.

Gig & on-demand

Sign up earners in seconds with a tap-to-authorize flow, web, mobile, or NFC card.

Something else?

If you file information returns, we can fit. Tell us your flow →

Why platforms switch

Less to protect. Less to prove. Nothing lost.

Shrink your compliance scope. Holding tokens instead of SSNs pulls whole systems out of the sensitive-data boundary your auditors assess.
Collapse your breach blast radius. If a token leaks, the identifier stays sealed in the vault. There is nothing on your side to steal.
Keep filing exactly as before. W-2, 1099-series and quarterly returns still go to the IRS and SSA — Othentity resolves the protected fields at transmission time.
Tenant-isolated by design. Your data never crosses another business's domain. Every lane carries its own keys, sandbox, and audit trail.
What stays on your side
RemovedRaw SSN / ITIN / EIN in your database, backups, logs, and downstream vendors.
RemovedIndefinite retention risk — every extra year and system multiplied your exposure.
You keepA scoped token per person, safe to store anywhere across payroll, HR, and compliance.
You keepFull filing authority — plus a per-tenant audit log proving who acted and when.
How embedding works

Four moves from SSN field to sealed filing.

A high-level tour. The exact SDK calls, environments, and webhook events live in the developer guide.

01

Drop in the consent widget

Swap your SSN input for the “Authenticate with Othentity” button — one component from the SDK. Keep a manual fallback if you want one. The customer reviews a plain-language request: who, what for, and for how long.

02

Receive a scoped token

On approval we issue an opaque, scoped token bound to that authorization and hand it back through your webhook. Store it in place of the SSN across every system that referenced the identifier.

03

File by token reference

Submit a W-2, 1099, or batch of thousands against the token. The resolution engine — the only system that can map a token to identity — completes the protected fields and transmits via IRS MeF / FIRE and SSA.

04

Get the receipt, keep the audit

You get an agency acceptance receipt and a redacted document; the identifier never left the sealed layer. Every action lands on your tenant's append-only audit log, and the customer can see and revoke at any time.

Ready to wire it up? We're onboarding design partners now and will share the SDK, the sandbox & live environments, token lifecycle, bulk filing, and the webhook event catalog as we bring you online. Talk to us about integrating →

Agency transmission to the IRS and SSA is pending IRS authorized-transmitter certification (Form 8633). The sandbox uses simulated agency responses today.

The partner console

A full operations surface, not just an API.

Beyond the SDK, every tenant gets a console for the humans on your team — operators, risk analysts, engineers, and compliance.

People & lookup

Find a verified person by detail or phone token and act on their behalf — without an SSN on screen.

token-referenced

Filings & templates

File single or batch returns, or render filled PDFs from a template — all by token reference.

IRS MeF · FIRE · SSA

Roles & access

RBAC with teams and custom roles today, plus optional GitOps sync from your own repo. SSO (SAML 2.0) and SCIM provisioning are on the enterprise roadmap.

RBAC · OAuth/OIDC · SAML/SCIM (roadmap)

Audit & reporting

An append-only, per-tenant activity stream across every operator, system job, and GitOps change.

per-tenant · append-only
Open a live console demo
Plans

Start free in the sandbox. Pricing is set per partner.

We're pre-seed and onboarding our first design partners, so we price each engagement directly rather than publishing fixed tiers. The sandbox is always free; production volume and agency-channel terms are agreed with you.

Talk to us about pricing. Tell us your platform type and approximate annual filing volume, and we'll scope a plan and a sandbox key. Talk to us →
Questions partners ask

The practical stuff.

Yes — that's the whole point. You submit returns by token, our resolution engine completes the protected fields and transmits via IRS MeF / FIRE and SSA, and you receive the agency acceptance receipt. Othentity is completing IRS authorized-transmitter certification (Form 8633); until that's in place, filing runs in the sandbox with simulated agency responses.

An opaque, scoped token — for example idv_a7f3…c21e. It is meaningless outside Othentity, bound to a specific authorization and scope, and safe to store across your payroll, HR, and compliance systems in place of the identifier.

The consent widget is a single SDK component, and the sandbox is free with realistic fixtures and simulated agency responses. Most teams have the authorize-and-receive-token loop working in a day; production filing follows once channels are enabled on your tenant.

You can. The widget sits next to your existing field, so you can run both during migration and retire the manual path on your own timeline. Anything collected through Othentity is sealed in the vault from the first keystroke.

Completely. Every tenant gets isolated Sandbox and Live workspaces with their own keys, domains, and audit. Your data never crosses another business's boundary — see the architecture and security pages for the model.

Talk to us

Tell us where you collect a tax identifier today.

We'll map Othentity onto your exact flow and get you a sandbox key.

Please enter your name.
Enter a valid work email.
What company are you with?
This is an interactive demo — no data is submitted. By contacting us you agree to be reached about Othentity.

Thanks, there — we're on it.

A solutions engineer will reach out to scope your integration and provision a sandbox key. In the meantime, the architecture overview shows how the pieces fit.

See the architecture