Administration Panel

• Intro slides
• Overview
• Token Management Administration Panel Overview
• MDES administration panel
• Finance Administration Panel Overview
• KYC Panel Overview

Intro slides

Overview

The Administration Panel is the essential tool for our Partners to work with your Verestro services. The main purpose of Admin Portal is to provide a web-based environment with the ability to manage customer service actions. The presented solution is prepared for customisation with Partner's brand.

This document is divided into sections that describe the various components of the system. Each section contains a screen presenting the functionality and a detailed description of the states occurring in it. 

The mechanisms described in this documentation are the most important ones for all web-based products that rely on Admin Portal. Some functionalities of Verestro have specific screens and processes that are not described here. Administration Panel is going through on-going development and changes to improve its performance so there may be differences in this description and real panel.

Purpose and scope

This product guide provides a high-level overview of Admin Panel Management. This document covers the following topics:

Terminology

This section explains a number of key terms and concepts used in this document.

Name	Description
Operator	User using the Portal regardless of role or level of rights.
Session token	Access to the system by a web application user is secured using a session token to uniquely associate the session with the user. It is required to perform any action.

Access and configuration

Access solutions

The access to Admin Portal in available in 3 ways:

Admin Portal is available on two environments:

▪ test environment (dev/UAT environment),
▪ production environment.

Sample of test environment (URL): https://admin-panel-nameofclient.verestro.dev/
Sample of production environment (URL): https://admin-panel-nameofclient.verestro.com/

IMPORTANT: There is also option to use custom domains.

Configuration of Admin Portal

Admin Panel has a several default parameters related to the time of each action. Table below describes particular action and time of session token.

Action	Description	Accessibility time
Reset password	Validity of link to reset password.	60 minutes
Create an account	Validity of link to first login to Admin Panel.	60 minutes
Login to the panel	Validity of code (4 numbers) to login.	10 minutes
User session	Session after successful login to the panel.	15 minutes
User lock	Time of lock due to incorrect password.	max 24h (until midnight next day)
Registration link	Validity of invitation link.	60 minutes

These are the default values, they can be changed at the request of the customer. 

Security

The systems offered by Verestro are fully secure, which is confirmed by current third-party certificates. As we store card and payment data we are obliged to comply with strict legal requirements. Card and user data are stored in a specially designed environment - Data Core. This environment is PCI DSS certified. The PCI-DSS standard guarantees the security of payment card data. It ensures that sensitive information is properly guarded and provides maximum security in the payment process. The portal operators' passwords are kept in a different database from the end users' data for security reasons. To encrypt them the algorithm Bcrypt with a cost of 10 is used. The cost parameter specifies a key expansion iteration count as a power of two, which is an input to the crypt algorithm.

We achieve high security standards by, among other things :

Architecture

Admin Panel uses Verestro's distributed systems to provide the highest quality of service. It is practically the best architectural solution these days. As mentioned in the previous chapter, the communication between services is completely secure, maintaining the highest security standards. This kind of system guarantees not only high efficiency, due to the division of responsibilities between the components, but also allows for easy and fast scaling of the system according to the customer's requirements.

Below is a sample architecture for the product VCP or in other words Admin Panel MDES along with MCBP Wallet.

Login procedure

First login (activation)

Users could be added only from the panel. It is not possible to register in the system without an invitation. Basic administrators accounts that can be used to create a user hierarchy are provided with the panel instance.

In order to create a new user account you have to log in to the panel using your e-mail address, which is user login. Then go to the "Administrators" tab and fill in the required data. After filling in the role, personal data and e-mail address there will be sent a welcome message with an activation link for new account.

Once the email send process is complete, the invited user will receive a message. It contains a welcome and an activation link - used to set a password to access the system.

Clicking on the link redirects to the login page, where the employee will have to set a password during the first logging in. The required password standard is a minimum of 8 characters, at least one digit, one capital letter and one letter.

Login procedure

Operator must provide correct pair – e-mail and password. If the provided login is incorrect, a message informing the employee of an error “Incorrect e-mail or password” and the possibility of another attempt will be displayed.

If the data provided is correct, an authentication code is sent. This is required to complete the next step of the two-step login.

As last step application asks for code. Sent code has set validity time. If code will not be provided in this time, login procedure must be started from first step.

Reset password procedure

In order to reset password, admin has to open the login page and click option “reset password” (located under e-mail and password inputs). In next step, admin must provide correct e-mail address.

If the provided e-mail is correct, reset password link will be send to the employee's company e-mail address.

Clicking on the link redirects to the reset password page, where the employee will have to provide his e-mail address and set a new password. The required password standard is a minimum of 8 characters, at least one digit, one capital letter and one small letter.

Main view

Once the authentication process is properly completed, the bank employee has access to the panel. He is shown the main screen of the system. Depending on the assigned rights group its appearance may vary. Different roles in the system have different tabs available. 

The components that make up the Admin Portal are:
1) Main menu contains aggregates as: customers, cards, devices, payment history, IBANs, project administration (administrators, visuals, logs).
2) Admin Panel adjusted to the client’s colours and logotype. 
3) Filters allows to select multiple filter options and display results that contain information all the selected criteria. 
4) List of the most important information referring to each aggregate (example: customers).  
5) Actions allows admin to change the status of aggregate or edit data.  

Operator administration

Roles and permissions

From the actions of the bank's operations team or call centre point of view, three types of authorization are characterized by diverse access levels have been created:
•    employee, 
•    manager, 
•    administrator. 

Above levels are characterized by privileges with access to operational functionalities, which significantly influence the portal operators. The basic tasks at this level is customer verification, data preview and potential editing. 

Below are the default function descriptions divided into areas.

Aggregate	Action	Admin	Manager	Employee
Portal management - Operators	View	x	x	-
	Create	x	x	-
	Edit	x	x	-
	Delete	x	x	-
	Lock	x	x	-
	Unlock	x	x	-

With the default setting of permissions according to the table above, the administrator can see operators in all roles in the list (including other admins, managers and employees) and can add operators with any role. The Manager, on the other hand, only can see operators with Employee status and can only create such operators.

