When your process a transaction, the terminal screen displays a green check mark or a red X to indicate if the transaction was approved or not.
Approved transaction |
Declined transaction |
In addition to the on-screen confirmation, the terminal makes a distinct sound to indicate whether a transaction is approved or declined.
If you accept gift cards, and you configure the application to process gift cards (using the Gift Cards transaction), the transaction confirmation screen displays a Gift Card button.
You need to touch the Gift Card button to process a sale as a gift card redemption, otherwise the terminal will not recognize the card, the transaction will be declined, and the screen will display a message indicating an invalid card type.
This section describes the different transactions you can perform on your terminal when in standalone mode (i.e.: the terminal is not linked to a POS system).
The most common transaction is a purchase where the client uses their credit or debit card as the method of payment.
To process a sale with no tip:
|
|
|
|
|
|
|
If you work in the service industry (bar, delivery, restaurant, transportation), the most common transaction is a purchase with an additional tip, where the client uses their credit or debit card as the method of payment.
NOTE: This procedure is available only if you activate the Tip Processing option.
To process a sale with tip:
|
|
|
|
|
|
|
|
|
When clients pay with a debit card, you can offer the option to receive cashback in addition to paying for their purchase. NOTE: This procedure is available only if you activate the Cashback Processing option, and the feature is not available if a terminal is configured to operate as an unattended device.
To process a sale with cashback:
|
|
|
|
|
|
|
|
|
A pre-authorization allows you to set aside (reserve) an amount on a client’s card prior to completing the transaction.
NOTE: The difference between the pre-authorized amount and the final sale amount remains reserved on the card balance until the completion of the pre-authorization or until the posting date on the client’s account, depending on the card issuer’s policies. It is recommended to complete the pre-authorization after you finish the purchase.
To pre-authorize an amount on a client’s card:
|
|
|
|
|
|
|
|
|
|
|
|
|
When you pre-authorize an amount of money on a client’s card, the card issuer reserves that amount for a period that varies with each user and card issuer. This reserve (or freezing of funds) reduces the client’s available spending limit.
If the pre-authorized amount is greater than the final sale, the unused portion of pre-authorized amount remains reserved until the card issuer releases the reserved funds. When you complete a pre-authorization, you release the unused funds earlier.
To complete a pre-authorization:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There are two types of reimbursements available: void and refund. The transaction you choose depends on when the original sale was processed.
Voiding a transaction provides a refund on a sales transaction that is still in the open batch of transactions (you have not yet performed a settlement). Typically, a void transaction occurs the same day as the original sale; if the original purchase used a credit card, the customer does not need to present their card, only their copy of the transaction receipt. If the original purchase used a debit card, the client needs to present their debit card in addition to their copy of the transaction receipt. When you void a credit transaction, the customer does not see the original sale or the refund on their statement; a voided debit transaction appears as two transaction on the statement.
Refunding a transaction occurs when the original sales transaction is part of a previously settled lot. A refund transaction requires that the client present their card and transaction receipt. When you refund a transaction, the customer can see the original sale and the refund as two separate lines on their statement.
To void a sale:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To refund a sale:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If desired, you can perform a credit account check on a client’s card before processing a transaction.
NOTE: A credit verification does not authorize a transaction, it only indicates if the cardholder account has the available funds to make the purchase.
To verify the available credit on a client’s card:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There could be situations where you need to obtain an authorization directly from the card issuer; when dealing with this situation, you need to manually enter the authorization code to complete the transaction.
To enter the authorization code for a force post transaction:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The application allows you to track cash sales if you want to consolidate all your transactions on the terminal as part of your bookkeeping.
Pour traiter une vente par argent comptant :
|
|
|
|
|
|
|
|
|
|
|
|
|
If you begin a transaction other than a sale and you need to return to the main screen without completing the transaction, you can simply cancel it.
To cancel a transaction before using the payment card:
|
|
When you process transactions, they are saved on the terminal and on the authorization server. Funds collected are only transferred to your merchant account when you perform a reconciliation between the terminal and server; this reconciliation process is the settlement.
Typically, a merchant would process a settlement at the end of a business day. You can choose to process a settlement more than once a day or once every few days. The impact of not processing a settlement every day is a longer delay before funds are deposited to your merchant bank account.
When you process a settlement, the system validates that the transactions processed on the terminal match those on the authorization server before transferring the funds to your merchant account. As you process transactions, the terminal and authorization server track the transaction history (operations) in the open batch. When you process a settlement, you close the active batch and clear the transaction history on the terminal and authorization server.
NOTE: When you process a settlement, the terminal is unable to perform any other transaction at that time.
To process a settlement:
|
|
|
|
|
|
|
|
|
|
|
|
|
You can configure your payment terminal to the specific type of business and situation it is used in. This enables the terminal to refer to the operator in a way that is appropriate to the business situation and is particularly helpful when you have multiple operators configured for the terminal.
Business Type |
Operator Name |
Operator Management Screen |
Retail |
Clerk |
|
Restaurant |
Waiter |
|
Delivery |
Driver |
To configure the terminal use:
|
|
|
|
|
|
|
|
|
|
|
You can configure your payment terminal to accept credit cards, debit cards, or both. If you select only one type of card, the terminal will not recognize the other type.
For example, if you configure the terminal to accept only debit cards, when a customer tries to pay with a credit card, the terminal will display a message that it only accepts debit cards.
To configure the card types the terminal accepts:
|
|
|
|
|
|
|
|
|
|
|
You can change the language that appears for terminal operations. The merchant language is the language used for the application’s menus and commands and is separate from the language configured on the customer’s card.
For example, your terminal’s merchant language could be English, but when a French speaking customer uses their card, the instructions appear in French.
To set the language of operation for the terminal:
|
|
|
|
|
|
|
|
|
|
The application returns to the main screen in the selected language. |
You can change the appearance of the terminal’s display to better match your business environment. The application theme can be light or dark, as shown in the following examples:
Dark Theme |
Light Theme |
To set the application’s appearance:
|
|
|
|
|
|
|
|
|
By default, the application displays the PayFacto logo on the main screen. You can hide the logo from the screen if desired.
To display of hide the PayFacto logo on the main screen:
|
|
|
|
|
|
|
|
|
As a security measure, the application requires, by default, the entry of the Admin password before closing the application. You can disable this function if desired, however this means that anyone can close the payment application and access the other applications and functions on the terminal.
To enable or disable password protection on application exit:
|
|
|
|
|
|
|
|
|
For bookkeeping purposes, invoices are numbered. The numbering can be done manually or automatically. By default, the terminal numbers the invoices automatically, in sequence. If you disable automatic invoice numbering, the terminal prompts the operator to manually input an invoice number (maximum of 12 numeric characters); you cannot process a transaction without an invoice number.
To enable/disable automatic invoice numbering:
|
|
|
|
|
|
|
|
|
The terminal provides feedback on transactions by displaying messages and with sounds. Sounds are enabled by default. If you disable sounds, the terminal will be muted and only the only feedback you will receive is the display messages.
NOTE: The audio confirmation when transactions are approved or declined is not affected by this setting; they will be heard even if you disable all other terminal sounds.
To enable/disable terminal sounds:
|
|
|
|
|
|
|
|
|
By default, as a fraud-prevention method for swipe transactions, the terminal requires the operator to verify that the card’s last 4 digits match the numbers that appear on screen. If you disable card verification, the terminal will process swipe transactions without card verification.
To enable/disable card verification:
|
|
|
|
|
|
|
|
|
You can configure the terminal to ask the customer if they want to pay with cash or with a card. When you enable the cash or card question, the operator enters the amount of the sale before passing the terminal to the customer. The customer then touches the payment method they want to use to continue the transaction. By default, the cash or card question is disabled.
To enable the terminal to ask the customer what method they want to use to pay:
|
|
|
|
|
|
|
|
|
If your business includes the option to tip, you can enable tipping on the terminal, where the customer can add a tip value in addition to the sale. By default, tipping is disabled on the terminal.
To enable tipping in addition to the sale:
|
|
|
|
|
|
|
|
|
When you enable tipping, you can configure as many as three preset percentages that are presented as options to the customer. The customer can touch one of the preset values or manually enter an amount for the tip.
To add a preset tip percentage option for the customer:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If required, you can easily change the value of any of the preset tip percentages presented to the customer.
To edit a preset tip percentage:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In addition to offering preset tip percentage options to the customer, you can also allow the customer to manually enter their own tip percentage by touching the Other % button.
NOTE: At any time, the customer can manually enter a dollar and cents value for the tip, regardless of the percentage options that are available.
To enable a manual tip percentage option for the customer:
|
|
|
|
|
|
|
|
|
If your sales include the option to tip, but the terminal cannot be brought to the customer, you can pre-authorize a transaction amount and bring the printed receipt to the customer to allow them to manually enter the tip and total amounts.
To enable the tip and total lines on a pre-authorized sale:
|
|
|
|
|
|
|
|
|
If you want to offer your customers the ability to withdraw cash in addition to their purchase, you can do so for debit card transactions only. By default, cashback is disabled on the terminal.
To enable tipping in addition to the sale:
|
|
|
|
|
|
|
|
|
When you enable the cashback option, you can configure as many as three preset amounts that are presented as options to the customer. The customer can touch one of the preset values or manually enter an amount for cashback.
To add a preset cashback amount option for the customer:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If required, you can easily change the value of any of the preset cashback amounts presented to the customer.
To edit a preset cashback amount:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
As a security measure, you can require customers receiving a cashback amount to confirm they received the cash by signing on the merchant copy of the receipt.
To enable the customer signature for cashback:
|
|
|
|
|
|
|
|
|
The following sections describe the different application functions you can configure to better suit your business needs.
The following procedures explain how to configure contactless transactions on your terminal.
By default, the terminal supports contactless transactions (sales and refunds) through touch or tap with a card or supported device. If desired, you can disable contactless transactions, or re-enable it if you have previously disabled it as an option.
To enable/disable contactless transactions:
|
|
|
|
|
|
|
|
|
Each payment processor/card has their own touch/tap payment technology. The terminal supports all major technologies. When you enable contactless transactions, you can select which technologies you will accept. The available technologies include:
TIP: As a security measure, it is recommended that you disable any contactless technology you do not accept, to prevent a client from attempting to use a card from a payment processor you do not have an agreement with.
To enable/disable a contactless technology:
|
|
|
|
|
|
|
|
|
If you use multiple terminals, it is possible that a pre-authorization performed on one terminal cannot be completed on the same terminal. For example, a hotel might pre-authorize an amount using one terminal, but complete the pre-authorization using a different terminal. The Completion without Pre-Authorization function saves the pre-authorization information on the payment server rather than on the terminal; this allows the completion of a pre-authorization on any available terminal.
IMPORTANT: This function can only be used with the terminal in ECR mode, where pre-authorization and completion transactions are saved on a POS system.
To activate or disable the completion without pre-authorization function:
|
|
|
|
|
|
|
|
|
Processing a settlement is the reconciliation of transactions between the terminal and the authorization server. Manual settlement is explained in the Process Settlement procedure. You can request that your merchant account have access to automated settlements; automated settlements occur every day at the same time (as defined by the merchant). To request automated settlements, contact customer support at 1-888-800-6622.
By default, the Enable Auto-Settlement function is disabled in the Application Options menu, as shown below:
After configuring automated settlements for your merchant account, the terminal may need to download updated parameters; should this be required, the terminal will display error code 381 when you try to process a transaction, as shown below:
This is a temporary situation, and you can retry the transaction after the terminal updates the parameters.
NOTE: The terminal is unable to process any transactions during the time that it is performing an automatic settlement; this interruption is generally brief and it is recommended that automated settlements occur outside of normal business hours.
After automated settlements are enabled on your merchant account, three additional fields appear in the Auto-Settlement section:
The PayFacto payment application can process DataCandy-issued gift cards by adding the gift card transactions to the list of available transactions. When you enable the processing of gift cards, the list of available transactions expands as shown below:
Payment-Only Transactions |
Payment and Gift Card Transactions |
IMPORTANT: To be able to process gift cards, you must install and configure the Gift PayFacto powered by DataCandy application on the terminal.
To activate gift card transactions in the PayFacto payment application:
|
|
|
|
|
|
|
|
|
|
|
If your business has multiple employees who use the payment terminal, you can enable each operator to identify themselves before completing a transaction. Additionally, you can require each operator to enter a password before they can complete an operation; this ensures that no unauthorized individuals can use the terminal.
By default, any number of clerks can operate the terminal, but you can require individual clerks to identify themselves. When enabled, the terminal identifies individual clerks using their identification number, which they enter prior to completing a transaction.
NOTE: You cannot enable or disable clerk identification if there is an open batch of transactions; process the settlement before performing this procedure.
To enable/disable clerk identification:
|
|
|
|
|
|
|
|
|
IMPORTANT: When you enable the use of clerks, you must add at least one operator/clerk before you can process a transaction.
When you enable clerk identification prior to completing a transaction, you need to add at least one clerk to the terminal.
NOTE: If your business uses more than one payment terminal, you will need to enable clerk identification and add the individual clerks on each terminal separately.
To add a clerk:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In addition to requiring terminal operators to identify themselves, you can require that they enter a password to further prevent unauthorized use of the terminal.
HINT: You should consider whether you will require clerks to use a password before configuring the clerk “accounts”. If you forget the passwords before enforcing their use, you will have to delete all the clerks and start over.
To require clerks to enter a password before completing a transaction:
|
|
|
|
|
|
|
|
|
NOTE: If an operator forgets their password, you can use the Merchant or Administrator password as a workaround. If you have also forgotten the password, you will need to delete that clerk and re-create it with a new password.
When you enable the identification of clerks on the terminal, you can synchronize the settings with the host server.
To synchronize clerks on the terminal with the host server:
|
|
|
|
|
|
|
|
|
It is simple to change a clerk’s password. You may need to change a password if an employee is assigned another employee’s clerk number, or you may want to change passwords on a recurring basis for terminal security.
To change a clerk’s password:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You may want to remove the requirement for clerks to identify themselves. There are 3 ways to remove clerks from the terminal:
IMPORTANT: If your business uses more than one terminal, you must disable or delete the clerk(s) from all terminals.
NOTE: You cannot disable or delete clerks if there is an open batch of transactions; process the settlement before performing the procedure.
If you choose to disable clerk identification, any clerks you have previously configured (including their passwords) will remain stored on the terminal. The procedure to disable clerk identification is the same as the Enable Clerk Identification procedure, but you toggle Enable Clerk/Operators to Off.
Deleting a single clerk only removes that clerk and its associated password from the terminal. All other clerks configured on the terminal will remain operational.
To delete an individual clerk:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If required, you can delete all existing clerks on the terminal at one time.
IMPORTANT: IF you delete all clerks from the terminal, you must either disable clerk identification or add at least one new clerk before you can process any transactions. Refer to Disable Clerk Identification or Add a Clerk for the appropriate procedure.
To delete all clerks on the terminal:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You can view the number and type of transactions (credit, debit, and pre-authorization) for each clerk configured on the terminal. This list of transactions is for the current, open batch and resets to zero when you process a settlement.
To view a clerk’s transactions on the terminal:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You can print a list of transactions in the current batch for all clerks configured on the terminal. This prints a consolidated list for all clerks of the information you can view in the View a Clerk’s Terminal Activity procedure.
To print the list of transactions for the clerks on the terminal:
|
|
|
|
|
|
|
|
|
|
|
You can assign passwords to specific operators and terminal functions to protect the terminal from unauthorized use. Passwords are numeric (numbers only) and between 4 and 6 characters in length to provide security without slowing down the overall time it takes to process a transaction.
The terminal uses passwords for different user levels. The user levels follow a hierarchy, and a “higher” level password can enable a function for a “lower” level user. For example, an operator can use a Merchant password to enable a password-protected sale, while an Administrator password can unlock functions that require a Merchant password.
The hierarchy of passwords is the following:
User Level |
Description |
Superuser |
An algorithm-generated password provided by the Technical Support team when required to access the terminal’s advanced settings. Each Superuser password is unique and can’t be re-used. |
Administrator |
Assigned at the time of terminal configuration, the Administrator password protects the terminal against unauthorized password changes and closing the PayFacto app. You can use the Administrator password for any function that requires a Merchant or operator password. |
Merchant |
Assigned at the time of terminal configuration, the Merchant password protects the terminal from completing sales-related functions without authorization. You can use the Merchant password to complete a transaction when operator identification requires a password to process a sale. |
Operator |
Assigned when configuring one or more terminal operators. Can be enabled to protect unauthorized sales when paired with the associated operator identifier. |
If you enter a password incorrectly, the terminal displays an Access refused error message.
The Password field re-appears, prompting you for the required password with a number in parenthesis, which represents the number of tries remaining before the terminal locks out the user profile. An operator has 5 attempts to enter the password correctly; the counter resets after the password is entered correctly.
If a user forgets a password, the reset procedure depends on the user level. The following table explains who can reset which password and what procedure to use:
User Level |
Who can reset the password |
What to do |
Administrator |
Technical Support |
The Administrator password can only be reset with a Superuser password, which requires the assistance of Technical Support. Refer to the Obtaining Support procedure. |
Merchant |
Administrator |
A Merchant password can be reset using the Administrator user level and password. Refer to the Change Merchant Password procedure. |
Operator |
Administrator or Merchant |
The Operator password can be reset using the Administrator or Merchant user level and password. Refer to the Change a Clerk’s Password procedure. |
Before using the terminal, an Administrator password was assigned during the initial configuration. The Administrator password provides access to advanced terminal functions and can also enable password-protected operations. You can change the Administrator password whenever you feel it necessary.
IMPORTANT: Do not forget the new Administrator password; the only way to reset it is to contact the technical support team.
To change the Administrator password:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Before using the terminal, a Merchant password was assigned during the initial configuration. The Merchant password protects against unauthorized users performing certain operations. You can change the Merchant password whenever you feel it necessary.
IMPORTANT: Do not forget the new Merchant password; the only way to reset it is to contact the technical support team.
To change the Merchant password:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For added security, you can require the Merchant password for certain functions or transactions before the operation can proceed. By default, this security measure is enabled for the following functions and transactions:
Additionally, you can require the Administrator password for the Refund and Void transactions for additional security.
If you disable the password requirement for a feature or transaction, any terminal user can perform that operation without entering the merchant password.
NOTE: To ensure the security of your transactions, it is strongly recommended that you enable password use for the selected features.
To enable/disable password protection for a feature or transaction:
|
|
|
|
|
|
|
|
|
|
|
If your terminal has a built-in printer, or connects to an external printer, there are several printing options you can enable in addition to the transaction receipts for sales.
If your terminal is equipped with a printer, you can adjust the printer settings to suit your business needs. The available printing options are:
IMPORTANT: It is strongly recommended that you do not disable the printing of sales receipts, as customers need their receipt to get a refund or otherwise have proof of purchase.
To adjust the terminal’s printing options:
|
|
|
|
|
|
|
|
|
|
|
|
|
In addition to printing receipts for sales transactions, you can print receipts for some non-sales transactions, including:
IMPORTANT: If you disable printing for any of these settings, the customer will have no physical evidence of these transactions.
In addition to the transactions listed above, the terminal can configure the following printer settings:
To enable/disable additional printing options:
|
|
|
|
|
|
|
|
|
You can add a personalized message at the bottom of every printed receipt. Your message can contain up to 4 lines with 44 characters (including spaces) per line.
HINT: You should prepare your message on a piece of paper in advance, to ensure that you have the correct number of characters per line.
To a personalized message to your printed receipts:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
NOTE: The personalized message appears on all printed receipts, the merchant copy as well as the customer copy.
If you notice an error in your personalized message, or you want to change some text in the message, you can easily edit your message. Repeat the Add a Personal Message procedure and adjust the text on the line(s) you want to modify.
You can easily remove your existing personalized message, in order to enter a new one or to leave the receipts blank.
To a delete the personalized message on the receipt footers:
|
|
|
|
|
|
|
|
|
If a transaction receipt is lost or damaged, you can easily reprint a duplicate copy of the receipt.
IMPORTANT: Reprinting a receipt is only available for the current batch of transactions. If you process a settlement, the transactions from that settlement are no longer available to reprint.
To reprint a transaction receipt:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The terminal can report on the transactions, allowing you to view either detailed or summary information on the transactions and transaction types in the current batch. Detailed reports display a list of every transaction in the current batch, including date, time, transaction type, payment method, invoice number, and amount.
The terminal’s printer (built-in or external) can print transaction reports for the current batch. For reconciliation purposes, you may want to print a report prior to processing a settlement, but it is not a requirement. Printing reports is meant to assist with your bookkeeping.
Viewing the detailed report for the current batch of transactions allows you to see each individual transaction’s details and allows you to reprint or void the transaction if desired.
To view a detailed list of transactions for the current batch:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When viewing a detailed report, the current batch of transactions may be too large to easily scroll through when looking for a specific transaction. The search function allows you to locate a transaction using the invoice or sequence number.
To search a detailed list of transactions for the current batch:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You may want to have a printed copy of the transactions for the current batch prior to processing the settlement. Printing a detailed report allows you to reconcile each transaction as part of your bookkeeping.
NOTE: Printing a detailed report can consume a large quantity of paper, depending on the number of transactions in the current batch.
To print a detailed list of transactions for the current batch:
|
|
|
|
|
|
|
|
|
|
|
Viewing the summary report for the current batch of transactions allows you to see the totals for each payment method used, including sales, refunds, tips, cashbacks, and fees.
To view a summary list of transactions for the current batch:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You may want to have a printed copy of the transactions for the current batch prior to processing the settlement. Printing a summary report allows you to reconcile transactions by payment type as part of your bookkeeping.
To print a summary list of transactions for the current batch:
|
|
|
|
|
|
|
|
|
|
|
The terminal has a training mode that allows users to process transactions in a simulated environment to learn and understand the terminal’s various functions. When in training mode, the terminal does not communicate with the server, and it functions even when the terminal has no network connection.
IMPORTANT: You cannot enable or disable training mode if there are any open batch transactions on the terminal; you must process your settlement to close out the open transactions before you can access or leave training mode.
To enter/leave training mode:
|
|
|
|
|
|
|
|
|
|
|
|
CAUTION: It is possible to lock a card in training mode, as some security features are stored on the card’s chip.
The Host Options menu displays information about the payment host. You should not change any of the settings in the Host Options menu unless specifically instructed by PayFacto support. The Host Options menu contains the following information:
The PayFacto application offers 24/7 technical support at 1-888-800-6622
The About menu displays information about the terminal, the software version, and current batch information. You may be asked by PayFacto support to reference this information, but none of the fields are editable.