Manager Manual

Introduction

Payneteasy Payment Gateway (here and hereafter System, Payment Gateway or Payneteasy) provides accepting, processing, storage and transmitting of payment data between members of payment processes. This guide is intended for managers of the Payment Gateway software and hardware complex, which enable effective processing of transactions between:

  • merchants (and their facilitators),

  • their end customers (referred to as Payers or Receivers),

  • acquiring banks or other PSPs (or their facilitators).

Payneteasy provides a Manager account, which has broad UI and API access to the functionality of the system. This type of account allows to create and configure payment solutions for all merchants according to compliance requirements, limitations and business specifics, assign additional participants to selected merchant projects, and track financial flows of each participant.

The guide is arranged according to the structure of the Payment Gateway user interface and contains detailed information about each commonly used function.

Payment Gateway Objects

The hierarchy and data scope among users of the System is defined on the Simplified infological model of the System. All user roles and processing entities are described in the sections below.

Infological Model

title Simplified Infological Model of the System class Administrator #e1d5e7;line:black;line.dotted { } class Superior #e1d5e7;line:black;line.dotted { } class Manager #e1d5e7;line:black;line.dotted { } class Merchant #e1d5e7;line:black;line.dotted { } class Reseller #e1d5e7;line:black;line.dotted { } class Dealer #e1d5e7;line:black;line.dotted { } package "Processing configuration" <<Rectangle>> { class Project #dae8fc;line:black;line.dotted { } class Processor #d5e8d4;line:black;line.dotted { } class Gate #f5f5f5;line:black;line.dotted { } class Endpoint #ffe6cc;line:black;line.dotted { } } Administrator -down-{ Superior Superior --{ Manager Manager }-left-{ Merchant Manager }-down-{ Reseller Manager }-right-{ Dealer Manager --{ Project Merchant --{ Endpoint Endpoint }-right- Project Reseller --{ Project Dealer -down-{ Processor Processor -down-{ Gate Gate }-left- Project hide members hide circle

Processing Configuration

The system provides a set of integrations, named as “Processors”, with external payment institutions and payment providers. Each processor is a software module that implements a consistent communication protocol for transferring messages with external systems. To receive, process and transmit payment data, the following entities must be configured.

Object type

Description

Processor

Payment Gateway entity, which incapsulates interconnection with third-party processing system.

Gate

A set of parameters, which identify account registered in a third-party processing system. These parameters can be used to process payment data in an external system using the messaging protocol implemented in the Processor.

Project

System entity which determines the conditions for receiving a payment message from Endpoints and its further routing to the connected Gates.

Endpoint

Uniquely identified terminal, which is assigned to the Merchant and has to be provided in the commands within gateway API.

Endpoint group

A set of Endpoints with different currencies consolidated and available as one logical unit, which is used in gateway API URL address.

Master Endpoint

Additional logical unit which connects multiple Endpoints for Payment Cashier integration.

Note

Minimal configuration: 1 Processor, 1 Gate, 1 Project, 1 Endpoint.

The system allows to work with multiple currencies. Currency could be added by request.

User Roles

The Payment Gateway supports a dedicated account access for each user of the system. Discuss the most suitable Payment Gateway accounts model with support manager.

Each root user account can have its own Employees who can get access to the data from the root account, but with certain restrictions. Data scope is defined for all screens and reports of the system. See Employees for details.

See the list of root user accounts below:

Merchant

Provided to the merchant’s representatives. Merchant accounts can browse their transactions and linked Projects and Endpoints. They can process transactions and manage their own restriction lists.

Manager

Provided to the representatives of PSP or payment institutions. Manager accounts have full access to the configuration of the system.

Superior

Provided to the representatives of multiple Managers. Superior accounts can browse and configure all entities for the linked Managers.

Reseller

Provided to the agents, which engage merchants for Manager. Reseller accounts can browse multiple linked Projects and Endpoints of Merchants and manage Reseller rate plans. They cannot process any transactions, manage restriction lists, or create new entities. Payment facilitators which represent Merchants can receive Merchant accounts for each represented Merchant, or a single Reseller account connected to Merchant accounts of each represented Merchant.

Dealer

Provided to the agents, which engage processing solutions for Manager. Dealer accounts can browse multiple Gates linked to the Processor and manage Dealer rate plans. They cannot process any transactions, manage restriction lists, or create new entities.