Veritran Docs

Transaction that can be performed by a bank user classified under a specific profile.

Effects used to change specific attributes of a component at a certain moment or upon a specific action.

Invoking an external service via a REST protocol.

Invoking an external service via a SOAP protocol.

Standards that define how apps should be created, structured, and maintained in order to guarantee consistency, efficiency and scalability in the entire building process. These standards must ensure that the app structure and design align with the design system defined for the project.

VT-NET's processes that manage the transaction’s route, which is the path that communicates apps with the back-end, and execute the necessary functions to implement business functionalities within the app.

A software intermediary that allows two apps to communicate.

Pre-designed app that offers a complete user interaction flow and is oriented towards a specific use case.

Preset packages of graphical appearance details, such as colors, size, fonts and backgrounds, which define the look & feel of a screen.

Unique state of an app that is identified by a unique number. This number is assigned automatically in increasing order and corresponds to new developments in the app.

Previously called "resources", assets are all images, icons, fonts, video files, audio files, widgets or any type of file that can be uploaded to the different systems of the VT platform.

Characteristics of a component configured in the attributes editor of the screens editor.

Platform component that offers users credentials authentication and adds two-factor authentication to transactions.

Veritran's main security component. It offers a service that provides user credentials authentication and adds two factor authentication to transactions.

Core Server's process that validates if a transaction is enabled. If it is enabled, it determines the transaction's route and sends it to the corresponding Host Interface using the internal messaging format.

Middleware process responsible for determining the routing that will be given to each transaction, applying the business rules themselves and transmitting them to an external processing system (Host).

Apps built with Veritran technology, ready to upload to stores.

In Lambda processes, blocks represent a variety of functions and operations that can involve transactions, registers, arrays, conditionals and more.

Feature that allows you to test changes in a controlled environment by deploying changes to a reduced number of users to minimize risks.

Test of an app or platform version in a controlled environment.

Production node.

Copy of an app or module used to develop and test changes made to screens and processes of an app in an independent manner.

Action that brings changes from the main branch to another branch.

Generation of an app's binary.

Blue-Green experiment that tests updates on a product of the platform.

Rule applied to the logic of a transaction that involves the conditions under which such transaction is approved.

Platform service that defines and applies business rules to transactions upon evaluating them and then approving or rejecting transactions.

Information regarding products or services provided to the app user.

Simulator that allows you to see what the screen of your app will look like while adding or removing components and setting their attributes.

Any experiment stopped in your system.

The action that brings changes made in a branch to the main branch. Each commit generates a new app version.

Save changes made to an entity stored in GIT.

Set of rules that determines transmission of data between services within the same network. Also known as network communication protocol.

Middleware's communication layer. It's the first component that interacts with an incoming message in a transactional flow.

Element used to build a screen using the drag & drop feature that may have different functionalities depending on its function.

Interface that will be displayed as a component in the screens editor. To use it, the module must be linked to the app in the app dependencies.

Component built using native components that serves a specific function and can be reused in different apps and projects. Configurable components have a limited functionality and enable the creation of parts of a screen, like an input, a header or footer. They are created through interfaces of a module and their structure can be modified through parameters. Formerly called configured component, component-type interface, fragment or organism.

Low-code transaction created in Studio that is automatically created in the middleware.

Transaction configured with low-code and published from Studio, interpreted and executed by the middleware.

Changes or differences between the main branch and another branch.

Component that includes other several components within

Sum of app or module and a branch a user is working on in a specific environment.

Middleware's processing layer that contains VT-NET, the runtime system.

Branch used in cases where the previous branch types do not apply.

Studio feature that allows the user to link a module to an app or to another module to be able to use the module's content.

Collection of guidelines, best practices and tools that help keep the look and feel of the app and the user experience consistent, while improving sustainability. It includes the app style, UI components, fonts, assets, among other elements.

Branch used to create feature branches. This branch is initially created as a copy of the main branch, and is then modified with each update or fix.

List of devices that are not allowed to operate the app in order to avoid fraud.

