Skip to main content
Shift4 Server Status

What Can We Help You With?

Store & Forward Mode for BroadPOS Shift4

  • Updated

Description: The following guide outlines the appropriate steps for PAX devices running the
BroadPOS Shift4 application to set up and adjust “Store & Forward” settings (also called “SAF”
or colloquially called “Offline Mode”).

Offline Disclaimer

The merchant is responsible for the risks and declines potentially associated with taking offline
transactions and there are no guarantees that transactions will be approved when uploaded. The merchant is also responsible for uploading their offline transactions in a timely manner.

Each location has its own networking environment and the offline mode settings will need to be
determined per location to best suit their needs.

SAF should always be disabled when it is not needed, such as when internet connectivity has
been restored. If a location desires its SAF to be enabled at all times, it assumes responsibility for the risks and declines potentially associated with taking offline transactions.

Adjusting SAF Settings via PAXSTORE

Finding the Terminal

Important: Updating the Store & Forward (SAF) settings via PAXSTORE means that the next user to
touch the file will need to ensure they disable or double-check the SAF settings before
completing a push task unrelated to SAF. Accidentally forcing a device into offline mode could
have heavy repercussions for the merchant and their customers! Additionally, some SAF
settings are only available in PAXSTORE and not the terminal-level settings and vice-versa.

Log in to the PAXSTORE website using your assigned credentials.


Click on the Market Place List (3 x 3 grid) button at the top right of the window by your user name.

Click SHIFT4 MARKETPLACE from the Marketplace List.

Click on Terminal Management on the left side panel.

Click the Terminal List tab from the navigation along the top.

Enter the search criteria (usually MID or device SN) into the search bar, then click the desired device from the results list.

Important: Ensure the search category is “Name” or “SN” depending on what you plan to search. (Example: if searching by MID, use “Name.” If searching by device serial number, use “SN.”)

Once you enter your search criteria and select enter, click on the device that matches what you’re searching for. Ensure that the device shows that it is “Online”!

Adjusting the BroadPOS Shift4 App Settings

After clicking the device you desire to update, you will be brought to its general information page. Begin by clicking on App & Firmware.

Click on the down arrow in the Operation History box.

Click the latest successful push of the BroadPOS Shift4 app.

Click the Reset button in the bottom right corner.

Click OK.

SAF Settings

Click the Industry tab.

Click on the Store And Forward box to expand it.

Set Allow Store&Forward and SAF Mode to the location’s desired settings.

  • Allow Store&Forward has two options:
    • Enabled allows SAF to function dependent on its SAF Mode.
    • Disabled will not allow SAF to function at all.
    • This setting can also be adjusted via terminal-level settings.
  • SAF Mode has 4 different settings.
    • Stay Online: The application will behave as if it were online and SAF will not be able to trigger at all. This means that if the device has no internet connectivity, it cannot record offline transactions!
    • Stay Offline: The application will be forced into an offline state until the user returns to this page and takes it off this mode. An “OFFLINE” indicator will appear within the BroadPOS application while in Internal POS/Standalone Mode.
    • Offline Till Batch: The application will be forced into an offline state until the user initiates a “Batch” command within the “FUNC” menu or takes it off this mode manually. An “OFFLINE” indicator will appear within the BroadPOS application while in Internal POS/Standalone Mode.
    • Offline On Demand: The application determines its online/offline state per transaction. If it is able to complete a sale with no network connectivity issues, it will do so. However, if it encounters a transaction it cannot complete due to network connectivity issues, it will then do one of two things depending on terminal-level, user-defined SAF settings:
      • Prompt if the user desires to re-attempt the transaction or store it as an offline transaction
      • Immediately store it as an offline transaction with no prompt
        There will not be an “OFFLINE” indicator in Offline On Demand mode.
    • This setting can also be adjusted via terminal-level settings.

