FAQ.

Just2Pay SAJ is a unified-commerce platform that helps businesses manage products, selling links, storefront sales, orders, payments, invoices, inventory, customers, and reports from one merchant account.

Just2Pay SAJ is intended for adults and lawful businesses. A merchant-account user must be at least 18 and legally capable. Product and payment availability may still depend on the business type, country, plan, verification, and partner approval.

You can create physical products, digital products, or services where those product types are enabled for your account. Delivery, inventory, payment, and customer-information settings can be configured according to the product type.

No. Sell Anywhere is designed for merchants who want to sell through product or catalog links without operating a full storefront. Merchants who need a complete online store can use or upgrade to BUZZ.

Unified commerce means that products, customers, selling channels, orders, inventory, payments, invoices, and reports use one connected business record instead of separate systems for each sales channel.

Yes. You can create channel-specific links for supported social platforms and other sharing channels while keeping orders and performance connected to the same merchant account.

The merchant and customer experiences are designed to work on modern mobile and desktop browsers. Some administration tasks may be easier on a larger screen.

The planned product routes are Quick SaaS, SaaS with Payments, and Payments Only. Merchant capabilities can also include Sell Anywhere and the BUZZ storefront according to the selected product and approved entitlements.

SaaS with Payments combines the commerce and storefront experience with eligible payment services. Payment activation may require additional business information, verification, and provider approval.

Payments Only is intended for eligible merchants who need payment capabilities without using the full Just2Pay SAJ storefront. The available tools depend on the approved product configuration and activated payment services.

Sell Anywhere lets a merchant create shareable product, service, collection, catalog, or basket links and accept orders through a focused public checkout without first building a full online store.

BUZZ is the full storefront experience. It includes storefront presentation and management capabilities such as pages, themes, navigation, domains, search settings, and the shared commerce tools enabled for the merchant.

Sell Anywhere focuses on direct and social selling through shareable links. BUZZ provides a complete browsable storefront. Both can use the same merchant identity, products, customers, orders, payments, and reports when enabled together.

Yes. The target experience allows an eligible merchant to add BUZZ while retaining the same Merchant ID and existing business records, including products, customers, links, orders, invoices, and reports.

No. An upgrade should add the new entitlement to the existing merchant account rather than creating a separate merchant or duplicate catalog.

Choose the product route that fits your business, create the owner account, enter the required business information, and complete the steps shown in your onboarding checklist.

The requested information can include owner details, business details, address, sales channels, website or social presence, product selection, payment needs, and verification information. The exact questions depend on the selected route.

Yes. Completed onboarding steps should be saved so you can resume the application later, including from another supported device.

Just2Pay SAJ uses route-aware onboarding. It asks for information relevant to the selected product, business type, sales channels, and requested services instead of presenting every question to every merchant.

The merchant dashboard displays the status and next action for the account, commerce setup, KYC, signature, and payment activation as separate processes.

Not necessarily. Identity or business verification and payment-service activation are separate decisions. A merchant may complete one while the other is still under review.

The platform should show which information or document is required and allow an authorized merchant user to respond without losing the previous application history.

Where permitted, the platform will show an appropriate reason or next action. Some decisions may be limited by legal, compliance, risk, or provider requirements.

The Merchant ID is the stable identifier for the business in Just2Pay SAJ. It helps connect the merchant's products, staff, services, orders, payments, invoices, and reports.

Yes, where the selected plan allows staff accounts. Authorized users can invite team members and assign roles according to the work they need to perform.

Yes. Access is permission-based. Roles can be limited for catalog, Sell Anywhere, orders, inventory, payments, refunds, invoices, reports, KYC, financing, settings, and other sensitive activities.

Only users with the required permission can perform sensitive actions. Some actions may also require additional approval or stronger authentication.

Important actions should be recorded with the actor, time, reason, and relevant before-and-after information so authorized users can review the activity history.

A merchant may cancel under the applicable order form. Account closure does not remove accrued payment, refund, chargeback, confidentiality, audit, dispute, or recordkeeping obligations. Data export and deletion follow the contract and Privacy Policy.

Open the catalog or Sell Anywhere product area, choose the product type, add its content and price, configure variants and availability, select eligible delivery and payment methods, and publish it.