Core Server's process that enables communication with the different types of devices (mobile, web, SmartPOS, third-party services). It receives and interprets messages sent by the devices and translates them into an internal format recognizable by the Authorizator. Then, it receives the Authorizator's response and translates it back to the original format.

Middleware process responsible for enabling communication with the different devices.

Transaction that cannot be performed by a bank user classified under a specific profile.

Feature that allows you to grab an object and place (drop) it into a different location.

Platform component that manages promotions and points of interest (POI) based in geographic locations to be implemented in mobile and web apps.

Unique identifier for a transaction evaluation.

Different types of pre-built elements – such as app templates or feature templates - available at Veritran Marketplace that accelerate the app building process.

Acquisition of extensions in Veritran Marketplace to be used in a Studio environment to accelerate the app building process.

Service that solves the business logic of a transaction by invoking API services (third-party services) via a REST or SOAP communication protocol.

Branch created to work on a copy of the main branch without affecting the productive version of the app.

Type of extension that solves a specific business or cross-market functionality with a limited flow of interaction.

Logic executed within the steps of a process. Each step of a process can contain only one function.

Set of screens that represent a sequence of steps executed by an app user and is created through an interface of a module. These steps usually share similar characteristics and require to be grouped in a flow to represent a specific functionality. Formerly called screen module, screen-type interface or screens flow.

Configuration information whose scope applies to your Studio environment.

Registers available for all the apps within the same Studio environment. Their numeric IDs go from 1 to 1000.

Node that receives the new updates first. This is not the production node.

Core Server's process that manages communication between the middleware and external services. It orchestrates and integrates services to process a transaction, and transforms and uses its data. This process executes the transaction's logic.

Immediate patch or fix applied to correct defects found within the app.

Branch containing a hotfix to avoid making changes in the main branch.

Component that allows to connect to third-party or client databases .

Platform component that allows to expose configurable transactions that can then be consumed by third-parties.

Platform service used to create, search and manage organizations and users.

Functionality that communicates a module with an app or another module. It is required to use a module's content.

Blocks of code that can be assigned to variables, passed as an argument, or returned from a function call.

Process built in the Lambda Editor through the use of a visual programming language.

Reusable feature configuration to enable adding instances to different components.

Process built using the form method. Processes are currently created using the lambda editor.

Reusable component that can be added to screen by duplicating it or referencing the original element.

VT-NET object in charge of opening a conection socket to the exterior from the Core Server, and of accepting entry connections. There are server lines (those that open a listening port so that the middleware can receive transactions from different devices and systems), and client lines (those that open a port to stablish exit connections  to the different services integrated by the middleware for each solution). Lines have their own messages queue.

Registers that are specific to an app or module. Their numeric IDs can range from 1000 upwards.

Stable, read-only branch of your app or module from which new branches are created.

Module that represents the app itself in the branch navigator.

The main component within the Veritran platform ecosystem, which allows communication between the front-end (apps) and third-party, client or Veritran-owned services.

App that is accessible using a mobile device.

Platform component used to generate and manage mobile apps, and to visualize and configure each app's parameters, the environments and products associated to it, the platform versions and the runners used to generate the app.

Reusable configuration unit that you can create for a screen or for a component.

Configuration unit that can be instanced through its interfaces in an app or another module, which is called the parent app or module. It has the same functionalities of an app, but they cannot be published. Through modules, you can built functional flows or configurable components.

Individual component installed in Studio by default that solves a specific problem or functionality and can be used in the app screens, together with their statuses and corresponding styles and behavior. They appear available in the left panel of the screens editor in Studio and their structure cannot be modified. Formerly called built-in component.

Former type of transaction created on the middleware. It can be invoked in Studio.

Controlled configuration issues that might affect an app's functioning.

Veritran platform's service that allows to create, manage and execute messaging campaigns.

Approach which streamlines all the customer interactions across multiple touchpoints in a unified way to deliver a consistent experience across different devices and channels.

Global configuration information given to the different components of the platform. It consists of an ID, the type of information stored, a value, and a scope (global or site).

Extension with restricted access to specific users.

Sequences of steps that add logic to an app. Each step runs an operation or function.

