Account sessions launch merchant-facing embedded provider components after onboarding is complete. Creating a session returns short-lived credentials for the requested component, along with a structured summary of the merchant's outstanding verification requirements: what is currently due, what becomes due later, and any deadline.
Use this when a merchant needs to update business details, view payouts or balances, manage documents, or review a provider notification without leaving your product. The public session_kind values are allowlisted to account_management, payouts, balances, documents, and notification_banner. Sessions expire quickly by design; create a fresh one each time you render the surface rather than storing credentials.
For the initial verification flow, use the onboarding API instead. Account sessions require an existing processor account and are for keeping an already-onboarded merchant in good standing. See the API and agent onboarding guide.