Business Intelligence Platformtillpayments.com/documents/Business Intelligence Platform User Guide.pdf3.1 My Dashboard No matter which page in BIP a user is in, a click on My Dashboard

Business Intelligence Platform

W W W . T I L L P A Y M E N T S . C O M

USER GUIDE

Table of Contents1. Business Intelligence Platform (BIP)

2. Log In Security and Access Control

2.1 Security #1: Creating a Strong Password

2.2 Security #2: Session Time-Out

2.3 Security #3: Unauthorised Log In Attempt or Lost Password

2.4 2FA: Two Factor Authentication

2.5 Set up of Google Authenticator

3. The Dashboard

3.1 My Dashboard

3.2 My Preferences

3.3 Add Widget

4. Widgets

4.1 Chargeback Overview Widget

4.2 Risk Overview Widget

4.3 Rejection Rates Widget

4.4 Transaction

4.5 Channel Count Widget

4.6 Maintenance Widget

5. Transactions

5.1 Transaction Search and View

5.2 Transaction Details

5.2.1 Transaction Details: Customer Information

5.2.2 Transaction Details: Action

5.2.3 Transaction Details: Processing

5.2.4 Transaction Details: Connector Result

5.2.5 Transaction Details: Transaction Log

5.2.6 Transaction Details: Advanced

5.2.7 Transaction Details: Risk Intelligence/Validation

Page 4

Page 5

Page 5

Page 6

Page 6

Page 6

Page 6

Page 7

Page 8

Page 8

Page 8

Page 9

Page 9

Page 9

Page 9

Page 10

Page 10

Page 10

Page 11

Page 12

Page 13

Page 13

Page 13

Page 14

Page 15

Page 15

Page 16

Page 16

Table of Contents6. Blacklist Menu

6.1 Account Blacklist

6.2 BIN Blacklist

6.3 IP Blacklist

6.4 Email Address Blacklist

7. Virtual Terminal

7.1 Virtual Terminal

7.2 Accessing Virtual Terminal

7.3 Entering Payment Data

8. Glossary

8.1 General

8.2 Entities

8.3 Payment Methods

8.4 Transaction Types

8.5 Transaction Status

8.6 Transaction Status Codes

8.7 Reason Codes

8.8 Return Codes

8.9 Chargeback (CB)

8.10 Chargeback Tools

8.11 Entity State

8.12 3-D Secure

8.13 Risk Management

8.14 Upload Descriptors

8.15 Upload Status Descriptors

Page 17

Page 17

Page 18

Page 18

Page 19

Page 19

Page 19

Page 19

Page 19

Page 20

Page 20

Page 20

Page 20

Page 22

Page 24

Page 25

Page 25

Page 25

Page 25

Page 25

Page 25

Page 25

Page 25

Page 27

Page 27

1. Business Intelligence diPlatform (BIP)Our Business Intelligence Platform (BIP) is a graphical user interface of our backend system. The platform is a powerful tool for:

Payment Processing

Risk and fraud management

Integration Interfaces

Configuration

Monitoring

Analysis

4 Business Intelligence Platform User Guide

Username

Login Button

Password

Forgot your password link

2. Log in Security and Access ControlFor security purposes, you will receive your username, a first password and your log-in hyperlink in separate emails. A click on the hyperlink will take the user to the BIP which will prompt the user to select their preferred language from the drop-down menu then you are able to login.

2.1 Security #1: Creating a strong passwordOnce the user has logged in with the credentials that were emailed, they will be directed to anew window which will be setting a new password. The new password must meet thefollowing criteria:

1At least 8-24 characters long and must contain a combination of num-bers and letters;

2Passwords must be changed every six (6) weeks

3Passwords must be different from the user last four (4) passwords


2.2 Security #2: Session time-outBy default, users will be securely logged out of BIP within 30 minutes of inactivity when which the user will simply need to login again.

2.3 Security #3: Unauthorised log-in attempt or lost passwordIn the event that the user forgets their password, they can click on the Forgot your password hyperlink which will have their credentials sent to their email. For added security, access to a BIP account will be automatically restricted if they have failed to input the correct credentials after three consecutive attempts. If a user has been locked out of their BIP account, they must contact Till Payments at [email protected] to have their password reset.

