Preferred PAX parameters for all processors

This document outlines the NorthStar recommended parameter settings for PAX terminals using PAXSTORE or BroadPOS configuration utilities.

Each PAX device is initially set up at paxstore.us with default settings and parameters tailored for various PAX devices and processors. Parameters are organized across tabs corresponding to different processor applications and versions deployed to the PAX device. 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. 

Preferred Settings

Parameter Tab

Value

Parameter Tab

Value

Processor tab (e.g., TSYS, FirstData, etc)

If available for the selected processor

Start Batch Time,
End 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

This setting allows for quick dip or insert and remove of the card chip without waiting for approval. Generally it still requires a 2-sec dip or less to read the card and is a pre-requisite, separate setting for the Insert Any Time feature. Disabled can cause more instances of "CHIP READ" errors on the PAX when the card is removed quickly.

  

Insert Any Time or Allow Insert Any Time

 

Disabled - This function is not supported with Order Entry before version 4.9.1 and requires Enable Quick Chip and Http/Https Browser Cancel Mode - Communication tab, as 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. 

There might be an additional setting located on the Misc tab, called Swipe Any Time for processors like Heartland.

 

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 

 

There might be an additional setting located on the Misc tab, called Swipe Any Time Timeout (100ms) for different processors like Heartland.

 

Contactless Limit

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). 

Industry

 

Industry Type

Restaurant

Fleet/Commercial Card Support

Disabled

Disabled Fleet/Commercial Card Prompts

Yes

Allow MOTO

Disabled

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"

Local Duplicate Check For ECR Reference Number

Enabled

Semi Integration Only: 

Gift/Loyalty Check type INPUTACCOUNT

Excluded from Credit Bin - this will send Gift Card and Mag Card info back to Order Entry for processing.

Allow Store & Forward

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.  

 

SAF Mode

Offline On Demand, or Stay Online

 

SAF Modes Explained:

  1. Stay Online:

  2.  

    • 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.

  3. Stay Offline:

  4.  

    • 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.

  5. Stay Offline Till Batch:

  6.  

    • 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.

  7. Offline On Demand:

  8.  

    • 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.

Max Number (Store and Forward section)

500 (number of SAF transactions allowed for this device)

Total Ceiling Amount

5000.00 ($5000.00 in SAF transactions for this device)

EDC

 

Auto EDC Support (if it exists)

Disabled - Do not use "All EDC" or "Credit & Debit" or PAX will not prompt for TIP 

AID Filter Rule (if it exists)

Auto Credit

For Transactions settings under Credit Features:

  • Sale

  • Pre-Auth

  • Completion

  • Refund

  • Tokenize

  • Void (all settings)

  • Transaction Adjustment

Enabled - for all devices.  

 

Credit Features > Verify (if available)

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.)

Enabled

Secure Card (Credit Features>Others)

Disabled

Tip (Credit Features>Others)

Enabled

Debit (Debit Features)

Disabled

EBT (if option available, EBT Features)

Disabled

Receipt

 

*add customer info (among other things this can used for troubleshooting with card processors who will look for Merchant info and also for PAXSTORE reporting)

Restaurant Name on line 1

Address on line 2 

City, ST and Zip on line 3

Tip

 

Tip Select

Disabled (Optional - If enabled it should be noted that Tip Select will prompt for $ selection, unless all $ amounts are set to $0.00, then it will go to %. If using % it is based on the Total sent to PAX, not counting adjustments and including Tax). See: PAX Device - Select Tip % Buttons

Input Mode 

Input Tip Amount

Tip Edit Confirm (Android)

Disabled - Note if enabled the prompt for Tip confirmation on PAX (Android) device, might cause the Order Entry to 'move on'/get out of sync with PAX device. Example: Transaction might wait for Credit Card Tip/Process and meanwhile the guest is saying 'No' to Tip Confirmation on PAX, PAX goes forward to process, but Order Entry cancels or gets stuck in processing mode. 

Tip Unit

In Cents (should be default)

Amount Option (1-3)

0.00 (0.00 allows PAX to skip down to using %   

Percent Option (1-3)

%, unless requested differently from the merchant:

  • 15

  • 18

  • 20

Misc

 

(Android) ECR-Terminal Integration Mode

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.   

(Android) Dedicated Device (Full Screen) Mode

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

(Android) Password on Exit

Enabled - added security to restrict from leaving the processor app to the Android Home screen. Use with Dedicated Device (Full Screen) mode

(Android) Batch Close for App Update

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.

Local Duplicate Check  (BroadPOS setting on Misc tab, it may also be Industry tab depending on processor.)

Disabled

PAX terminals use only card number, transaction type, and amount to determine duplicates – they don't use invoice number.

Idle Image File

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.
 

 

 

Support Print

Disabled

Contactless Module (Peripheral Features)

Internal if supporting tap-to-pay; otherwise. Disabled

Receipt Settings > Pre-print

Disabled

Function Menu Protection (Android)

Manager Protected

NFC Logo Settings > Pay Logo (all logos)

Both

NFC Logo Settings > Logo Orientation

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

Enabled - 0530 (time should be after batch time and before opening the site, this should force device to get PAXSTORE App/Settings Update)

Communication

 

DHCP

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.

Ping URL

www.google.com

DNS

If not specified 8.8.8.8 and/or 8.8.4.4 in DNS 1 & 2

Communication Type 

Ethernet   (REQUIRED)

Protocol Type

HTTP GET   (REQUIRED)

Http/Https Browser Cancel Mode

Enabled   (REQUIRED with Insert Any Time)

BroadPOS

 

Time zone

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

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 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.

The best time to check for transactions that are not settled is by logging onto each PAX device in the morning and before new transactions for the day. If found, the site can attempt to manually batch and/or call into support to troubleshoot any network or config issues.

To check the current active transactions/amounts:

  • Log on to the PAX device main menu, enter password. 

  • Tap Display Transactions

  • Tap Review

  • Enter password

To manually batch:

  • Log on to the PAX device main menu, enter password. 

  • Tap Settings

  • Enter password

  • Tap Batch Close

  • Tap Batch All

  • If prompted, tap Yes to close without tip.