Yes. Products can have variants such as size, color, or another merchant-defined option where supported. Price, inventory, and availability can be managed at the appropriate product or variant level.

Yes. Categories and collections help merchants organize products for management, storefront browsing, and shareable catalog links.

Yes. Sell Anywhere is designed to support product, service, collection, catalog, and predefined-basket links, subject to the merchant's enabled capabilities.

Yes. A product can be unpublished or made unavailable while preserving its order and reporting history.

Existing orders retain a snapshot of the purchased item and source information. Changing the current catalog does not rewrite historical order details.

Where enabled, merchants can control publication, link status, payment methods, and fulfillment rules for the relevant product or selling experience.

Choose a product, service, collection, catalog, or predefined basket; configure the customer and checkout requirements; set availability or expiry if needed; and publish the link.

An eligible product or variant can have a reusable base selling link. The merchant can also create separate attributed channel links for specific social pages, accounts, or campaigns.

Yes. You can create channel-specific links with a platform, page or account label, and campaign label so their views, orders, and sales can be reported separately.

The planned channel list includes WhatsApp, Facebook, Instagram, Messenger, TikTok, email, SMS, QR, and generic sharing. Actual sharing behavior depends on device support and approved platform integrations.

No. Basic channel attribution and link sharing do not require your social media password. Direct publishing integrations, if introduced, should use the social platform's approved authorization process.

Yes, but separate channel links are recommended when you want accurate reporting by platform, social page, or campaign.

Yes. A QR code can represent the selected selling link and retain its configured attribution.

Yes. A link can be paused, expired, archived, or revoked according to the available controls. Historical orders and attribution remain available to authorized users.

The customer receives a safe availability message and cannot submit a new order through that link.

Yes, where enabled. Expiry can be used for campaigns, limited availability, or time-bound offers.

The order stores a source snapshot that can include the selling link, platform, social page or account label, campaign, and link type used at checkout.

No. The signed channel link is the primary attribution source. Browser referrer information may be used only as supporting evidence.

Yes. Sell Anywhere reporting is designed to show performance by product, link, channel, page or account label, and campaign.

The platform should count valid views after applying rate limits and basic bot checks. Analytics may be delayed, filtered, or unavailable until tracking is active.

No. A selling link presents products or services and creates a commerce order. A payment link collects a specified amount or settles an eligible order or invoice.

No. An invoice link relates to a specific invoice and its balance. A product link starts a product-purchase journey.

Sell Anywhere supports a focused guest checkout where enabled. The customer provides only the information required for the product, delivery, payment method, and merchant configuration.

The form may request name, contact details, delivery information, product options, quantity, and payment information. Required fields depend on the order and selected payment method.

The customer can choose from the options and quantities allowed by the selling link and current product availability.

Yes. Price, discount, tax, delivery charge, stock, and payment eligibility are recalculated on the server before the order is accepted.

The customer receives an updated availability message. The platform should not create a confirmed order for inventory that cannot be reserved.

After a valid submission, the customer sees a confirmation page with a safe order reference and the correct online-payment, COD, or manual-transfer status.

No. The checkout is designed to recognize a repeated submission and return the original result instead of creating a duplicate order.

Where payment orchestration is enabled, Just2Pay SAJ evaluates the active method, merchant eligibility, service health, and approved routing rules before selecting an eligible connection.

Provider preference and routing controls depend on the merchant product and operational configuration. A preference can only use an active, compatible, and approved connection.

The platform follows its approved routing and failure-handling rules. It will not retry an uncertain charge through another provider unless the original result is safely confirmed.

The order and transaction screens show the normalized payment status after the platform verifies the provider response or callback.

Pending means a final successful or failed result has not yet been confirmed. The order should not be treated as paid until an approved success state is recorded.

Just2Pay uses idempotency and duplicate-event controls to reduce repeated processing, but no system is completely secure or error-free. A customer who sees an unexpected duplicate charge should contact the merchant or Just2Pay with the order and payment references.

Just2Pay initiates eligible merchant settlements every 15 Working Days to the verified settlement destination. An order becomes eligible after fulfillment is confirmed, funds are received and cleared, and no active cancellation, return, refund, chargeback, reversal, fraud review, delivery dispute, or legal restriction applies. Provider processing times and bank cutoffs can affect when the funds appear.

