Billing and Payment Policy

Only billing cycles actually configured may be displayed. No billing cycle, charge date or renewal is created until supported by an authoritative backend transaction.

Taxes apply according to the service provider’s actual tax position and current Egyptian law.

Before payment, the order summary must clearly show the base amount, applicable tax and total payable, or expressly state that the price includes tax where that is true.

A non-Egyptian customer country does not establish zero rating by itself. Qualifying treatment requires legal conditions, evidence, rule version and review.

Prices are shown, and the transaction is presented, in the configured price-book currency for the selected Business Country. Each market is priced in its own currency rather than converted from another market’s price.

Whether the amount is finally settled in that same currency depends on the payment provider, and is not yet established. Until it is, no representation is made that the currency shown is the currency of settlement, and no conversion rate, conversion fee or absence of one is promised.

Where settlement occurs in a different currency, the customer’s bank or card issuer may apply its own conversion and charges, which are outside OCTK’s control. Once the position is established, it is stated here before any charge is taken.

Payment methods are available according to the country, market and approved provider at the time of the transaction. No gateway is displayed as active before it is connected.

Selecting a future final payment control authorizes only the transaction amount and total displayed with the selected payment method and applicable subscription and billing terms. The current provider and methods are unconfigured.

An automatic-renewal clause is displayed only when renewal is actually enabled. Before confirmation it must identify the cycle, price or calculation method, next charge timing and how renewal can be stopped. No automatic renewal is represented as configured by this draft.

Where renewal is enabled, notice is given three times: seven days before the renewal date, two days before, and on the day itself. Each notice states the date and the amount.

The seven-day notice exists so that a decision to reduce the plan can still be made in time, since a downgrade takes effect at renewal and cannot be applied retroactively once the renewal has occurred.

Where a discount or promotional price is ending, the notice states that it is ending and shows the amount that will be charged instead.

If collection fails, OCTK may retry, request a payment-method update or suspend paid services only according to the actual system and notices given to the customer. No grace period or retry count is configured.

An upgrade takes effect immediately. The customer pays only the difference between the two plans for the days remaining in the current billing cycle, calculated in proportion to those days. The billing date itself does not move.

A downgrade takes effect at the next renewal, not immediately. Nothing is charged at the time of the request, the customer keeps the higher plan for the remainder of the cycle already paid for, and the lower price applies from the renewal onwards. Because the paid period is never cut short, a downgrade does not give rise to a refund.

Where a downgrade would place the account above the limits of the lower plan, the customer is shown before confirming exactly what will be affected at renewal, and how much of it. The request is not blocked on that basis.

A change scheduled for a future renewal is a request until it takes effect, and may be cancelled at any time before then.

On a change from monthly to annual billing, the unpaid value of the days remaining on the monthly cycle is applied as a credit against the annual invoice rather than being forfeited. A change from annual to monthly is treated as an ordinary downgrade and takes effect at renewal.

The financial effect of any change is shown before it is confirmed. No additional amount that was not displayed and authorized is charged.

Withholding is not a commercial discount and must not silently reduce VAT or the gross invoice. It requires tax-profile review, evidence and a certificate workflow.

OCTK provides documents and invoices required for transactions according to its actual tax position and the legal and tax rules applicable to it. The customer is responsible for accurate billing information when requesting a document in the business name.

Customer invoices, receipts and payment confirmations remain distinct from official B2B electronic invoices and official B2C electronic receipts. No OCTK document is official until enrollment, integration and acceptance are verified.

Prices may change in the future. A new price is not applied retroactively to a subscription period already paid. Where a change affects a later renewal, the new price is shown or notified through the approved mechanism before collection where required.

Legal updates require official-source verification, effective dating, review, approval and controlled publication. Historical transactions are not silently recalculated.

Payment disputes and chargebacks follow the actual payment-provider process, transaction evidence and applicable law. They do not erase the original financial event or tax document, and no provider outcome or timing is promised while the provider is unconfigured.

Billing questions use the centrally configured OCTK Restaurant OS billing mailbox.