Description

Version

File timestamp

Deployed on

1 - Production SIM

It should be in all stores that already use P400.

2021.12.17.1

2021-12-17 9:05 AM

9 Pilot stores

2 - Harvey’s dummy SIM with call to IPP320

Used previous of the installation day to make easier and faster the activation process that day. But at the end, it is overwritten by the production one.

2022.1.6.1

2022-01-06 9:23 AM

None so far

3 - Swiss dummy SIM with call to IPP320

All Swiss locations that are still using IPP320 have this one, and the EM server is already configured to call it. It is replaced by the production one on the day of the P400 installation.

2022.1.5.1

2022-01-05 8:38 AM

All Swiss except the pilot ones

4 - Dummy SIM

With this file all the related buttons are disabled, and it is used only for stores that already have the “Payment Dvc Mgmt” touchscreen, but the EM server is still pointing to the IPP320. So far all Harvey’s not in the pilot project.

2021.11.9.1

2021-11-09 11:55 AM

All Harvey’s except the pilot ones, and some labs

Inquire number and name

Usage from which button and screen

11 - Start session

Called when the payment screen is called

12 - Purchase or refund

“PAYMENT CARD” on Payment screen

13 - Manual purchase or refund

“Manual Pay” on Payment screen

14 - Finish session

Automatically called on “final_tender” and “trans_cncl” events

Also by “CLOSE SESSION” on Payment Dvc Mgmt screen

15 - Print customer receipt

“Reprint Receipt” on Function screen

and “LAST RECEIPT” on Payment Dvc Mgmt screen

16 - Print merchant receipt

Not called in any button so far

18 - Test device

“TEST P400” on Payment Dvc Mgmt screen

19 - Pair device

“PAIR P400” on Payment Dvc Mgmt screen

20 - Pair device by IP

“PAIR BY IP” on Payment Dvc Mgmt screen

21 - Switch connections

“SWITCH CON 1 & 2” on Payment Dvc Mgmt screen

22 - Print specific customer receipt

“PRINT RECEIPT” on Payment Dvc Mgmt screen

23 - Reboot device

“REBOOT P400” on Payment Dvc Mgmt screen

24 - Set parameters

“SAF” on Payment Dvc Mgmt screen

26 - Show device ID

“DEVICE ID” on Payment Dvc Mgmt screen

Name

Description and content

\Bin

Application files. Additionally to the SIM file, This folder is the only required during a new installation.

• RPI_P400_LIB.dll - Main application used to communicate with the P400 device. Check version list.
• RPI_P400_LIB.pdb - This file is used for adding more technical details to the logs when a handled error occurs. It is for troubleshooting and corrections purposes.
• RPI_P400_LIB.Config.txt - File containing the configuration parameters of the application. See the config parameter list for further details.
• …\Textfiles\*.txt - Files with most of the text used for messages and receipts.

\Data

Files generated as a result of the device pairing process and the automatic language detection.

• POS_<terminal_name>.txt - With the device serial number assigned
• P400_<serial_number>.txt - With IP’s, mac-addresses, and encryption data
• P400_<serial_number>_Counter.txt - With an incremental numeric value
• Language.txt - With “EN” or “FR” depending of the detected language

\Journals

Files generated with receipts. One per day. They are used by the print receipt button.

The format name is:

• RPI_<date>_<store_number>_<terminal_name>_Journals.log

\Logs

Several log files generated by day. Their format name is:

RPI_<date>_<store_number>_<terminal_name>_<type>.log

And the possible types are:

• Summary - One line per transaction. See the summary fields list.
• Details - Detailed log file
• Details_BG - Detailed log file for background tasks
• Messages - Requesting messages content to the device
• Messages_BG - Requesting messages content to the device on background
• Warnings - Only warning situation messages
• Errors - Handled error messages in the original form

\Output

Files used for pass text from the DLL results to the SIM inquiries

• response.txt - File with the last full message to display on the POS screen. By the way, the approved one is written but not displayed
• receipt_<n>.txt - Files with last printed receipts, one per each single receipt.

\Temp