Subscription fees, commissions, payment charges, shipping or handling charges, advertising fees, taxes, and other amounts must appear in the electronically accepted Commercial Schedule. No unpublished fee or penalty applies. Percentages must identify their calculation base and VAT treatment.

Just2Pay does not state that it stores full payment-card numbers. Customers should enter card credentials only in the authorized payment provider's secure payment environment.

Yes, where COD is enabled for the merchant, product, customer location, channel, and order amount.

No. COD is an offline collection workflow and remains unpaid until the money is collected. It must not be reported as an online payment-provider capture.

Yes, where configured. The applicable fee is calculated on the server and shown to the customer before order confirmation.

Yes. Merchants can require approval and move eligible orders through the configured operational states before fulfillment.

Manual transfer can be offered where the merchant has configured approved instructions and the order is eligible.

The customer uses the private proof-upload page connected to the order, selects the required information, and submits the file for merchant review.

No. A manual-transfer or InstaPay proof is evidence for merchant review. Uploading it does not confirm payment and does not create a Just2Pay payment guarantee.

Yes. Where the merchant requests a replacement, the customer can submit a new file while the earlier review history remains recorded.

No. Payment-proof files form part of the shopper, order, payment, and support records. Access must be limited to authorized users and service providers that need the information for the transaction, security, support, or legal duties.

The unified order inbox shows orders from supported sources, including storefront, Sell Anywhere, social links, invoices, APIs, COD, and manual entry where enabled.

Yes. Orders can be filtered by channel, selling link, campaign, product, customer, date, payment method, and operational status where those dimensions are available.

The platform keeps approval, payment verification, payment, and fulfillment as separate status areas. This prevents an online payment, COD decision, proof review, or delivery update from incorrectly changing another part of the order.

Yes, when the order requires approval and the user has permission. The action is validated against the current state and recorded in the activity history.

Authorized users can move an eligible order through the configured fulfillment stages, such as processing, ready, shipped, delivered, completed, returned, or cancelled.

A shopper may request cancellation before dispatch through the order page or support channel. If the order has already been dispatched, the return process applies. Cancelling an order does not by itself complete a payment refund.

The shopper opens a return request and follows the issued return or pickup instructions. The merchant records the condition and any serial or IMEI evidence where relevant. A refund or replacement is handled under the applicable consumer rights and remains connected to, but separate from, inventory and payment records.

Yes, when the order is eligible and the merchant has the required capability and permission.

Authorized merchants can export supported order information. Large exports may be prepared in the background and sensitive exports are recorded for audit.

Yes, for products and variants configured for inventory tracking. The target platform separates available, reserved, sold, returned, and adjusted quantities.

Stock is reserved when an eligible order is created according to the merchant's checkout and payment rules.

The reservation is released through a recorded inventory movement when the cancellation or expiry rule allows it.

Availability checks and reservation creation occur together under server-side controls. The platform rejects or updates an order when the requested stock cannot be safely reserved.

Authorized users can create a stock adjustment with a reason. The adjustment is recorded as a movement instead of silently overwriting inventory history.

Yes. Merchants can set low-stock thresholds and view or receive alerts where notifications are enabled.

Return processing follows the merchant's inventory rules. Stock becomes available only when an authorized and valid return movement is recorded.

An authorized merchant user may request a full or partial online-payment refund when the transaction, provider capability, refundable balance, merchant policy, and applicable consumer law allow it. Valid statutory remedies cannot be restricted by a merchant rule.

The transaction and order areas show whether the refund is pending, successful, or failed and retain the refund history.

No. Order cancellation and payment refund are separate actions so each can be verified and audited correctly.

The merchant must approve a valid refund within the applicable statutory timeframe. After initiation, the payment provider or bank may need more processing time. The customer interface should show the refund reference and a realistic estimated completion date.

A consumer may not be charged an extra fee for a valid defective-goods remedy. Shipping and handling are refunded where the law requires it or where the merchant caused the return. Other return costs may be allocated only where Egyptian law and the disclosed checkout terms permit.

