PUBLIC OFFER

for the provision of AirPOS payment and technology services

Version: 1.0
Effective date: 30 October 2026

1. GENERAL PROVISIONS

1.1. This Public Offer (the “Offer”) constitutes an official proposal by TRANZA LLC to enter into an agreement for the provision of AirPOS payment and technology services on the terms set out below.

1.2. The operator of the AirPOS platform is TRANZA LLC, a company incorporated under the laws of Saint Vincent and the Grenadines under registration number 4527 LLC 2026, with its registered office at Euro House, Richmond Hill Road, Kingstown, St. Vincent and the Grenadines (the “Operator”).

1.3. The Offer is addressed to legal entities, sole proprietors and other persons lawfully carrying on business and intending to use AirPOS to accept payments for their own goods, works or services (the “Merchant”).

1.4. The Offer is not addressed to individuals acting solely for personal, family or household purposes. The rights of payers and consumers are not limited by this Offer and are governed by applicable law, the rules of the relevant payment systems and the Merchant’s terms of sale of goods or services.

1.5. Acceptance of the Offer occurs when an authorised representative of the Merchant completes all of the following actions:

• registers an AirPOS account or follows an onboarding link provided by the Operator;
• reviews this Offer and the related documents;
• checks the box indicating agreement and clicks “Accept”, “Connect”, “Continue” or another button with equivalent meaning;
• confirms the action using an available authentication method, if such confirmation is requested by AirPOS.

1.6. Upon acceptance, an agreement in electronic form is concluded between the Operator and the Merchant (the “Agreement”). To the extent permitted by applicable law, the Agreement has the same binding force as a document bearing the handwritten signatures of the parties.

1.7. AirPOS electronic records, including the account identifier, date and time of acceptance, version of the Offer, IP address, authentication information and other technical logs, may be used to evidence the conclusion and terms of the Agreement. The Merchant is provided with an opportunity to save or reproduce the applicable version of the Offer.

1.8. A person accepting the Offer on behalf of the Merchant confirms that he or she has the required authority. The Operator may request documents evidencing such authority.

1.9. Conclusion of the Agreement does not automatically activate payment functionality. Access is granted after successful completion of KYB/KYC procedures and risk assessment, agreement of commercial terms and confirmation of activation by the Operator.

1.10. The Agreement incorporates the then-current AirPOS Terms of Use, Privacy Policy, AML/CFT Policy, applicable tariff plan, individual commercial terms, acceptable use rules, technical documentation and any other terms expressly referenced in the Offer or the AirPOS interface.

1.11. In the event of inconsistency, the following documents prevail in the order stated: an individual written agreement; individual commercial terms; this Offer; the applicable tariff plan; the Terms of Use; and the technical documentation, unless mandatory law requires otherwise.

2. TERMS AND DEFINITIONS

AirPOS means the Operator’s software and technology platform providing access to agreed tools for payment acceptance, transaction data processing, reporting and settlement.

SoftPOS means functionality enabling a compatible NFC-enabled mobile device of the Merchant to be used as a software-based payment terminal without a separate physical POS device.

Merchant means a person that has entered into the Agreement with the Operator and accepts payments for its own goods, works or services.

Authorised User means a director, employee, cashier, representative or other person to whom the Merchant has granted access to AirPOS.

Payer means a person initiating payment for the Merchant’s goods, works or services.

Payment Partner means a bank, acquirer, processing organisation, payment system, payment infrastructure provider or another participant engaged by the Operator in the execution of a Transaction.

Payment Instrument means a bank card, tokenised payment method, compatible mobile device, QR instrument or another supported fiat payment method.

Transaction means an operation initiated using AirPOS and a supported Payment Instrument.

Payment Request means a request for payment generated through AirPOS and specifying the amount, currency, Merchant and other required parameters.

Merchant Dashboard means the Merchant’s secure interface for accessing AirPOS functions and transaction information.

Settlement Account means a technical accounting record reflecting Transaction amounts, fees, refunds, disputes, reserves, adjustments and amounts payable to the Merchant. The Settlement Account is not a bank account, deposit or separate payment instrument.

Settlement means the calculation of the amount due to the Merchant and its transfer in accordance with the agreed schedule.

Hold means a temporary restriction on the availability of an amount or the execution of an operation based on contractual, legal or risk-based grounds.

Reserve means an amount retained under the individual terms to cover potential Refunds, Chargebacks, payment-system fines, a negative balance and other substantiated obligations of the Merchant.