Set Max Number and the various Ceiling Amounts to the desired settings.

  • Max Number refers to the total amount of transactions that the application is allowed to store as offline transactions before it requires an upload or clearing. Once the application reaches the number of transactions defined in this parameter, it cannot take more until the user uploads or clears their current offline transactions or adjusts this number.
    • This setting cannot be adjusted via terminal-level settings and can only be adjusted via PAXSTORE.
  • Total Ceiling Amount sets a hard limit on the total amount that offline transactions can add up to before it requires an upload. Once the application reaches the limit defined in this parameter, it cannot take more transactions in SAF mode until the user uploads or clears their offline transactions or adjusts this ceiling amount.
    • This total is for all card brands.
    • This setting can be adjusted via terminal-level settings.
  • [Card Brand] Ceiling Amount sets a hard limit on the total amount for the card brand defined that offline transactions can add up to before it requires an upload. Once the application reaches the limit defined in this parameter, it cannot take more transactions in SAF mode for that card brand until the user uploads or clears their offline transactions.
    • This total is per card brand.
    • Per card-brand settings cannot be adjusted via terminal-level settings and can only be adjusted via PAXSTORE.

Next, edit the High Amount Lock Out (HALO) Amounts for each card brand if needed.

  • HALO Amounts are hard limits for transactions. A singular transaction cannot exceed the amount defined by the HALO amount. If a transaction exceeds the amount, the application will refuse it.
    • The HALO Amount includes tips. If the HALO amount is for $1.00 and a transaction with the base amount of $1.00 and a $0.01 tip comes in, the application will refuse the transaction as it exceeds the defined HALO amount.
    • There is no equivalent for offline transaction HALO settings via the terminal-level. The HALO settings available via terminal-level settings affect all transactions, offline or online!

Set SAF Upload Mode, Auto Upload Interval Time, and Delete SAF Confirmation to the desired settings.

  • SAF Upload Mode has two settings.
    • Upload Before Batch will cause the application to attempt to upload stored offline transactions when the user uses the “Batch” function within BroadPOS. The user can still manually upload transactions with the Store&Forward function.
    • Silent Auto Upload will cause the application to upload stored offline transactions when the device detects that it has obtained an internet connection. Silent Auto Upload does not supply the user with upload confirmation receipts (per transaction) when the upload occurs. The user can still manually upload transactions with the Store&Forward function, though auto upload may occur before they can do so.

      Important: In order for Silent Auto Upload to function at all, the Auto Upload Interval Time must be configured with a valid entry. Neglecting this fact will result in Silent Auto Upload being unable to upload without manual user intervention.
    • This setting can be adjusted via terminal-level settings.
  • Auto Upload Interval Time (100ms) defines the amount of time the application will wait before attempting to upload offline transactions when it detects that it has an internet connection.
    • This parameter only applies if SAF Upload Mode is set to Silent Auto Upload.
    • This setting must be configured if SAF Upload Mode is set to Silent Auto Upload. If it is not configured or is configured incorrectly, Silent Auto Upload will not function. Always double-check this parameter if the location is working with SAF’s Silent Auto Upload.
    • The units are defined as 100ms, so entering “1” will result in a 1 second delay before the application attempts to upload. Entering “10” results in a 10 second delay (and so on.) There is no limit defined within the file, but so far only values between 1 and 10 have been tested.
    • This setting cannot be adjusted via terminal-level settings and can only be adjusted via PAXSTORE.
  • Delete SAF Confirmation has two settings.
    • With Prompt ensures that a warning prompt will appear asking if the user wants a report of all the transactions that failed to receive approval in a given uploading of offline transactions.
    • Without Prompt ensures that a warning prompt will not appear asking if the user wants a report of all the transactions that failed to receive approval in a given uploading of offline transactions.
    • This setting can be adjusted via terminal-level settings, however it is named “Print Failed Report With Prompt” in the application.

Once the desired settings are entered, click Next in the bottom right corner.

If the location is ready to update that device, click Activate in the bottom right corner.