Temporarily files used to make track of a short time-period data

• LastSetTime.txt - Last time that the clock on the device was set up. Used to not do it again on the same day on each transaction.
• LastTransactionNotConfirmed.txt - With the identification data of the last transaction which was not possible to be confirmed if it was approved or not. Used to personalise the result message in case a duplicate transaction detection matches with the last not confirmed one.
• DuplicatedTransaction.txt - With the identification data of the last transaction that was detected as a duplicate. Used for force to pass the duplication transaction in case it was retried again.

Parameters and current values

Description

dataFolder = C:\RPI_P400\Data

logFolder = C:\RPI_P400\Logs

journalFolder = C:\RPI_P400\Journals

textfilesFolder = C:\RPI_P400\Bin\TextFiles

outputFolder = C:\RPI_P400\Output

tempFolder = C:\RPI_P400\Temp

Full path of the location of these application folders. All of them are generated automatically, and the Bin subfolder is the only that can not be relocated.

logPrefix = RPI_

logBackgroundPostfix = _BG

Prefix used for all logs files and the postfix used for the background one.

logDaysToKeep = 300

Days that a log file remains on the terminal before being deleted. The default value is 30.

An old log file is going to be deleted only during an attempt to write another log file of the same type.

generalMessageTimeout = 6000

saleMessageTimeout = -1

These are how many milliseconds the DLL is going to wait to receive an answer message back from the P400 device for a sale transaction and for any other kind of message. The value -1 means no limit of time.

secondaryStatusInterval = 2000

Time interval (milliseconds) for check the status thru the secondary port during sales and refund transactions

detectDuplication = TRUE

If this flag parameter is turned off (FALSE), the duplicate transaction detection is not going to be used.

earlyCardEntry = FALSE

If this parameter is set to TRUE, it is allowed to present a card just after the session is started.

switchConnectionTimeMargin = 10

The number of milliseconds that the secondary connection must have is less than the primary one to be considered “faster”.

writeJournal = TRUE

To enable the writing of the receipt data on the journal's files.

receiptLogDetails = FALSE

To enable extra verbosity to the detail log related to the individual receipt’s fields.

receiptTypes = M,C

Comma separated list of types of receipts to generate. These characters should match with the last character of the receipt template files on “TextFiles” folder:

• ReceiptTemplate_EN_C.txt
• ReceiptTemplate_EN_M.txt
• ReceiptTemplate_FR_C.txt
• ReceiptTemplate_FR_M.txt

receiptMaxDaysToPrint = 3

When a receipt is printed, this is the maximum number of days to search it in, starting from today.

backupMinutes = 5

When a backup mode is started, it is going to be active at least for this amount of minutes. See WiFi Failover Connection.

secondaryEnabled = TRUE

backupEnabled = TRUE

scanEnabled = TRUE

To enable the use of the secondary connection, the backup mode, and the IP scan option. All this related to the WiFi Failover Connection.

scanLastOctetStart = 2

scanLastOctetEnd = 126

When the IP scan is used, it is going to use the POS terminal first three octets, and the last one is going to be searching in a range built with these two parameters.

defaultParamHost = UGP

When a parameters.txt located on the Data subfolder is pushed up to the P400 device through the SAF button, this value is used to know to which host sends them.

#

Field name

Format: values or example

1

Transaction date

Format: yyyy-mm-dd

2

Transaction time

Format: hh:mm:ss.mss

3

Store Number

Format: 9999

4

POS terminal name

Examples: DRVTHRU1, TAKEOUT2

5

P400 serial number

Format: 999-999-999

6

Transaction type

Values: Purchase and Refund

7

Original amount

Example: $23.48

8

Check number

Example: 8075

9

Device ID

Examples: 701, 712. See Device ID format

10

Payment media

Examples: VISA, DEBIT, MC, Interac

11

Payment type

Values: DEBIT and CREDIT

12

Card entry mode

Values: Contactless, Chip Read, Swiped

13

Tip amount

Example: $1.86

14

Authorised amount

Example: $23.48

15

Transaction duration

In seconds, example: 7.831

