Onboarding

New user signs up.
Everything's already connected.

Your product needs users to set up other systems before it can do its job. Deck handles that setup: inside payroll, inside the carrier portal, inside whatever your product depends on. Day one looks like day thirty.

Connect portals
Link external accounts
ADP ADP Payroll
UnitedHealthcare UnitedHealthcare Benefits
IRS IRS Tax withholding
Setup actions
ADP · UnitedHealthcare · IRS
Set up direct deposit
Enroll in benefits plan
Update tax withholding
Enable notifications
Setting up…
Configuring external portals
Portals connected 3 logged in
Setup completed 4 actions
Changes confirmed Verified
Account activated Complete

Built for automated onboarding

Your users shouldn’t have to configure external systems before your product works. Deck logs into those portals and completes setup on their behalf.

ADP
Gusto
UnitedHealthcare
IRS
Experian
SSA
Anthem
Con Edison
T-Mobile
Payroll, benefits, government portals, and more

No portal API required

Most external systems don’t have APIs for onboarding actions. Payroll platforms, benefits portals, government sites. Deck operates them through the browser, the same way a person would.

User links source account Via your app · Auth Component or API
Credentials stored Encrypted in Deck Vault · AES-256
MFA handled automatically OTP · SMS · Passkey · CAPTCHA
Session established Authenticated, ready to configure

Authentication built in

Your user links their accounts through your app. Deck stores the credentials, handles MFA, and establishes authenticated sessions so it can complete setup inside each portal.

POST /tasks/v1/onboarding/run
200 OK
{
  "setup_status": "complete",
  "actions_completed": 3,
  "portals": ["adp", "uhc", "irs"],
  "status": "activated"
}

Setup complete, instant confirmation

Every setup returns structured confirmation. Portals configured, actions completed, status verified. Your user is ready to go from the moment they sign up.

Connect. Setup. Confirm.

Store your user’s portal credentials, trigger the setup, and get confirmation when it’s done.

POST /v2/credentials
{
  "auth_method": "username_password",
  "auth_credentials": {
    "username": "[email protected]",
    "password": "••••••••"
  },
  "source_id": "src_adp",
  "external_id": "user_123"
}

Store portal credentials

Your user provides their login for the external portal through your app. Store it in Deck Vault via the API. Keep it for ongoing access or delete after setup.

POST /v2/tasks/task_id/run
{
  "credential_id": "cred_a1b2...",
  "input": {
    "action": "complete_setup",
    "setup_tasks": ["direct_deposit", "benefits_enroll", "w4_update"]
  }
}

Run the setup

One API call triggers setup. Deck agents log into the external portals, complete the configuration, and confirm every action succeeded.

task_run.completed
{
  "status": "completed",
  "setup_status": "complete",
  "actions_completed": 3,
  "portals": [
    { "name": "ADP", "status": "configured" },
    { "name": "UHC", "status": "configured" }
  ],
  "runtime_ms": 12400
}

Get setup confirmation

Results arrive as structured JSON. Every portal configured, every action confirmed. Ready for your user to start using your product.

Who’s this for?

Rewards & loyalty

User links their rent or payment portal. Deck activates the rewards program, updates the payment method, and your product works from day one.

Payroll & HR platforms

Deck connects to carrier and benefits portals to complete enrollment on behalf of the user. Direct deposit, benefits selection, tax withholding — all done at signup.

Property tech

User links their city or utility portal. Deck completes tax setup, payment configuration, or account transfers so your product works from day one.

Vertical SaaS

Any product that depends on external system configuration during onboarding. Deck handles the setup so your users don’t have to.

FAQ

Payroll systems, benefits portals, government sites, utility providers, carrier portals, and more. Most of these don’t have APIs for onboarding actions. Deck operates them through the browser.

Yes. Deck handles OTP, SMS codes, passkeys, and CAPTCHAs automatically. Your user authenticates once through your app, and Deck manages the session from there.

Deck agents adapt to UI changes. They operate the portal the same way a person would, so minor layout changes don’t break the flow. We monitor portal health and update agents proactively.

Every action is confirmed individually. If a step fails, Deck reports exactly what succeeded and what didn’t, so you can retry or surface the issue to the user.

Minimally. Deck plugs into your existing signup flow. You keep control of the UX. Deck handles the portal configuration behind it.

Setup time depends on the number of portals and actions involved. Most configurations complete in seconds. Multiple portals are accessed in parallel.