Click OK. The update will then become active.

Regardless of whether or not the location has done transactions for the day, have the merchant open the BroadPOS Shift4 application if it is not already open.

For locations that need to “batch out” their BroadPOS Shift4 application, they will see a pop-up in the application after you Activate the update. They need to tap OK on the device screen to “batch out” their device so the update can install.

Note: The user must be in the BroadPOS Shift4 application and have “unbatched” transactions in the app in order to see this pop-up. Additionally, this does not affect their deposit for the day and is simply a report of transactions that the device has recorded since their last “batch out”. If the location relies on the printout from the PAX A930 for their auditing/reporting, please advise them to hold on to this report as the device will delete this record when “batched out.”

If no pop-up appears when the application is entered, then the device has likely installed the update as the app’s transaction database was empty.

The user should test the application to ensure that the desired settings have been set.

Adjusting SAF Settings In the A930

If the merchant desires to flip the BroadPOS Shift4 application in and out of Store & Forward Mode (SAF, or “Offline Mode”) manually on the device itself, the following steps will explain how to adjust the settings pertaining to SAF within the BroadPOS app.

Accessing the BroadPOS App Settings

  • For devices currently in External POS mode, refer to Figure A. The user must tap on the icon in the top right corner of the screen and they will then be prompted for a password.
  • For devices currently in Internal POS/Standalone mode, refer to Figure B. The user must tap on the FUNC button, then the Settings button, and they will then be prompted for a password.

                                            Figure A                                                           Figure B

When prompted for the password, the password is the current date in a MM/DD/YYYY format.

Example: The date of January 3rd, 2023 will be entered as 01032023.

Once in the settings page, the user must tap on Operation Settings.

Store & Forward’s Main Toggle

Once in the Operation Settings list, the user must swipe up on the terminal screen in order to scroll down. The user must find “Store&Forward” and from there they can tap on the option in order to toggle it between Disabled and Enabled. A blue slider indicates that it is Enabled. A gray slider indicates that it is Disabled.

  • When Enabled, SAF is allowed to function depending on the Store&Forward Mode set.
  • When Disabled, SAF is not allowed to function at all.

An example receipt while SAF is active; note the “pending transaction” tag!

If the user needs to make no other changes, they can now exit the settings by pressing the Back

 button on their device until they’re returned to the front page of the BroadPOS application.

Store & Forward Mode

If the user has Enabled their Store&Forward, they must now edit their Store&Forward Mode. They can choose what mode they desire by tapping on Store&Forward Mode. The S&F Mode will need to be determined and set by the user’s network conditions and desires.

  • Stay Online: The application will behave as if it were online and SAF will not be able to trigger at all. This means that if the device has no internet connectivity, it cannot record offline transactions.
  • Stay Offline: The application will be forced into an offline state until the user returns to this page and takes it off this mode. An “OFFLINE” indicator will appear within the BroadPOS application while in Internal POS/Standalone Mode.
  • Offline Until Batch: The application will be forced into an offline state until the user initiates a “Batch” command within the “FUNC” menu or takes it off this mode manually. An “OFFLINE” indicator will appear within the BroadPOS application while in Internal POS/Standalone Mode.
  • Offline On Demand: The application determines its online/offline state per transaction. If it is able to complete a sale with no network connectivity issues, it will do so. However, if it encounters a transaction it cannot complete due to network connectivity issues, it will then do one of two things depending on later-defined SAF settings:
    • Prompt if the user desires to re-attempt the transaction or store it as an offline transaction
    • Immediately store it as an offline transaction with no prompt

There will not be an “OFFLINE” indicator in Offline On Demand mode.

The “OFFLINE” indicator for applicable modes will appear like so:

Store & Forward Upload Mode