A dispute is a challenge or chargeback associated with a payment. The platform records its status and related evidence while the applicable provider and merchant agreement determine the formal process.

The customer should submit the order number and relevant evidence through the order page or to infosec@just2pay.net. The merchant or platform provides return instructions and may escalate an unresolved consumer case to Egypt's Consumer Protection Agency. Payment-provider disputes follow the relevant provider's evidence and deadline rules.

Yes, where invoicing is enabled. A merchant can create a draft from an order, products, services, or approved custom line items and then issue it to the customer.

The planned states include draft, issued, viewed, partially paid, paid, expired, cancelled, and refunded, based on invoice events and payment allocations.

Yes, if the invoice includes an active payment link and the merchant has an eligible online payment method.

Offline settlement can be recorded where the invoice and merchant configuration allow it. The offline state is kept distinct from an online provider payment.

Partial payment is supported where the invoice terms, link configuration, and payment method allow it.

Authorized users can share or resend an issued invoice through available channels such as email, WhatsApp, copy link, or QR where enabled.

A Just2Pay-generated invoice is not automatically a regulated tax or electronic invoice. The merchant, as seller of record, remains responsible for compliant invoices and tax duties unless checkout or an approved legal integration expressly states otherwise.

The target platform distinguishes one-time amount links, product payment links, unpaid-order payment links, and invoice payment links. Sell Anywhere selling links remain a separate commerce feature.

Recurring invoice schedules are planned where enabled. Each scheduled occurrence creates a normal invoice and retains its own status and history.

Authorized users can manage an active schedule according to its state. Existing invoices remain part of the business history even if future generation is paused or cancelled.

The dashboard can show sales, orders, online payments, COD, manual transfers, refunds, inventory alerts, active links, top channels, and required actions according to the merchant's enabled features.

Yes. Sell Anywhere reporting can compare attributed activity from supported channels, pages or account labels, campaigns, and individual links.

Yes, after real tracking is active. Conversion is calculated from approved view and order definitions, and bot or repeated traffic may be filtered.

Yes. Reports can use product, variant, collection, channel, link, customer, date, and order dimensions where data is available.

Yes. Each method has a distinct operational or financial meaning and should be reported separately.

Yes. Authorized users can report payment captures, refunds, disputes, and their effect on net results according to approved financial definitions.

Currencies remain separate unless the platform uses an approved reporting conversion method and clearly identifies the conversion basis.

Yes, subject to permissions and plan limits. Large exports may be prepared asynchronously and include a data-through timestamp.

Recent payments, callbacks, refunds, order changes, filtered traffic, or reconciliation updates can change a result. Reports should display the applicable time range, filters, currency, environment, and data-through time.

Yes. Summary values should use the same definitions as drill-down records so authorized users can trace totals to the related orders, transactions, invoices, links, or inventory movements.

BUZZ is designed to provide a complete online-store experience with storefront pages, themes, content, navigation, domains, search settings, and access to the merchant's enabled commerce capabilities.

Merchants can use the available Page Studio, theme, content, and navigation controls according to their plan and permissions.

No, unless the merchant chooses to pause or revoke them. Adding BUZZ should preserve existing selling links and their order history.

Yes. They should use the same catalog and inventory records so stock and reporting remain consistent across the merchant's channels.

Just2Pay may request corporate, ownership, authorized-signatory, KYC or KYB, bank, tax, licensing, and settlement information to verify the merchant, prevent fraud, meet legal duties, or satisfy an activated partner's requirements.

Use the secure document-upload area in the onboarding or verification workflow. Upload only the requested document types and ensure the information is readable and current.

Verification documents may be accessed by authorized Just2Pay personnel and the relevant identity, KYC, banking, payment, fraud, professional, or public-authority recipient where the disclosure is necessary and lawful. Just2Pay applies access controls, protected storage, logging, and monitoring.

Yes, when the reviewer requests a replacement. The new version is added without removing the decision history.

Some merchants or products may require a separate physical or electronic signature process. The dashboard should show its status and next action independently from KYC and payment activation.

KYC records are retained for the period required by Egyptian law, regulators, contracted payment providers, limitation periods, fraud controls, and active disputes or legal holds. They are deleted or anonymized when the applicable purposes and retention duties end.

