AIRPOS TERMS OF USE

rules for access to the website application and payment platform

Version: 1.0
Effective date: 30 October 2026

1. GENERAL PROVISIONS

1.1. These Terms of Use (the “Terms”) govern access to the AirPOS website, mobile application, payment pages, Merchant Dashboard, SoftPOS functionality, application programming interfaces (APIs) and other components of the AirPOS platform.

1.2. The operator of AirPOS 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 Terms apply to:

• visitors to the AirPOS website;
• Payers using payment pages or supported payment interfaces;
• Merchants connected to AirPOS;
• directors, employees, cashiers, representatives and other Authorised Users of a Merchant;
• developers and technical specialists using the AirPOS API or documentation.

Those persons are collectively referred to as “Users” and individually as a “User”.

1.4. By using the relevant AirPOS component, the User confirms that the User has read the applicable version of the Terms and agrees to comply with it. Where separate confirmation is required for a particular function, access to that function is granted after the corresponding action is completed in the interface.

1.5. The Operator’s relationship with a Merchant concerning payment acceptance, settlement, fees, Holds, Reserves, Refunds and Chargebacks is additionally governed by the AirPOS Public Offer, individual commercial terms and the applicable tariff plan. In the event of inconsistency concerning financial matters, those documents prevail.

1.6. A Payer purchases goods, works or services directly from the relevant Merchant. These Terms do not replace the agreement between the Payer and the Merchant.

1.7. If a User does not agree to the Terms, the User must cease using the relevant AirPOS components.

2. DEFINITIONS

AirPOS means the Operator’s software and technology platform comprising the website, applications, payment pages, Merchant Dashboard, API and agreed payment tools.

Merchant means a business or organisation connected to AirPOS to accept payments for its own goods, works or services.

Payer means an individual or legal entity initiating a payment in favour of a Merchant.

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

SoftPOS means functionality for accepting contactless card payments using a compatible NFC-enabled mobile device without a separate physical POS terminal.

Payment Page means an interface through which a Payer receives payment information and initiates payment by an available method.

Payment Partner means a bank, acquirer, processing organisation, payment system or other infrastructure provider participating in execution of a payment operation.

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

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

Account means the data and access credentials used to identify a User and grant access to relevant functions.

3. PURPOSE AND FUNCTIONS OF AIRPOS

3.1. AirPOS provides technology tools for arranging and supporting fiat payments and interaction among Merchants, Payers and payment-infrastructure participants.

3.2. Depending on territory, Merchant category, currency, technical compatibility and onboarding terms, AirPOS may provide:

• acceptance of contactless payments through SoftPOS;
• a virtual POS interface for card payments;
• payments by QR codes;
• creation and use of PayLink payment links;
• Gateway and API integration with Merchant websites and applications;
• Payment Pages;
• management of Transactions, Refunds and reports;
• notifications and display of operation results;
• other supported fiat payment methods.

3.3. Available functions may differ among Users and may change to reflect applicable law, security requirements, payment-system rules and the capabilities of Payment Partners.

3.4. Availability of the website or application in a country does not automatically mean that all payment functions are available there.

4. REGISTRATION AND ACCESS

4.1. Certain functions require registration, confirmation of contact details, authentication, acceptance of applicable contractual documents and successful completion of required checks.

4.2. The User must provide accurate, complete and current information and update it promptly.

4.3. A Merchant independently determines its Authorised Users and their access rights where AirPOS supports that function.

4.4. Transferring an Account or granting access to an unauthorised person is prohibited.

4.5. The User must keep passwords, one-time codes, API keys, tokens and other access credentials confidential. The Operator does not request a password or complete one-time code outside the designated authentication interface.

4.6. The Operator may apply multi-factor authentication, device checks, session restrictions, operation confirmations and other security measures.

4.7. The User must immediately notify the Operator of Account compromise, loss of a device, suspicious activity or unauthorised access.

4.8. Actions performed using valid access credentials are treated as actions of the relevant User unless established otherwise. This does not release the Operator from liability for a proven breach of its own security obligations.

5. MERCHANT RIGHTS AND OBLIGATIONS

5.1. A Merchant may use AirPOS only for its own lawful business activities disclosed and approved during onboarding.

5.2. The Merchant must:

• comply with the Public Offer, these Terms, payment-system rules and applicable law;
• ensure the legality and accurate description of its goods and services;
• disclose to the Payer the seller’s name, price, currency and payment, delivery, cancellation and refund terms;
• accept payments only through approved websites, applications, points of sale and devices;
• supervise its employees and other Authorised Users;
• retain evidence of orders, performance and communications with Payers;
• respond promptly to Operator requests concerning Transactions, Refunds, Chargebacks, complaints and reviews;
• hold the permits and licences required for its activities.

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

• accept payments for another person;
• provide AirPOS to another seller or payment intermediary;
• connect an undisclosed domain, application, brand or point of sale;
• accept undisclosed, redirected or commingled payment traffic;
• change its actual business model or category of goods and services without notice;
• state an incorrect seller, MCC, purpose or place of a Transaction;
• use AirPOS for payment aggregation or re-acquiring.

5.4. The Merchant is responsible for the actions of its Authorised Users and for the content of its websites, applications, advertising and commercial offers.

6. SOFTPOS AND MOBILE DEVICES

6.1. SoftPOS requires a compatible mobile device with a functioning NFC module, supported operating system and current security updates.

6.2. The AirPOS application must be obtained from an official source specified by the Operator. Use of a modified, unofficial or outdated version may be restricted.

6.3. SoftPOS must not be used on a device with root or jailbreak access, disabled security controls, malicious software or other indications of compromise.

6.4. An Authorised User must:

• ensure the physical security of the device;
• not provide it to unauthorised persons;
• lock the screen when not in use;
• allow the Payer to verify the amount and currency;
• not record or photograph card details, PINs or confirmation codes;
• verify the final result of an operation before repeating a payment.

6.5. The Operator may restrict SoftPOS on a particular device in the event of incompatibility, a security threat, breach of the Terms or a requirement of a Payment Partner.

6.6. SoftPOS operation depends on the device, NFC, internet connection, operating system, card issuer and payment infrastructure. Not every contactless Payment Instrument is necessarily supported.

7. PAYMENT PAGES AND PAYER ACTIONS

7.1. A Payment Page is used to initiate a payment in favour of the identified Merchant.

7.2. Before confirming payment, the Payer must review the available information concerning the Merchant, amount, currency and purpose of the operation.

7.3. The Payer must use only a Payment Instrument that the Payer is legally entitled to use and must not disclose authentication codes to third parties.

7.4. A payment should not be confirmed if the payment information is incorrect or the Merchant is unknown to the Payer.

7.5. AirPOS is not the seller of a Merchant’s goods or services and does not confirm their quality, availability, delivery or conformity with description.

7.6. Questions concerning an order, cancellation, delivery, quality or refund should first be addressed to the Merchant. The right to contact the issuer, payment system, Operator or a competent authority remains available where provided by law.

7.7. The Operator may perform anti-fraud, sanctions, technical or other mandatory checks and decline or suspend an operation where appropriate grounds exist.

8. BANK CARDS AND CONTACTLESS PAYMENTS

8.1. Card operations are executed with the participation of the relevant issuers, acquirers, processing organisations and payment systems.

8.2. Authorisation and authentication are performed under the rules of the applicable payment infrastructure. The issuer or another authorised participant may decline an operation.

8.3. AirPOS may receive and display limited operation data, including masked card information, an identifier, amount, currency, date, time and result.

8.4. The Operator does not request a PIN, complete card security code or other sensitive authentication data outside the protected process of the relevant Payment Partner.

8.5. A preliminary notification on the Payer’s or Merchant’s device does not necessarily mean that the Transaction has been finally completed. The final result received through the payment infrastructure is determinative.

9. QR PAYMENTS PAYLINK VIRTUAL POS AND GATEWAY

9.1. A QR code or PayLink must be created and distributed only through approved AirPOS tools and used for the Merchant’s disclosed activities.

9.2. The Merchant must prevent substitution of a QR code, payment link or Payment Page and immediately report suspected compromise.

9.3. Before confirmation, the Payer must verify the Payment Page address, amount, currency and recipient information.

9.4. A Merchant using Virtual POS or Gateway must comply with the technical documentation, payment-form placement rules, security requirements and restrictions on storage of payment data.

9.5. The Merchant must not modify a payment interface in a manner that misleads the Payer as to the recipient, amount, currency or purpose of payment.

10. OPERATION RESULTS AND CONFIRMATIONS

10.1. AirPOS displays available information on the processing and result of a Transaction using the designations provided by the relevant interface and payment infrastructure.

10.2. A Transaction is successfully completed only after final confirmation is received through AirPOS. A preliminary notification, commencement of processing or other interim or uncertain result does not confirm final receipt of payment.

10.3. If the Transaction result is not unambiguous, the Merchant must check the operation information in AirPOS or contact support before initiating payment again.

10.4. Operation information may be updated with delay due to the activities of a bank, payment system, communications network or another payment-infrastructure participant.

10.5. An AirPOS electronic confirmation does not replace a fiscal or cash-register document that the Merchant must issue under applicable law.

11. REFUNDS CHARGEBACKS AND COMPLAINTS

11.1. Terms for returning goods or services are established by the Merchant, subject to applicable law and mandatory rules of the payment method.

11.2. A Refund may be initiated by the Merchant through an available AirPOS interface and is usually sent to the original Payment Instrument.

11.3. Availability, timing and method of a Refund depend on the original operation, available funds, the method used and applicable restrictions.

11.4. A card operation may be disputed under issuer and payment-system rules. The Operator does not guarantee the outcome of a Chargeback.

11.5. A Payer may send a complaint concerning the payment interface to info@airpos.co. The complaint must contain sufficient information to identify the operation, but must not include a PIN, complete card number or complete security code.

11.6. Contacting AirPOS does not relieve the Payer of the need to contact the Merchant or issuer promptly where necessary to meet a refund or dispute deadline.

12. API AND TECHNICAL INTEGRATION

12.1. The API is available only to authorised Merchants and developers within their granted access rights.

12.2. An API User must:

• comply with the current technical documentation;
• keep secret keys out of public code and client applications;
• use encryption and secure communications channels;
• verify signatures and authenticity of notifications where required;
• prevent repeated processing of identical events;
• comply with applicable request-rate limits;
• replace compromised keys immediately.

12.3. Attempts to circumvent authorisation, limits or security mechanisms or to obtain data of other Users are prohibited.

12.4. The Operator may change API versions, decommission obsolete methods and establish migration periods, giving notice through the documentation or agreed channels.

12.5. API access may be restricted immediately in the event of a security threat, abnormal load, breach of documentation or compromised keys.

13. PROHIBITED ACTIONS

13.1. Users must not:

• use AirPOS for unlawful activity, fraud, money laundering, terrorist financing or sanctions evasion;
• use stolen, forged or unauthorised payment data;
• provide false information or forged documents;
• substitute the seller, Payment Page, QR code, payment purpose or amount;
• split operations to circumvent limits or controls;
• interfere with the platform, introduce malicious code or impose excessive load;
• engage in unauthorised access, vulnerability scanning or security testing without written permission;
• copy, modify, decompile or reverse engineer the application or its components except where expressly permitted by law;
• use automated tools to extract data contrary to the documentation or established restrictions;
• infringe the rights of the Operator, Merchants, Payers or third parties.

13.2. The Operator may block content, an Account, device, API key or operation where there are reasonable indications of a breach.

14. AML CFT SANCTIONS AND CHECKS

14.1. The Operator applies risk-based identification, verification, sanctions screening, fraud-prevention and transaction-monitoring measures.

14.2. A User must provide requested information and documents where necessary to verify identity, authority, activities, source of funds, purpose of an operation or compliance with applicable requirements.

14.3. Refusal to provide mandatory information, inability to complete a check or identification of unacceptable risk may result in restriction of a function, operation or Account.

14.4. The Operator may disclose information to Payment Partners and competent authorities where a legal basis exists and may withhold from the User information whose disclosure is prohibited by law.

15. GEOGRAPHICAL AND AGE RESTRICTIONS

15.1. Payment functions are available only in supported jurisdictions and within applicable legal, technical and commercial conditions.

15.2. A User must not conceal the User’s actual location or provide false information to circumvent restrictions.

15.3. A Merchant and an Authorised User must have the legal capacity and authority necessary to assume obligations.

15.4. AirPOS is not intended for independent registration or business use by minors. Processing a minor Payer’s payment where permitted by law does not constitute granting that minor a Merchant Account.

16. INTELLECTUAL PROPERTY AND LICENCE

16.1. Rights in AirPOS software, designs, databases, interfaces, documentation, trade names and other materials belong to the Operator or the relevant rights holders.

16.2. Subject to compliance with the Terms, the User is granted a limited, revocable, non-exclusive and non-transferable right to use the relevant AirPOS components solely for their intended purpose.

16.3. The right of use terminates when access to the relevant function or Account ends.

16.4. Use of AirPOS does not transfer ownership of the platform, source code, documentation or trade names to the User.

16.5. The Merchant grants the Operator the right to display the Merchant’s name, logo and point-of-sale information to the extent necessary for the Payment Page, recipient identification and provision of services.

17. THIRD PARTY SERVICES AND APP STORES

17.1. AirPOS may interact with banks, Payment Partners, communications providers, cloud infrastructure, mapping services and other third-party services.

17.2. Certain third-party services may be governed by their own terms and policies. The User must review them where required to use the relevant function.

17.3. Downloading the mobile application through the App Store, Google Play, AppGallery or another official source may additionally be governed by the rules of the relevant store.

17.4. The relevant app store is not a party to the agreement between the User and the Operator and is not responsible for AirPOS payment services unless its rules provide otherwise.

18. PERSONAL DATA AND COOKIES

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

18.2. The website and application may use cookies, local storage, session identifiers and similar technologies for authentication, security, saving preferences and analysing technical performance.

18.3. Optional technologies are used where the required legal basis and available consent controls exist.

18.4. A User must not send a PIN, complete card number, complete security code or password by ordinary email.

19. SECURITY AND INCIDENTS

19.1. The Operator applies reasonable technical and organisational security measures appropriate to the nature of the platform and processed data.

19.2. The User must maintain the security of the device, browser, operating system, network and access credentials.

19.3. If phishing is suspected, the User must verify the domain, application source and sender address and must not enter account or payment information through an unverified link.

19.4. The User must report incidents affecting AirPOS without undue delay and cooperate with the investigation.

19.5. No information system can guarantee complete absence of threats. This provision does not release the Operator from obligations that cannot be excluded by law.

20. AVAILABILITY UPDATES AND SUPPORT

20.1. The Operator takes reasonable measures to maintain AirPOS operation but does not guarantee continuous or error-free availability unless a separate service-level agreement provides otherwise.

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

20.3. Continued use of certain functions may require an update to the application, operating system, API integration or security settings.

20.4. The Operator may change the interface, technical requirements and functions to reflect security, compatibility and development of the platform.

20.5. Support requests may be sent to info@airpos.co or through the available support interface.

21. RESTRICTION AND TERMINATION OF ACCESS

21.1. A User may cease using publicly accessible AirPOS components at any time. Closure of a Merchant Account is governed by the Public Offer.

21.2. The Operator may temporarily restrict access in the event of:

• breach of the Terms or related agreements;
• a security threat;
• suspected fraud or unlawful activity;
• failure to complete a mandatory check;
• an applicable sanctions restriction;
• a requirement of a Payment Partner or competent authority;
• the need to prevent harm to a User, the Operator or third parties.

21.3. A restriction is applied to an extent proportionate to the identified risk. The User is notified to the extent permitted by law and confidentiality requirements.

21.4. Termination of access does not extinguish obligations arising before termination, including obligations concerning Transactions, Refunds, Chargebacks, data protection, intellectual property and dispute resolution.

22. LIABILITY

22.1. A User is liable for breach of the Terms and actions performed through the access credentials provided to the User, subject to applicable law.

22.2. The Operator is liable for breach of its own obligations in accordance with applicable law and the relevant contractual documents.

22.3. The Operator is not liable for:

• the quality, legality, availability or delivery of a Merchant’s goods or services;
• a decision of an issuer, acquirer or payment system to decline or dispute an operation;
• acts of an independent third-party service outside the Operator’s reasonable control;
• device incompatibility resulting from modification or non-compliance with requirements;
• loss caused by the User providing access credentials to an unauthorised person;
• indirect loss or loss of profit unless such liability is imposed by mandatory law.

22.4. The Operator does not limit liability for wilful misconduct, fraud or other cases in which limitation is prohibited by law.

23. FORCE MAJEURE

23.1. A party is not liable for delay or non-performance caused by circumstances beyond its reasonable control, including natural disasters, war, civil unrest, epidemics, large-scale communications or power failures, cyberattacks and binding decisions of public authorities.

23.2. The affected party takes reasonable measures to mitigate the consequences and resume performance.

23.3. Lack of funds and ordinary commercial difficulty do not in themselves constitute force majeure.

24. AMENDMENTS TO THE TERMS

24.1. The Operator may update the Terms to reflect changes in functions, law, security requirements and payment infrastructure.

24.2. The current version is published on the official AirPOS website with its effective date.

24.3. Registered Users are notified of material changes through the Account, application, email or another available channel where required by applicable law or contract.

24.4. Continued use of the relevant function after an amendment takes effect constitutes acceptance of the new version to the extent permitted by law. If the User does not agree, the User must cease using the affected function.

25. GOVERNING LAW AND DISPUTES

25.1. The Terms are governed by the laws of Saint Vincent and the Grenadines, without prejudice to mandatory rules of other jurisdictions applicable to a particular User or operation.

25.2. A dispute must initially be addressed by submitting a complaint to the Operator and exchanging the necessary information.

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

25.4. The Terms do not restrict consumer rights that cannot be excluded or limited by agreement.

26. FINAL PROVISIONS

26.1. If any provision of the Terms is held invalid, the remaining provisions continue in effect.

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

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

26.4. Electronic records and communications may be used to evidence the User’s actions to the extent permitted by applicable law.

27. CONTACT INFORMATION

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