Customizing and localizing the UI
You can customize the text and style of the user interface for multiple platforms without writing any code. Edit a cross-platform JSON UI configuration file to replace strings and images, specify colors and choose friendly names for authenticators. See App UI Customization for details.
Your application can include localized versions of the JSON UI Configuration file. The App SDK applies the UI Configuration file that corresponds to the system's local language and region.
Replacing the UI
The DigipassONE App SDK makes it easy to completely replace customer-facing screens. Please refer to Replace the UI for iOS, Android, and Web.
Changing the layout
If you don't want to build your own UI but you need to modify the color or the placement of UI elements, you can choose to modify just the layout of each screen in an Android app. If you choose this option, please be aware that you might need to modify your code when DigipassONE makes improvements to its default UI in future releases. Please refer to the following pages for more details.
Integrating with existing proxy servers
For the majority of customers, the DigipassONE standard architecture works seamlessly with their infrastructure. Some customers have business requirements revolving around security or company standards which call for modifications to the architecture which are described below. If you feel your company may need these changes, contact OneSpan customer support.
If your company needs to filter incoming traffic to satisfy internal security requirements before it reaches the DigipassONE API Server, you can implement a thin proxy in front of the API Server. In addition, you need to create a plugin, or REST Client, for the DigipassONE App SDK. Your REST client replaces the App SDK's default REST client. Your REST Client serves as the conduit between the DigipassONE App SDK and your thin proxy. It makes sure that requests from the App SDK are sent in a form your thin proxy can process. Likewise it takes the responses from your thin proxy and returns them in a form that the App SDK expects.
.png?sv=2026-02-06&spr=https&st=2026-10-01T06%3A34%3A35Z&se=2026-10-01T06%3A46%3A35Z&sr=c&sp=r&sig=tl98%2FPrcJsyp644i8EWe49DwyhSWjqjt2dLtcqVh1Xs%3D)
Figure 11 Thin proxy in front of the DigipassONE API server
Please refer to the followingdocumentation for more information:
Reference to the REST API: To understand the scope of the REST API implemented by DigipassONE and used by the API Server.
Web app developer guide: Describes how to implement, modify, and integrate web applications.