tbltap

Restaurant Payments, Fees, Refunds & Disputes

How Tbltap, restaurant merchant-of-record responsibilities, Stripe Connect fees, payouts, refunds, and disputes work.

LegalUpdated Jun 12, 2026

Effective Date: June 12, 2026

This document explains Tbltap's current business-customer billing model for restaurant partners. It is intended to be read together with the Tbltap Terms of Service, order flow, store flow, and applicable Stripe terms.

Tbltap is a platform marketplace and guest-experience service. For restaurant food, beverage, service, and similar transactions, the restaurant is the merchant of record unless a specific checkout flow expressly states otherwise. Tbltap is not the restaurant merchant of record, food provider, payment processor, bank, stored-value provider, or money transmitter.

1. Current Fee Model

As of June 12, 2026, Tbltap's standard restaurant fee disclosures are:

  • A restaurant-paid Tbltap usage fee on each customer charge, collected from restaurant proceeds through Stripe Connect. Diners see a clean bill; Stripe charges the diner only the bill, tax, tip, and other restaurant-approved amounts shown in the order flow. The usage fee is:
    • Dine-in: 25 cents + 0.5% of the charge base, per charge
    • Pickup: 40 cents + 2% of the charge base, per charge
    • Minimum platform usage fee: 20 cents per qualifying charge
    • The "charge base" is everything the diner pays except the tip, including food subtotal, tax, service charge, and similar restaurant-approved charges. Tip-only add-ons are not charged a Tbltap usage fee.
  • Stripe processing fees charged separately under Stripe's terms
  • Restaurant membership: a 14-day free trial, then $24.99/month per location
  • Physical tbltags: $34.99 for a Production NFC Kit (24 tags), or $24.99 for a Trial Kit (24 tags)

Taxes, shipping charges, duties, import fees, currency-conversion fees, processor fees, and similar third-party charges are separate unless Tbltap expressly states otherwise in the applicable checkout or order flow.

2. How Customer Payments Work

Tbltap's current standard restaurant payment flow uses Stripe Connect.

For restaurants on that flow:

  • the restaurant is the merchant of record for restaurant food, beverage, service, and similar transactions
  • customer charges are created on the restaurant's connected Stripe account
  • Stripe charges the diner only the bill, tax, tip, and other restaurant-approved amounts shown in the order flow
  • the Tbltap usage fee is not added on top of the diner's bill as a separate Tbltap surcharge
  • Tbltap collects its usage fee from restaurant proceeds via the Stripe Connect application fee on each charge
  • Tbltap software may create, confirm, manage, route, display, or reconcile charges, refunds, disputes, and payout metadata
  • Stripe handles regulated payment processing, settlement, charge movement, risk controls, and payout movement
  • payout timing depends on Stripe verification, Stripe payout schedules, reserves, holds, reviews, and other risk controls

Tbltap is not the restaurant merchant of record, payment processor, bank, stored-value provider, or money transmitter.

3. Restaurant Responsibilities

Restaurants are responsible for:

  • menus, pricing, item descriptions, taxes, service charges, and required disclosures
  • order acceptance, preparation, fulfillment, customer communications, and local permits
  • refund policy decisions and customer-facing refund communications
  • dispute responses, chargeback evidence, and order records
  • connected-account verification, tax information, payout information, and processor compliance

Tbltap may provide software, support routing, and operational tooling, but Tbltap does not control restaurant fulfillment, refund entitlement, chargeback outcomes, or processor decisions.

4. Tbltap Fee vs Stripe Fee

Tbltap's fee and Stripe's fee are different:

  • Tbltap's usage fee is the per-charge fee charged for using Tbltap's payment and commerce tooling, collected from restaurant proceeds through Stripe Connect
  • Stripe's fee is the processor fee charged by Stripe for payment processing and related services

Unless Tbltap explicitly states otherwise, these fees are separate and may both apply to the same restaurant transaction.

5. Membership Billing

Restaurant membership begins with a 14-day free trial and then renews automatically at $24.99/month per location on the billing interval shown at purchase, unless canceled before the renewal cutoff.

Current membership policy:

  • cancellation is scheduled for period end
  • current-cycle membership charges are non-refundable
  • access remains active until the end of the paid period
  • Tbltap may reject a cancellation request if the renewal window has already closed

6. tbltags

tbltags are licensed products, not sold outright. Each license is restaurant-scoped, non-transferable, and subject to the tbltags License Agreement, purchase terms, and checkout flow shown for the applicable kit.

7. Refunds

Restaurants control the customer-facing refund policy they offer to diners.

Tbltap cannot decide, approve, guarantee, or process refunds on behalf of restaurants unless the restaurant has authorized the action through platform tooling, staff permissions, support workflows, or another approved instruction. Tbltap may provide software tools that let authorized restaurant staff or authorized Tbltap support personnel route, assist with, or process restaurant-approved refunds through Stripe.

A processor may keep or separately charge processor-side fees related to the original charge, the refund, or both. For restaurants using Stripe Connect, refunds may reduce the Stripe balance on the connected account or affect future payouts.

8. Disputes and Chargebacks

If a customer disputes a restaurant charge:

  • the restaurant is responsible for accurate order records, timely evidence, and customer communications
  • Tbltap may surface dispute information or operational tooling in the platform
  • Stripe may debit the connected account or future payouts for the disputed amount, related fees, reversals, or negative-balance recovery under Stripe's terms

Tbltap does not control processor-side dispute outcomes.

9. Payout Verification and Holds

Tbltap may require payment or payout onboarding steps before a restaurant can fully use payment features. Orders, fulfillment release, or payout release may be delayed if:

  • connected-account verification is incomplete
  • payout details are missing or invalid
  • Stripe or another processor places a reserve, hold, or review on the account
  • Tbltap detects risk, abuse, rights, security, or compliance issues

10. Where Current Pricing Appears

Tbltap expects current pricing to be visible in one or more of these places:

  • the business store screen
  • the business checkout flow
  • membership or tag order details
  • the restaurant legal or billing help surface
  • this public disclosure page

If there is a conflict between an outdated marketing screen and the live checkout or order flow, the live checkout or order flow governs the price for that purchase.

11. Questions

Questions about business billing, payouts, refunds, or disputes can be sent to:

[email protected]

Was this helpful?
Need help?

Contact tbltap support and include the document title so we can route your question quickly.

Contact support