2.4 Two Factor AuthenticationThe third layer of security when accessing BIP is the two-factor authentication process. This is only for users who have either administrator, operator or account access. Users with these types of account access will be required to use a one-time code that is generated by the Google Authenticator phone application.

2.5 Set up of Google Authenticator

Insert username here

Request Email button

Download the Google Authenticator app onto a smart phone device (Note: the device that is registered with Google Authenticator is where

the one-time codes will always be sent)

An email will be sent to the user with a link that will direct them to register their chosen mobile device. It will also provide them with a QR code that users will

need to scan to complete the registration.


Bank MID field

Bank TID field

On the dashboard there is also a menu, where they are able to access Trans-actions, Analysis, Administration, Risk Management, Batch Processing, Black-list and Monitoring.

3. The DashboardOnce logged into BIP, users are taken to ‘My Dashboard’. At the top right of the window, you will see My dashboard, My preferences, Documentation and Logoff.

Users are able to configure the layout of their dashboard by clicking add widget.

Users can add multiple widgets and organise them according to their viewing preference. To open a widget, click on the title of one the widgets and the information will drop down.


3.1 My DashboardNo matter which page in BIP a user is in, a click on My Dashboard will take the user back to thedashboard for a total overview.

3.2 My PreferencesMy Preferences will allow a user to configure their dashboard language, how many transactions per page, their preferred time zone and to change their password.

Select the number of transactions

Change time zoneChange password

Set default search timeframe

3.3 Add WidgetTo add a new widget, click on ‘add widget’ on the dashboard. This will open a pop-up window with drop-down menus for you to choose from a variety of widgets. You are able to add the same widget multiple times. E.g. if you want to compare data against different time frames. To rearrange the widgets, simply hold and drag the widget to where you want to place it.

To add a widget, tick the box and press ‘Add’ in the bottom right corner.


4. Widgets4.1 Chargeback Overview WidgetWith the Chargeback Overview Widget, you can compare the chargeback counts and volumes of current versus last month. Time span and currency can be select from dropdown lists. You can add this widget several times and place them side by side e.g. to compare a chargeback overview in EUR with an-other on in USD.

4.2 Risk Overview WidgetRisk Overview counts the average of risk checks done per channel (plus the current daily total of all transac-tions, risk checks and rejected transactions).

4.3 Rejection Rates WidgetRejection Rates lists all rejected transactions by bank, risk and validation. Depending on the chosen time frame. It compares rejections from today versus yesterday, but also from current versus last week or month. All changes appear in percentage and absolute count.


4.4 TransactionCount / How Many Transactions Widget A Transaction Count / How Many Transactions widget counts all the transac-tions. You can configure the time frame by clicking on the settings icon in the top-right corner of the widget and select either day, month or year.

4.5 Channel Count WidgetThe How Many Channels widget counts all divisions, merchants and channels already configured which helps you identify how many channels are active.

4.6 Maintenance WidgetThe Maintenance widget lists all previous release updates and linked them to a PDF file with more detail. It also announces upcoming releases and updates. This tool can be used to track and record your complete update history and have always have it readily accessible.


5. TransactionsThese tools help the user search for, view and modify all transactions in detail. This menu will also allow the user to adjust, test, change or even block a transaction. Users are also able to export transaction data for analysis.

Transactions can be identified using various filters such as time and date ranges, currency, transaction ID or payment method. Use the drop-down menu to choose the desired filter and press on Search in the bot-tom right corner to access the transaction data you are after. Users can use multiple filters to narrow down their search and they can remove filters by click on Delete or to delete all the filters, click on Reset.

Input date and time

Sort by various time and date ranges

Search button

Reset searchSearch by

type options


5.1 Transaction Search and ViewOnce the user has made their search, all the transactions that match the filters are presented in list view. Users can change the view to aggregated view e.g. sorted by different payment methods by clicking on Switch to aggregated view (1). Transaction data can also be saved or printed by clicking on the icons indicated below (2). Transaction data can be copied to a clipboard and pasted elsewhere by clicking on the icon shown below (3).

Switch to aggregated view buttton

Save or print button

Copy transaction data button


5.2 Transaction DetailsTo see all further information for a particular transaction, the user should click on the transaction which will open a pop-up window. In this pop-up window, there are six tabs that categorise the transaction details which will make it easier for the user to locate the specific information they are after.

