Enabling Offline Credit Card Processing
Normally, the internet must be available to process credit cards. Credit card transactions made using the Magtek card reader can be captured in offline mode when the internet is unavailable.
By enabling offline credit card processing, the restaurant can continue to accept credit cards payments when the internet is down. Note, though, that the system is unable to verify that cards are valid when in offline mode. The transaction information is held locally; when the internet becomes available, the information is sent to the payment processor. This prevents an interruption in service, with the small chance of a payment not successfully authorizing when the Internet becomes available.
Once configured, you can decide how many transactions to accept while offline. You can also set limits on the total value you're willing to accept while offline.
Other devices
PAX devices can be configured for offline credit card processing on the device or through BroadPOS/PAX Store to update configurations. (Not configured through ECM for offline processing.)
VX-805 cannot be used for offline credit card processing. Information from the VX-805 device is transmitted directly to the payment processor and it is not held locally. There is no transaction information available to be sent when the internet is back up.
Instructions | |
---|---|
Log into ECM and navigate to the sites page. | |
| Click Edit (pencil) for the site to configure offline credit cards. |
| Click Payment (tab). Select Enable Offline Transactions. Enter the Max Dollar Amount (limited to $9,999.99). This is the maximum value of all offline transactions you're willing to accept while offline. When this limit is reached, transactions will be declined until the Internet connection is restored. Enter the Max Payment Amount (limited to $9,999,99). This is the maximum value of a single transaction you're willing to accept while offline. A transaction exceeding this amount will be declined. Enter the Maximum Transaction Count (limited to 9,999) Save changes and deploy to site. |