Refund means repayment of a Transaction amount to the Payer.

Chargeback means a challenge to a card Transaction under the rules of the applicable payment system.

KYB/KYC means procedures for identifying, verifying and assessing the Merchant, its representatives, directors, controlling persons and ultimate beneficial owners.

3. SUBJECT MATTER OF THE AGREEMENT

3.1. The Operator grants the Merchant access to AirPOS and provides the agreed payment and technology services for arranging the acceptance and processing of fiat payments, recording Transactions, producing reports and arranging settlements with the Merchant.

3.2. Subject to the agreed terms, AirPOS may provide:

• SoftPOS acceptance of contactless card payments through a compatible NFC-enabled device;
• card acceptance through a virtual POS interface;
• acceptance of payments by QR codes;
• creation of PayLink payment links;
• integration of a payment form or Gateway with the Merchant’s website or application;
• a Merchant Dashboard, API, notifications, registers and reports;
• Refund tools and support for disputed operations;
• other fiat payment methods made available to the Merchant in the AirPOS interface.

3.3. The specific functions, currencies, territories and Payment Instruments available are determined by the onboarding terms, the capabilities of Payment Partners, the Merchant’s business category and applicable restrictions.

3.4. The Operator may perform individual elements of the service itself or engage Payment Partners. Authorisation, processing, clearing, settlement and other operations may be performed by the relevant Payment Partner under the applicable payment-infrastructure rules.

3.5. AirPOS is not the seller of the Merchant’s goods, works or services and does not become a party to the agreement between the Merchant and the Payer. The Merchant remains solely responsible for the legality, quality, description, delivery and return of its goods or services.

3.6. The Operator does not provide the Merchant with a bank account, deposit or credit facility unless expressly agreed in a separate document and permitted by applicable law.

4. REGISTRATION VERIFICATION AND ACTIVATION

4.1. To be activated, the Merchant must register an account, accept the mandatory AirPOS documents, provide the requested information and successfully complete KYB/KYC and risk assessment.

4.2. The Operator may request, among other things:

• registration and constitutional documents;
• registered and actual address information;
• documents of directors and authorised representatives;
• information and documents concerning ultimate beneficial owners and the ownership structure;
• evidence of representatives’ authority;
• a description of the business, goods, services, sales channels and target geography;
• addresses of websites, applications, points of sale and other resources;
• information on expected volumes, average transaction value, currencies and the nature of operations;
• information on source of funds and origin of the business, where necessary;
• bank and settlement details;
• licences, permits and evidence of the right to conduct the stated activity;
• other information required for AML/CFT, sanctions compliance, fraud prevention and compliance with payment-system rules.

4.3. The Merchant warrants that all information provided is accurate, complete and current and must notify the Operator of changes without undue delay.

4.4. The Operator may conduct initial, periodic, repeat and ad hoc reviews itself or through specialist providers.

4.5. Successful completion of a review does not oblige the Operator to activate the Merchant. The decision is made in light of the review results, risk profile, availability of payment infrastructure and applicable requirements.

4.6. Payment functions are deemed activated after the Merchant is notified or the account status is changed in AirPOS.

4.7. The Operator may refuse activation without disclosing confidential monitoring criteria and without liability to reimburse costs incurred by the applicant in preparing for onboarding, unless mandatory law provides otherwise.

5. ACCOUNTS AND AUTHORISED USERS

5.1. The Merchant is responsible for actions taken through its account and the accounts of Authorised Users unless it proves that the action became possible solely as a result of a breach by the Operator.

5.2. The Merchant must assign individual access rights, immediately revoke access for persons who have left or are no longer authorised and prevent the sharing of credentials.

5.3. Passwords, one-time codes, API keys, tokens and other access credentials must be kept confidential.

5.4. The Merchant must immediately notify the Operator of suspected compromise, an unauthorised operation, loss of a device or credentials and take available steps to restrict access.

5.5. The Operator may apply multi-factor authentication, session restrictions, device binding and other security measures.

6. SOFTPOS AND DEVICE REQUIREMENTS

6.1. To use SoftPOS, the Merchant must use a compatible mobile device that meets the published technical requirements of AirPOS and the Payment Partners.

6.2. The device must have a functioning NFC module, a supported operating-system version, current security updates and an official version of the AirPOS application.

6.3. SoftPOS must not be used on a device with disabled or circumvented security controls, an unauthorisedly modified operating system, malicious software or other indications of compromise.