Eligible merchants may request financing where an approved financing product and provider are available. Just2Pay does not guarantee financing approval, and the regulated financing service is supplied under the relevant partner's terms.

The request may include business information, requested amount, purpose, supporting documents, and consent for specified data sharing. Exact requirements depend on the financing product and partner.

No. Submission only starts the review process. Approval, offered amount, terms, and disbursement are separate decisions made under the applicable financing process.

Financing data is shared only when the merchant requests the service and the required consent or authority exists. The consent should identify the recipient, purpose, information, and applicable version before a handoff occurs.

Authorized merchant users can view the customer-visible status, information requests, and timeline without access to restricted internal review notes.

Just2Pay uses proportionate organizational and technical measures, including access controls, role separation, encryption in transit, protected storage, logging, monitoring, backups, vulnerability management, and incident procedures. No system is completely secure, so users must also protect their credentials and report suspected misuse.

No. Merchant data and operations must be scoped to the correct tenant, and access requires the appropriate identity and permission.

Payment-provider credentials and other security information receive restricted access and heightened protection. They should not appear in ordinary pages, reports, exports, or logs.

Public links use opaque tokens and can support expiry, pause, rotation, and revocation. The server validates the merchant, link status, price, stock, and payment eligibility on every relevant request.

Protect the account, review authorized users, revoke suspicious access where available, and report suspected misuse promptly to infosec@just2pay.net. Include the Merchant ID and relevant event references, but do not send passwords or full card information.

Send a privacy request to infosec@just2pay.net. Subject to Egyptian law and lawful exceptions, a person may request information, access, correction, completion, deletion, restriction, objection, consent withdrawal, or review of certain automated outcomes. Just2Pay may verify identity and may direct a shopper to the merchant that controls the data.

The website legal center should publish the Privacy Policy, Terms of Use, Cookie Policy, Refund Return and Cancellation Policy, and Marketplace Merchant Agreement. The applicable order form, commercial schedule, data-processing terms, service levels, prohibited-products rules, and partner terms may also form part of a merchant's agreement when displayed or linked before acceptance.

Notifications can include new orders, approval requests, payment results, submitted proofs, low stock, refunds, disputes, invoice activity, KYC actions, financing updates, and operational exceptions according to enabled features.

Optional notifications can be managed according to user preferences. Security, legal, billing, and critical service notices may remain mandatory.

Check the in-app notification center, contact details, preferences, spam folder, and team permissions. Delivery status may also show whether the notification is queued, delivered, or failed.

The target platform includes versioned APIs for approved merchant and administrator use cases, subject to entitlement, credentials, permissions, and rate limits.

Planned merchant APIs cover products, inventory, catalogs, selling links, orders, offline proofs, invoices, payment links, transactions, reports, and other enabled capabilities.

An authorized merchant user creates credentials in the developer or integration settings where the feature is enabled. Credentials should have a defined scope, environment, expiry, and revocation control.

Yes. Environments and credentials should remain separate so test activity is not treated as live commerce or included in live financial reporting.

Yes. Operations that can create financial or business records should accept idempotency controls so safe retries do not create duplicate orders, payments, refunds, invoices, or handoffs.

Signed webhook delivery is planned for supported merchant events. Delivery attempts, retries, and status should be visible to authorized users.

Integrations depend on available connectors and approved APIs. The platform architecture is intended to support payment providers, couriers, accounting systems, social platforms, and financing partners without mixing their credentials or records.

Authorized users can view the active product, entitlements, limits, billing status, and available upgrades in the plan and billing area.

Billing follows the electronically accepted order form, pricing schedule, Commercial Schedule, or Merchant Agreement. These documents govern subscription fees, commissions, transaction charges, add-ons, renewal, settlement, and taxes.

Just2Pay may suspend access for non-payment under the applicable contract, but restrictions must preserve accrued payment, refund, chargeback, confidentiality, audit, dispute, and recordkeeping obligations. The specific retry and grace-period rules must appear in the merchant's accepted order form or service schedule.

Authorized account owners can update an eligible billing method according to the available billing options and security checks.