Once the Store&Forward Mode desired has been set, the next setting to adjust is the Upload Mode. The user must tap Upload Mode to select it.

  • Upload Before Batch: The application will upload offline transactions when the user taps the “Batch” function in the “FUNC” menu. The application will automatically print out a report as the upload completes. Preferably, the user should upload offline transactions manually (covered later in the guide.)
  • Silent Auto Upload: The application will automatically upload offline transactions when the device establishes an internet connection again. The application will not automatically print out receipts regarding the transactions uploaded by this mode!
    • The parameter titled “Auto Upload Interval Time (100ms)” must have a valid entry in it. This can only be configured via PAXSTORE! If the parameter is blank or has an invalid entry in it, Silent Auto Upload cannot function at all and the user will need to manually upload their offline transactions!

Retry If Offline On Demand

Once the Upload Mode has been set, the next setting that can be adjusted is “Retry If Offline On Demand.” A blue slider indicates that the option is Enabled. A gray slider indicates that the option is Disabled. Tapping on the slider will toggle it on and off.

  • If Enabled, this only matters if the Store&Forward Mode is set to Offline On Demand. When a transaction fails due to network-related issues while SAF is Enabled, a prompt will appear asking the user if they wish to simply retry the transaction like normal or instead log it as an offline transaction.
  • If Disabled, all transactions that fail due to network connectivity issues while SAF is Enabled and in Offline On Demand mode will be immediately logged as an offline transaction with no prompt.

The prompt if Enabled:

Print Failed Report With Prompt

Once the Retry If Offline On Demand option has been set, the next setting that can be adjusted is “Print Failed Report With Prompt.” A blue slider indicates that the option is Enabled. A gray slider indicates that the option is Disabled. Tapping on the slider will toggle it on and off.

  • If Enabled, when the user uploads their offline transactions and any transaction gets a declined response, the application will prompt if the user would like a report detailing the totals for declined transactions.
  • If Disabled, when the user uploads their offline transactions and any transaction gets a declined response, the application will not prompt if the user would like a report detailing the totals for declined transactions.

The prompt if Enabled:

Credit Total Limit

Once the Print Failed Report With Prompt option has been set, the next setting that can be adjusted is “Credit Total Limit.” The user must tap on the “Credit Total Limit” option to select and edit it.

The Credit Total Limit defines a hard limit on the total amount offline transactions can add up to before an upload is required. This total, if set, will need to be determined by the user.

Example: If the Credit Total Limit is set to $1.00 and there is already a transaction stored offline for $0.99, the next transaction can only be completed if it is for $0.01. If it is for $0.02 or greater, the device will not allow it until the current offline transactions are uploaded.

Additionally, this also means that no transaction taken offline can be greater than $1.00.

 



 

Uploading Transactions from SAF

Uploading and auditing offline transactions should always be completed whenever internet connectivity is restored.

In order to upload transactions taken while offline, the merchant must initiate the upload manually. This can be accomplished by navigating to the proper function in the BroadPOS Shift4 application. The user must tap on the FUNC button.

The user must tap on the Store&Forward button.

The user must tap Upload Trans.

The device will attempt to upload all transactions that have been marked as taken while offline. As the application uploads SAF transactions for approval, it will print out a receipt of each transaction and whether they are approved or declined. These transactions – successful or failed – can also be confirmed in the Lighthouse Transaction Manager.

If transactions fail, they need to be taken care of as soon as possible.

Note: If any transaction declines when uploaded, the device will display a warning of “UPLOAD FAILED.” This does not mean that the entire upload failed and it only means that the upload had at least one decline in it. Additionally, if “Print Failed Report With Prompt” is Enabled, the device will prompt the user if they’d like a printout detailing the totals of all failed transactions that were uploaded.

Reviewing Currently Stored/Failed Offline Transactions

If the user would like to review all offline transactions that are currently unuploaded or failed, the user must first tap on FUNC.

The user must then tap on the Store&Forward button.

The user must then tap on the Display Trans. button.

The user must then tap on the Scroll All button.

The user will be asked what type of transaction they are looking for: Stored (un-uploaded) or Failed (uploaded but declined). The user must tap on the empty box above CONFIRM. They may then tap on the type of transaction they desire to review.