Operators list

Administration Panel Accounts list contains filters and columns with dates. In this section detailed lists don’t occur. The filters are used for dynamic searching, such data as:  e-mail, first name, last name, group (available: admin, manager, employee). 

Basic list includes following information:

Parameter	Description
Group	Group determines the access level.
E-mail	Admin e-mail address.
First name	Admin first name.
Last name	Admin last name.
Status	Admin status (described in admin statuses part).
Actions	Action which can be performed on particular admin (described in admin actions part).

Account statuses

Referring to the above tables, the possible transition of operator states is presented in the diagram below.

Standard flow - operator is created in status invited (Admin Panel MDES/VCP scenario).

Alternative flow - operator is created in status inactive.

Accounts actions

Administration Panel user can perform the following actions for the particular user (admin, manager, employee):
a)    add admin/manager/employee – necessary to input following data: group (select: admin, manager, employee), first name, last name, e-mail. In order to confirm “Save” button should be clicked. Added user should receive e-mail with link to activate account and set the password. 

b)    edit admin/manager/employee – possible to change following data: group (select: admin, manager, employee), first name, last name, e-mail. There's no option to edit operator with status "invited", in this particular case it's necessary to delete invitation and add a new operator.

c)    lock admin/manager/employee – temporary lock of user.

Notifications in the system

This section contains all email messages that are sent in the system to the portal operator.

Emails from Admin Panel to operator.

Process	Topic	Details	Comment
Invitation to the system	Set password to administration panel.	Hello! You are receiving this e-mail because an account was created for you, and you need to set a new password. <button to set password> Regards, < NameOfClient >	Standard email sent when portal operator added new operator.
Login process	Login code.	Hello! Your login code: <code> Regards, < NameOfClient >	Standard AP email sent when portal operator entered correct email and password.
Reset password	Reset password to administration panel.	Hello! You are receiving this mail because someone initialized password reset for your account. If it was not you, you can ignore this mail. <button to reset password> Regards, <NameOfClient>	Standard Admin Panel email sent when portal operator uses "reset password" button on login page.
Additional password policy	Password expiration reminder.	Hello! Your password will expire in <NumerOfDays> days. Please change your password to avoid losing access to the portal. Regards, <NameOfClient>	Related to additional policy to force password changes.
Inactive account policy	Inactive account reminder.	Hello! Due to inactivity your account will be blocked in <NumerOfDays> days. Please log into the portal to avoid losing access to the portal. Regards, <NameOfClient>	Related to the additional policy of automatically deactivating unused accounts.

Additional features

This section focuses on additional functionality in the system. By default they are disabled, they can be enabled upon request during panel creation or panel version upgrade.

Token blacklisting 

For better security, a mechanism for blacklisting session tokens has been prepared. This makes it possible to prevent unauthorized access to the portal and data using the session token of a logged out user (if the token life has not expired yet). 

It should be noted that during the logout process the session token in the user's browser is destroyed, regardless of whether the blacklisting mechanism is enabled. Also, closing the browser deletes the token.

However, a theoretical scenario is that the user's token is intercepted and used for unauthorized access to the system. Access possible for the lifetime of the token. 

When this mechanism is enabled, the token is blacklisted (and therefore prevented from further use despite the active life time) and each query to the backend (API Admin Panel) checks whether the token used by the user is not blacklisted. 

Session extension popup 

Sometimes the session time may not be sufficient to perform the portal user's operations. For this reason a mechanism has been created to ask the user if there is a need to extend the current session. 

It should be noted that by default when half of the session time elapses and the user performs some action (moves to another tab, clicks a button) the session time is renewed. By session time renewal it is meant that a new session token is assigned to the user and the session time counter is restored to its default, maximum value.

When the mechanism is active at a certain time before the end of the session the user is asked if he needs more time (screen below). If user chooses affirmative answer, there is assigned a new session token and the session time is restored to the default, maximum. Selecting no closes the dialog. Not selecting an option will close the dialog when the session time expires and the user is logged out.

Tooltip for table row values

Depending on the resolution and screen size, the appearance of each screen may vary cosmetically. Admin Panel is responsive but values in tables can be of different length (up to 255 characters). It is not always possible to display the entire value in a single table cell. For this reason, a mechanism was created to display a tooltip for table cell values. 

The default mechanism is to show the user as many characters as fit into the table cell - depending on the screen size of the device. It is possible in this case to copy the whole, valid value of the cell. Unfortunately it is not possible to preview it by user in simple way - it is necessary to copy cell value e.g. to text document to know its characters that do not fit in the cell. 

By enabling described mechanism the tooltip is displayed when the user hovers the mouse over a particular value in the table and waits for 1 second without moving the mouse. The user can easily see the entire value of such a variable.
 

Password policies 

As it is extremely important for us to ensure the security of the portal operators' data and the data to which the operators have direct access, we are providing an additional policies for passwords.

Force password change  

The first of the additional policies that can be used on the admin instance of the panel is to force the operators to change the password every specified number of days. In the case of inactivity on the part of the operator the account is locked - its unlocking is possible through a password reset mechanism. Before the account is blocked, an email notification is sent about the need to change the password - the time when the email is to be sent is configurable. 

Force unique password   

A second, additional safeguard in password security policies is to prevent a user from setting a password that they have already used in the past. With this mechanism, it is possible to configure how many previous passwords should be excluded from reuse. Of course, for data security reasons, previously used passwords are not stored but only their unique hash, which is used for uniqueness comparison. 

Deactivate inactive accounts

In order to ensure the safety of the data contained on the portal, an automatic deactivation mechanism for unused accounts has been created. It allows to define the time without logging in after which the operator will be blocked. Unblocking the account is possible by using the password reset mechanism, which is tantamount to confirming your identity and access to your e-mail address.

Handling an unavailable service 

