--- title: "Post-activation: device binding with standard licenses" slug: "mas-5-pg-post-activation-device-binding-with-sdl-5-5-0" updated: 2025-11-07T11:37:38Z published: 2025-11-25T13:41:47Z canonical: "docs.onespan.com/mas-5-pg-post-activation-device-binding-with-sdl-5-5-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Post-activation: device binding with standard licenses Once Mobile Authenticator Studio has been activated locally, the server must receive the information to ensure that both parties are synchronized. Device binding is an enhancement of the regular server activation process and is a Mobile Authenticator Studio post-activation process. ## Post-activation process The post-activation process starts right after Mobile Authenticator Studio has been activated on the device. It is enabled in the post-activation section of the application’s configuration file. It serves, amongst other purposes, to synchronize the server and the device. ## Device binding The post-activation process can also be used for device binding, where the authenticator on a device is bound to its BLOB on the server by injecting the device seed in the authenticator's BLOB. Because this seed is used by the Mobile Authenticator Studio app to generate responses, only the authenticator installed on the bound device will generate valid responses. The user can start the device binding process in the Manage accounts screen of the Mobile Authenticator Studio app. For more information on this, see [Managing authenticator accounts: Device Binding](/mobile/docs/mas-5-pg-manage-authenticator-accounts-5-5-0#device-binding).