A payment gateway is a crucial component of the electronic payment processing system, as it is the front-end technology responsible for sending customer information to the merchant-acquiring bank, where the transaction is processed. Customers' private data (i.e., credit or debit cards) can travel via a safely established channel between the payment processor and Lunchbox.

A payment processor handles credit card transactions and funds transferred from the payment gateway to the merchant's bank account. It communicates and relays information from the customer's card to the merchant's and customer's banks. Lunchbox integrates with different payment processors.

There is a specific way to set up each payment processor inside Lunchbox.

Integrated payments, such as Apple Pay and Google Pay, allow users to make payments in person and online when placing an order with Lunchbox. Integrated Payments are only supported by some POS and can replace a credit or debit card transaction at a contactless-capable point-of-sale terminal.

There are many ways to pull reports in Lunchbox. All reports can be printed or exported to Excel. The best way to see a payment report is to pull a Credit Card Detail. This report displays the online orders, total $ amounts, credit card type used for the orders, authorization codes sent by your merchant when the credit card was authorized, the reference number for the captured amount, and refund date/amount, if any.

Lunchbox integrates with multiple POSs (i.e., Toast, Aloha, Revel, Brink), and each POS has its own limitations on how to cancel, void, refund, and adjust payment. Each integration will determine if the action should be first taken on the POS or inside Lunchbox. Double-check both systems to ensure that cancel, void, refund, and adjust payments are appropriately performed.

Merchants can opt to reconcile payments against POS by pulling a payment report from their integrated POS and comparing it to Lunchbox. Because of POS limitations when integrating order cancelation, refunds, and/or adjustments payments inside Lunchbox, merchants should double-check both systems for reporting accuracy.

Payment failure error messages can have varying causes (i.e., payment declined). It's important to recognize the root of the error before troubleshooting the problem.

Handling disputes works differently for each payment processor. Operators can manage disputes through each of the processor's dashboards.

Merchants can enable SIFT inside the Lunchbox dashboard to help prevent fraudulent transactions. SIFT protects transactions and automates payment reviews with advanced machine learning and fraud detection capabilities, allowing the technology to detect and block suspicious transactions automatically. Lunchbox uses SIFT by comparing customer emails to the SIFT fraud score. The transaction will be declined if the customer fraud score exceeds the threshold in Lunchbox's dashboard.

Pay at Store allows guests to place their orders online using Lunchbox without entering a CC because they have agreed to pay for the order on-site upon pickup. Pay at Store also allows guests to pay in cash since they will pay in person at the location.