UniPay Directory Structure

Top Level Resources:


Name Type Description
$app-home Virtual Root folder for UniPay installation
$ftpgates-root Virtual Root folder for FTP Gates's batch service. All file exchanges occur through this folder.

Files to be sent to Providers are placed in respective sub-folders and are subsequently processed by UniBroker or by UniPay. Tokenization results are placed in respective sub-folder by UniBroker for further consumption by UniPay.
$profiles-home Virtual Stores build profiles and associated resources necessary for the application deployment.
$sources-home Virtual Root directory for the repository with the source code (currently GIT).
$telium2-root Virtual Root directory for the entire file structure inside the terminal from the Tellium2 family. This directory can contain 5 applications.
$unibroker-home Virtual Root folder for UniBroker installation
$unibroker-root Virtual Root folder for UniBroker's batch service. All file exchanges occur through this folder.

Files to be sent to Providers are placed in respective sub-folders and are subsequently processed by UniBroker. Results are placed by respective sub-folders by UniBroker for further consumption by UniPay.

Resource Types:


Directoryphysical directory on server's hard drive
Filephysical file on server's hard drive
Virtualvirtual directory, which maps to a physical directory, name and location of which are determined by the deployment conditions and requirements


1000
($app-home/resources/paypage/1000)
Added On:  11/12/12
Status:  Active
Type:  Directory
Parent:  paypages
Stores default versions of payges used in the PayPage mechanism.

If there is a need to customize look and feel of PayPage for specific business needs, a subfolder with merchant or merchant account code should be created, e.g:

$app-home\resources\pages\2002\paypage.html - for the account with code 2002;
$app-home\resources\pages\2000\paypage.html - for all accounts of a merchant with code 2000.

Contents:


Name Type Status Description
resources Directory Active Stores files used for the paypage's customization (CSS, images, scripts, etc).
paypage_account.html File Active Form used for sale, sale-auth and credit operations done with bank accounts.
paypage_card.html File Active Form used for sale, sale-auth and credit operations done with payment cards.
result.html File Active Default page shown to a user once an operation is successfully completed.
tokenization_account.html File Active Form used for tokenization operations done with bank accounts.
tokenization_card.html File Active Form used for tokenization operations done with payment cards.