As Admin Panel consists of multiple services (as a reminder, individual services are responsible for the corresponding sections in the side menu), it is important to ensure the availability of the application when any of the individual components is not working (for example, due to a scheduled maintenance outage). For this reason, a mechanism for graying out unavailable services in the side menu has been implemented and enabled by default. If any product/service is temporarily unavailable, the portal operator can still use the functionality provided by the other services. In the case that the unavailable service becomes operational, the section becomes available again after refreshing the page. 

Token Management Administration Panel Overview

The TMP Administration Panel (or the admin portal/portal for short) is the essential tool for you to work with your online application. Here you can manage payment tokens and track history of payments. The presented solution is prepared for rebranding for the client's brand. The document is divided into sections that describe the various components of the system. Each section contains a screen presenting the functionality and a detailed description of the states occurring in it.

Purpose and scope

This product guide provides a high-level overview of Admin Panel Management. This document covers the following topics:

Abbreviations & Acronyms

This section explains a number of key terms and concepts used in this document.

Name	Description
MDES	Mastercard Digital Enablement Services
VTS	Visa Token Service
TMP	Token Management Platform
OTP	One Time Password

Terminology

This section explains a number of key terms and concepts used in this document.

Name	Description
Customer	Cardholder.
Operator	User using the Admin Panel.
Token	Payment Token.
Session token	Access to the system by a web application user is secured using a session token to uniquely associate the session with the user. It is required to perform any action.

MAIN VIEW

Once the authentication process is properly completed, the bank employee has access to the panel. It is shown the main screen of the system. Depending on the assigned rights group its appearance may vary. Different roles in the system have different tabs available. 

The components that make up the Admin Portal are:
1) Main menu contains aggregates as: tokens, history of payments, reports in Token Management Tab and Portal Management Tab.
2) Admin Panel adjusted to the client’s colours and logotype. 
3) Filters allows to select multiple filter options and display results that contain information limited all the selected criteria. 
4) List of the most important information referring to each aggregate (example: tokens).  
5) Actions allows admin to change the status of a single entity or edit data.  

TOKEN MANAGEMENT

Tokens

Tokens section contains a list of tokens and the filters. The filters are used for dynamic searching, such data as: phone number, VPAN (external card id), path, status last four digits of card or token, payment scheme and others.

Basic list includes following information:

Parameter	Description
VPAN	External Card ID provided by the Issuer.
Payment scheme	Payment scheme - Mastercard of Visa.
Token	Token last 4 digits.
Phone Number	Cardholder's Phone number.
User name	Cardholder's User name.
Status	Token status.
Token requestor	Token Requestor/Wallet.
Device	Device form factor.
Path	Inital authorization path - green/yellow/orange/red.
Action	action which can be performed on particular customer (described in customer actions part).

Available actions

Action	Description
Activate	This action activates the token. Available if the token can be activated and is currently INACTIVE.
Suspend	This action suspends the token. Available only for ACTIVE tokens.
Unsuspend	This action unsuspends the token. Available only for SUSPENDED tokens.
Deactivate	This action deactivates the token. Available for all INACTIVE, ACTIVE and SUSPENDED tokens.

Generate tokens report

This button in the top right corner allows generating a report with tokens with applied filters. Maximal date range for a single report is 31 days. The excel file will be generated and automatically downloaded. This report can also be downloaded in Reports section later.

Token Details

Selecting a specific token allows to see more detailed data. In addition to basic information.

A list of related status changes, transactions and activation methods used is available.

Detailed list includes following information:

Parameter	Description
Token ID	Internal Verestro Id of the token.
Token unique reference	MDES/VTS token unique reference.
VPAN	External Card Id - Issuer Card Id.
Status	Token Status.
Status process	Status of the tokenization process - IN_PROGRESS, FINISHED.
Sms count	Number of sms messages with OTP code sent.
Token type	The type of the token: CLOUD/EMBEDDED_SE.
Wallet ID	Wallet ID of the token requestor.
Correlation ID	Value linking pre-digitization messages generated during provisioning.
Reason code	Reason of the last token update.
Payment app instance ID	Identifier of the Payment App instance within a device. NOTE - This may contain the identifier of the Secure Element or a mobile device for some wallets.
Issuer decision	Final tokenization decision returned to MDES/VTS.
Issuer reason	Reason of the DECLINE, if the tokenization is declined because of invalid card data, exp date or cvc.
uPaid reason	Reason of the DECLINE, if the tokenization is declined because of Verestro velocity controls triggered.
Account source	Account source - Manual entry, card on file, from mobile application.

Payment history

Payment history list

Payment history list contains filters and columns with dates. In this section actions don’t occur. The filters are used for dynamic searching, such data as: phone number, VAPN, date range, status and token requestor . The date is displayed in local time.

Basic list includes following information:

Parameter	Description
Phone number	Cardholder's phone number (if provided by the Token Requestor).
VPAN	External Card ID.
User name	Cardholder's username (if provided by the Token Requestor).
Date	Transaction date.
Status	Status of the transaction.
Amount	Amount.
Currency	3-character ISO 4217 currency code of the transaction.
Token requestor	Token requestor .

Generate transactions report

This button in the top right corner allows generating a report with transactions with applied filters. Maximal date range for a single report is 31 days. The excel file will be generated and automatically downloaded. This report can also be downloaded in Reports section later.

Payment history details

Reports

Reports section contains reports that can be downloaded. Each report is valid for a specific duration and can be "Ready" to download or "In progress", which means that a report is still generating.

Tokens

This tab contains Tokens reports, generated from Tokens section.

Transactions

This tab contains Transactions reports, generated from Transactions section.

Apple Pay

This tab contains Apple Pay reports, which are generated automatically each month.

Activity

This tab contains Activity reports, which are generated daily. Activity report contain the information about all actions performed on Tokens by Admin Panel users.

OPERATOR ADMINISTRATION

Default privileges per role in the portal

Below are the default function settings for described product divided into areas.

Aggregate	Action	Admin	Manager	Employee
Token Management - Tokens	View	x	x	x
	Deactivate	x	x	x
	Suspend	x	x	x
	Unsuspend	x	x	x
Token Management - Payment history	View	x	x	x
Token Management - Reports	View	x	x	-
	Generate	x	x	-
Token Management - Rules	View	x	x	x

MDES administration panel

The MDES Administration Panel (or the admin portal/portal for short) is the essential tool for you to work with your online application. Here you can manage customers, their cards, IBANs, devices and track history of payments. The presented solution is prepared for rebranding for the client's brand. The document is divided into sections that describe the various components of the system. Each section contains a screen presenting the functionality and a detailed description of the states occurring in it.

Purpose and scope

This product guide provides a high-level overview of Admin Panel Management. This document covers the following topics:

Abbreviations & Acronyms

This section explains a number of key terms and concepts used in this document.

Name	Description
VPN	Virtual Private Network
MPA	Mobile Payment Application
IBAN	International Bank Account Number
MCBP	Mastercard Cloud Base Payment
MDES	Mastercard Digital Enablement Services
LCAPI	Lifecycle API

Terminology

This section explains a number of key terms and concepts used in this document.

Name	Description
Customer	Customer who uses MPA.
User	User using the Admin Panel.
Card	Section contains information about customer PANs – physical cards added by customer manually in MPA or bank using LC API.
IBAN	Customer bank account number. MCBP enables bank account numbers to be digitized and used for payments.
Token	Payment Token in context of MCBP. Tokens are result of correct digitization. Each token has one wallet account, one card/IBAN number and one device related.
Device	Device is data aggregate related to customer. Device is entity in MDES – created during MDES registration. Each registration of customer has device on Verestro side, but each customer may have multiple MDES registrations.
Payment history	It’s possible that transaction history will be stored on Verestro wallet server for infinite time (this setting can be specified during onboarding with Mastercard). If these options are enabled, MPA can retrieve transaction history for given user and payment instrument ID. Transactions are returned in corresponding parts for better user experience. Particular transaction may appear on the list with delay – depending on integrated external components.
LCAPI	API Used for direct integration to partner. Allows to manage users, cards, etc.
Session token	Access to the system by a web application user is secured using a session token to uniquely associate the session with the user. It is required to perform any action.

Main view

Once the authentication process is properly completed, the bank employee has access to the panel. He is shown the main screen of the system. Depending on the assigned rights group its appearance may vary. Different roles in the system have different tabs available. 

The components that make up the Admin Portal are:
1) Main menu contains aggregates as: customers, cards, devices, payment history, IBANs, project administration (administrators, visuals, logs),
2) Admin Panel adjusted to the client’s colours and logotype. 
3) Filters allows to select multiple filter options and display results that contain information all the selected criteria. 
4) List of the most important information referring to each aggregate (example: customers).  
5) Actions allows admin to change the status of aggregate or edit data.  

Customers management

Customers list

Customer list contains filters and columns with dates. The filters are used for dynamic searching, such data as:  customer ID, external ID, e-mail, phone number, status (unverified, verified, locked, deleted). 

Basic list includes following information:

Parameter	Description
Customer ID	Internal Verestro Id of customer.
External ID	External customer identifier provided by client (for example: recordID).
E-mail	Customer e-mail address.
Phone number	Customer phone number with country prefix.
First name	Customer first name.
Last name	Customer last name.
Status	Customer status (described in customer statuses part).
Action	Action which can be performed on particular customer (described in customer actions part).

Customers details

Selecting a specific user allows to see more detailed data. In addition to personal information, a list of related devices, IBANs, tokens, and payment history is available. 

Detailed list includes following information:

Parameter	Description
Customer ID	Internal Verestro Id of customer.
External ID	External customer identifier provided by client (for example: record ID).
First name	Customer first name.
Last name	Customer last name.
Phone number	Customer phone number with country prefix.
E-mail	Customer e-mail address.
Status	Customer status.
Number of failed logins	Number of login failures.
Created at	Date of customer registration.
Deleted at	Date of customer deletion (parameter displayed only if customer has been removed from system).

Additionally, in details are available lists of aggregates related to the particular customer:
•    customer devices (more information in devices management),
•    customer IBANs (more information in IBANs management),
•    customer cards (more information in cards management),
•    customer tokens (more information in tokens management),
•    payment history (more information in payment history). 

Customer statuses

A user can be defined by one of four statuses. The system created by Verestro divides the statuses into the following: 

Customer actions

Admin can perform the following actions on the particular customer:
a)    view customer – redirect to the screen with customer details data,
b)    edit customer – redirect to the screen with edition (screen below). The following data can be edited:
•    first name, 
•    last name, 
•    phone number, 
•    e-mail,

c)    lock customer – temporary lock of customer (more information in customer statuses part),
d)    delete customer – permanent delete customer data (more information in customer statuses part).

The following table shows the states of the user's token after performing each action.

Action	Token status
Add customer	Unverified
User authentication	Verified
Lock customer	Locked
Unlock customer	Verified
Delete customer	Deleted

Referring to the above table, a diagram has been created showing the change of states of the user token. This allows for better visualization of actions and dependencies between them.

Cards management

Cards list

Cards list contains filters and columns with dates. The filters are used for dynamic searching, such data as:  card ID, last 4 digits, date of creation, status (available: unverified, verified, locked, deleted). 

Basic list includes following information:

Parameter	Description
Card ID	Internal Verestro Id of card.
Customer ID	Internal Verestro Id of customer.
Last 4 digits	Last four digits of physical PAN.
Exp date	Expiration date in MM/YY format.
Type	Card type (Mastercard, Visa).
Status	Card status (described in card statuses part).
Action	Action which can be performed on particular card (described in card actions part).

Card details

Selecting a specific card allows to see more detailed data. In addition to basic information, a list of related customers, and payment history is available.  

Detailed list includes following information:

Parameter	Description
Card ID	Internal Verestro Id of card.
Last 4 digits	Last four digits of physical PAN.
Expire date	Expiration date in MM/YY format.
Description	Friendly name of card.
Type	Card type (Mastercard, Visa).
Status	Card status. Available: verified, unverified, deleted, locked.
Created at	Date of card addition to the wallet database.
Deleted at	Date of card deletion from the wallet database.