6.4. The Merchant must ensure the physical security of the device, must not provide it to unauthorised persons and must not use it in circumstances that prevent the Payer from verifying the payment amount and details.

6.5. Before initiating a Transaction, the Merchant must correctly enter the amount and currency and allow the Payer to verify them before presenting the Payment Instrument.

6.6. The Merchant must not reinitiate a payment while the result of the previous attempt is uncertain until the result has been checked in AirPOS or instructions have been obtained from the Operator.

6.7. The Operator may remotely restrict SoftPOS functionality on a device where a security threat, incompatibility or breach of the terms of use is identified.

7. PAYMENT PROCESS

7.1. The Merchant creates a Payment Request specifying the amount, currency and other required parameters.

7.2. The Payer reviews the available information and confirms the Transaction by the method provided for the relevant Payment Instrument.

7.3. A Transaction may be subject to authorisation, authentication, anti-fraud, sanctions, technical and other required checks.

7.4. The Merchant must rely on the final result displayed in AirPOS and must not treat a payment as completed solely on the basis of the Payer’s actions, a notification on the Payer’s device or a preliminary message.

7.5. Where the result of an operation is uncertain, the Merchant must await an update or contact support before attempting another charge or delivering the goods, unless its internal rules expressly provide for acceptance of the relevant risk.

7.6. A payment may be declined because of an issuer decision, insufficient funds, limits, authentication, risk assessment, sanctions restrictions, technical incompatibility or other payment-infrastructure requirements.

7.7. The Operator does not guarantee the success of every Transaction and cannot reverse a decision of an issuer or payment system unless it has been granted such authority.

7.8. Electronic payment confirmation may be sent to the Payer or provided by the Merchant by an available method. The Merchant is responsible for issuing any fiscal, cash-register or other mandatory receipt unless applicable law provides otherwise.

8. MERCHANT OBLIGATIONS AND PERMITTED TRAFFIC

8.1. The Merchant may use AirPOS solely to accept payments for the goods, works and services disclosed and approved during onboarding.

8.2. Without the Operator’s prior written consent, the Merchant must not:

• accept payments for the benefit of third parties;
• provide another seller or payment intermediary with access to AirPOS;
• connect undisclosed websites, applications, domains, points of sale or brands;
• accept payments for goods or services materially different from the approved business model;
• submit undisclosed, redirected or commingled payment traffic;
• use inaccurate information concerning the seller, MCC, purpose or place of the operation;
• engage independently in re-acquiring, payment aggregation or any other acceptance of payments for third parties.

8.3. The Merchant must:

• comply with the laws of the countries in which it offers goods or services;
• hold all required licences and permits;
• disclose to the Payer its name, contact details, prices, currency and terms of sale, delivery, cancellation and refund;
• not mislead the Payer as to the recipient of the payment;
• retain documents evidencing the order, the Payer’s consent, delivery and performance;
• respond promptly to requests concerning disputes, Refunds and Chargebacks;
• comply with payment-system rules and the Operator’s security instructions.

8.4. The Merchant is responsible for the actions of its employees, contractors, websites, applications and points of sale.

9. PROHIBITED AND RESTRICTED ACTIVITIES

9.1. AirPOS must not be used for unlawful activities, fraud, money laundering, terrorist financing, sanctions evasion, trade in prohibited goods, use of stolen payment data or other operations that violate applicable law.

9.2. The Operator may establish a separate list of prohibited and restricted business categories and special conditions for higher-risk activities.

9.3. The absence of a category from a published list does not constitute automatic approval. The Merchant must disclose the true nature of its business in advance.

9.4. If the product range, business model, geography, website, MCC, ownership structure or nature of traffic changes, the Merchant must notify the Operator in advance where the change may affect the risk assessment or terms of service.

10. SETTLEMENT ACCOUNT AND REPORTING

10.1. AirPOS maintains the Merchant’s Settlement Account and records Transactions, fees, Refunds, Chargebacks, Holds, Reserves, adjustments and Settlement amounts in it.

10.2. Display of an amount does not mean that it is unconditionally or immediately available. Availability depends on finality of the operation, the settlement schedule, applicable retentions and the results of checks.

10.3. The Operator may correct technical, calculation and operational errors, retain a documented basis for the correction and reflect it in the reports.