A merchant may cancel under the accepted order form. Unless mandatory law or a written plan states otherwise, fees already earned for an activated or consumed service are non-refundable. This rule does not limit a shopper's statutory product-refund rights.

For legal, privacy, security, return, and complaint matters, contact infosec@just2pay.net or write to Just2Pay for Technical Financial Payments - S.A.E., 1171, 9th Street, Mokattam, Cairo, Egypt. The business should publish any separate general-support channels and operating hours before launch.

Include the Merchant ID, order or transaction reference, time of the issue, affected feature, and screenshots that do not expose passwords, full payment credentials, or unnecessary personal data.

The public legal terms do not promise a general support response time. The Merchant Agreement allows service levels to be defined in an incorporated Services and SLA schedule. Publish response targets only after that schedule is approved.

An online authorization does not guarantee merchant acceptance or fulfillment. A pending payment should not be treated as successful until the provider result is confirmed. Do not start an uncertain charge again through another provider until the original attempt is safely resolved.

Review the order timeline and transaction details, avoid manually changing the financial result, and submit a reconciliation support request with the relevant references.

The legal entity is Just2Pay for Technical Financial Payments - S.A.E., an Egyptian Joint Stock Company with Commercial Register No. 156229 and Tax ID 602-136-626.

Just2Pay's registered office is 1171, 9th Street, Mokattam, Cairo, Egypt.

The Privacy Policy, Terms of Use, Cookie Policy, Refund Return and Cancellation Policy, and Marketplace Merchant Agreement have an effective date of 01 September 2026.

The legal center includes the Privacy Policy, Terms of Use, Cookie Policy, Refund Return and Cancellation Policy, and Marketplace Merchant Agreement. Merchant-specific order forms, commercial schedules, data-processing terms, service levels, prohibited-products rules, and partner terms may also apply when displayed or linked before acceptance.

An authorized user reviews the displayed documents and selects Approved, I Agree, or an equivalent affirmative control. Just2Pay records the merchant and user data, accepted document versions, date and time, account identifier, IP address, device or browser evidence, and relevant verification records.

No handwritten signature or uploaded signed contract is normally required. A separate instrument may still be required when a regulator, payment provider, or applicable law requires it for a specific regulated service.

Yes. The system may activate an account after required information and automated validation rules pass. Just2Pay may still require verification or partner approval and may refuse, restrict, or suspend access for incomplete, misleading, expired, fraudulent, or legally restricted information.

A merchant-account user must be at least 18, legally capable, and authorized to bind the organization where acting for a company.

Unless a product page or checkout expressly says otherwise, the named merchant is the independent seller of record. The merchant is responsible for product legality, accuracy, stock, price, tax, invoice, delivery, warranty, return, and consumer rights.

No. Just2Pay supplies commerce software, marketplace technology, order management, and payment enablement. Regulated payment, financing, and delivery services are supplied by the relevant partner under its terms.

A customer's order is an offer to purchase from the merchant. Acceptance occurs when the merchant confirms the order or as otherwise stated at checkout and under applicable law.

No. Payment authorization does not by itself guarantee merchant acceptance or fulfillment. Product availability, pricing errors, verification, and lawful cancellation rules can still affect the order.

COD is an offline collection workflow and remains unpaid until collection. The merchant must track fulfillment and collection accurately; no online-provider capture should be reported for COD.

No. A bank-transfer or InstaPay proof is evidence for merchant review. It is not confirmation of payment by Just2Pay and does not create a Just2Pay guarantee.

Data may include identity, contact, credentials, access logs, merchant registration, ownership, tax, KYC or KYB, settlement, product, pricing, inventory, shopper, delivery, order, invoice, return, support, transaction, transfer-proof, device, cookie, usage, communication, consent, and audit information.

Just2Pay does not state that it stores full payment-card numbers. Card credentials should be entered in the authorized payment provider's secure environment.

Just2Pay processes data to operate contracts and services, create accounts, verify merchants, prevent fraud, configure commerce and payment workflows, process orders and refunds, provide support, secure the platform, keep audit trails, bill fees, meet legal duties, improve performance, measure usage, and send lawful marketing.

Depending on the activity and applicable law, Just2Pay may rely on consent, contractual necessity, legal obligation, protection of legitimate interests, and other grounds recognized by Egyptian law.

