Every detail matters when you’re building payroll into your product - especially when it comes to reducing friction, supporting migrations, and giving developers the tools they need to move fast. This month, we’re releasing updates that help teams onboard more flexibly, simplify transitions from previous providers, and gain more control over how Salsa components are integrated.
Let’s take a look at what’s new.
Fine-grained components for employer onboarding
We’ve broken out our employer onboarding flow into a set of fine-grained, embeddable UI components. Previously only available as a single, full workflow, these components are now exposed individually - giving developers the ability to build custom, step-by-step onboarding flows that fit their platform’s UX.
The available components include:
- employer-address-list
- employer-bank-accounts
- employer-onboard-workers
- employer-pay-groups
- employer-sign-documents
- employer-taxes-setup
- employer-setup-personalization
[.c-highlighted]This update gives partners greater flexibility - whether they want to fully customize the experience, integrate Salsa alongside existing workflows, or only embed the steps they need. It also reduces the need for workarounds or full custom builds, helping teams move faster - and more consistently - while still relying on Salsa’s logic and compliance infrastructure.[.c-highlighted]
Improved previous payroll history collection flow
We’ve updated the flow for helping employers migrate from a previous payroll provider. Employers can now more easily discover instructions for retrieving historical payroll data - or choose to provide concierge access by customizing the email address used to request it.
[.c-highlighted]This update makes it easier for employers to access the instructions and tools they need to provide historical payroll data during migration. Whether they’re retrieving reports or granting concierge access to their previous provider, the updated flow reduces confusion and enables employers to complete this step with fewer support touchpoints - even outside typical working hours.[.c-highlighted]
Salsa-js now available via NPM
For teams that prefer package-based workflows, the salsa-js SDK is now available as an NPM package. The original script tag integration remains fully supported - this just adds another way to install Salsa, depending on your development preferences or CI/CD setup.
[.c-highlighted]NPM support allows for more predictable dependency management, tighter alignment with internal security policies, and greater flexibility to development workflows, all without changing how the SDK behaves.[.c-highlighted]
Smoother token refresh in salsa-js
We’ve introduced a new method, replaceUserToken, to simplify how teams manage user token refreshes in embedded components. Rather than reloading or reinitializing a component, developers can now update the token in place.
[.c-highlighted]This is particularly helpful for teams using shorter token lifecycles as part of their security practices. The update happens seamlessly - no interruptions, no reloads, just a smoother user experience.[.c-highlighted]
Looking ahead
From onboarding modularity to improved migration support and developer flexibility, we’re making it easier to embed payroll infrastructure into any product - faster, with fewer tradeoffs, and more control at every step.
Stay ahead with these updates designed to streamline payroll operations and improve the employer experience.