5.2.1 Transaction Details: Customer InformationThe first tab, Customer Information, shows the user customer specific details such as card or account holder name, card type/brand, address and contact information. This tab also 12 shows the user the cli-ent’s frontend URL.

5.2.2 Transaction Details: Action

The second tab, Action, allows a user to initiate transaction Refund, Rebill or to trigger an internal action such as Receipt or Chargeback. Users can also define a Presentation Amount or Other Amount.If the transaction (debit/charge) has already been processed and exported to the receiving connection, only a refund can be triggered. Refund is a payback to the shopper’s payment instrument (e.g. credit card or bank account). A transaction successfully refunded should appear as a credit transaction on the shopper’s account statement. A rebill is needed to process a successful transaction again or to make a subscription payment (fully automatable with our system).

Second tab: Actions

Amount field


5.2.3 Transaction Details: ProcessingThe third tab, Processing, informs users on a transaction’s source and identification(merchant, internal and towards clearing network). It also gives you clearing information anddetails on a transaction’s result, broken down into Header, Transaction, Identification andProcessing.

Third tab: Processing


5.2.4 Transaction Details: Connector ResultThe fourth tab, Connector Result, the user will find a full record of all acquirer/sender/bankresponses involved. The Connector log entry helps you verify whether all of the dataassociated with a specific transaction have reached their destination e.g. acquirer or bank.The connector log entry will also indicate whether all transaction relevant IDs and URLs arecorrect or which time stamps were created.

The below example shows the connector log entry of a transaction including three individualreceiver (connectors) transaction IDs. To print or save this log, click on the icons as indicated below.

Fourth tab: Connector Result

Connector log entry


5.2.5 Transaction Details: Transaction LogThe fifth tab, Transaction Log, shows the user the full transaction history including XML code and timestamps of internal module and external system interactivities.

Fifth tab: Transaction log

Example of datestamp/timestamp


5.2.6 Transaction Details: Advanced

The last tab, Advanced, shows the user additional information on the merchant account. A single click on Show will open a new window with the account settings, whereas Edit will lead to the Administration section to change these settings.

5.2.7 Transaction Details: Risk Intelligence/ValidationCompleted Risk Checks (if activated in risk management) appear in the Risk Intelligence/Validation tab. The risk management menu described in chapter 4 shows you how to monitor, modify, activate and deactivate a variety of risk checks.

Sixth tab: Advanced

Edit button


6. Blacklist MenuThis menu allows you to blacklist either accounts, BINs, IPs, or e-mail addresses. If an account is blacklisted (and the corresponding risk check is activated) all transactions by this account will be blocked. It is also possible to whitelist BINs and IPs or to search for these black- or whitelisted BIPs and IPs. The section falls into the four blacklists: Account, BIN, IP and E-Mail Address.

Blacklist options

6.1 Account BlacklistThe following illustration shows the Account Blacklist screen. To find a blacklisted account, select an account type, fill in holder and card number and select a brand from the right drop-down list. Click Search to see the results or click Reset to clear the fields. Click the Add button to blacklist a new account.

The next screen shows the pop-up to add such an account to a blacklist. Once the data has beensubmitted, the account will be blocked for all further transactions. The handling is almost identical to the search screen before. The only difference is that you have to select a reason, fill in a description and click Submit to save your changes.

Select Account Type‘Holder’ Field

‘Card Number’ Field

Reset Button

Search Button

Add button

‘Brand’ drop down


6.2 BIN BlacklistThis submenu allows you to blacklist or whitelist certain BINs (e.g. to block transactions only of a specific country). The BIN Blacklist main screen gives you three options: To search for existing entries, select a BIN kind and type from the drop-down lists and click Search. Click Download and store an already existing entry to your computer. To replace an existing entry with a new list, click Upload, select a BIN kind and type from the drop-down lists, browse your computer for the needed file and click Import (all existing BIN lists will be replaced).

6.3 IP BlacklistThe main screen of this submenu helps you search for existing entries and upload new lists to replace them.

6.4 Email BlacklistThe main screen of this submenu allows you to search for existing entries and upload new lists to replace them. All functions work almost identically as with the BIN and IP blacklist menus before.

BIN type Type drop down

Search button

Upload button

Email Address Field

Search button


7.1 Virtual Terminal

The Virtual terminal option allows users to manually generate transactions for all available payment meth-ods and types.