Just2Pay acts as a controller for its own accounts, security, billing, compliance, and service operations. It may act as a processor or service provider for customer and order data handled only on a merchant's instructions. Payment, shipping, identity, analytics, and financing partners may act as independent controllers.

The merchant is responsible for its own customer notices, lawful instructions, products, and direct marketing. A Data Processing Addendum applies where Just2Pay processes shopper or order data solely on the merchant's documented instructions.

Necessary data may be shared with the relevant merchant, payment and banking partners, fraud and identity providers, KYC providers, shipping and fulfillment providers, cloud and hosting services, communications, analytics, customer support, security advisers, professional advisers, approved financing providers, corporate transaction counterparties, and public authorities where legally required.

Just2Pay states that it does not sell personal data as an ordinary business activity.

Some providers may process data outside Egypt. Restricted transfers must follow the approvals, permits, contractual safeguards, and other measures required by Egypt's Personal Data Protection Law No. 151 of 2020 and its applicable executive framework.

Just2Pay retains data only for the service purpose and applicable limitation, tax, accounting, anti-fraud, dispute, payment-network, regulatory, legal-hold, and lawful-request periods. Data is deleted or anonymized when those purposes and duties end.

Subject to Egyptian law and lawful exceptions, a person may request processing information, access or a copy, correction, completion, deletion, restriction, objection, withdrawal of consent, and review of certain automated outcomes.

Send the request to infosec@just2pay.net. Just2Pay may verify identity and may direct a shopper to the merchant where that merchant controls the data.

Yes. A person may complain to the competent Egyptian data-protection authority through its officially published channels.

Just2Pay uses proportionate controls including role separation, access controls, encryption in transit, protected storage, logging, monitoring, backups, vulnerability management, and incident procedures. No system is completely secure.

Electronic marketing must include an appropriate unsubscribe choice, and consent records are retained where required. Merchants must use customer data only for fulfillment, support, and lawfully consented marketing.

No. Merchant services are intended for adults and lawful businesses, and Just2Pay does not knowingly offer merchant accounts to persons under 18.

Strictly necessary technologies operate security, authentication, session continuity, load balancing, checkout, fraud prevention, consent storage, and requested features. They generally cannot be disabled through the preference center.

The policy defines functional, analytics, advertising, and social-media technologies. A category may be activated only when it is actually configured and the required visitor choice has been obtained.

Yes. Visitors can accept all, reject all non-essential cookies, or select categories through Cookie Preferences. Rejecting them does not block basic access, although some optional features may not work.

Yes. Cookie choices can be changed at any time through Cookie Preferences. Browser settings may also block or delete cookies but can affect authentication and checkout.

Only tags listed in the verified live cookie register should be described as active. The register must identify the name, provider, purpose, category, domain, expiry, data, recipient or country, and consent requirement. Google Tag Manager alone is a deployment tool, not a lawful basis for other tags.

Users must not violate law or rights, impersonate others, upload malware, bypass security, scrape without permission, interfere with service integrity, launder proceeds, misrepresent payment status, publish deceptive content, abuse promotions or returns, misuse reviews, or use customer data outside the permitted transaction and lawful marketing basis.

Just2Pay and its licensors own the platform, software, design, documentation, trademarks, and platform analytics. The merchant retains its content and gives Just2Pay a limited license to host, display, transmit, secure, and use it to operate the services and promote it only as authorized.

Just2Pay may change prospective fees with 30 days' notice unless a provider or law requires an earlier change. No unpublished fee or penalty applies.

Unless mandatory law or a written plan states otherwise, fees already earned for an activated or consumed service are non-refundable. This does not limit consumers' statutory product-refund rights.

No. Just2Pay aims for reliable service but does not guarantee uninterrupted or error-free operation, sales volume, financing approval, delivery outcomes, or provider acceptance.

Subject to the stated exceptions and applicable law, aggregate business liability is limited to fees paid for the affected services during the preceding 12 months. The exclusions include fraud, wilful misconduct, confidentiality or data-protection duties, failure to account for settlement funds, and other non-excludable liability.