10.4. The Merchant must regularly review reports and notify the Operator of a suspected discrepancy without undue delay and within the period prescribed by the relevant Payment Partner or individual terms.

10.5. The Settlement Account is intended to record obligations under the Agreement, is not the Merchant’s bank account, does not accrue interest and may not be used to hold funds outside the purposes of settlement through AirPOS.

11. SETTLEMENT AND TRANSFER OF FUNDS

11.1. Settlement is made in the agreed currency and according to the schedule established by the tariff plan or individual commercial terms.

11.2. The Settlement amount is calculated as the amount of confirmed Transactions less fees, Refunds, Chargebacks, Reserves, adjustments, taxes and other agreed and lawful deductions.

11.3. Transfers are made to the Merchant’s verified bank or other permitted settlement details. The Operator may request evidence that the details belong to the Merchant.

11.4. The transfer period may be extended for the duration of a mandatory review, technical processing, a bank holiday, delay by a Payment Partner or where there are grounds for a Hold.

11.5. The Operator provides information on a material delay and its general basis to the extent permitted by law, payment-infrastructure rules and confidentiality requirements.

11.6. The legal and operational routing of settlement funds is determined by applicable law, the payment scheme and agreements with Payment Partners. Depending on the method used, funds may be processed through accounts and infrastructure of the Operator or the relevant Payment Partner.

12. TARIFFS FEES AND TAXES

12.1. The amount and method of charging fees are established in the tariff plan and individual commercial terms communicated to the Merchant before activation of the relevant paid function.

12.2. Fees may be charged for payment acceptance and processing, Settlement, Refunds, Chargebacks, conversion, additional reviews, technical services and other agreed operations.

12.3. The Operator may deduct agreed fees from Settlement amounts or invoice the Merchant.

12.4. The Operator may amend tariffs by giving advance notice within the period specified in the individual terms or notice. If an amendment is adverse to the Merchant, the Merchant may discontinue the affected service before the amendment takes effect, unless otherwise required by mandatory law, payment-system rules or a change in third-party costs requiring immediate application.

12.5. The Merchant is solely responsible for determining and complying with its tax, fiscal and accounting obligations. The Operator’s fees do not include the Merchant’s taxes unless expressly stated otherwise.

13. CURRENCY CONVERSION

13.1. Where payment and Settlement are made in different currencies, conversion may be performed by the Operator or a Payment Partner.

13.2. The exchange-rate mechanism, applicable fee and quotation source are specified in the tariff plan, individual terms or the AirPOS interface.

13.3. A quotation may be updated before final execution if market conditions change, its validity period expires or confirmation of the operation is delayed.

13.4. The Merchant accepts the risk of exchange-rate movements between initiation of the payment and Settlement to the extent contemplated by the agreed settlement model.

14. HOLDS AND RESERVES

14.1. The Operator may impose a Hold on a Transaction, Settlement amount or account where there are reasonable contractual, legal, sanctions, fraud or AML/CFT grounds.

14.2. Grounds may include:

• suspected fraud or unauthorised operations;
• a material deviation from the disclosed profile;
• an increase in Refunds or Chargebacks;
• indications of undisclosed or commingled traffic;
• the need to verify source of funds or the economic purpose of operations;
• a sanctions match;
• a requirement of a competent authority, payment system or Payment Partner;
• risk of substantiated losses arising from the Merchant’s activities;
• breach of the Agreement.

14.3. The scope and duration of a Hold must be proportionate to the identified risk and must not continue longer than reasonably necessary to complete a review, comply with a mandatory requirement or cover the relevant obligation.

14.4. The Merchant is notified of a Hold and its general basis to the extent permitted by law and confidentiality rules.

14.5. The Reserve, its amount, funding method, retention period and release procedure are established by the individual terms in light of the Merchant’s risk profile.

14.6. The Reserve may be used only to cover the Merchant’s obligations in respect of Refunds, Chargebacks, payment-system fines, a negative balance and other amounts expressly contemplated by the Agreement.

14.7. Any unused Reserve balance is released after the applicable period and completion of final settlement, provided that no outstanding obligations remain.

15. REFUNDS AND CANCELLATIONS

15.1. The Merchant is responsible to the Payer for its cancellation, return-of-goods and reimbursement policies to the extent required by applicable law.

15.2. A Refund is initiated through AirPOS or an agreed channel and, as a rule, is returned to the original Payment Instrument.

15.3. The Operator may decline technical execution of a Refund if there is an insufficient balance, the original operation cannot be identified, the permitted period has expired, legal restrictions apply or the method used does not support refunds.

15.4. Where a Refund is mandatory under law or payment-system rules, the Merchant must provide the funds and cooperation required to execute it.

15.5. The fee for the original Transaction and any separate Refund fee are returned or retained in accordance with the tariff plan and applicable law.

16. CHARGEBACKS AND DISPUTED OPERATIONS

16.1. A card Transaction may be disputed by the Payer or issuer under the rules of the relevant payment system.

16.2. Within the period set by the Operator, the Merchant must provide documents evidencing the order, authentication, delivery, provision of the service, communications with the Payer and compliance with the refund policy.

16.3. The Operator may debit or retain the Chargeback amount, applicable fees and substantiated costs from the Settlement Account, Settlement or Reserve.

16.4. Submission of documents does not guarantee that the dispute will be decided in the Merchant’s favour. The final decision may be taken by the issuer, acquirer or payment system.

16.5. If the final decision is in the Merchant’s favour, the relevant amount is reinstated to the extent actually returned through the payment infrastructure.

17. NEGATIVE BALANCE AND SET OFF

17.1. A negative balance may arise from Refunds, Chargebacks, fines, fees, adjustments and other substantiated obligations of the Merchant.

17.2. The Merchant must discharge a negative balance within the period specified in the Operator’s notice or individual terms.

17.3. The Operator may set off the debt against subsequent receipts, Settlement or the Reserve and, if they are insufficient, demand separate payment.

17.4. The Operator provides the Merchant with information on the basis and amount of the debt, except for information whose disclosure is restricted by law or payment-system rules.

18. AML CFT SANCTIONS AND MONITORING

18.1. The Operator applies risk-based KYB/KYC, sanctions compliance, fraud-prevention and Transaction-monitoring measures in accordance with applicable law and the AML/CFT Policy.

18.2. The Operator may request information on the economic purpose of an operation, source of funds, the Payer, counterparty, goods or services and supporting documents.

18.3. The Merchant must cooperate with reviews and provide the requested information within the prescribed reasonable period.

18.4. The Operator may decline, suspend or restrict an operation or service where an applicable sanctions prohibition exists, a mandatory review cannot be completed, there are material indications of unlawful activity or the risk is unacceptable.

18.5. The Operator may disclose information to competent authorities and Payment Partners where required or permitted by law. The Operator is not required to inform the Merchant of a report or review where such notice is prohibited.

19. GEOGRAPHICAL RESTRICTIONS

19.1. Availability of AirPOS depends on the Merchant’s country of incorporation and activity, place of operations, currency, payment method and applicable requirements.

19.2. The Operator may establish and amend lists of supported, restricted and prohibited territories in light of sanctions, licensing, Payment Partner requirements and risk assessment.

19.3. Availability of the website or application in a country does not mean that payment services are available there.

19.4. The Merchant must not conceal the actual geography of its activities or use technology to circumvent established restrictions.

20. SECURITY AND DATA PROTECTION

20.1. The parties take reasonable technical and organisational measures to protect data, accounts, devices and payment information.

20.2. The Merchant must not request, record, photograph or store full card details, PINs, confirmation codes or other sensitive authentication data except where expressly required by a certified payment process.

20.3. Processing of personal data is governed by the AirPOS Privacy Policy and applicable data-processing agreements.

20.4. The Merchant must immediately report incidents capable of affecting AirPOS, Payment Instruments, Payer data or the payment infrastructure and cooperate with the investigation.

21. SERVICE AVAILABILITY AND CHANGES

21.1. The Operator takes reasonable measures to maintain the availability of AirPOS but does not guarantee uninterrupted or error-free operation unless a separate SLA provides otherwise.

21.2. Functions may be temporarily restricted for maintenance, updates, threat remediation or compliance with a requirement of a Payment Partner or competent authority.

21.3. The Operator may change the interface, API, technical requirements and available functions, while maintaining reasonable compatibility and notifying the Merchant of material changes where reasonably practicable.

21.4. The Operator is not liable for disruptions affecting communications networks, banks, issuers, payment systems, app stores or other independent third parties outside its reasonable control, except where liability may not be limited by law.

22. LIABILITY AND INDEMNIFICATION

22.1. Each party is liable for breach of its obligations in accordance with the Agreement and applicable law.

22.2. The Operator is not liable for the quality, safety, legality, delivery or conformity with description of the Merchant’s goods and services or for disputes arising from the relationship between the Merchant and the Payer.

22.3. The Merchant indemnifies the Operator against documented losses, costs, Chargebacks, fines and third-party claims arising from the Merchant’s unlawful activity, breach of the Agreement, payment-system rules, consumer rights or third-party rights, or use of undisclosed traffic, to the extent caused by the Merchant’s acts or omissions.

22.4. Neither party is liable for indirect loss, loss of profit or loss of business opportunity unless such liability is imposed by mandatory law or results from wilful misconduct, fraud, breach of confidentiality or unlawful use of data.

22.5. Limitations of liability do not apply where their application is prohibited by law.

23. SUSPENSION AND TERMINATION

23.1. The Merchant may terminate the Agreement by giving notice and following the account-closure instructions unless the individual terms prescribe a notice period.

23.2. The Operator may suspend individual functions or terminate the Agreement in the event of a material breach, failure to complete a mandatory review, unlawful activity, unacceptable risk, a sanctions prohibition, a prolonged negative balance or a requirement of a Payment Partner or competent authority.

23.3. If a breach can be remedied without unacceptable risk, the Operator may allow the Merchant a reasonable period to remedy it.

23.4. Termination does not extinguish obligations relating to prior Transactions, Refunds, Chargebacks, Reserves, debt, confidentiality, data protection and dispute resolution.

23.5. Final settlement is performed after termination. Amounts not subject to lawful retention are transferred to the Merchant after completion of required reviews and the applicable liability period for disputed operations.

23.6. The Merchant is given an opportunity to obtain available reports in the manner and within the period specified in the interface or the Operator’s notice.

24. FORCE MAJEURE

24.1. A party is not liable for delay or failure caused by circumstances beyond its reasonable control, including natural disasters, war, civil unrest, epidemics, large-scale telecommunications or power failures, cyberattacks, binding governmental decisions and cessation of critical infrastructure.

24.2. The affected party must take reasonable measures to mitigate the consequences and resume performance.

24.3. Lack of funds or ordinary commercial difficulty does not in itself constitute force majeure.

25. NOTICES AND AMENDMENTS TO THE OFFER

25.1. Legally significant notices may be sent through the Merchant Dashboard, to the registered email address, through the application or by other agreed channels.

25.2. The Merchant must keep its contact details current and regularly review AirPOS communications.

25.3. The Operator may amend the Offer. A new version is published on the website and, where the amendment is material, communicated to the Merchant by an available method before it takes effect, unless the law or an urgent mandatory requirement permits another procedure.

25.4. Continued use of the affected service after an amendment takes effect constitutes acceptance of the new version. If the Merchant does not agree, it may discontinue the service and terminate the Agreement before the effective date, subject to completion of obligations that arose previously.

26. GOVERNING LAW AND DISPUTES

26.1. The Agreement is governed by the laws of Saint Vincent and the Grenadines, without prejudice to mandatory rules of other jurisdictions applicable to a particular operation or party.

26.2. Before commencing court proceedings, a party must submit a claim describing the circumstances and relief sought. Merchant claims must be sent to info@airpos.co.

26.3. The parties will seek to resolve a dispute through negotiation and exchange of documents within a reasonable period, taking into account the complexity of the matter and mandatory time limits under applicable law.

26.4. If a dispute is not resolved, it is subject to the jurisdiction of the competent courts of Saint Vincent and the Grenadines unless an individual agreement or mandatory law provides otherwise.

27. FINAL PROVISIONS

27.1. The Merchant may not assign its rights or obligations under the Agreement without the Operator’s prior written consent. The Operator may assign the Agreement to an affiliate or successor in connection with a reorganisation or transfer of the relevant business, provided that the Merchant is notified and its mandatory rights are preserved.

27.2. If any provision is held invalid, the remaining provisions remain effective. The invalid provision is enforced to the maximum extent permitted or replaced by a provision that most closely reflects its lawful purpose.

27.3. Failure or delay in exercising a right does not constitute a waiver of that right.

27.4. Headings are for convenience only and do not affect interpretation.

27.5. The electronic version of the Offer and related electronic records are admissible evidence of the parties’ relationship to the extent permitted by applicable law.

28. OPERATOR DETAILS

TRANZA LLC
Registration No.: 4527 LLC 2026
Euro House, Richmond Hill Road
Kingstown, St. Vincent and the Grenadines
Email: info@tranza.io