Payment readiness checklist
A restaurant should treat payments as ready only after the business has completed onboarding requirements and tested the guest-facing payment path it plans to use.
- The connected processor account should not show unresolved owner, business, tax, banking, verification, or risk-review requirements.
- The restaurant should review public payment terms, platform fees, processor fees, refund responsibilities, and dispute responsibilities before enabling live paid ordering.
- Run a staff-side and guest-side check of the intended flow: paid ordering, Quick Pay, split bill, or payout-only readiness.
- Confirm staff know where to route duplicate-charge, receipt, failed-payment, refund, and dispute questions before the first live service.
Before taking paid orders
Restaurants should complete payment onboarding and review the public payment terms before enabling live paid ordering.
- Processor onboarding may require owner, business, tax, banking, and verification details.
- Payout availability depends on processor status, risk review, refunds, disputes, and connected account rules.
- Platform fees and processor fees are separate and should be reviewed before launch.
Payout timing and fees
Payout timing and fees can vary by processor, connected account status, risk review, country, refund activity, and dispute activity. Public docs should set expectations without promising a fixed payout schedule.
- Payout availability is not only controlled by tbltap; processor rules and account status can delay or restrict payouts.
- Processor fees, platform fees, refunds, disputes, and chargebacks can reduce the amount available for payout.
- Banking changes, tax information issues, identity verification, or unusual activity can trigger additional review.
- Owners should keep payout, tax, and bank information current before busy service periods.
Operational responsibilities
tbltap provides payment surfaces and documentation. The restaurant owns fulfillment, customer service decisions, and the accuracy of what it sells.
- Keep refund expectations clear for guests and staff.
- Monitor failed payments, disputes, and payout restrictions.
- Contact support if the restaurant cannot complete onboarding or cannot identify a payment.
Maintain the connected Stripe account
Restaurants are responsible for keeping their connected Stripe account accurate, verified, and in good standing. Stripe may request updated business, owner, tax, banking, dispute, or compliance information at any time.
- Respond promptly to Stripe requirements, account restrictions, dispute notices, identity checks, and bank account issues.
- Unresolved Stripe requirements can affect payout availability, card acceptance, Quick Pay, split-bill checkout, and paid ordering.
- For live restaurants, unresolved billing or processor issues may also affect public table menu availability, menu editing or publishing controls, and other in-menu business functions until the account is brought back into good standing.
- Verified review creation and review edit surfaces that depend on completed payment or order proof may be unavailable when payment verification cannot be completed.
If payment status changes after launch
A restaurant that was previously ready may still need to respond to processor, billing, or membership changes later.
- If the processor asks for updated information, resolve it before assuming paid ordering, payouts, Quick Pay, split bills, or verified review proof will continue normally.
- If billing or membership status is not current, live menu actions and business tools may be limited until the account is brought back into good standing.
- If guests report payment issues during service, staff should preserve receipt/order context and route the issue according to the refund and dispute guide.