Adding a Verifone Integration in the API

EXTERNAL ID/LOCATION TOKEN: Location GUID

TYPE: verifone

URL BASE (PAR ONLY): not relevant for Verifone

SFTP HOME DIRECTORY (SAVI SFTP ONLY): not relevant for Verifone

CLASSIFICATION TYPE: Whichever option is applicable.

VERIFONE SERVER HOST (IP): IP address of the Commander.

VERIFONE SERVER USERNAME: The username they create for us in the Commander.

VERIFONE SERVER PASSWORD: The password for the user created for us in the Commander.

QUERY PERIOD (HOUR, SHIFT, DAY): Leave on "day", unless someone smarter than us specifies otherwise.

HOURS TO WAIT BETWEEN QUERIES (0 FOR DAILY): Leave on "0".

ALLOW SYSTEM TO CHANGE PASSWORD?: (Should be checked unless the user is shared)

The next step is Camera Mapping. This won't be possible until the next day after we have created the new configuration and it is successful. We get a data dump for all POS transactions once a night for Verifone, thus our system won't recognize any onsite registers until the next day after a successful data dump.

The REGISTER ID drop down menu won't have any options to see. The SOURCE will show every camera added to the location regardless of the integration status.

The day after a successful integration will have options in the REGISTER ID drop down menu. Ignore every option that is in the 900 range, unless someone smarter than me tells you otherwise.

There should be options in the 100 range, ie. 101, 102, which typically represents the indoor registers.

From this point it's a guessing game as to which of our register cameras should be attached to which register ID. This is confirmed as we get data in the dashboard and we can adjust register cameras to register ID's as needed.