Legal
Stripe and Payments Disclosure
DineStack is a restaurant technology product provided by LEAP RIDE, INC., a New York corporation.
1. Two distinct payment relationships
DineStack subscription fees: LEAP RIDE, INC. sells its software subscription to restaurants and may use Stripe Billing/Checkout to collect the SaaS fee.
Restaurant guest payments: An eligible restaurant may, after certification and enablement, process in-person payments through its own Stripe connected account and supported Stripe Terminal/reader services. These are separate transactions from DineStack's SaaS fee.
2. Restaurant is the seller of food and services
The restaurant, not DineStack, is responsible for its menu offers, food safety, sales taxes, tips, workers, customer disputes, refunds, cancellations, consumer notices, receipt obligations and chargeback evidence, except to the extent mandatory law or a separate agreement assigns a responsibility otherwise. DineStack provides tools and transmission of authorized payment operations but does not become the restaurant's seller of record for its food by doing so.
3. Stripe agreements are separate
Restaurant use of Stripe requires acceptance of the Stripe Connected Account Agreement and Stripe Services Agreement applicable to its country and selected account type.
Accepting only DineStack's MSA is not a substitute.
Stripe determines eligibility, capabilities, settlement schedule and processing restrictions. Stripe may suspend a connected account under its own terms.
Current reference: https://stripe.com/legal/connect-account
4. Direct-charge configuration and fees
The approved payment design intends Stripe direct charges on the restaurant's connected account, with Stripe's applicable processing fees assigned to that account. DineStack's commercial decision is no separate application fee per restaurant card transaction.
Payment provider fees, reserves, chargebacks, refunds and payout delays are not waived by DineStack.
5. Payment authorizations and access
By using an enabled integration, the restaurant authorizes DineStack to create or retrieve payment operations, refund instructions, limited account-status requests, transaction reconciliation and related records on behalf of that restaurant, strictly within the subscribed features and granted permissions. DineStack must never initiate unauthorized charges, refunds or transfers. Platform employees must not use restaurants' funds as operating capital.
6. Disputes and payouts
The presence of server support alone does not activate payouts, live merchant processing or refunds.
Restaurant staff supply truthful evidence for guest payment disputes and are responsible for responding on time, subject to the respective Stripe terms. Any DineStack automated dispute alert, payout reporting or transfer capability must have been separately enabled and certified; the presence of code alone does not mean the capability is active. Neither DineStack nor Stripe guarantees that a chargeback will be won or that any payout arrives on a particular date.
7. Hardware and Canada
Only supported, certified devices and permitted regional payment methods may be used. The approved manual source choices are Uber Eats, DoorDash, Grubhub and SkipTheDishes, plus restaurant-configured labels after release certification; a source label is not a payment gateway or partner integration. U.S. M2/other readers and Canada Interac capture/refund behaviors require separate certification.
Mobile Tap to Pay requires supported business-controlled devices and applicable permissions and processor requirements.
8. Security and customer card data
Do not enter card numbers, CVV or magnetic stripe data into DineStack support requests, manual order notes or ordinary media uploads.
The restaurant and relevant payment provider remain responsible for applicable PCI DSS roles.
Stripe's products do not automatically exempt DineStack or restaurants from their own compliance duties.
9. Contact and precedence
Payment-related product inquiries: info@dinestack.app. In case of conflict, mandatory law and Stripe's direct agreement with the restaurant govern Stripe processing; the DineStack MSA governs the software-service relationship to the extent permitted by applicable third-party agreements.