Just2Pay may suspend or terminate access for breach, fraud or security risk, unlawful activity, non-payment, provider instruction, legal requirement, counterfeit or unsafe goods, or imminent consumer harm. Urgent legal, safety, or fraud risks may require immediate action.

The laws of the Arab Republic of Egypt govern the Terms of Use and Marketplace Merchant Agreement.

The parties should contact infosec@just2pay.net and allow 15 business days for good-faith escalation. If unresolved, the competent Egyptian courts have jurisdiction; merchant disputes identify the competent courts of Cairo, without limiting mandatory consumer or regulatory rights.

Consumers generally may request the return or exchange of eligible goods within 14 days after receipt without giving a reason and without expense, subject to lawful exceptions. Egyptian Consumer Protection Law No. 181 of 2018 prevails if it provides a stronger right.

A defective, incorrect, damaged, counterfeit, or materially misdescribed product should be reported as soon as possible and within at least 30 days after receipt. The valid statutory remedy must be provided without an extra fee.

Lawful exclusions may include goods that cannot return to their original condition, rapidly perishable goods, goods altered by the consumer, conforming made-to-specification goods, books, newspapers, magazines, software and similar items, jewelry, and opened intimate apparel or wedding dresses. Merchant exclusions cannot override mandatory rights.

Submit the request through the order page or support channel before dispatch. If the product has already been dispatched, follow the return process.

Submit the request from the order page or email infosec@just2pay.net with the order number and relevant evidence. The merchant or platform provides instructions and, where offered, a return label or pickup.

Approved refunds normally return to the original payment method. For COD or a lawful operational exception, the shopper may be asked for a verified bank or wallet destination.

Contact infosec@just2pay.net first. If unresolved, the consumer may contact Egypt's Consumer Protection Agency through its official channels, including hotline 19588, subject to updated official contact information.

A merchant must provide and maintain accurate company, registration, tax, ownership, authorized-signatory, bank, address, licensing, product, and verification information and permit lawful verification.

The merchant must hold required registrations and licenses, sell authentic and lawful goods, maintain accurate stock and prices, issue compliant invoices, fulfill orders, protect customer data, honor warranties and consumer remedies, secure its account, and comply with applicable Egyptian law.

Merchants may not list counterfeit, stolen, recalled, unsafe, sanctioned, infringing, or unlawfully regulated goods; weapons; illegal drugs; exploitation material; unlawful financial products; or any category in the current Prohibited Products Schedule.

Just2Pay initiates eligible net settlement every 15 Working Days to the verified settlement destination. Working Days exclude Fridays, Saturdays, and official Egyptian public holidays.

No. Any positive eligible net balance is included in the next scheduled settlement. A negative balance may be carried forward, set off against future settlements, or requested from the merchant.

The electronic statement can show gross collections, eligible orders, commissions, service fees, payment and shipping charges, promotions, taxes or withholding, refunds, returns, chargebacks, reversals, prior adjustments, reserves, and the resulting net amount.

A transaction-specific reserve or temporary hold may be used only for a reasonably identified exposure such as refunds, chargebacks, fraud, counterfeit or prohibited goods, customer claims, delivery disputes, unpaid fees, negative balances, legal instructions, partner requirements, or incomplete verification.

Undisputed funds may be held for up to 60 calendar days after suspension or termination to complete pending returns, refunds, claims, chargebacks, and verification. A longer hold is limited to a specific unresolved legal, provider, chargeback, or fraud matter and the reasonably connected amount.

Submit a documented reconciliation dispute through the dashboard or to infosec@just2pay.net within 15 Working Days after the statement becomes available. Accepted corrections appear in the next practicable settlement cycle.

The merchant is responsible for chargebacks, reversals, and fraud caused by its goods, fulfillment, representations, staff, or breach. The merchant may challenge an adjustment within 15 business days with evidence.

Confidentiality obligations continue for five years after disclosure or termination, while trade secrets remain protected for as long as the law protects them.

Either party may terminate for an uncured material breach after 15 business days' notice. Immediate suspension remains available for credible fraud, unsafe or counterfeit goods, security incidents, unlawful conduct, authority or provider direction, or imminent consumer harm.

Where Arabic and English versions are provided, the Arabic version prevails to the extent required for interpretation or enforcement under Egyptian law.