/
Contact usSee pricingStart building
Node
​

    About Stytch

    Introduction
    Integration Approaches
      Full-stack overview
      Frontend (pre-built UI)
      Frontend (headless)
      Backend
    Migrations
      Migration overview
      Migrating users statically
      Migrating users dynamically
      Additional migration considerations
      Zero-downtime deployment
      Defining external IDs for users
      Exporting from Stytch
    Custom Domains
      Overview

    Authentication

    DFP Protected Auth
      Overview
      Setting up DFP Protected Auth
      Handling challenges
    Magic Links
    • Email Magic Links

      • Getting started with the API
        Getting started with the SDK
        Replacing your password reset flow
        Building an invite user flow
        Add magic links to an existing auth flow
        Adding PKCE to a Magic Link flow
        Magic Link redirect routing
    • Embeddable Magic Links

      • Getting started with the API
    MFA
      Overview
      Backend integration
      Frontend integration
    Mobile Biometrics
      Overview
    M2M Authentication
      Authenticate an M2M Client
      Rotate client secrets
      Import M2M Clients from Auth0
    OAuth
    • Identity providers

      • Overview
        Provider setup
      Getting started with the API (Google)
      Add Google One Tap via the SDK
      Email address behavior
      Adding PKCE to an OAuth flow
    Connected AppsBeta
      Setting up Connected Apps
      About Remote MCP Servers
    • Resources

      • Integrate with AI agents
        Integrate with MCP servers
        Integrate with CLI Apps
    Passcodes
      Getting started with the API
      Getting started with the SDK
    • Toll fraud

      • What is SMS toll fraud?
        How you can prevent toll fraud
      Unsupported countries
    Passkeys & WebAuthn
    • Passkeys

      • Passkeys overview
        Set up Passkeys with the frontend SDK
    • WebAuthn

      • Getting started with the API
        Getting started with the SDK
    Passwords
      Getting started with the API
      Getting started with the SDK
      Password strength policy
    • Email verification

      • Overview
        Email verification before password creation
        Email verification after password creation
    Sessions
      How to use sessions
      Backend integrations
      Frontend integrations
      Custom claims
      Custom claim templates
      Session tokens vs JWTs
      How to use Stytch JWTs
    TOTP
      Getting started with the API
      Getting started with the SDK
    Web3
      Getting started with the API
      Getting started with the SDK

    Authorization

    Implement RBAC with metadata

    3rd Party Integrations

    Planetscale
    Supabase
    Feathery
    Unit

    Testing

    E2E testing
    Sandbox values
Get support on SlackVisit our developer forum

Contact us

Consumer Authentication

/

Guides

/

3rd Party Integrations

/

Unit

Stytch and Unit

Stytch and Unit

With Unit as a banking provider in your app, you'll be required to use the customer token mechanism for certain card related user actions. Creating a customer token requires the end user to complete a two factor authentication. If you are using Stytch as your authentication provider, you will be able to complete this two factor authentication challenge via Stytch, and pass the Stytch JWT into Unit's API.

In this guide you will configure Stytch JWT information in your Unit application and pass Stytch JWTs to Unit to prove user authentication.

Check out the Stytch integration information in the Unit documentation.

Key setup

Step 1: Configure your Stytch JWKs path on the Unit dashboard

In the Unit dashboard, under Org Settings > JWT Settings, ensure that "Stytch" is selected under Provider, and add your Stytch JWKs URL to the JWKs Path field:

https://[live|test].stytch.com/v1/sessions/jwks/<project-id>

Your project ID can be found in the Stytch Dashboard under API Keys. You should use the Test environment for any pre-production integration and testing.

Integrate Stytch authentication into your Unit flows

Step 2: Include jwtSubject in your Unit Applications

When you create an Application for a new user in Unit, the Application object must include the Stytch user_id in the jwtSubject field.

Key actions:

  1. Sign up user via a Stytch API or SDK flow - here's an example of how to get started with a sign up flow using email magic links.
  2. Recieve Stytch user_id from session or API response.
  3. Pass Stytch user_id into the user Application via Unit's APIs, using one of these options:
  • ApplicationFormPrefill
  • Application creation
  • Patch Customer

Step 3: Create a customer token on a card related action

See Unit's docs for this step here.

Key actions:

  1. Step up user with a second factor of authentication using a Stytch API or SDK flow - here's an example of how to get started with 2FA using Authenticator App.
  2. Upon successful 2FA, pass the returned/cached Stytch JWT into the Unit customers/token API (as seen in Unit's docs linked above).
  3. The Unit API will return a customerBearerToken that can then be used to perform sensitive Unit actions.

Questions?

You just finished all the critical components to integrate your Stytch authentication with Unit's banking APIs. Have any feedback or questions? Get in touch with us in our developer forum, support@stytch.com, or in our community Slack.

Key setup

Step 1: Configure your Stytch JWKs path on the Unit dashboard

Integrate Stytch authentication into your Unit flows

Step 2: Include jwtSubject in your Unit Applications

Step 3: Create a customer token on a card related action

Questions?