7.2 Accessing Virtual TerminalOnce the user has logged in, Virtual Terminal will be accessible via the dashboard. Click on Virtual Terminal. Once the Virtual Terminal has been selected, a second window will appear. To ensure thecorrect Virtual terminal is in use the second entity will need to be selected.

7.3 Entering Payment DataEnter payment data in the required fields and select currency from drop down. Credit Card obliges you to fill in card number, expiry date, holder name, and CVV. Once details have been entered, click Pay Now.

7. Terminal Menu

Pay now button

Enter card details in the fields

Shopper ID field

Currency drop downEnter ($) amount

Transaction ID field


8. Glossary8.1 General

PSP Payment Service Provider

WPF Web Payment Frontend

SSL Secure Sockets Layer

PCI DSS Payment Card Industry Data Security Standard

BIN Bank Identification Number

AVS Address Verification Service

CSV Comma-Separated Values, a simple file format for tabular data

VbV Verified by Visa

MSC MasterCard Secure Code

8.2 Entities

A Division, a Merchant, or a Channel (usually one client is one merchant). You can create different channels to separate transactions within one client (different countries, currencies, subsections etc.). Divisions can also group merchants (e.g. ecommerce/gambling merchants) to ease billing etc.

Merchant Account: Needed for processing and connecting to banks, risk management providers, acquirers etc. Defines where merchant transactions from the same entity are sent to (bank, acquirer etc.), if configured respectively. Can also be used for any lower entities.

8.3 Payment MethodsCredit Card (CC): Payment card issued by a credit card company and often distributed by licensed banks to customers for buying goods and services. The endcustomer’s credit card is debited with the payment amount. In regular intervals the customer receives an invoice from the credit card issuer.

Direct Debit (DD): The merchant collects money from the bank account of the customer. This usually requires in general an authorization by the customer in any form. Online, the customer electronically gives the merchant the collection authorization, the merchant directly debits the customer account. Providers of direct debit payment are banks that accept this method of payment. Direct debit basically works the same offline as online. As there is no security measure such as entering a PIN or signing a document, direct debit is not considered legally binding, which is why the customer can relatively easily revert the payment. This is one reason why this method is so popular with customers.


8.3 Payment Methods (continued)

Pre-Payment (PP): With the prepayment method, the merchant provides his goods or services to the cus-tomer only after receiving the money. The end customer receives all the credit transfer details necessary from the merchant and transfers money to the bank account of the merchant. The incoming money is matched manually or automatically and subsequently the goods or services are delivered to the end cus-tomer.

Invoice (IV): The customer purchases something on account and pays after being invoiced. This is possible in combination with other methods of payment (cash, cheque, electronic money transfer etc.).

Credit Transfer (CT): The customer transfers money to the bank account of the merchant directly from his banking account. Credit transfer over the Internet 18 (conventional method of payment: invoice, prepay-ment). The importance of internet credit transfers is rising as online banking booms. Customers are famil-iar with this payment method in the form of conventional offline credit transfers. Confirmationhappens through entering the account number plus PIN/TAN

Virtual Account (VA): The customer first credits and then debits a virtual accountwithin the merchant shop. The account can be credited with all methods above and isusually debited with micro amounts.

Debit Card (DC): The customer’s debit card is debited with the payment amount. Only if the customer account is in sufficient funds, the transaction is authorised. A debit card (also known as a bank card or check card) is a plastic card that provides the cardholder electronic access to his or her bank account(s) at a financial institution. Some cards have a stored value with which a payment is made, while most relay a message to the cardholder’s bank to withdraw funds from a designated account in favor of the payee’s designated bank account.

Online Transfer (OT): Offers merchants a real-time payment method (publicized as virtually risk-free) to accept internet payments. The level of security depends on the participating bank. Some German banks offer two-factor authentication, such as a challenge-response access token based on the chip embedded in the debit card or ATM card. Others, however, offer simpler PIN and TAN based online banking services. No sensitive information is being shared with the merchant, such as credit card or giro account numbers. There is no chargeback right however, which can be considered a disadvantage for the consumer using this payment method. This is considered an advantage to the merchants. The customer performs an online credit transfer via home banking interface. On successful authorisation, the merchant receives an acknowl-edgement.

Risk Management (RM): Also includes risk management checks non-related to a real payment process.


8.4 Transaction Types

PAYMENT TYPES CODE DESCRIPTION

Pre-Authorisation PA

