Gå til innhold
  • Det finnes ingen forslag fordi søkefeltet er tomt.

Aritma Pay - Functional Requirements Specification



    We support all versions of Microsoft Server that receives Windows security updates. 

    1 Introduction 
    2 Purpose
    3 Function 
    4 Requirements
    5 Security
    6  Requirements
    6.1 Technical Requirements
    6.2 Firewall 
    6.3 Users 
    6.4 Other


    1 - Introduction

    This document contains the functional requirements for Aritma Pay and ZData Workflow Service.


    2 - Purpose

    The purpose of this document is to provide an overview of the functionality of Aritma Pay and ZData Workflow Service and to specify the requirements related to the installation of these services.


    3 - Function

    Aritma Pay is a software application for processing and converting all types of payment files between accounting systems and banks. Additionally, the program can split and combine payment files according to customer needs. The program can be automated and connected to Aritma's Bank API via ZData Workflow Service. Aritma's Banking API is integrated with most Nordic banks today.


    4 - Requirements

    Aritma Pay is preferably installed in the same environments as the current accounting software. This means the same application server and SQL server.
    Databases and tables are created during the installation of Aritma Pay. Therefore, the database user must be able to create databases. It is best to create a dedicated database user with the necessary permissions.

    Database login information is stored encrypted within the file areas of Aritma Pay.
    All relevant directories must be set up with UNC paths (share). The service user must have the ability to read, write, and modify these directories. Relevant file areas include the program file and program data areas of Aritma Pay and directories for the exchange of payment files between the accounting system and the bank.

    ZData Workflow Service connects Aritma Pay to the Aritma Banking API, ensuring a seamless flow of bank files. This service is installed on the same server as Aritma Pay and requires a dedicated service user with access to the necessary UNC paths. It can also share the same database user as Aritma Pay. A dedicated database for the service is automatically installed, and all configurations are stored there. The configuration can easily be customized by an Aritma consultant via a proprietary interface.
    Firewall openings are required for communication with the Aritma Banking API (see section 6.2).


    5 - Security

    All payment files created by Aritma before sending to the bank are encrypted with PGP. All communication with Aritma's Banking API occurs over SSL (https). Communication between Aritma Banking API and banks is encrypted according to the requirements of each bank. Files converted without using Aritma’s bank integration are not encrypted.

    6 - Requirements

    6.1 Technical Requirements

    Supports Windows Server versions that are supported by Microsoft and still receives security updates.

    CPU: Runs on all CPUs
    Disk space for software: approx. 1 GB
    Disk space for SQL database: approx. 1 GB
    Memory: 1 GB - 2 GB, depending on file size.
    Aritma Pay also installs Microsoft® ODBC Driver 17 for SQL Server (Integration with Visma Business requires Microsoft® ODBC Driver 17 for SQL Server to be installed on all clients).

    6.2 Firewall

    Firewall openings are required for the following DNS:
    License server: https://license.zdata.no
    Bank API: https://bankservice.zdata.no (bankservice.zdata.no redirects to id.zdata.no for login).
    It is possible to open to IP 51.13.21.13 (https://bankservice.zdata.no) port 443 and port 80 and to
    51.13.82.166 port 443 and port 80 (license server).
    We prefer that the customer opens to DNS as IP addresses can change.

    6.3 Users

    Aritma Pay and ZData Workflow require the following users for installation and setup:
    SQL user, with the following permissions (not a Windows user):
    - db_ddladmin
    - db_datawriter
    - db_datareader
    - db_backupoperator

    Service user:
    - Local admin on the app server.
     This is necessary for the service to be installed on the server. Local admin rights can be changed after installation.
    - Access to the program file and program data directories of Aritma Pay.
    - C:\Program Files (x86)\ConvertX (Read)
    - C:\ProgramData\ConvertX… (Modify)
    - Access to the file directory for bank files (Modify).

    6.4 Other
    Antivirus/applocker – If necessary, add exceptions for the program file and program data areas of Aritma Pay (ConvertX).