User and Administrator Interfaces

Bansoft provides separate browser-based interfaces for customers and authorized administrators, with menus and permissions configured according to the institution's operating model.

Two interfaces, one configured environment

The user interface supports customer-facing account activity, while the administrator interface supports operations, review, configuration, and oversight.

Client and user interface

Accounts, transfers, reports, and profile access

  • View accounts, balances, and transaction history
  • Use enabled transfer and wire workflows
  • Read system and administrator messages
  • Generate statements and account reports
  • View or update permitted profile fields and upload documents where enabled
Back office and administrator interface

Requests, profiles, accounts, transactions, and settings

  • Review transfer, registration, and document requests
  • Create and manage user and administrator profiles
  • Create, modify, activate, block, or inactivate accounts
  • Process manual transactions and operational workflows
  • Generate reports, review logs, and configure system behavior

Role-based administration

The Master Administrator can define administrator classes and assign permissions and profile-group access. This supports delegation without giving every administrator the same system access.

Request workflows

Configured transactions, registrations, and document submissions can be processed automatically or routed to pending queues for administrator review.

Contextual help

Interface Overlay Help can provide page-specific guidance without requiring the user or administrator to leave the current workflow.

Administrator configuration areas

Settings determine how the institution's environment behaves.

Profiles and roles

Profile groups, administrator classes, permissions, registration fields, and user-status rules.

Accounts and fees

Account types, currencies, transfer fees, optional card-account settings, and wire instructions.

Regional and interface settings

Language, date and number formats, time offsets, logos, interface colors, and system emails.

Security settings

Password policies, MFA, device authentication, IP controls, session behavior, and transaction verification.

Workflow settings

Pending-request behavior, approval requirements, automated processing, and transaction options.

Integrations

Enabled modules, API access, notification providers, and approved third-party connections by scope.

Demo boundary

Shared demonstrations use test data only

Shared demo environments should not be used for personal, confidential, regulated, or production data. A customized environment can be discussed when a more specific evaluation is required.

Configuration boundary

Visible menus depend on enabled scope

Modules, transfer types, reports, documents, card functions, portfolios, and integrations may appear only when included and activated in the institution's deployment.