Additionally, in details are available aggregates related to the particular card:
•    customers (more information in customers management),
•    customer tokens (more information in tokens management),
•    payment history (more information in payment history).

Card statuses

A customer can be defined by one of four statuses. The system created by Verestro divides the statuses into the following: 

Card actions

Admin can perform the following actions on the particular card:
a)    view card – redirect to the screen with card details data,
b)    lock card – temporary lock of card (more information in card statuses part)
c)    delete card – permanent delete card data (more information in card statuses part).

Below table presents how action may change the statuses of card

Action	Statuses
	Card’s status	Token’s status
Add card	Unverified
Verify card	Verified
Lock card	Locked	Suspended
Unlock card	Verified	Active
Delete card	Deleted	Deleted

Referring to the above table, a diagram has been created showing the change of states of the card. This allows for better visualization of actions and dependencies between them.

IBANs management

IBANs list

IBANs list contains filters and columns with dates. The filters are used for dynamic searching, such data as:  IBAN ID, IBAN number, status (active, deleted). 

Basic list includes following information:

Parameter	Description
IBAN ID	Internal Verestro Id of IBAN.
Customer ID	Internal Verestro Id of customer.
IBAN number	IBAN number; example. IBAN=PL100020003000030000.
Status	IBAN status (described in IBAN statuses part).
Action	Action which can be performed on particular IBAN (described in IBAN actions part).

IBANs details

Selecting a specific IBAN allows to see more detailed data. In addition to basic information, a list of related customers, and payment history is available.  

Detailed list includes following information:

Parameter	Description
IBAN ID	Internal Verestro Id of IBAN.
IBAN number	IBAN number eg. IBAN=PL100020003000030000.
Created at	Date of IBAN addition to the wallet database.
Deleted at	Date of card deletion from the wallet database.

Additionally, in details are available aggregates related to the particular IBAN:
•    customer (more information in customers management),
•    tokens (more information in tokens management),
•    payment history (more information in payment history).

IBAN statuses

IBAN actions

Admin can perform the following actions on the particular IBAN:
a)    view IBAN – redirect to the screen with IBAN details data,
b)    delete IBAN – permanent delete IBAN data (more information In IBAN statuses section)

Action	Statuses
	IBAN’s status	Token’s status
Add IBAN	Active	Active
Delete IBAN	Deleted	Deleted

Tokens management

Subsection tokens list

Tokens list contains basic information such as TSP Type, Token ID, Status or Type. This section is available under the following tabs: Customers (screen below), Cards, Devices, IBANs. 

Basic list includes following information:

Parameter	Description
TSP Type	Payment token tsp type.*
Token ID	Internal Verestro Id of Token.
Status	Payment token status (described in token statuses part).
Type	Payment token type.**
Action	Action which can be performed on particular token (described in token actions part).

*TSP Types of payment token:
a)    Mastercard,
b)    Visa. 
**Types of token:
a)    device – type is created after payment instrument digitization for contactless payments,
b)    cloud – type is created after payment instrument digitization for e-commerce payments.

Token details

Selecting a specific token allows to see more detailed data.  

Detailed list includes following information:

Parameter	Description
Date and time	The date/time stamp when status of payment token has last changed represented ISO 8601 format.
Token ID	Internal Verestro Id of Token.
Token Unique Reference	Token unique reference. Exists if tsp type is MASTERCARD.
Status	Payment token status.
Type	Payment token type.
TSP Type	Payment token tsp type.

Tokens statuses

Tokens action

Customer can perform the following actions on the token:
a)    view token, 
b)    suspend token, 
c)    unsuspend token, 
d)    delete token. 

Below table presents how action may change the statuses of token.

Action	Token’s status
Digitization	Inactive
Provisioning	Active
Suspend token	Suspended
Unsuspended token	Active
Delete token	Deleted

Referring to the above table, a diagram has been created showing the change of states of the token. This allows for better visualization of actions and dependencies between them.

Devices management

Devices list

Devices list contains filters and columns with dates. The filters are used for dynamic searching, such data as:  device ID, producer, creation date, deletion date, status (available: inactive, active, locked, deleted). 

Basic list includes following information:

Parameter	Description
Device ID	Unique identifier of app installed on device.
Device name	Description of phone device model.
Version	Version of operating system.
Producer	Description of phone device manufacturer.
Status	Device status (described in device statuses part).
Actions	Action which can be performed on particular token (described in token actions part).

Devices details

Selecting a specific device allows to see more detailed data. In addition to basic information, a list of related customers, and payment history is available.  

Detailed list includes following information:

Parameter	Description
Device ID installation	Unique identifier of app installed on device.
Producer	Description of phone device manufacturer.
Device name	Description of phone device model.
Device version	Version of operating system.
Created at	Creation date greater than specified date or equal. Format Y-M-D.
Deleted at	Deletion date greater than specified date or equal. Format Y-M-D.
Status	Device status.

In details there are available aggregates related to the particular device:
•    customers (more information in customers management),
•    customer tokens (more information in tokens management),
•    payment history (more information in payment history).

Device statuses

Device actions

Admin can perform the following actions on the particular device:
a)    view device – redirect to the screen with device details data,
b)    lock device – lock of device. None actions on this device are possible 
c)    delete device – permanent delete device data. 

Below table presents how action may change the statuses of device

Action	Statuses
	Device’s status	Token’s status
Add device (not paired yet)	Inactive	-
Pair device	Active	-
Lock device	Locked	Suspended
Unlock device	Active	Active
Delete device	Deleted	Deleted

Referring to the above table, a diagram has been created showing the change of states of the device token. This allows for better visualization of actions and dependencies between them.

Payment history

Payment history list

Payment history list contains filters and columns with dates. In this section actions don’t occur. The filters are used for dynamic searching, such data as: Card ID, amount, currency, date of transaction, status (available: cleared, declined, authorized, reversed). The date displayed in both the transaction list and details is in UTC+0 and ISO8601 compliant. Also, the filters are selected by the user in UTC+0. At no time is there a conversion to the local time zone of the portal operator. 

