This section lists the required connection information and settings for supported Pay-by-Plate Sync parking providers.
Parking provider | Connection information and settings | Expected format |
---|---|---|
Aparc Systems | Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. | A valid HTTP or HTTPS URL pointing to the web service. |
Client ID. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | Numerical | |
Client key. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Time offset from UTC. Time to add to UTC to get the local time of the provider’s server. This must be updated to reflect daylight savings time, when applicable. | Numerical in minutes | |
Grace time (mins). You can add a grace period to the last chance lookup. | Numerical in minutes | |
Cale | Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. |
String: http://webservice.mdc.dmz.caleaccess.com/cwo2exportservice/Enforcement/1/EnforcementService.svc
|
Username. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Password. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Timeout (secs). Configure how long the server waits for a response from the third-party vendor. | Numerical in seconds | |
Grace period (mins). (Optional) You can add a grace period to the last chance lookup. | Numerical in minutes | |
Cardinal Tracking -TickeTrak | Server. Provided by the customer or parking vendor. This is the IP address or URL of the server running Cardinal Tracking TickeTrack. Different Pay-by-Plate Sync setups can use the same string if they are all hosted on the same server. | A valid IP address or URL pointing to the Cardinal Tracking Server |
Database. Provided by the Customer or parking vendor. This is the database name of the server running Cardinal Tracking TickeTrack. Different Pay-by-Plate Sync setups can use the same string if they are all hosted on the same server. | String | |
Username. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Password. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Timeout (ms). Configure how long the server waits for a response from the third-party vendor. | Numerical in milliseconds | |
Contract Permit Parking | Grace period (mins). (Optional) You can add a grace period to the last chance lookup. | Numerical in minutes |
Digital Payment Technologies | Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. | A valid HTTP or HTTPS URL pointing to the web service. |
Token. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Account. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Username. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Password. Provided by Digital Payment Technologies. | String | |
EziCom |
NOTE: The EziCom parking provider has a limit of 1000 plates per transaction.
Schedule more frequent permit updates for this provider.
|
|
Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. | A valid HTTP or HTTPS URL pointing to the web service. | |
Username. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Password. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Merge zones location (checkbox). (Optional) Zones will be displayed differently when merged with the Pay-by-Plate Sync system. Use this setting only when you need to merge and duplicate the list of zones. | ||
Timeout (secs). Configure how long the server will wait for a response from the third-party vendor. | Numerical in seconds | |
Time offset (mins). (Optional) You can add a time offset or grace period to the last chance lookup. For example, if you add a five-minute grace period, 5 minutes are added to the time of the Genetec Patroller™ plate read when it is sent to the parking vendor during a last chance lookup. | Numerical in minutes | |
Generic REST Service | Api Key. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String, provider specific |
Api URL. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same URL if they are hosted by the same vendor and their Api Key is different. The URL should be in the format: https://your-url-here/api/pbp/v2014-06/ | A valid HTTP or HTTPS URL pointing to the REST service. | |
Skip last chance lookup (checkbox). When a possible permit hit is
detected, the system performs a last chance lookup to verify if the permit was
recently added to the permit list. If ALPR cameras register many permit hits within
a short period of time, you might notice slower system speed due to the many
required last chance lookups. If last chance lookups are not required, enable this
feature to skip the lookup and increase system speed. NOTE:
|
||
MacKay Meters | Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. | A valid HTTP or HTTPS URL pointing to the web service. |
Username. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Password. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Parkeon | Ignore valid SSL (checkbox). Select this option when the connection string is pointing to an HTTPS website that has an SSL certificate error. | |
Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. | A valid HTTP or HTTPS URL pointing to the web service. | |
Requester. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
City code. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String (typically a number) | |
Parkeon V2 |
NOTE: The following maximum values are applied by Parkeon V2 and can be modified by
Parkeon per implementation.
|
|
Ignore valid SSL (checkbox). Select this option when the connection string is pointing to an HTTPS website that has an SSL certificate error. | ||
Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. | A valid HTTP or HTTPS URL pointing to the web service. | |
Username. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Password. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String (typically a number) | |
ParkMobile (discontinued) | Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. | A valid HTTP or HTTPS URL pointing to the web service. |
Username. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Password. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
ParkMobile V2 | Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. | A valid HTTP or HTTPS URL pointing to the web service. |
Username. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Password. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
API Key. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
PayByPhone | Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. | A valid HTTP or HTTPS URL pointing to the web service. |
Username. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Password. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Vendor lot CSV. Type the location of the CSV that contains the list of zone IDs for enforced parking lots. The CSV must be on a drive that is accessible by the Pay-by-Plate Sync plugin role. |
VENDORLOTID;SYSTEMNAME;STREET
Example:
123;VendorSystem;VendorStreet
|
|
CSV data delimiter. Type the character you used as a delimiter to separate data in the CSV file (for example, a semi-colon or comma). | Single character delimiter (coma, semi-colon) such as "," or ";". | |
Grace time (mins). (Optional) You can add a grace period to the last chance lookup. | Numerical in minutes | |
Time zone. Type “UTC”. | ||
Connection timeout (secs). Configure how long the server waits for a response from the third-party vendor. | Numerical in seconds. | |
T2 Systems | Connection string. Provided by the parking vendor. Different Pay-by-Plate Sync setups can use the same string if they are all hosted by the same vendor. | A valid HTTP or HTTPS URL pointing to the web service. |
Username. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Password. Provided by the parking vendor. This must be unique for each Pay-by-Plate Sync setup. | String | |
Grace time (mins). (Optional) You can add a grace period to the last chance lookup. | Numerical in minutes | |
Get facilities query ID. T2 Systems might call this a
“Query UID”. For more information, see "Importing custom queries for T2 Systems integration" |
Numerical | |
Get permits query ID. T2 Systems might call this a “Query UID”. For more information, see "Importing custom queries for T2 Systems integration" |
Numerical | |
Get permits by modify query ID. T2 might call this a “Query UID”. For more information, see "Importing custom queries for T2 Systems Systems integration" |
Numerical | |
Get permits by plate query ID. T2 might call this a “Query UID”. For more information, see "Importing custom queries for T2 Systems Systems integration" |
Numerical | |
Get permits by plate in all facilities query ID. T2 might call this a
“Query UID”. For more information, see "Importing custom queries for T2 Systems Systems integration" |
Numerical | |
Default state. Enter the state ID that the system should use if the state is not defined by the vendor. | String |