Preferred PAX parameters for all processors

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

Enabled

Insert Any Time or Allow Insert Any Time

Quick Chip Reset Timer(100ms)

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

Offline On Demand, or Stay Online

SAF Modes Explained:

1. 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.
2. 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.
3. 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.
4. 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

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

Disabled

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

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.