Payment processing
tbltap provides the guest payment surface for restaurant transactions, while third-party payment processors handle card processing. For restaurant food and service transactions, the restaurant is the merchant of record; tbltap is not the merchant of record, bank, money transmitter, food provider, or payment processor.
- Guests should only enter payment details in the secure checkout flow.
- tbltap does not ask for full card details through email or support chat.
- Receipts and payment status can depend on processor confirmation.
- The restaurant is responsible for what it sells, taxes, fulfillment, service decisions, refund policy, disputes, and chargebacks.
- Card issuer holds, reversals, and disputes may take time outside tbltap.
Quick Pay from the table
When restaurant staff marks a table bill ready for payment, the table tag can become a Quick Pay entry point for that bill instead of only opening the menu.
- Guests can scan or tap the same tbltag at the table to reach the active bill when the table is in billing mode.
- Quick Pay can work for guests who did not use the public menu to order, as long as staff entered the table items into the bill.
- Split-bill options may let guests pay the full bill, an equal share, or selected items depending on the active payment flow.
Refunds and order issues
Restaurants own fulfillment and customer service decisions. tbltap helps route platform and payment questions to the right place.
- Start with restaurant staff for food, service, timing, or substitution issues.
- Contact support for duplicate charge, payment page, receipt, or platform access questions.
- Include the restaurant name, visit date, and any receipt details when asking for help.