Performs all risk management validations and stores all transaction data for later retrieval. Additionally reserves (blocks) the payment amount on the customer’s credit card. A later Capture (CP) or Credit (CD) with reference to the Pre-authorisation (PA) triggers the actual booking.

Credit CD Credits the customer and debits the merchant account.

Debit DB Debits the customer and credits the merchant account.

Capture CP Captures a preauthorized (PA) amount.

Refund RF

Credits the customer account with a reference to a prior Debit (DB) or Credit (CD) transaction, so the customer’s account statement will show two bookings. Some receivers and senders don’t support Refunds.

Rebill RB

Debits the customer account with a reference to a prior Debit (DB) transaction. Usually rebills an already processed Debit (DB) transac-tion in case of a chargeback or to add more products to an already processed order.

Reversal RV

Reverses an already processed Preauthorization (PA), Debit (DB) or Credit (CD) transaction, so the customer’s account statement will not show the booking. Reversals are possible only until a predefined cutoff time. Some senders and receivers don’t support them.

Chargeback CBA negative booking on the merchant account, usually triggered by a customer or bank returning a Debit (DB) or Rebill (RB) transaction.


REGISTRATION TYPES CODE DESCRIPTION

Registration RG

Initial account/customer registration that later Debit (DB) or Credit (CD) transactions can always refer to (without storing sensitive information in the merchant system). Some registrations contain recurring rules for generating future Debit (DB) or Credit (CD) transactions automatically. For some countries, the direct debit registration generates a PDF mandate.

Re-Registration RR An “update” of account/customer registration data that is changing.

Deregistration DRA process to deactivate a prior registration. All following Debit (DB) or Credit (CD) transactions which reference to the registration will be rejected as soon as the deregistration has been acknowledged.

Confirmation CFSigned copy of a PDF direct debit mandate that “confirms” theregistration for such mandates. Confirmation (CF) transactions areeither generated automatically or by a manual entry process.

SCHEDULING TYPES CODE DESCRIPTION

Schedule SD

Schedules upcoming payment transactions of the same type andamount. Usually one or more SD transactions define a subscriptionpattern. Exact execution parameters and cancellation notice restrictions can be provided within the Job tag group.

Reschedule RSReschedules a prior scheduled job that is already running. Usuallychanges the execution or cancellation notice parameters of a specific subscription.

Deschedule DS Cancels a running job. The cancellation notice becomes effective after the period defined in the Notice tag has elapsed.

Receipt RC

A positive booking on the merchant account, usually triggered by abank returning a Credit (CD) or Refund (RF) transaction, or by acustomer’s credit transfer to the merchant’s bank account. Such areceipt appears especially in conjunction with prepayment or invoice transactions.


8.5 Transaction Status

Rejected (_BANK;_RISK;_VALIDATION): Transaction was rejected (e.g. due to a blacklist) Success: Transaction was proceeded

Holder: Owner of a credit card, account etc

Risk Score: Result of all proceeded risk checks, weighted in risk logic

Unique ID: A globally unique transaction identification number. Usually hidden from the customer in favour of the Short ID (but may be used as well). The format is: <32 digit hex number> (e.g.8a09123487649304df-34501b4ce1000a) and has to be entered exactly like that to be found.

Transaction ID: Transaction identification defined by the merchant. Usually used when a merchant picks transactions from the system to learn more about the processing status. The search entry ‘order-no 123456_’ will find all transactions with that exact ID or starting with the same string (e.g. ‘orderno 123456_1324’). Such an ID search has to be at least 4 digits long

Reference ID: Establishes a direct connection between transactions.

Sender ID: Identification of the merchant (every merchant has one).

Payment Analysis: Real-time tool to analyse aggregated payment data.

Aggregated Export: Tool to download aggregated payment data as CSV or Excel sheet.

Null values: When no is selected (default), the data rows (as shown in the legend) for which all values are zero for the current selection are hidden. Only data rows that have a non-zero value somewhere are shown. When yes is selected, all data rows are included in the chart and in the legend, even if for one such data row all values are zero. This is valid for either Payment Analysis or Chargeback Analysis

Transaction count: Number of a certain processed transaction type.

Transaction volume: Sum of the monetary amount of certain transactions.


8.6 Transaction Status Code

00: SUCCESS

40: NEUTRAL

60: REJECTED_BANK

65: REJECTED_RISK

