Skip to main content

Advanced Implementation

This hub covers optional work you can add on top of the core flow in Implementation. Use it when you want stronger branding, a smoother onboarding path, multi-user business banking, custom identity, richer automation (webhooks and APIs), or a unified onboarding story with payment processors.

You can adopt topics in any order; most teams start with theming and JWT (if you are not using the default token path), then add pre-fill, team access, or webhooks as product needs grow.

Managed Banking experience

Optional by design

Nothing here is required to ship Managed Banking. Several features need Unit-side configuration (for example pre-fill or team-list endpoints, webhook subscriptions, or API tokens). When a page says to contact Unit, plan for that in your rollout.

Typical starting points
  • Theming — align the Managed Solution component with your brand.
  • Custom JWT Authentication — if your customers sign in with your own identity system and you give Unit the public keys to verify those tokens.
  • Implementation — core embed and setup if you have not finished it yet.

In this section​

TopicWhat it’s forEffort (guide)
ThemingColors, logos, fonts, and settings-json for the Managed Solution component—
Pre-filling User InformationLet Unit pre-fill the application from your API1–2 days
Custom JWT AuthenticationRS256 JWTs and public key / JWKS validation3–4 hours
Embedded Application FormOptional add-on — embed onboarding-only flow during registration with unit-elements-application-form~30 minutes
Standalone UI ComponentsOptional add-on — surface Activity and Balance Summary on dashboards and other surfaces in your product~30 minutes
Handling End-User EventsListen for application form lifecycle events—
Unified OnboardingSingle flow across Managed Banking and payment processors2–3 hours
Webhook EventsReal-time notifications for Banking activity2–3 hours
CardsCo-branded Visa debit cards, card design, and Apple Pay / Google PayVaries
API ReferenceBanking HTTP APIs (accounts, transactions, payments, payment intents, etc.)—
Multiple AccountsPartner-configured default accounts on approval, or customer-created accounts in the UIVaries
Multi-User AccessBusiness team roles, invites, and partner user-list API1–2 days
Unit Dashboard AccessDashboard URLs, capabilities, user roles, and operational account—

For customer-facing emails and notifications, see Customer Outreach.