VT-NET object in charge of implementing business logic. This object has its own messages queue and can interact with an associated database. There are system and application processes.

Bank product on which the rules that determine whether a transaction is approved or rejected are applied.

Collection of settings associated to a user whose permissions and information are set in the Veritran platform.

VT-NET framework's object that functions as a load balancer between entities such as the Device Handler, the Authorizator, the Host Interface, exit stations or other qservices. This object has its own messages queue and implements different balancing strategies.

Studio feature that allows you to generate and publish only the changes made to a process or screen.

Previously called token. Data repository where you can store any value, relating it to a numeric identifier.

Branch used to integrate feature branches and execute a throrough test of what is being implemented and published. The release branch represents the final package.

Blue-Green experiment divided into blue and green groups.

Process used to associate response codes of a client's service to the platform's response codes and add custom messages.

HTTP communication protocol to involve services in a specific environment.

Functionality in Veritran Studio that allows to restore a previous commit of an entity.

Virtual machine used to generate an app's binary.

VT-NET object that grants the kernel permission to manage processes that are external to the framework, like a proxy. Satellites guarantee that these external processes are running and, in case any process is stopped abruptly, it identifies the issue and restarts the process. This object has a messages queue.

Visual areas with distinct content that can be arranged to form a site view.

Interface that will be displayed as a screen or screens flow in the screens editor. To use it, the module must be linked to the app in the app dependencies.

Canvas that allows the to simulate the look and feel of the screens of an app by using the drag & drop feature.

Authentication service to log in to different platforms or systems with a single user and password.

Configuration information whose scope applies only to your current app.

Groups of screens that have the same layout.

Exact picture of an app that captures values for arrays and registers during its execution.

XML communication protocol to invoke services in a specific environment.

Origin of the API configuration of the entity.

Digital work tools where project tasks are performed, either tools within the Veritran platform or external platforms. For example: Figma, Studio, etc.

VT-NET object in charge of reading and writing through the different connection sockets set and managed by lines. There can be more than one station per socket to increment connections' processing capacity. This object has its own messages queue.

Blue-Green experiment that tests a new version of the platform.

VT-NET processes necessary to guarantee that VT-NET runs correctly. These processes are: the Kernel, Command Server, Model Server, Application Server and Security Server.

Ability of a device to sense that an active attempt to compromise the device integrity or the data associated with the device is in progress.

Preventive measure to avoid any attempt to tamper with an app without consent.

Substitution of sensitive data for a "non-sensitive" token. It guarantees that apps are subscribed to cards tokenization programs.

Feature that allows you to collect and visualize data on how users interact with your app by setting specific tracking events and user properties.

Services executed in the middleware of the Veritran platform used to implement complex business logic in your app, consume databases and invoke external services and processes.

Flow that represents how a message travels from an app's front-end, through the middleware, and to the services in the back-end, and how it returns the information received from the service.

Unique identifier for a transaction.

Codes configured to identify a transaction's flow response and set a message to be seen by the app user during the response.

App that can be accessed through an internet browser or from mobile devices.

Set of guidelines, best practices and patterns that define which is the most efficient and effective way to perform a task, in the case of the Veritran Low-Code Platform, to design and build, set up and operate an app.

Functionality that stores values that are then used in a transaction flow.

Digital repository for users to consume and share extensions that accelerate the building of apps in Veritran Studio.

Veritran platform's low-code component, developed to build web, mobile and SmartPOS transactional apps.

PHP component that works as a gateway between messages sent from mobile devices to VT-NET, middleware's transactional processing system.

Mission-critical, transactional system on which other high-performance applications are built (Core Server, Auth Server and Notif Server) that provides network functions such as communication management and transactional messaging.

Profiles assigned to the platform users that have permissions to execute commands in the Operator

Also called Operator. Tool used to introduce command lines, restart, stop, modify or check processes. It notifies the platform about business updates required and acts as a debugging tool.

Association of a VT service with a native transaction to invoke services when executing the transaction.

App that is accessible using any web browser.

Java application that interprets web metadata received through VT-NET to present an app to web apps' users.