The user must then tap on CONFIRM after they’ve selected which type of offline transaction they’d like to review.

The user will be shown all transactions that are currently applicable to their desired search. Swiping up on this screen will scroll through transactions if there are more than can fit on the page at once. Additionally, the user can tap on a transaction to review it in greater detail.

Once the user is done reviewing the transaction, they can tap CONFIRM to return to the search results.

Resending/Reattempting Failed Transactions

Note: Failed transactions denote that the transaction was declined. Reattempting failed transactions repeatedly can result in complications for the cardholder and the business. If the user desires to write off failed transactions as being entirely lost, the user should delete the failed transactions. The process of deletion will be covered further down the guide.

To resend or reattempt authorization for failed offline transactions after upload, the user must first tap on FUNC.

The user must then tap on the Store&Forward button.

The user must then tap on Resend Failed.

If the user desires to re-attempt authorization for all currently Failed offline transactions, they can tap OK. Otherwise, they can tap Cancel.

Obtaining Reports for SAF Transactions

In order to obtain proper reporting for SAF transactions, the user must navigate to the reporting area within the Settings of the BroadPOS application.

The user must tap on the FUNC button, then the Settings button, and they will then be prompted for a password.

When prompted for the password, the password is the current date in a MM/DD/YYYY format. Example: The date of January 3rd, 2023 will be entered as 01032023.

Once in the settings page, the user must tap on Operation Settings.

Once in the Operation Settings, the user can swipe up on the screen to scroll down through the settings. The user will need to find the option “Reports” and tap on it to select it.

There are three different types of reports: Status, Offline, and Failed and they will be covered in their own sections ahead.

Print Status

Print Status prints out the totals of both currently stored (un-uploaded) transactions and failed (uploaded & declined) transactions.

In this example, the SAF Mode is set to “OFFLINE ON DEMAND MODE”. Depending on the SAF Mode set in the user’s application, this text will change accordingly.

Max Sales Total: This indicates the hard limit defined by the user’s “Credit Total Limit”. The total amount between all non-uploaded offline transactions nor a singular offline transaction can go beyond this limit.

Total # Offline: The total number of transactions that are stored offline. This only counts transactions that are offline and have not yet been uploaded.

Total Offline: The total amount all the offline transactions add up to. This only counts transactions that are offline and have not yet been uploaded.

Total # Loss: The total number of transactions that have been uploaded but received declines.

This only counts transactions that were offline and have been uploaded.

Total Loss: The total amount all the declined transactions amount to. This only counts transactions that were offline and have been uploaded.

Offline Records: The total number of transactions that are stored offline. This only counts transactions that are offline and have not yet been uploaded.

Offline Overall: The total amount all the offline transactions add up to. This only counts transactions that are offline and have not yet been uploaded.

Lost Records: The total number of transactions that have been uploaded but received declines.

This only counts transactions that were offline and have been uploaded.

Lost Overall: The total amount all the declined transactions amount to. This only counts transactions that were offline and have been uploaded.

Print Offline

Print Offline prints out a report that shows a condensed version of basic information of each transaction that is currently stored offline. This does not include transactions that have been uploaded successfully or received a decline.

In this example, there are 3 sales. If one of these sales were instead a refund, it would mark it accordingly.

Terminal Reference #: The internal invoice number used by the PAX device for the offline transaction.

Card Type: The card type recorded for the offline transaction.

Account: The last 4 digits of the card for the offline transaction.

Entry: The method that the card was entered for the offline transaction. Common entry types are swiped or insert (EMV chip). Other entry types exist. Total: The total of the offline transaction.

Print Failed

Print Failed prints out a report that shows all offline transactions that were uploaded but received a declined response. These are failed transactions that are currently stored and are waiting to be re-attempted or deleted.

Terminal Reference #: The internal invoice number used by the PAX device for the offline transaction.