16

Account number

Example: ************9154

17

Card token

Example: 5446145534129154

18

Output message

Example: (4) APPROVED - CAPTURED

Brand

1 letter

• H - Harvey’s
• S - Swiss Chalet
• R - Bistro

Store

4 digits

Terminal ID

This is the Chase TID

3 digits

• 701 - 709: Takeout
• 711 - 719: Drive-Thru
• 721 - 729: Pitstop
• 731 - 739: Kiosk
• 741 - 749: Dining Room

Type of rebooting

instructions

From the POS / Remote

In the function screen, press the Payment Dvc mgmt button:

Then press the reboot P400 button:

Wait around 2 minutes to retry.

Using the device keys

(short way to do it)

Press and hold the green key for 10 seconds until the device starts the rebooting process with a blank screen. Wait until the device goes to the idle screen before sending a transaction from the POS.

Using the device keys (old way to do it)

Press the red X button and the black 0 button at the same time for 3 seconds.

Then select the reboot option on the device’s screen:

Physical disconnection

Unplug the power cable and plug it again.

This method normally is not needed, but if the device is frozen, it could be required. If there are already recent antecedents of this situation, ask for a device replacement.

Error message

Responsable

Description

Payment card button does nothing

Recipe

Wrong SIM file version:

C:\micros\res\pos\etc\pms21.isl

It must be the production one instead of the dummy one.

See SIM File Versions

“DEVICE ID” and “PAIR P400” buttons do nothing

Recipe

Wrong SIM file version:

C:\micros\res\pos\etc\pms21.isl

It must be the production one instead of any dummy version one.

See SIM File Versions

(6) DECLINED - INVALID MAC     499

Chase

This error could be normal if it is not frequent. And only happens with DEBIT cards. Normally, when it is retried, the transaction should go through.

If the error persists for more than 5 minutes, it is possible to Manually Downloading MAC KEY as a workaround, but even if it is fixed, it should be reported to Chase.

(6) DECLINED - KEYS OUT OF SYNCJ98

Chase

It is possible to Manually Downloading MAC KEY as a workaround, but even if it is fixed, it should be reported to Chase. This error only occurs with DEBIT cards.

(59002) BUSY - DEVICE IS BUSY

Chase

This error happens because a transaction is attempted but the P400 device is not available to answer.

The most common cause is because the device is asking for "Retry Mac Key Update?”. In this case press YES, and retry the transaction when the device arrives at the Idle screen.

If this is not the case, reboot the device and retry. If the issue continue, report it to Chase

(59003) BUSY - SESSION in progress - Session in progress

Recipe

(59026) COMM ERROR - Response timeout with  [api.vfipayna.com] (59026)

Chase

(-20) Transaction not confirmed due a lost of communication - Please try again

Recipe

(-601) Duplicate transaction based on account, invoice and amount combination - If you retry again it will be accepted

Legitimate

The payment was rejected because it was an attempt to pay the same amount, in the same check number twice. However, if the payment is retry again, it is going to be accepted by repetition. See Duplicate transactions.

(-602) DECLINED - Duplicate transaction based on account/invoice/amount combination - This transaction was previously approved but not confirmed - Please use offline tender

Legitimate

This error -602, it is similar to the -601, but this is triggered when additionally, the amount and the check number match with a previous non confirmed transaction due a loss of communication, error -20. Like in the -601, it is possible to be accepted by repetition, however, in most of the cases is not needed. They need just to close the check using offline tenders. See Duplicate transactions for more details.

(-31) Device communication timeout - IP scanner was started - Please try it again in 30 seconds

Recipe

(-32) IP scanner is still running - Please try it again in 10 seconds

Recipe

(59024) COMM_ERROR - Unable To Process

Recipe

Chase

It is missing the device pairing process. If it was missing, it is possible to do it remotely if the device is on, and if you got the serial number in the back label.

Legitimate

This is a normal message provoked after 30 seconds of inactivity on the Pinpad

Recipe

Possible SIM file missing:

C:\micros\res\pos\etc\pms21.isl

See the SIM section.