70: REJECTED_VALIDATION

80: WAITING

90: NEW

8.7 Reason Codes

See http://support.ctpe.net/payment/codes/reasonCodes.jsp for a full list of reason codes. 8.8 Return Codes

These show the result of a transaction. See http://support.ctpe.net/payment/codes/resultCodes.jsp for a full list of return codes.

8.9 Chargeback (CB)This process will return funds to a consumer. Typically, the chargeback process will look like this:

• Merchant’s acquiring bank receives a Request for Information (RFI) from cardholder’s card issuing bank

• Cardholder’s card issuing bank will ask for card transaction’s details.• Acquiring bank will forward RFI asking for copies of supporting documentation.• Acquiring bank will try to defend the chargeback

8.10 Chargeback Tools• Chargeback Analysis: Flexible tool to quickly spot anomalies in the volume and distribution of your

chargeback transactions (also for a drill-down to analyse the causes of such anomalies).

• Chargeback Rate (Volume): The sum of the amounts of successful chargeback transactions for a given grouping and selection, divided by the sum of the amounts of all transactions with positive turnover for the same grouping and selection, given as a percentage.

• Chargeback Rate (Count): The number of successful chargeback transactions for a given grouping and selection, divided by the number of all transactions with positive turnover for the same grouping and selection, given as a percentage.

• Chargeback Volume: The sum of the amounts of successful chargeback transactions for a given grouping and selection, given in the currency of the respective transactions.

• Chargeback Count: The number of successful chargeback transactions for a given grouping and selection


8.11 Entity State

The Merchant /Channel/Division states have following meanings:

• LIVE: The entity is now live. All entities in the hierarchy above this entity also have to be live to allow live processing. Transactions in mode LIVE, CONNECTOR_TEST and INTEGRATOR_TEST are accepted.

• INTEGRATOR_TEST: The entity is in mode INTEGRATOR_TEST. Only test transactions in INTEGRATOR_TEST are accepted.Back-channel transactions are possible - Switch this mode if you want to stop live processing, but you still want to retreive back-channel transactions like Chargebacks (CB) etc.

• Chargeback Rate (Count): The number of successful chargeback transactions for a given grouping and selection, divided by the number of all transactions with positive turnover for the same grouping and selection, given as a percentage.

• Chargeback Volume: The sum of the amounts of successful chargeback transactions for a given grouping and selection, given in the currency of the respective transactions.

• Chargeback Count: The number of successful chargeback transactions for a given grouping and selection

A change of the status of an entity affects all entities below. Switching to any other mode than LIVE disables live processing for all entities below.

8.12 3-D Secure

XML-based protocol used as an added security layer for online credit and debit card transactions (e.g. VbV or MSC). Card holder must register for 3-D Secure with the bank, then set a password and a safety note. The payment process requires this password to be entered on the issuer’s authentication page.

8.13 Risk Management• Risk Check: A variety of options to check a transaction risk internally (Miscellaneous,

Plausability Checks, Correlation Detection, Black- and Whitelists) and externally (3-D Secure, Schufa etc)

• Risk Logic: Additional feature to rate the importance of internal risk checks.

• Rating Method Scores: Optional rating assigned to each risk check in order to find out how import-ant a risk check really is (a negative rating receives negative score points; a positive one scores positively.


8.13 Upload Descriptors• File Type: Fill in which file type you want to upload

• Bank: Fill in from which bank/acquirer a file is coming

• Country: Fill in from which country the file is coming

• Range: Fill in from which time frame you upload the file

• File: Click ‘Browse’ to select the file from your local storage

• When complete, click ‘Upload’

• After pop-up window closes, check the ‘Import’ screen for the new line

8.14 Upload Status Descriptors• Processed: Upload is ok and complete

• Aborted: Upload error (roll mouse pointer over ‘Aborted’ to see the reasons)

• Import Time Stamp: Shows the time that you uploaded the file


Need a bit of help?Please contact [email protected]

This user guide is intended to provide all the necessary information regarding Till Payments Busi-ness Intelligence Platform (BIP). For further support please contact [email protected].

www.tillpayments.com | 1300 369 692 | [email protected]

Documents

Business Intelligence Platformtillpayments.com/documents/Business Intelligence Platform User Guide.pdf3.1 My Dashboard No matter which page in BIP a user is in, a click on My Dashboard