Basic list includes following information:

Parameter	Description
Transaction ID	Internal Verestro transaction identifier.
Card ID	Internal Verestro Id of Card.
Created at	The date/time when the transaction was made. In ISO 8601 extended format.
Amount	The transaction monetary amount in terms of the minor units of the currency.
Currency	3-character ISO 4217 currency code of the transaction.
Status	Transaction status (described in transaction statuses part).

Payment history details

Selecting a specific payment history allows to see more detailed data. 

Detailed list includes following information:

Parameter	Description
Transaction ID	Internal Verestro transaction identifier.
Token ID	Internal Verestro Id of Token.
Card ID	Internal Verestro Id of Card.
IBAN ID	Internal Verestro Id of IBAN.
Created at	The date/time when the transaction was made. In ISO 8601 extended format.
Amount	The transaction monetary amount in terms of the minor units of the currency..
Currency	3-character ISO 4217 currency code of the transaction.
Status	Transaction status.
Decline reason	Additional information provided by the issuer for a declined transaction.*
Customer ID	Internal Verestro customer identifier.
External ID	External customer identifier provided by client (for example: recordID).
E-mail	Customer e-mail address.
Phone number	Customer phone number.
Transaction channel	Information about transaction channel. One of: [CONTACTLESS, CLOUD, MONEYSEND].
Merchant name	The merchant ("doing business as") name.
Merchant postal code	The postal code of the merchant.
Transaction country code	The country in which the transaction was performed. Expressed as a 3-letter (alpha-3) country code as defined in ISO 3166-1.
Type	Transaction type.**

*Type of declined transactions:
a)    invalid card number,
b)    format error, 
c)    maximum amount exceeded, 
d)    expired card, 
e)    PIN authorization failed, 
f)    tranaction not permitted, 
g)    exceeds withdrawal amount limit, 
h)    restricted card, 
i)    exceeds withdrawal count limit, 
j)    allowable number of PIN tries  exceeded, 
k)    incorrect pin, 
l)    duplicate transmission detected. 
**Type of transactions:
a)    purchase transaction, 
b)    refund transaction, 
c)    payment transaction, 
d)    ATM cash withdrawal, 
e)    cash disbursement, 
f)    ATM deposit, 
g)    ATM account transfer. 

Transaction statuses 

Each transaction has a transaction id given by the client, a type and a status. In payment systems, when a transaction is of type REFUND, it has the same id as a transaction of type PURCHASE. Therefore, the unique key is(the id given by the customer and the transaction type). Transaction amounts are stored in the system as a minor(1.25 to 125). 
Each transaction has a type that can have different statuses. Immediately after a transaction is executed, it may receive one of the following statuses:

Parameter	Description
AUTHORIZED	The transaction was authorized correctly. The funds in the Cardholder's account are blocked and an amount of the same value is "promised" to the Merchant. No transfer of funds is performed at this time.
DECLINED	The transaction was declined. No funds are blocked/transferred from Cardholder's account.

For a transaction authorized correctly (AUTHORIZED), the following scenarios are possible. It may go into status:

Parameter	Description
REVERSED	The transaction is reversed, e.g. due to an error reported by Merchant. The lock is lifted and the funds remain on the Cardholder's account. No transfer of funds is performed.
CLEARED	The transaction was settled correctly. The funds in the Cardholder's account are unblocked, and are then transferred to the Merchant's account. The block on the Cardholder's account becomes a debit, and the "promised" funds become a credit on the Merchant's account.

Referring to the above tables, the possible transition of transaction states is presented in the diagram below.

Operator administration

Default privileges per role in the portal

Below are the default function settings for described product divided into areas.

Aggregate	Action	Admin	Manager	Employee
Customers - Cards	View	x	x	x
	Delete	x	x	-
	Block	x	x	-
	Unblock	x	x	-
Customers - Endusers	View	x	x	x
	Edit	x	x	-
	Delete	x	x	-
	Lock	x	x	x
	Unlock	x	x	x
Customers - Devices	View	x	x	x
	Lock	x	x	x
	Unlock	x	x	x
	Delete	x	x	-
Customer -  Tokens on details of Endusers/Devices/Cards	View	x	x	x
	Suspend	x	x	x
	Unsuspend	x	x	x
	Delete	x	x	-
Customers - Payment history	View	x	x	x
Customers - Reports	View	x	x	-
	Generate	x	x	-

Reports

Payment history report

Payment history reports use the same filters that are used to select the payment history list. After applying the appropriate set of filters (Card ID, amount, currency, data range and status) it is possible to generate a report that will include the records displayed in the list. 
Clicking the "Generate transactions report" button launches the generation mechanism. If the generation request was successful a popup is displayed at the bottom of the panel informing about the start of work (image below). In case of an error caused by missing data in the specified filter range the message "Cannot find transactions to generate the report" is displayed.

When user opens the "Reports" tab, a list of reports is displayed. It contains ready to download output files (.xlsx) in Ready status and information about reports currently being processed - In_Progress.

The report file contains the following columns:

Column	Description
Transaction ID	Internal Verestro transaction identifier.
Payment token ID	Internal Verestro token identifier.
IBAN ID	Internal Verestro IBAN identifier.
Card ID	Internal Verestro Id of Card.
Card last four digits	Last four digits of card, which has been used to process transaction.
Created at	The date/time when the transaction was made. In ISO 8601 extended format.
Amount	The transaction monetary amount in terms of the minor units of the currency.
Currency	3-character ISO 4217 currency code of the transaction.
Status	Transaction status (described in transaction statuses part).
Issuer response information	Additional information received from Issuer in context of transaction.
Customer ID	Internal Verestro customer identifier.
Customer external ID	External system customer identifier.
Customer email	Customer email address in format alias@domain.
Customer phone number	Customer mobile phone number with prefix.
Transaction channel	Type of transaction channel used to perform the transaction.
Merchant name	The merchant ("doing business as") name.
Transaction country code	3-character ISO 3166-1 country code of the transaction.

