Operator and contact
Legal company name: MEFETE General Trading FZE LLC. Business licence no.: 2624919525888. Registered address: BC-893611 26th Floor, Sheikh Khalifa Street Amber Gem Tower, Ajman. Email: [email protected].
Contract structure and effective date
A final agreement would identify the provider and merchant, effective date, accepted products, order form, pricing schedule, technical documentation and any processor or acquirer terms. A conflict order between these documents and the acceptance method must be agreed (XXX). The public website is not the acceptance mechanism.
Eligibility and onboarding
The merchant would provide accurate business, ownership, representative, website, product and bank details through an approved secure process and keep them current. Verification, risk review, permitted territories and activation criteria must be described in the final onboarding materials; submission does not guarantee approval.
Scope and activation
Only modules named in a signed order form would be available: gateway/API, payment links and/or online store. The form must specify the operating entity, merchant role, supported methods, currencies, territories, limits, third-party dependencies and any implementation work. Features shown on the public site are illustrative.
Gateway and API schedule
The gateway would provide a defined method for initiating a payment and receiving its result through approved interfaces. The final technical schedule must identify endpoints, credentials, authentication, request fields, status meanings, webhooks, retry rules, idempotency, testing and version changes. The merchant must not assume that a displayed success screen proves final settlement.
Payment-link schedule
A payment link would connect a specific merchant request to a customer-facing payment page. The merchant remains responsible for the underlying invoice or order, amount, currency, product description, expiry, recipient and any cancellation or reuse rules. The final schedule must describe link creation, distribution, revocation, status and misuse handling.
Online-store schedule
Store tools would allow the merchant to present a catalogue, product details and a route to checkout. The merchant is responsible for descriptions, prices, taxes, stock, delivery, returns, customer support and consumer disclosures. The final schedule must define hosting, domain, content ownership, theme changes, order records and what happens to store content when service ends.
Merchant and customer relationship
The merchant sells its own goods or services and remains the first contact for fulfilment, returns, cancellation, complaints and accurate receipts. It must obtain any required customer authorisation, state the full price and material terms before payment, and avoid misleading or prohibited offers. A final agreement must allocate any additional consumer-law duties.
Payment routing and third parties
Whether any payment is acquired, processed, held or paid out by this provider or by another licensed party has not been established in this draft. The final agreement must identify every relevant payment party, its role and separate terms before processing begins. A company trade licence number alone must not be read as proof of payment-services authorisation.
Refunds, reversals and disputes
The merchant would operate a clear refund and cancellation policy and respond to customer and payment-method disputes with records and evidence. The final schedule must state who may initiate refunds, time limits, fees, chargeback handling, reversals, negative balances and recovery procedures (XXX). No automatic refund outcome is promised here.
Fees, taxes, settlement and reconciliation
Transaction and service fees, taxes, invoicing, settlement currency, payout destination and timing, reserves, holds, set-off and reconciliation must be itemised in a signed commercial schedule (XXX). The merchant remains responsible for its own tax treatment and financial records unless a final agreement expressly allocates a task elsewhere.
Security and API credentials
Each party would protect its systems and report suspected compromise through a documented channel. The merchant must limit access, protect credentials, validate responses and webhooks, and never place secret keys in public code. Card-data handling, applicable security standards and incident-notice periods depend on the approved technical and payment architecture (XXX).
Data protection and confidentiality
The final documents must allocate controller/processor roles, permitted data use, subprocessors, transfer locations, retention, deletion, audit and breach procedures. Each party would protect confidential business and customer information and use it only for the agreed service or legal duties. A separate data processing addendum may be required (XXX).
Restricted and unlawful activity
The merchant must not use the services for unlawful transactions, deceptive sales, unauthorised third-party processing or activity prohibited by the applicable payment parties. A final restricted-business schedule must be published and approved (XXX); this draft does not imply that any particular industry is accepted.
Ownership and licences
Each party retains its pre-existing marks, software and data. A final contract would grant only the limited rights needed to operate the selected modules and display merchant-provided content. The merchant warrants that it may use uploaded product images, descriptions and marks and will remove content that infringes another party's rights.
Availability, support and changes
The final service schedule must identify support channels and hours, maintenance notices, availability targets, incident escalation, version changes and end-of-life rules (XXX). A public screenshot or marketing statement does not create a service-level guarantee. Changes affecting an active integration should be communicated under the agreed notice process.
Suspension, termination and exit
A final contract must define its term, renewal, ordinary termination, urgent suspension for security or unlawful use, cure periods and post-termination access. It must also specify final settlement, outstanding disputes, data export or deletion, store-content return and survival of necessary obligations (XXX).
Liability, governing law and final approval
Warranties, exclusions, liability caps, indemnities, force majeure, dispute steps, governing law and forum require counsel and commercial approval (XXX). Mandatory rights cannot be excluded by this draft. Only a completed version accepted through the agreed process can bind either party.