Card Type: The card type recorded for the offline transaction.

Account: The last 4 digits of the card for the offline transaction.

Entry: The method that the card was entered for the offline transaction. Common entry types are swiped or insert (EMV chip). Other entry types exist. Total: The total of the offline transaction.

Deleting Failed Transactions

Deleting failed transactions means that the user desires to write off their failed transaction(s) entirely. Once a failed transaction is deleted, it cannot be recovered or resubmitted via the device.

The user should decide on what to do with failed transactions immediately after an internet outage ends.

The user must tap on the FUNC button, then the Settings button, and they will then be prompted for a password.

When prompted for the password, the password is the current date in a MM/DD/YYYY format.

Example: The date of January 3rd, 2023 will be entered as 01032023.

Once in the settings page, the user must tap on Operation Settings.

Once in the Operation Settings, the user can swipe up on the screen to scroll down through the settings. The user will need to find the option “Delete Failed” and tap on it to select it.

Once in the Deleted Failed section, the user has two choices to delete transactions. All, and By Trans. No.

  • All: Deletes all transactions that are marked as Failed – these are offline transactions that received a decline response when uploaded. The user must tap All and then OK.
  • By Trans. No.: Deletes a specific transaction that is marked as Failed – these are offline transactions that received a decline response when uploaded. The user must tap By Trans. No. and then OK. The user must then enter their desired transaction number (which can be obtained from the SAF reporting function) to delete.

FAQ

Q: How will some SAF Modes appear when doing transactions?

A: Depending on the SAF Mode set, they will appear to the user as follows:

  • Stay Online: SAF cannot trigger at all. Transactions cannot be stored offline at all.
  • Stay Offline: Transactions will run and complete like normal with no differentiation in process. Receipts will show a “Pending Transaction” tag.
  • Offline Till Batch: Transactions will run and complete like normal with no differentiation in process. Receipts will show a “Pending Transaction” tag.
  • Offline on Demand: Transactions will run and complete like normal with no differentiation in process unless “Retry If Offline On Demand” is set to Enabled. If “Retry If Offline On Demand” is Enabled, the user will be prompted upon transaction failure(due to network connectivity issues) to either retry the transaction or store it as an offline transaction. Receipts will show a “Pending Transaction” tag if they are stored offline.

The prompt for “Retry If Offline On Demand”:

An example receipt while SAF is active; note the “pending transaction” tag!

Q: Why can’t I take Debit-type transactions while offline?

A: Debit-type transactions cannot be completed while offline. The card will instead need to be run as a Credit-type transaction.

Q: The application isn’t showing “OFFLINE” and my receipts aren’t showing “Pending Transaction”. Why?

A: There are a few points to check here:

  • Is the device actually offline?
  • Is the proper SAF Mode set in regards to the “OFFLINE” indicator? Currently, the SAF Modes of Stay Offline and Offline Till Batch are the only modes that display the “OFFLINE” indicator. If the application is set to Stay Online or Offline on Demand, it will not display an “OFFLINE” indicator.
  • Is the proper SAF Mode set in regards to the receipt not showing “Pending Transaction”?
    • If set to Stay Online, SAF can never store transactions offline.
    • If set to Stay Offline or Offline Till Batch and receipts still do not show “Pending Transaction,” restart the device and then re-confirm the settings in the BroadPOS application.
    • If set to Offline on Demand, is the device actually offline?

Q: The application said “UPLOAD FAILED” when I uploaded my offline transactions. Did the entire upload fail?

A: If a single transaction gets a declined response when uploaded, the application will display the “Upload Failed” message. This does not mean that the entire upload failed and it only means that the upload had at least one decline within it. Reviewing the receipts that print during an upload, printing a SAF report, or reviewing currently stored transactions in the SAF function menu can help figure out what still remains un-uploaded and what

Comments

0 comments

Please sign in to leave a comment.

Help improve this platform

Provide Feedback

Would you like to contact us?