By default, both report generation and report retrieval are unlimited, meaning that any role can use this functionality in an unlimited way. If there are reasons to limit e.g. only Administrator to generate reports and allow everyone to view them - please let us know during project configuration stage. 

Finance Administration Panel Overview

The Finance Administration Panel  is the essential tool for you to work with your online application. Here you can manage balances for both corporations and endusers and generate virtual cards also. The presented solution is prepared for rebranding for the client's brand. The document is divided into sections that describe the various components of the system. Each section contains a screen presenting the functionality and a detailed description of the states occurring in it.

Purpose and scope

This product guide provides a high-level overview of Admin Panel Finance section. This document covers the following topics:

Terminology

This section explains a number of key terms and concepts used in this document.

Name	Description
Customer, Partner	Customer who uses MPA.
Operator	User using the Admin Panel.
Balance	Representation of funding collection in specific currency.
Session token	Access to the system by a web application user is secured using a session token to uniquely associate the session with the user. It is required to perform any action.

Customer Balance

Customer balances can be managed from End user detail view, in "Balance" tab. 

Balance table provides following information:

Parametr	Description
Balance ID	Unique virtual wallet ID.
Currency	Currency for given balance in ISO 4217 format.
Balance	Amount of funds available on balance.
IBAN	IBAN for given balance. It is hidden by default and can be viewed after clicking "Reveal" button.

Add new balance

Operator can create new balances with "Add new balance" button. After clicking it, operator should choose currency for new balance from dropdown list. Newly created balance is visible on Balances list right away.

Balances can be created for any currency. However cards can be created only for currency compliant with End user balance currency and currency configured in terminal for given project.

Balance detail view

Balance detail view can be entered by click on a row in Balance table, described above.

Page consists of 3 sections:

1. Details
Contains Balance ID, Balance Currency and Balance Amount and IBAN.

2. List of cards
Contains all cards assigned to given balance along with informations: Card ID, Activation date, Expire date, Type and Processor ID.

3. Statements
A list of statements generated for given balance. Automatycznie generowane i dodawane, co miesiąc.

Generate card

Feature enables Operator to create a virtual card. After clicking "Generate card" a popup with list of terminals configured for Partner is shown. Operator should choose terminal with currency corresponding to end user balance currency. Generated virtual card is verified right away.

Change balance

Operator with Admin role can change end user balance using "Change Balance" button.

1. Select type:
   a) credit - increase balance
   b) debit - decrease balance
2. Select transaction type (described below).
3. Enter transaction amount.
4. Enter transaction description.
4. Add transaction ID (optional).
5. Click 'Confirm'.
Balance is changed right away.

Type	Transaction type	Description
Credit	Cashback	Internal transaction for a Partner who wants to top up the user's balance as part of the loyalty program. Antaca automatically debits the credit Master balance with this transaction.
	Loan	Internal transaction for a Partner who want to top up end user's balance as part of the credit agreement. Antaca automatically debits the credit Master Balance with this transaction.
	Payment	Internal transaction type used to top up the user's balance. This type indicates that the funds come from the antaca system, usually in conjunction with a funding type a debit transaction on the user's balance. Antaca automatically debits the credit masterbalance with this transaction.
	Top up	Internal transaction type used to top up end user balance. This type indicates that the funds come from outside the antaca system, e.g. payment to an account at a bank branch. Antaca automatically debits the credit masterbalance with this transaction.
Debit	Commission	Internal transaction for a partner who wants to debit user balance as a fee. Antaca automatically credits company balance with the funds debited from end user balance.
	Fee	Internal transaction for a partner who wants to debit user balance as a fee. Antaca automatically credits company balance with the funds debited from end user balance.
	Funding	Internal transaction type used to debit the user's balance. This type indicates that the funds still remain in the Antaca system, usually in conjunction with a credit type transaction on the user's balance. Antaca automatically credits the credit Master Balance with this transaction.
	Withdrawal	Internal transaction type used to debit end user balance. This type indicates that the funds go outside of Antaca system, e.g. withdrawal from an account at a bank branch.

Delete balance

Operator with Admin or Manager role can delete end user balance on balance detail view. Option is available only for balances equal to 0.00 and all transactions are cleared. Deleted balance is no longer visible in the End user's Balances tab. All cards assigned to deleted balance are deleted as well.

Master balance

Master Balance page contains 3 sections:

1. Deposits/ Credits - includes a list of Master Balances created for Partner with amount of funds and currency.

2. Filters - allow searching for transactions specific for given time frame, type (credit or debit), amount and transaction title.

3. List of transactions - list of transactions generated for selected Master Balance.

List includes following information:

Parametr	Description
Transaction date	Transaction date in YYYY-MM-DD format and 24 hour format (UTC+0).
Title	Title of transaction.
Amount	Amount of transaction with currency code.
Type	Type of transaction. Available values "Debit" and "Credit".

BIN sponsor can perform 'Change balance' action. Operator should do following actions:

1. Select proper Master balance.
2. Select "Change balance" button.
3. Select transaction type.
4. Enter transaction amount.
5. Enter transaction description.
6. Add transaction ID (optional).
7. Click "Confirm".

This action results in Master Balance change and saving transaction in "List of transactions" table.

Operator with any role can use 'Generate report' functionality.

Balance

Balance page provides information on how much money Partner should have on their bank account to ensure money liquidity on their project. It combines totals of end users' balances and partner balances for chosen currency. 
For projects using credit Master Balance, "Bank account" should be equal to sum of credit Master Balance end users' balances and partner balances for chosen currency.
For project using deposit Master Balance, "Balance" page should not be visible.

Manual clearings

Manual clearings page shows all transactions registered in Antaca and settlements generated in payment network.
Manual clearings enable Operators with Admin role to clear transaction whish were not cleared automatically.

Page is divided into two sections:
1. Transactions
Operator can filter transactions using following filters: Date from, Date to, Terminal, Transaction ID, Customer ID, Card ID, Type, Status
Table below filter section presents following information:

