Payroll Rollout Detail
A direct-deposit and wallet-adoption view for employee opt-in, linked payout rails, payroll timing, and wallet-access boundaries.
The payroll detail should open on the real program state instead of a generic enablement badge.
Wallet adoption should stay measurable from the same detail lane that owns the rollout.
Finance and operations should both see the next funding window without jumping into another tool.
Program health is easiest to explain when adoption and payout readiness stay in the same lane.
That gives payroll and operations one shared view into how the program is landing without hiding the employee choice model that keeps the wallet optional.
That separation keeps payroll convenience from blurring the recovery boundary or the user's control over wallet-sensitive actions.
Operators should also be able to jump from the payroll rollout into employee access and company-market rollout so the three workforce lanes stay connected.
{
"program_id": "northstar_direct_deposit_rollout",
"employee_opt_in_rate": "38%",
"wallet_setup_complete": 312,
"linked_payout_rails": 208,
"next_payroll_window": "2026-03-15T09:00:00Z",
"employer_program_state": "active"
}Payroll rollout detail should combine adoption, wallet readiness, and payout-rail coverage without crossing the wallet recovery boundary.
The payroll detail should show how far adoption has moved inside the active cohort.
Wallet readiness belongs on the same screen as payroll enablement.
Payout-rail readiness should stay visible before the next payroll window opens.
Wallet-sensitive access remains on-device even when payroll funding is enabled.
The Continuity Key remains the recovery boundary for new-device or lost wallet-sensitive access.
Support can point to the policy but cannot recover the key or unlock the wallet for the user.
The program is open to the full organization cohort tied to the current rollout.
Enrollment is moving, but still trails the broader employee approval pace.
Most enrolled users already have a withdrawal or payout path configured.
The latest direct-deposit enrollments were written into the program summary and finance lane.
The next payroll-linked funding event is already scheduled and visible to operations.
The latest employee cohort acknowledged the Continuity Key and local wallet boundary during setup.
A payroll rollout detail page should show how many employees have opted into direct deposit, how many still need wallet setup, and which teams are driving adoption fastest.
That gives payroll and operations one shared view into how the program is landing without hiding the employee choice model that keeps the wallet optional.
Even when payroll funds can land in the Commitment Wallet, the wallet still follows its own local-password, biometric, and Continuity Key rules. Payroll enrollment should never be mistaken for employer-owned wallet access.
That separation keeps payroll convenience from blurring the recovery boundary or the user's control over wallet-sensitive actions.
The payroll detail should show direct-deposit timing, linked payout rails, funding adoption, and the employer program line items in one place. Finance teams need to see what is payroll, what is platform fee, and what belongs to the employer agreement without cross-referencing multiple tools.
Operators should also be able to jump from the payroll rollout into employee access and company-market rollout so the three workforce lanes stay connected.