Settings in the Hyper Client Application
Depending on your authorization level, use Hyper (client app) to control website headers, email content, and other global configurations."Server Side Settings" is the primary step when performing the initial installation of the Web-App module.
Web-App General Settings
The fields defined here affect the behavior of all active Web Applications.Fields prefixed with "Website" specifically impact Web Applications operating in "Web Portal" mode.
| Field Name | Description |
|---|---|
| Default Agency | Defines the default branch used to "plug holes" (provide missing data) in any operation lacking a direct link to an entity or branch. This includes setting the local time zone for the system clock. |
| Default Translation Language |
Since the Agency does not define a language, this field sets the global default until a specific preference is
detected from source documents or client/supplier records.
OR until a specific language is selected by the user (in HTML mode). |
| Default Public Email Address |
The primary outgoing address selected from Hyper's Public Mailboxes. This address is exclusively used for
security alerts, verification messages, and system notifications.
For official client declarations or source documents, a branch-specific email setting will override this field. |
| Sandbox Email to |
Sandbox mode is intended for initial implementation, testing phases, or development databases.
Entering a developer's private email here acts as a strict block, preventing any outgoing mail from reaching the outside world. Instead, all correspondence is redirected to the specified address for template testing and debugging. |
| Sandbox SMS to | Similar to the email sandbox, this redirects all outgoing text messages (including WhatsApp calls/messages) to a single mobile number assigned to the system integrator. |
| PDF Encryption |
Defines the logic for password-protecting automated PDF exports (e.g., client activity reports):
|
| Website English Title |
The global HTML title for pages generated by the Web-App, unless overridden by a specific software module.
Typically, this should contain the organization name or primary brand in English. |
| Website Account Verification |
Specifies the verification method for new client registrations via the Web Portal.
|
| Website Login System |
Defines the identification requirements for clients, as detailed on the Login Page.
|
| Website Login OTP |
Defines the One-Time Password (OTP) method enforced during login. This field supports multiple item selection:
|
| Website Registration Steps |
Configures the workflow for the standard onboarding site. This field supports multiple item selection:
|
| Accept Client Age above # years | Enables age-based restrictions for new registrations or leads submitted via the Data Port Module, calculated using the "Birthday" field. |
| Website Payments Interface |
Enables e-commerce payments or account deposits. This field supports multiple item selection:
See the Online Payments Interface section for more info. |
| Website Limit New Client Payment |
|
| Website Withdraw Request Page |
This field supports multiple item selection:
|
The "Website Features" Field
Use this field to enable or disable specific functionalities within the HTML Portal or API:| Function Name | Description |
|---|---|
| Companies on Gender Fields | Standard gender fields in Hyper include: "Male", "Female", "Private Company", and "Public Company". Enabling this option restricts the selection to only "Male" and "Female". |
| Create a Live Account | Enables the registration page for creating real accounts (New Client Leads). |
| Documents Module | Allows clients to view and upload required documentation. This can be set to READ-ONLY using the following option. |
| Personal Info & Docs in READ ONLY mode | Restricts clients from modifying personal data, managing contact persons, or uploading new documents. |
| Account Journal | A report page displaying the client's bookkeeping journal entries. |
| PDF Storage | A repository page for client statements, invoices, and receipts, provided as a downloadable PDF list. |
| Customer Service | Enables the ticketing system where clients can submit and track service requests. |
| Internal Mail |
An incoming messages page displaying internal communications from the [hyp_Website Mail to Clients] table.
|
| Trading Reports | Displays activity-specific trading reports (e.g., CFD, Forex, Crypto) pulled from relevant database tables. |
| Does_Entity_Exist_json | Warning: This API function allow external apps to search inside hyper Index: Clients, Suppliers, Users (employees) and all contact persons. |
| Direct_Client_Entity_json | Warning: This API function allow external apps to read and write any field of a Client Entity (access 6 tables per client number). |
Google ReCaptcha Configuration
Implementing these keys enables security challenges across all Web Portals: V2 "I'm not a robot" in the front page, and V3 for integrated background monitoring.Note: You don't have to use V3. Enabling ReCaptcha after the initial Web-App installation requires a service restart.
| Field | Description |
|---|---|
| ReCaptcha v2 Site Key | The public key used in your client-side code to render the "I'm not a robot" checkbox or invisible challenge. |
| ReCaptcha v2 Secret | The shared secret key used for server-side communication to verify the user response token with Google. |
| ReCaptcha v3 Site Key | The public key used to generate friction-less tokens. This version allows Hyper to monitor user behavior and page transitions after login, assigning a risk score to every action without interrupting the user experience. |
| ReCaptcha v3 Secret | The private key used by the Hyper server to retrieve the risk score (0.0 to 1.0) from Google's API, allowing the system to block automated scrapers or suspicious session activity in real-time. |