Parametr	Description
Transaction ID	Transaction identifier obtained from acquirer.
Description	Transaction description.
Card ID	DataCore card ID.
Type	Type of transaction
Amount	Transaction gross value.
Transaction date	Transaction date in YYYY-MM-DD format and 24 hour format (UTC+0).
Status	Transaction status. Available values: Authorized, Cleared, Reversed.

2. Settlement

Operator can filter settlements using following filters: Date from, Date to, Terminal, Transaction ID, Customer ID, Card ID, Status, Processed.
Table below filter section presents following information:

Parametr	Description
Transaction ID	Transaction identifier obtained from acquirer.
Description	Transaction description.
Card ID	DataCore card ID.
Amount	Transaction gross value with currency.
Transaction date	Transaction date in YYYY-MM-DD format and 24 hour format (UTC+0).
Processed at	Settlement clearing date in YYYY-MM-DD format and 24 hour format (UTC+0).

Manual clearing page provides 'Clear transaction' functionality for BIN Sponsors. To clear transaction, Operator with Admin role should perform following actions:
1. Select one or many transactions to be cleared.
2. Select settlement to be linked with transactions chosen in step 1 (this step is optional).
3. Click 'Clear transactions' button at the right top of the page.
Transactions status is changed to 'Cleared'. Settlement chosen in second step will have 'Processed at' parameter set to the date of clearing.

Partner accounting

Partner accounting page was created to present information about Partner's profits for given project. It contains a list of transactions such as fees, intercharge, fx conversion, and transactions generated manually by BIN Sponsor. 

Page is devided into 3 sections:

1. Company balance - list of Partner balances.

2. Filters - allow searching for transactions specific for given time frame and type (credit or debit).

3. List of transactions

Parametr	Description
Transaction date	Transaction date in YYYY-MM-DD format and 24 hour format (UTC+0).
Title	Transaction description.
Amount	Transaction gross value with currency.
Type	Transaction type. Available values: Credit, Debit.

Operator with Admin role can perform 'Generate a transaction'. To generate a transaction Operator should do following actions:

1. Select proper company balance.
2. Select 'Generate a transaction' button.
3. Select transaction type.
4. Enter transaction amount.
5. Enter transaction description.
6. Add transaction ID (optional).
7. Click 'Confirm'.

Operator with any role can use 'Generate report' functionality. Maximum time range for reports is 3 months.

AML User lock

AML User lock enables Operator with any role to lock a resource which doesn't comply with AML regulations. This lock will disable end user cards and balances and can be created only for ens users with accepted KYC application.

Page is devided into 2 sections:
1. Filters - allow browsing locked resources by their type (e.g. Customer), ID and Lock reason.
2. List of locked resources.

Parametr	Description
Blocked resource	Shows blocked resource type.
Resource ID	Verestro ID for given resource.
Reason	Available values: Any, Document expired.
Action	Available actions: Remove the lock.

Remove the lock option is available only for Operator with Admin role.

New lock can be created using "New lock" button in the top right corner of the page. After clicking it, a popup appears:

After entering Blocked resource, ResourceID and Reason for lock, newly added lock is visible in the list of locked resources.

To remove the lock, Operator should click on Action menu on lock's list and select "Remove the lock".

Lock will be removed from the list instantly.

Default privileges per role in the portal 

Below are the default function settings for described product divided into areas.

Area	Action	Admin	Manager	Employee
Customer Balance	View Company Balance	x	x	-
	Create Customer Balance	x	x	-
	View Customer Balance	x	x	x
	View Customer Balance Details	x	x	x
	Topup Customer Balance	x	-	-
	Delete Customer Balance	x	x	-
Customer	Delete Customer	x	x	-
Master Balances	View Master Balance	x	x	-
	Edit Master Balance	x	-	-
KYC	View KYC applications	x	x	-
	Update KYC applications	x	x	-
Cards	Create virtual card	x	x	x
	View cards	x	x	-
	Delete cards	x	x	-
	Create Card Limit	x	x	x
	View Card Limits	x	x	x
	Update Card Limits	x	x	x
	Delete Card Limits	x	x	x
	Generate CVV	x	x	x
Clearing	Manual clearing	x	-	-
	Manual reversal	x	-	-

KYC Panel Overview

The KYC Administration Panel  is the essential tool for you to work with your online application. Here you can manage Know Your Customer applications. The presented solution is prepared for rebranding for the client's brand. The document is divided into sections that describe the various components of the system. Each section contains a screen presenting the functionality and a detailed description of the states occurring in it.

Terminology

This section explains a number of key terms and concepts used in this document.

Name	Description
Customer, Partner	Customer who uses MPA.
Operator	User using the Admin Panel.
Balance	Representation of funding collection in specific currency.
Session token	Access to the system by a web application user is secured using a session token to uniquely associate the session with the user. It is required to perform any action.

KYC

KYC (Know Your Customer) page enables Operator with Admin role to manage end users' verification applications. Customer application page consists of:

1. Filters section - application can be filtered by Customer ID, date of creation and status.

2. Lists of applications

Parametr	Description
ID	KYC application ID.
Customer ID	End user ID given by Verestro.
First name	End user first name.
Last name	End user last name.
Status	KYC application status. Available values: In progress, Accepted, Rejected.

After clicking on a row of the list, Operator is navigated to KYC application detailed view.

In Details section all informations provided by end user are presented. Some of the data can be edited regardless of KYC application status [?]. Pencil icon indicates editable data.

Below Details section Operator can find documents attached to KYC application. Files can be added by end user during KYC process or by Operator with "Drag and drop" functionality available below files list. Admin Panel support following file formats: pdf, jpeg, png and jpg. Each file size is limited to 2 MB.

At the right bottom corner of the page Operator with Admin role can see 3 buttons to change KYC apllication status:
1. Success - changes KYC application status to "Accepted"
2. Fail - changes KYC application status to "Rejected". End user has to create new KYC application.
3. Block - changes KYC application status to "Rejected". End user cannot create another KYC application.

When changing KYC status to "Success" Operator has to select Risk Level for given end user, selecting one of folloing values: Low, Medium, High.