Payments Policy

1. Overview

Welcome to Yumzip. Yumzip is owned and operated as a multi-tenant software-as-a-service (SaaS) platform built specifically to empower independent restaurants, food brands, and culinary enterprises. Yumzip provisions branded restaurant storefronts, customizable digital menus, interactive ordering layers, and comprehensive backend delivery/takeaway management systems (collectively, the "Platform").

This Payments Policy explicitly governs, outlines, and delineates the operating mechanism, legal limits, and architecture of electronic monetary transactions initiated by End Customers ("Customers") purchasing goods or services on the digital storefronts hosted via the Platform, and the corresponding businesses or operating entities ("Restaurants") utilizing Yumzip infrastructure.

Restaurants retain full ownership and control of their payment gateway accounts, merchant accounts, transaction records, and settlement relationships.

2. How Payments Work

Yumzip functions cleanly and exclusively at the application software layer. The Platform’s architectural stack acts purely as an API facilitator, data transmitter, and connector between the front-end user checkout interface and external banking infrastructures chosen independently by the Restaurant.

Yumzip is NOT a payment aggregator, payment processor, merchant of record (MoR), escrow service, financial institution, money transmitter, or wallet provider. At no step in the transactional life cycle does Yumzip intersect with the flow of actual transactional value, currency, or cash liquidity.

3. Direct-to-Restaurant Payment Processing

All transaction configurations on the Platform utilize direct-to-restaurant processing architecture. When a Customer verifies an order and proceeds to check out on a Restaurant's branded website:

• The transaction payload is routed securely and directly to the specific payment gateway associated with that Restaurant's independent merchant profile.
• The underlying currency validation, card verification, authorization, capturing, and risk scanning occur directly between the Customer, the processing bank, and the Restaurant’s gateway provider.
• Monetary funds are moved from the Customer’s payment medium directly into the bank account, ledger account, or digital settlement account owned and controlled entirely by the specific Restaurant.

4. Supported Payment Gateway Integrations

Yumzip supports integrations with multiple third-party payment service providers. Available integrations may evolve over time based on technical, regional, operational, and business requirements. Restaurants are granted access to input their proprietary API keys, webhook URLs, tokens, and merchant identification numbers (MIDs) within their dedicated Yumzip administrative console to seamlessly link their pre-existing checkout capabilities.

5. Restaurant Responsibilities

Restaurants leveraging the Platform to manage their business operations are autonomously and solely responsible for maintaining active compliance with all financial, processing, and structural frameworks. This includes, but is not limited to:

• Obtaining, setting up, maintaining, and funding their independent business accounts with their chosen payment processing providers.
• Ensuring absolute verification accuracy of all integrated API keys, encryption secrets, tokens, and processing configuration parameters inside the platform.
• Paying all per-transaction commissions, monthly setup fees, operational surcharges, and interchange costs levied directly by their selected third-party payment gateways.
• Complying with all regional financial and commerce mandates, anti-money laundering (AML) protocols, tax declarations, and Know-Your-Customer (KYC) background checks.

6. Settlement & Payouts

Because Yumzip never handles or captures transaction capital, Yumzip possesses absolute zero awareness of, responsibility for, or technical control over settlement schedules, merchant payout times, funding delays, reserve requirements, or processing holds. All merchant fund clearing timelines, account balances, and cash availability periods are dictated explicitly under the independent merchant service agreements enacted between the Restaurant and its selected payment provider.

7. Failed Transactions

Transactional failures can result from several external processing vectors, including bank card declines, expired tokens, fraudulent alerts, networking timeouts, server outages, or incorrect gateway API keys implemented by the Restaurant. Yumzip does not assume liability for incomplete orders or financial losses arising from processing disruptions. If an order fails at checkout but funds are debited from the Customer's instrument, the resolution remains strictly within the operational purview of the processing gateway and the Restaurant.

8. Refunds & Cancellations

All adjustments, store credits, partial refunds, complete order cancellations, and structural modifications to financial items must be managed directly by the Restaurant through its independent payment gateway dashboard, or initiated using the integration interfaces facilitated through the Platform into the gateway’s API infrastructure. Yumzip cannot process, trigger, reverse, or issue cash distribution adjustments, nor does Yumzip hold operational reserves to assist with processing individual refunds.

9. Chargebacks & Disputes

Any and all chargeback actions, fraud complaints, claims of unauthorized transactions, or customer billing disputes are strictly matters of litigation between the applicable Restaurant and the End Customer. The Restaurant assumes full financial liability, legal defense costs, and administrative penalties linked to chargeback challenges. Yumzip is entirely exempt from involvement in dispute litigation and maintains no capacity to influence, challenge, modify, or overturn chargeback decisions rendered by credit card networks or acquiring institutions.

10. Payment Security

Yumzip prioritizes data transmission integrity and user safety across our multi-tenant SaaS systems. The Platform utilizes advanced security patterns to ensure safe transaction routing:

• Yumzip does not store, parse, save, log, or maintain raw credit card numbers, CVVs, or sensitive Primary Account Numbers (PANs) within its primary databases.
• All cardholder checkouts are secured via modern tokens, secure iframes, or direct hosted redirect portals supplied explicitly by the integrated payment processors.
• The Platform enforces industry-standard encryption and secure transmission protocols for all data requests passed between the Customer's browser and the payment provider's cloud endpoints.

11. Third-Party Payment Providers

By connecting a payment gateway to a website built via the Platform, the Restaurant agrees to conform to the terms of service, acceptable use parameters, and privacy statements issued by that third-party vendor. Yumzip does not audit, endorse, guarantee, or assume liability for the operations, system uptime, physical data practices, or policies of third-party payment providers.

12. Limitation of Responsibility

To the maximum extent permitted under applicable statute, Yumzip, its subsidiaries, executives, directors, developers, and partners shall under no legal theory (contract, tort, or otherwise) be held liable for any direct, incidental, special, consequential, or exemplary damages. This includes, without limitation, damages caused by lost revenues, systemic downtime, transactional failure, network security breaks, payment processor insolvency, illegal activities by third parties, or the unauthorized use of merchant credentials by third-party actors.

13. Changes to This Policy

Yumzip retains the unconditional right to modify, restate, amend, or rewrite this Payments Policy at any point to align with platform updates, scaling integrations, industry shifts, or evolving international legal frameworks. Changes become effective upon publication unless otherwise stated. Restaurants and users are urged to periodically monitor this URL to stay informed of compliance revisions.

14. Contact Information

For any clarifying questions, structural inquiries, or operational feedback regarding the technical parameters of our payment gateway integration rails, please contact our support and legal departments directly via the official channels listed below: