The purpose of this document is to provide the preferred PAXStore or BroadPOS This document outlines the NorthStar recommended parameter settings for PAX terminal configurationterminals using PAXSTORE or BroadPOS configuration utilities.
Each PAX device is setup initially set up at paxstore.us and in the configuration utility is setup with default settings and parameters tailored for the various PAX devices and processors. All the parameters Parameters are organized in tabs for each processor application and version that is sent across tabs corresponding to different processor applications and versions deployed to the PAX device. Some parameters are on different tabs and/or worded or not used in all versions/processors. Unless noted below in Preferred Settings, we generally leave the settings with the default value, except for processor banking account info and the device IP configuration.
If possible While most settings retain their default values, adjustments are made for NorthStar Order Entry semi-integration and merchant-specific information such as processor banking account details, receipt configuration, and device network settings.
The Preferred Settings below, are parameters that impact NorthStar Order semi-integration or usability; otherwise default values are generally retained across settings and parameters.
If possible create and use default templates for each processor, with the correct version and the preferred settings , below, already included.
Preferred Settings
| Parameter Tab | Value | |||||||
|---|---|---|---|---|---|---|---|---|
| Processor tab (e.g., TSYS, FirstData, etc) | If available for the selected processor | |||||||
Start Batch Time, | These values should be set close to System Daily Close (EOD) Time set up in ECM. For example, if System Daily Close Time is 4:00AM, set: Start Batch Time: 4:00AM End Batch Time: 5:00AM Also, if there are multiple PAX devices, they should be set up with the same batch time. Each PAX device has its own batch, and it may be reported separately to the merchant, but keeping the same batch time across multiple PAX devices will hopefully allow the funds to appear on the same day in the merchant account. Depending on the processor, the merchant can expect around 2-3 day delays between transaction time and seeing the batch amounts in their account. More info on batch reconciliation that may help explain this, and well it is older, most of the same issues apply: https://www.merchantequip.com/merchant-account-blog/1220/the-myth-of-bankcard-deposit-reconciliation | |||||||
| EMV | ||||||||
| Enable EMV Feature | Enabled | |||||||
| Credit > Pin Bypass | Auto Bypass | |||||||
| Debit > Pin Bypass | Auto Bypass | |||||||
Enable Quick Chip NOTE: Also called Support Quick Chip for some Processors like Heartland. | Enabled
| |||||||
Insert Any Time or Allow Insert Any Time | Disabled - (coming in This function is not supported with Order Entry before version 4.9.1 , not supported before and requires Enable Quick Chip and Http/Https Browser Cancel Mode - Communication tab, as Enabled)
Quick Chip Reset Timer(100ms) 300 - for 30 seconds to hold credit card information in the PAX before it is processed. Only in use with Insert Any Time = Enabled . This function allows for a credit card to be inserted and information held before Order Entry sends a payment request. There are risks with using Enabled and a credit card is inserted, but the cashier opens or changes to a different check. In that instance the wrong credit card is charged for a check.
| Industry | ||||||
| Industry Type | Restaurant | |||||||
| Fleet/Commercial Card Support | Disabled | |||||||
| Disabled Fleet/Commercial Card Prompts | Yes | |||||||
| Allow MOTO | Disabled | Store and Forward |
| Note | ||
|---|---|---|
| ||
Sites using SAF enabled (offline transactions) should have a process ensure transactions are getting settled. *See the bottom. |
Disabled
PAX terminals use only card number, transaction type, and amount to determine duplicates – they don't use invoice number.
Semi Integration Only:
Gift/Loyalty Check type INPUTACCOUNT
For Transactions settings under Credit Features:
- Sale
- Pre-Auth
- Completion
- Refund
- Tokenize
- Void (all settings)
- Transaction Adjustment
Enabled - for all devices.
| Info | ||||
|---|---|---|---|---|
| ||||
Under dropdowns for these settings are:
For 'A'-Series the default may be Manager Protected or Operator Protected, in these instances change to 'Enabled', unless extra security is requested by the owner/site:
|
Disabled - unless requested.
Verify will cause PAX to wait on Yes/No for Pre-Auth, Sale, Tip, Refund and will cause OE to timeout if Server/Cashier is not alert to PAX screen and running the CC.
For all Credit Manual Entry settings under Credit Features (Sale, Pre-Auth, Completion, Refund, etc.)
Restaurant Name on line 1
Address on line 2
City, ST and Zip on line 3
External POS
Quick Chip Reset Timer(100ms)
300 - for 30 seconds to hold credit card information in the PAX before it is processed. Only in use with Insert Any Time = Enabled
| Info |
|---|
There might be an additional setting located on the Misc tab, called Swipe Any Time Timeout (100ms) for different processors like Heartland. |
While the default value (100.00) might be OK, it can be changed as needed for the Merchant, some possible values:
- 100.00 (fast casual, low average check $)
- 250.00 (sit down, using servers $$)
- 1000.00 (fine dining, high average check $$$)
If the Merchant average check is $300, the $1000.00 limit on contactless tap of credit card should be sufficient. However, if the average check is $10, a $1000.00 limit is unnecessary and increases the likelihood of card being overcharged if a cashier makes a mistake. It should also be noted that different credit card brands have limits on what they will allow contactless (less secure) instead of inserting a card (more info, more secure).
Local Duplicate Check (PAXStore setting in Industry)
Disabled*
*PAX terminals use only card number, transaction type, and amount to determine duplicates – they don't use invoice number, unless there is "Local Duplicate Check For ECR Reference Number"
Semi Integration Only:
Gift/Loyalty Check type INPUTACCOUNT
Disabled -default and recommended; Enable only upon request:
Store and Forward (SAF) Setting Guidelines
The Store and Forward (SAF) feature on the PAX device allows automatic approval of payments when communication to the host processor's merchant account is interrupted. This typically occurs due to local network issues at the site or host processor, or incorrect Merchant ID or configuration on the PAX device resulting in communication rejection by the host processor.
Implementation Process:
Initial Disablement: SAF should remain disabled until after the site receives the device and goes live with it onsite. It is advisable to keep it disabled for a few days or weeks until the site validates that credit card funds are successfully received through the daily batching/settlement process. Funds can take 2-3 days to appear in the bank.
Enablement Post-Installation: Enablement of SAF should be scheduled as a post-installation task by Support, Implementation, or the Project Manager. This involves enabling the SAF setting and rebooting or forcing a download of the new PAX configuration.
Risks and Recommendations:
If Store and Forward is requested and enabled, it's crucial for the merchant (site) to understand the associated risks. There are no guarantees that payments taken while offline will be approved by the processor once the system is back online.
SAF Settings for taking Offline Transactions:
- Allow Store & Forward: Enabled
- SAF Mode: Offline on Demand
- Max Number: *500 or 600 (maximum count of SAF transactions at risk)
- Total Ceiling Amount: *$5,000.00 (maximum dollar amount allowed stored in SAF mode, 0 or blank is unlimited).
*Both Max Number and Total Ceiling Amount may vary when considering the number of PAX devices onsite, merchant number of daily transactions and the average check amount. Merchants may want to adjust these values when considering they are per-device limits. For instance, with 4 PAX devices onsite, a $5,000 Total Ceiling Amount per device results in a potential $20,000 at risk if internet interruption is prolonged over multiple days. If the site averages 100 credit card payments per day, per device with an average check of $10, one device could run offline for 5 days.
| Warning | ||
|---|---|---|
| ||
During Staging and Initial Test Transactions: Ensure 'Allow Store & Forward' remains disabled when testing Merchant Account Information (e.g., Merchant ID, Terminal ID, Group ID) with online communication to the Host Processor. Enabling SAF prematurely can lead to potential loss of payments:
Enabling SAF: SAF can be safely enabled and devices updated once Merchant Account Information and communication with the Host Processor are validated through online transaction at the site. Ensure consistent "Approval" messages are logged in c:\program files\custom business solutions\NorthStar Order Entry\Log\PAX.log for each PAX device and verified by the Host Processor for transactions above store. Recommendation for Sites Using SAF: Implement a robust process to monitor and settle transactions regularly. This practice minimizes the accumulation of unprocessed transactions and ensures financial integrity, reducing potential losses. |
Offline On Demand, or Stay Online
SAF Modes Explained:
- Stay Online:
- Description: Processes all credit cards online only, regardless of whether Store&Forward is enabled.
- Recommendation: Use when offline processing is not desired or permitted. Not suitable if Store&Forward functionality is required.
- Stay Offline:
- Description: Accepts all credit cards offline, stores them in a SAF batch on the PAX device, and does not send them to the card processor.
- Recommendation: Not recommended due to potential risks associated with storing transactions indefinitely offline without processor verification.
- Stay Offline Till Batch:
- Description: Accepts credit cards offline, stores them in a SAF batch on the PAX device, and sends them to the processor during the batch process (automated or manual).
- Recommendation: Not generally recommended due to the risk of declines if transactions are not processed immediately.
- Offline On Demand:
- Description: Attempts to process credit cards online. If the processor is unavailable and Store and Forward is enabled, accepts the transaction offline and adds it to a SAF batch for later processing.
- Recommendation: Recommended when using SAF to limit the number of offline transactions stored until batched. Ensures transactions are sent to the processor during the next batch process with any active batch.
- Note: If Store and Forward is disabled, all cards will be processed online only.
Usage Recommendation:
- For Safeguarding Transactions: Use 'Offline On Demand' if you need the flexibility to process transactions offline when necessary, while minimizing the number of transactions held in SAF until batched.
- Considerations: Ensure merchants understand the risks associated with offline processing and the potential for transaction declines if communication with the processor is not restored before processing.
For Transactions settings under Credit Features:
- Sale
- Pre-Auth
- Completion
- Refund
- Tokenize
- Void (all settings)
- Transaction Adjustment
Enabled - for all devices.
| Info | ||||
|---|---|---|---|---|
| ||||
Under dropdowns for these settings are:
For 'A'-Series the default may be Manager Protected or Operator Protected, in these instances change to 'Enabled', unless extra security is requested by the owner/site:
|
Disabled - unless requested.
Verify will cause PAX to wait on Yes/No for Pre-Auth, Sale, Tip, Refund and will cause OE to timeout if Server/Cashier is not alert to PAX screen and running the CC.
For all Credit Manual Entry settings under Credit Features (Sale, Pre-Auth, Completion, Refund, etc.)
Restaurant Name on line 1
Address on line 2
City, ST and Zip on line 3
%, unless requested differently from the merchant:
- 15
- 18
- 20
External POS - (REQUIRED for NorthStar Order Entry)
- The other option, sometimes default is: Internal POS/Standalone. This will set the PAX in Standalone and not interface with Order Entry. It should be noted that the Internal POS/Standalone setting, even if set, does NOT function for all processors on all PAX Android devices. Example: for A35 using FDMS, even if set as Standalone, the screen will stay with the same idle image and only function with an External POS. Internal POS/Standalone is only available if using A920PRO, A80 or other PAX terminal that has a printer, and is usually without a number pad.
Enabled - on restart, the device will start the process app automatically, after it loads the Android Home screen. It also removes the swipe up "Home" and "App Overview" and restricts the "Back" button from exiting the app. In this mode to get to the Android Home screen, the user will need to logon to the app main menu and either select "Exit" at the bottom (not all apps will have that option) or to go into System Settings and disable the Dedicated Device mode. This setting can be used with the "Password on Exit" for more security. Setup the Android settings for the device first as outlined in PAX A35 device or other A-series (Android) Device Setup
PAX_Android_DedicatedDeviceMode-FullScreen-autolaunch_app.mp4
Update After Batch Close - (recommended if present)
Default is Force Close w/Prompt or it may not be available in all apps, but where it exists Update After Batch Close provides a more seamless update and should allow for less user interaction.
Disabled
PAX terminals use only card number, transaction type, and amount to determine duplicates – they don't use invoice number.
Default is mt30_ad1.r (PAX Logo - Blue background). This can be updated to the NorthStar card background for idle screen and even a brand log added as well. To change the idle screen on the PAX device, create a image file to the specification listed when mouse over the file, for that device. Each device will have it's own image size, file type and and resolution or size. All images whether BMP or PNG, will need to be renamed to end in a '.r' type and the name of file cannot be long (best to be 8-9 characters or less). Clicking the file name will open explorer browser to select a new file, and existing image can be downloaded for editing. All images should be tested.
Here are some examples of S300
| Expand | ||
|---|---|---|
| ||
S300 examples of images, with and without brand logo, and the size below is 240x199 (height is shortened) and NFC Logos are on the bottom. Change NFC Logos location so they do not overlap the background image graphics:
Here is the S300 BMP image for NorthStar card background file that can be downloaded and resized |
for different devices, renamed and a brand logo added.
|
Bottom (if used with a Idle Image File) or Right (default)
Terminal Settings > Auto Reboot (Oct 2022 - New Feature for Traditional PAX: D190, S300, etc)
NOTE: Android PAX devices will have a reboot option in the Android Home screen > Settings > Security > Scheduled time reboot
Disabled
NOTE: IP addresses of PAX devices must be known ahead of time so that they can be set up in ECM, which precludes DHCP.
Each PAX device must be set up with its own IP address on the network.
HTTP GET (REQUIRED)
Http/Https Browser Cancel Mode
Set the time zone for the device (required on traditional PAX devices).
For PAX devices that have Android, usually starting with 'A' in the Model name (A35, A920, etc), the time zone must be set with the Android settings on the device itself.
SAF or Offline mode use
It If SAF is enabled at any point for the PAX device, it is strongly recommended that sites periodically, either daily or weekly, check the PAX devices for transaction totals. This is to ensure the PAX devices are settling batching correctly and they are not offline for an extended period. Keep in mind that if the PAX is offline this is usually “invisible” to Order Entry and during the transaction on the PAX device. Offline may only show in a minor change of the approval code on the receipt as it is getting autogenerated by the device and not the processor.
...