General Terms and Conditions

1. Legal Identity and Regulatory Status

1.1 Identity of the Service Provider

These Terms of Service (the "Terms") govern the contractual relationship between PAYSOLO LLC ("PaySolo", "the Company", "we", "us") and the natural or legal person who registers and accepts them ("Client", "you"). PAYSOLO LLC is a limited liability company organized under the laws of the State of Wyoming, United States. The Company operates the PaySolo software platform at paysolo.io.

1.2 Platform Role and Partner Services

PaySolo provides an intermediary software interface through which eligible Clients may access services made available by Contracted Partners. The Partner identified for the relevant service carries out the financial transaction under its own terms and applicable permissions. Service availability depends on the Client's jurisdiction, verification status, the Partner's requirements, and applicable law.

PaySolo is not a bank or deposit-taking institution and does not issue e-money, maintain Client payment balances, or provide custody of Client fiat currency or crypto-assets. Use of a Partner does not confer that Partner's license or authorization on PaySolo. Nothing in these Terms represents that PaySolo holds a financial-services license or eliminates any obligation imposed on PaySolo by applicable law.

1.3 Acceptance of the Terms

The Agreement enters into force when you sign up and expressly accept these Terms by selecting "I agree" or completing an equivalent affirmative acceptance step in the registration process. You must have access to the Terms before acceptance. A person accepting for a business confirms that they have authority to bind that business.

If you sign up before completing or passing KYC or KYB, these Terms apply immediately from your registration and acceptance, including the compliance, information, security, suspension, and termination provisions. Registration does not authorize transactions or guarantee approval. Required financial services remain unavailable until the necessary checks and Partner approvals have been completed.

If you sign up and complete or pass KYC or KYB, these Terms also apply from your registration and acceptance and continue after verification. Passing verification does not create a separate commencement date, exempt you from ongoing checks, or guarantee that every transaction will be accepted.

If verification is unsuccessful, refused, or left incomplete, PaySolo may reject onboarding, restrict access, or close the Account under Sections 6, 24, and 28. Obligations and rights that accrued while the Agreement was in force continue as provided in Section 28.3. PaySolo may retain an electronic record of the accepted version and acceptance time.

The applicable Tariff, risk disclosures, and Privacy Notice are made available through the System. Any Partner agreement required for a financial service must be presented through the relevant onboarding or transaction flow. Acceptance of these Terms does not by itself constitute acceptance of an undisclosed Partner agreement.

2. Definitions

The following terms have the meanings set out below.

3. Scope of Services

3.1 Access to Partner Services

The System may enable you to submit requests for fiat-to-crypto, crypto-to-fiat, or crypto-to-crypto conversion, or other transactions expressly displayed as available. Only the services offered by the relevant Partner, permitted in your jurisdiction, and approved for your Account are available. The Partner processes the financial transaction. PaySolo provides the software interface and related administrative coordination.

3.2 No Holding of Client Assets

PaySolo will not receive, hold, store, control, safeguard, or take custody of any Client fiat currency or crypto-assets. This prohibition includes temporary holding for execution, settlement, reversal, refund, safeguarding, or account closure. Client transaction assets do not pass through an account or wallet held or controlled by PaySolo.

Fiat payments are made directly between your external account and the relevant Partner's designated payment rails. Crypto-assets are sent or received using external wallets and the relevant Partner's designated infrastructure. PaySolo does not obtain your seed phrases, private keys, or authority to sign transactions from your external wallet.

3.3 Service Boundaries

Only the services expressly made available in the System and described in these Terms and the relevant Partner agreement may be used. Marketing material or a third-party description does not enlarge the services or create authority for PaySolo to hold Client assets.

3.4 Transaction Processing Role

PaySolo's transmission of a request, display of a Quote, or administrative confirmation does not mean that PaySolo takes possession of your assets or executes a financial transaction as principal. Transaction execution, acceptance, settlement, and any permitted refund are performed by the relevant Partner. Your request must satisfy the Partner's technical, compliance, and processing requirements.

4. Services Not Provided by PaySolo

PaySolo does not provide the following services in its own capacity:

• Custody, safekeeping, control of private keys, omnibus wallets, or holding of Client fiat currency or crypto-assets.

• Banking, deposit-taking, e-money issuance, Client payment balances, escrow, or collection accounts operated by PaySolo.

• Investment advice, portfolio management, investment recommendations, tax advice, accounting services, or legal advice.

• Credit, lending, margin, leverage, staking, interest, yield, derivatives, futures, options, or contracts for difference.

• Operation of a regulated market, order book, or peer-to-peer trading venue.

• Anonymous accounts, mixers, tumblers, or services intended to conceal ownership or evade screening.

• Services involving unsupported, restricted, or prohibited assets, networks, persons, or jurisdictions.

Any financial or payment service available through the interface is provided by the identified Partner under the relevant agreement. The interface is not a trading venue or a PaySolo custodial account.

5. Supported Assets and Asset Classification

5.1 Supported Asset Register

Only asset and network pairs displayed as available in the System may be used. The register identifies the asset, network, relevant Partner service, and applicable restrictions. Listing does not mean that PaySolo holds the asset, guarantees its value, or guarantees continued Partner availability. Annex 1 explains the register.

5.2 Stablecoins and Referenced Tokens

Stablecoins and other tokens referencing fiat currency or assets may be subject to issuer, redemption, reserve, and jurisdictional restrictions. Neither continued support nor maintenance of a reference price is guaranteed. PaySolo or the relevant Partner may restrict support because of applicable law, issuer status, market conditions, or compliance risk.

5.3 Privacy Coins and Anonymity-Enhanced Crypto-Assets

The System does not support Privacy Coins or transactions using features that materially obstruct identification, sanctions screening, or transaction monitoring. This applies to wrapped, bridged, or other representations of prohibited assets. Monero (XMR), Zcash (ZEC), Dash (DASH), and Xelis (XEL) are excluded under the platform's asset policy.

Optional mixing, shielding, or other concealment features on otherwise supported assets may also be prohibited. If Litecoin is displayed as supported, its MimbleWimble Extension Block (MWEB) feature must not be used for a transaction through the System. Prohibited or unsupported transfers may be rejected or restricted by the receiving Partner and may be unrecoverable. PaySolo has no custody of such assets. Responsibility for loss is assessed under Section 25.

5.4 Listing and Delisting

PaySolo or a Partner may restrict or remove an asset or network for legal, sanctions, AML/CFT, fraud, liquidity, cybersecurity, or operational reasons. PaySolo will notify affected Clients of material changes in accordance with Section 27, with reasonable prior notice where possible. Assets held in external wallets remain outside PaySolo's control; any pending Partner transaction is handled under the applicable Partner process.

6. Eligibility, KYC/KYB and First-Party Rule

6.1 Eligibility

Individuals must be at least 18 years old and have full legal capacity. Business Clients must be duly formed and represented by an authorized person. You must be eligible under applicable law and the relevant Partner's jurisdictional and compliance requirements. Account registration and acceptance of these Terms remain subject to approval for each service.

6.2 Restricted Jurisdictions

Availability is determined by the current country and service restrictions displayed through the System and by the relevant Partner's eligibility rules. Persons, entities, or transactions subject to applicable sanctions or other legal prohibitions may not use the services. PaySolo and Partners may apply additional risk-based restrictions or enhanced checks.

You must provide accurate residence, business location, incorporation, and beneficial ownership information. You must not conceal your location, misrepresent a material jurisdictional connection, or bypass restrictions. Country coverage may change and does not itself guarantee approval.

6.3 Customer Due Diligence and Partner Verification

KYC, KYB, AML/CFT screening, transaction monitoring, and related due diligence may be performed, subcontracted, or delegated to Contracted Partners to the extent permitted by applicable law. These measures help prevent financial crime and protect the integrity of the financial system. PaySolo may collect and transmit information needed for the checks and may request further information itself.

Each Partner applies the checks required for its service. PaySolo remains responsible for any compliance, oversight, data handling, or other duty that applicable law imposes on PaySolo; subcontracting does not remove those duties. Verification is ongoing and may be repeated after approval or when documents expire or circumstances change.

• Government-issued identity documents and any required selfie, liveness, or other identity verification.

• Proof of address and accurate contact and tax residency information.

• Source of funds and source of wealth evidence where required by the risk assessment.

• For businesses, formation documents, register extracts, ownership information, beneficial owner declarations, director identification, and evidence of authority.

• Evidence of ownership or control of external accounts and wallets.

• Transaction purpose and other information reasonably required for AML/CFT, sanctions, fraud prevention, or applicable transfer information requirements.

6.4 Accepted Identification Documents

Accepted identification documents and residual validity requirements depend on the relevant verification process, jurisdiction, and Partner. Documents must be original, unaltered, valid, fully legible, and issued by a competent authority. You must provide them through the designated secure process and complete any required liveness or authenticity checks.

PaySolo or a Partner may request additional documents, reject documents that cannot be authenticated, and require re-verification. You must provide updated documents when an identification document expires, is replaced, is lost, or when requested during the relationship.

6.5 First-Party Rule

Unless expressly approved in the applicable Partner service and permitted by law, transactions must use external accounts and wallets belonging to or controlled by the verified Client. Names, ownership, and beneficiary information must be consistent with the approved transaction purpose. An exception does not authorize PaySolo to hold Client or third-party assets.

6.6 Prohibition of Third-Party Use

You must not use the Account to pool, collect, or forward assets for undisclosed third parties, act as an unapproved intermediary, or allow another person to use your identity. A Partner service permitting supplier payments, invoice collections, or another approved business use may be used only within its disclosed scope and verification requirements.

6.7 Consequences of Non-Compliance

Missing, false, misleading, outdated, or incomplete information, refusal to cooperate, or failure to pass required checks may result in rejected onboarding, delayed or refused requests, restricted access, or Account closure. PaySolo may terminate access at any time for an AML/CFT breach under Section 28. A Partner may independently restrict a transaction or assets within its control where lawful. PaySolo does not freeze or hold assets itself.

7. Client Categorisation and Non-Discriminatory Commercial Policy

7.1 Categorisation

Clients may be categorized as individuals acting for personal purposes, freelancers or sole traders, business entities, or institutional businesses. Categorization depends on actual use, formation or registration where relevant, and the Partner service. You must keep this information current; material changes may require review or a different service approval.

7.2 Non-Discriminatory Commercial Policy

Access, transaction limits, pricing, and availability are determined by objective criteria, including Client type, verification status, risk rating, jurisdiction, sanctions exposure, source of funds, transaction size, Partner availability, network availability, and operational capacity.

Distinctions between Clients must have an objective basis consistent with applicable law, compliance requirements, or defined commercial criteria. Categorization does not remove mandatory consumer or other legal protections.

8. System Access, Operating Hours and Service Availability

8.1 System Access

The System may be accessible continuously, while transaction submission, review, execution, settlement, or refunds may depend on Partner operating hours, banking cut-off times, Business Days, network availability, screening, maintenance, and market conditions. Access to the System is not a guarantee of immediate transaction processing.

8.2 Service Availability

PaySolo may temporarily restrict the System or a service for maintenance, security, compliance, or operational reasons. PaySolo will use reasonable efforts to notify Clients of planned maintenance or prolonged restrictions where permitted and practicable.

8.3 No Guarantee of Uninterrupted Service

The System and Partner services may experience interruption or delay. PaySolo does not guarantee uninterrupted availability. Responsibility for a failure depends on its cause and the conduct of PaySolo, the Client, or the relevant Partner under Section 25.

9. Conversion Requests, Quotes, Finality and Cancellation

9.1 Quote

The System will identify whether a displayed Quote is firm for a stated period or indicative and subject to a disclosed pricing method. The Quote, relevant Partner, asset pair, network, fees, and applicable processing conditions must be reviewed before you confirm a request.

9.2 Firm Quote Processing

A confirmed request is submitted to the relevant Partner for processing under the disclosed conditions. Processing may depend on:

• Confirmation before the Quote expires and satisfaction of any stated Quote conditions.

• Availability of the required funds or crypto-assets in the designated external account or wallet or with the processing Partner.

• Completion of KYC/KYB and any further compliance, sanctions, fraud, or transfer information checks.

• Partner acceptance, liquidity, banking and network availability, and correct payment or transfer information.

If the request cannot be completed on the accepted terms, it may be rejected, canceled before execution, or re-quoted by the Partner. A changed Quote requires confirmation where applicable. Any return of assets is processed directly by the relevant Partner, subject to law and the actual transaction stage; PaySolo does not receive or hold a refund.

9.3 Finality of Conversion Request

A request becomes final for processing when you confirm it and the relevant Partner accepts it under the displayed process. An acknowledgment by the System alone does not establish execution or settlement. The System may show a request as pending, under review, accepted, processing, completed, failed, or rejected according to information received from the Partner.

Cancellation or amendment after Partner acceptance is available only if the processing stage, Partner rules, and applicable law permit it. A completed blockchain transaction cannot be reversed by PaySolo. PaySolo may help communicate a correction or recovery request but cannot guarantee cancellation, recovery, or refund.

9.4 Refusal or Reversal of Conversion Requests

PaySolo may refuse to transmit or continue coordinating a request, and a Partner may refuse, delay, restrict, or cancel processing, for legal, sanctions, AML/CFT, fraud, security, transfer information, liquidity, or technical reasons. A correction, reversal, or refund may occur only where legally and technically possible. No clause authorizes PaySolo to reverse a settled blockchain transfer or hold Client assets.

10. Pricing, Spreads, Fees and Transparency

10.1 Information Provided Before Order Confirmation

Before confirmation, the System will display the applicable asset pair and network, amount, price or pricing method, PaySolo fee, disclosed spread or margin, known Partner and network fees, expected receipt amount, Quote expiry, settlement method, and whether the Quote is firm or indicative. Unknown external charges or estimates must be identified as such.

10.2 Tariff

The applicable Tariff is made available through the System and forms part of the Agreement. Partner charges remain subject to the relevant Partner agreement and transaction disclosure. PaySolo charges no fee for custody or safeguarding of Client assets because it does not provide those services. Annex 2 summarizes fee disclosures.

10.3 Amendment of Fees

Changes to PaySolo fees are notified under Section 27. Charges for new requests are disclosed before confirmation. Changes do not retrospectively alter a previously agreed PaySolo fee for a confirmed transaction unless required by law or expressly agreed. Partner or variable network charges may change under their disclosed conditions.

10.4 Transparency of Pricing

The System explains the applicable pricing method and any disclosed spread or margin. Prices may differ from those offered elsewhere because of Partner pricing, liquidity, market conditions, or disclosed fees. Display of a price does not guarantee investment returns or establish PaySolo as the custodian of the transaction assets.

11. Custody and Administration of Crypto-Assets

11.1 No Custody Service

PaySolo does not provide custody or administration of Client assets and does not hold fiat currency, crypto-assets, or means of access to your crypto-assets. These Terms do not constitute a custody agreement with PaySolo.

11.2 External Wallets and Partner Agreements

You use external accounts or wallets in the approved transaction flow. The relevant Partner's terms govern any account, transaction balance, processing address, or custody service that Partner provides. PaySolo does not control or sign from your external wallet.

11.3 No Holding or Reuse of Client Assets

PaySolo does not pool, lend, pledge, invest, stake, reuse, or otherwise deploy Client assets. It has no authority under these Terms to transfer assets from your external wallet independently of your own authorization in the relevant transaction process.

11.4 Liability for Established Fault

Any loss is assessed according to the documented or otherwise established cause and each party's conduct under Section 25. The absence of custody does not exempt PaySolo from liability for its own proven fault or breach.

11.5 Third-Party Arrangements

A Partner providing transaction processing or custody acts under its own agreement and applicable obligations. It is not a sub-custodian of PaySolo under these Terms because PaySolo does not take custody of Client assets. PaySolo remains responsible for its own conduct and any duties imposed by law.

12. Master Wallet, Client Sub-Wallets and Position Register

12.1 No PaySolo Client Wallet Structure

PaySolo does not operate a master Client wallet, Client sub-wallets, or an omnibus account holding Client assets. Any wallet address displayed for a Partner transaction is supplied or designated under that Partner's service and does not establish PaySolo ownership or control of it.

12.2 Administrative Transaction Records

The System may record instructions, references, transaction status, external wallet identifiers, and information received from Partners. These are administrative records and do not represent assets held by PaySolo or an entitlement to a PaySolo custodial balance.

12.3 External and Partner Information

Any external or Partner balance displayed in the interface identifies its source and may be subject to reporting delay. A displayed figure is not a balance held by PaySolo. You should verify actual receipt, settlement, and external balances using the relevant account, Partner confirmation, or blockchain record.

12.4 Statements and Access

Available transaction history and confirmations may be accessed through the System or requested from support@paysolo.io. Information is provided in electronic form, subject to lawful verification and retention requirements. PaySolo does not issue statements of assets in its custody.

13. Safeguarding of Client Funds

13.1 No Fiat Holding or Safeguarding by PaySolo

PaySolo does not receive, hold, safeguard, or maintain Client fiat funds, including during transaction processing. You must not send transaction funds to an account held or controlled by PaySolo. Use only the payment details supplied for the relevant Partner transaction.

13.2 Partner Payment Rails and Settlement

Fiat payment rails, account details, settlement, and any permitted refund are supplied and processed by the relevant Partner. The Partner determines available currencies, methods, cut-off times, and eligibility. PaySolo may display information or coordinate requests without taking possession of the funds.

13.3 No Deposits with PaySolo

An Account on the System is not a deposit with PaySolo and has no deposit insurance through PaySolo. Crypto-assets are not FDIC-insured deposits. Any protection for fiat held by a Partner or its banking institution depends on that institution, the account arrangement, and the applicable scheme; consult the relevant Partner disclosures.

13.4 Payment Services by Third Parties

If a Partner offers payment accounts, account identifiers, bank transfers, or card-related services, its role and applicable terms must be disclosed in the relevant flow. Availability of a feature through the interface does not mean that PaySolo operates the payment service or holds the associated funds.

14. Transaction Instructions and Verified External Wallets

14.1 Partner Transaction Funding

Fiat payments must use an approved external account and the relevant Partner's instructions. Crypto-assets must use the exact supported asset, network, address, and any memo or tag designated for that request. These are payments or transfers for a Partner transaction, not deposits with PaySolo.

14.2 Verified External Wallets

You may be required to establish ownership or control of an external wallet through permitted evidence, such as a signed message, account information, or another disclosed verification method. You must never disclose your seed phrase or private key. Verification may be performed by PaySolo or a Partner and does not give PaySolo control of your wallet.

A one-active-wallet rule per asset or network may apply if disclosed in the System or Partner process. Changes to an approved wallet may require renewed checks, enhanced review, or a security delay.

14.3 Settlement and Refund Conditions

Partner settlement, transfers, and refunds are subject to screening, transfer information requirements, network availability, banking cut-off times, and disclosed limits. Additional verification may be required for larger or higher-risk transactions. PaySolo cannot release assets that it does not hold.

14.4 Wrong-Address and Wrong-Network Transfers

You must check recipient details, addresses, networks, memos, tags, amounts, and transaction purpose before authorizing a transfer. Errors in information you supply may cause permanent loss. Responsibility for an error introduced by PaySolo, a Partner, or the Client is determined under Section 25; it is not automatically assigned to the Client solely because a transfer is irreversible.

14.5 Approved Wallets and Destinations

Use only destinations permitted by the approved service and verification process. Unverified, unsupported, sanctioned, anonymous, or otherwise prohibited destinations may be refused. PaySolo may restrict the interface or refer a request for Partner review; only the party controlling the assets can apply a lawful asset restriction or process a transfer.

15. Travel Rule and Data Transmission

Where applicable transfer information or Travel Rule requirements apply, PaySolo and the relevant Partner may collect, verify, retain, and transmit originator and beneficiary information for the relevant transaction. You must provide accurate and complete information and respond promptly to lawful requests for clarification.

• Information may be shared with the processing Partner, counterparty providers, screening or transfer information providers, and competent authorities where necessary and lawful.

• Missing, inaccurate, incomplete, or inconsistent information may cause rejection, delay, further verification, or a lawful restriction by the processing Partner.

• External self-hosted wallets, higher-risk jurisdictions, or counterparty providers may require enhanced checks.

These controls do not authorize PaySolo to hold Client assets. Data sharing remains subject to Section 29 and the Privacy Notice.

16. Use of Contracted Partners and Outsourcing

16.1 Contracted Partners

PaySolo may use Contracted Partners for financial transaction processing, payment rails, conversion, KYC/KYB, AML/CFT screening, monitoring, sanctions checks, technology, and infrastructure. The relevant financial service provider must be identified in the applicable flow. Partner service agreements, operating rules, and approval requirements apply to their services.

16.2 Regulatory Responsibility

PaySolo is responsible for its own platform, communications, data handling, integration work, and any selection, oversight, or compliance duty applicable to PaySolo. A Partner is responsible for its own services, processing, controls, acts, and omissions under its agreement and applicable law. A Client is responsible for their own conduct and obligations.

The use of a Partner does not excuse PaySolo's own fault or a duty that cannot legally be delegated. These Terms do not bind a Partner that is not a party to them or replace your agreement with that Partner. Section 25 governs responsibility under the Agreement.

16.3 Subcontracted Compliance and Asset Flows

KYC, KYB, AML/CFT checks, and transaction monitoring may be subcontracted to a Partner where lawful. You may receive verification requests from the identified Partner through its official process. PaySolo communications must still come through the channels stated in Section 23.

Transaction assets go directly through your external accounts or wallets and the relevant Partner. PaySolo does not pre-fund Partner transactions using Client assets, act as their custodian, or receive assets for onward transfer.

17. Forks, Airdrops, Network Events and Delisting

Forks, chain splits, migrations, airdrops, snapshots, rebases, and other network events may affect Partner support and transaction processing. Support is determined by the relevant technical, legal, and operational requirements. PaySolo does not hold assets for a snapshot or allocate forked or airdropped assets from a Client wallet. Rights concerning assets in an external wallet or with a Partner depend on that wallet, network, or Partner arrangement.

17.1 Delisting

If an asset or network is removed, PaySolo will use reasonable efforts to notify affected Clients in advance where possible. New requests may become unavailable. Pending requests are handled by the processing Partner, and external assets remain outside PaySolo's custody. Material changes are notified under Section 27.

18. Risk Disclosure

Crypto-assets are high-risk assets. Use a service only if you understand its nature and risks and can bear the resulting loss. Assets may lose part or all of their value, transactions may be delayed or impossible, and incorrect or fraudulent transfers may be unrecoverable. Reading and accepting these Terms does not waive a claim arising from proven fault.

18.1 Risk Categories

Annex 3 summarizes these risks. The allocation of responsibility for a loss remains subject to Section 25 and applicable law.

19. Prohibited Use and Market Abuse

You must not use the System or a Partner service for unlawful activity or in a way that compromises the integrity of the financial system, including:

• Money laundering, terrorist or proliferation financing, sanctions evasion, or concealment of beneficial ownership.

• Fraud, deception, scams, ransomware proceeds, identity misuse, or false verification information.

• Market manipulation, wash trading, spoofing, insider dealing, or unlawful disclosure of inside information.

• Darknet activity, unlawful or unlicensed gambling, pyramid schemes, or Ponzi schemes.

• Mixers, tumblers, or transaction sequences intended to conceal illicit origin, destination, or ownership.

• Prohibited assets or privacy features described in Section 5 and Annex 5.

• Unapproved third-party use, bypassing restrictions, interference with the System, or infringement of others' rights.

19.1 Detection and Reporting

PaySolo and Partners may monitor Account and transaction information for AML/CFT, sanctions, fraud prevention, and financial integrity purposes. Monitoring and checks may be performed by Partners. Suspected or established breaches may lead to refusal of requests, immediate suspension or termination, further investigation, or reporting where required or permitted by law.

Asset restrictions are applied by the Partner or authority with legal power and control over the assets. PaySolo may be prohibited from disclosing a report or investigation and will comply with any applicable non-disclosure or tipping-off prohibition.

20. Conflicts of Interest

PaySolo takes reasonable steps to identify, manage, and disclose material conflicts affecting its platform services. Conflicts may arise from fees, spreads, Partner arrangements, group relationships, referrals, incentives, or access to transaction information. A material conflict that cannot be adequately managed will be disclosed to the affected Client before the relevant service where required. Disclosed commercial incentives do not excuse PaySolo's own misconduct or breach.

21. Statements, Records and Confirmations

21.1 Order Confirmations

The System may provide a request acknowledgment and subsequent confirmation using information received from the relevant Partner. A completion confirmation identifies the available transaction reference, asset pair, amounts, fees, and processing or settlement information. An acknowledgment or estimated status is not proof of final settlement.

21.2 Statements

You may view available request and transaction history through the System. Partner statements and external account or wallet records remain the authoritative records of assets held outside PaySolo. Any reporting discrepancy should be raised promptly with support@paysolo.io and the relevant Partner where appropriate.

21.3 Record Retention

PaySolo retains acceptance records, requests, transaction information, communications, verification information, and security records for the periods required by applicable law and legitimate record retention needs described in the Privacy Notice. Partners retain their own records under their applicable requirements. Account closure does not require deletion of records that must lawfully be retained. PaySolo has no Client custody ledger or Client private-key records.

22. Complaints Handling

22.1 Submission

You may complain free of charge to support@paysolo.io, through the System, or by post to PaySolo's mailing address in Section 1.1. You may use Annex 4, but use of the form is not mandatory. Include the relevant reference, events, supporting information, and outcome sought. Do not send passwords, seed phrases, private keys, or full authentication codes.

22.2 Handling

PaySolo will acknowledge the complaint, investigate matters within its responsibility fairly and in a timely manner, keep a record, and communicate an outcome within a reasonable period and any mandatory deadline. If more time is needed, PaySolo will explain the delay and expected response period where permitted.

If the complaint concerns a Partner service, PaySolo may help direct it to the relevant Partner and coordinate information with appropriate safeguards. Referral does not remove PaySolo's duty to investigate its own conduct or any responsibility imposed by law.

22.3 External Remedies

The complaints process does not prevent you from contacting a competent authority, using available statutory remedies, or bringing a claim in a court with jurisdiction. No mandatory right is waived by making a complaint.

23. Security and Shared Responsibility

23.1 The Shared Responsibility Model

PaySolo is responsible for the security and operation of the systems within its control and for fulfilling its own contractual and legal duties. You are responsible for securing your devices, passwords, external wallets, email account, and authentication factors. A Partner is responsible for security within its own service and obligations. Responsibility for a resulting loss depends on documented or otherwise established fault and causation under Section 25.

23.2 PaySolo Security Responsibilities

PaySolo will maintain reasonable technical and organizational measures for the System and Client data, including appropriate access controls, secure communications, authentication measures, logging, monitoring, and incident response. PaySolo does not manage your external wallet keys. A failure in your device security does not excuse an independent breach by PaySolo that caused or contributed to the loss.

23.3 Client Security Responsibilities

You must take reasonable steps to protect your Account and external assets, including:

• Use a strong, unique password and protect it with a reputable password manager if appropriate.

• Keep passwords, authentication codes, recovery codes, seed phrases, and private keys confidential and out of unprotected storage.

• Enable and maintain the multi-factor authentication required by the service and protect the device or hardware key used for it.

• Secure your associated email account and its recovery methods.

• Keep devices updated, protected against malware, and locked against unauthorized access.

• Check the website address before entering credentials and use the official paysolo.io domain or its expressly identified official subdomains.

• Do not approve an authentication prompt, sign a wallet message, or confirm a transaction you did not initiate or understand.

• Maintain current contact details and check transaction information before authorization.

23.4 Verified Communications from PaySolo

All emails purporting to come from PaySolo must originate from an address ending exactly in @paysolo.io. Verify the complete sender address, not just the display name. Treat look-alike domains, changed reply-to addresses, or unexpected requests as suspicious. A visible @paysolo.io address alone is not conclusive proof of authenticity because sender information can be spoofed; confirm a suspicious message through the System or support@paysolo.io using contact details obtained independently.

PaySolo's official Client communications are emails from @paysolo.io addresses and messages within the System. A message, call, social media contact, or SMS claiming to be PaySolo must be independently verified through an official channel. A genuine Partner may use its own separately disclosed domain for its own verification or service process; it must not be treated as a PaySolo email.

PaySolo never asks you to disclose a password, full authentication code, seed phrase, recovery phrase, or private key, or to grant remote access to your device. Report any such request immediately.

23.5 Notification Obligation — "At the Time of Discovery"

Notify support@paysolo.io without delay when you discover or reasonably suspect Account compromise, unauthorized access, phishing, loss of an authentication device, credential disclosure, an unexpected security alert, or an unauthorized transaction. Use the System as well if you can still access it. Do not wait for complete proof before reporting a suspected incident.

PaySolo may restrict Account access, block sessions, reset access credentials through a verified process, and contact a Partner to request appropriate action. Only the relevant Partner or wallet controller can stop a pending financial transaction or restrict assets within its control. Prompt reporting may reduce loss but does not guarantee recovery.

23.6 Consequences of Failure to Comply

You are responsible for a loss to the extent it is caused by your own breach, negligent conduct, or misuse of your device, credentials, wallet, or Account. PaySolo remains responsible to the extent its own documented or otherwise established fault caused or contributed to that loss. A Partner's responsibility is assessed under its agreement and applicable law. Assistance with an investigation does not itself establish or waive liability.

24. Suspension, Blocking and Refusal of Transactions

PaySolo may immediately suspend, restrict, block, or close access to an Account or stop transmitting a request where required or reasonably justified by law, a competent authority, sanctions, an AML/CFT breach or risk, suspected fraud, false information, a security incident, Partner requirements, or a material breach of these Terms. These powers apply before and after KYC/KYB approval. PaySolo does not hold or freeze Client assets; a Partner may apply a lawful restriction to a transaction or assets within its control.

A restriction will be reviewed and maintained only while its legal or reasonable risk basis continues. Immediate termination for an AML/CFT breach is available under Section 28.2. A registration or previous approval does not prevent later restriction.

24.1 Notification

PaySolo will notify you of an Account restriction and available next steps where lawful and reasonably practicable. Reasons, timing, or details may be withheld where disclosure is prohibited, would compromise security, or would breach applicable reporting or tipping-off restrictions. A restriction does not retrospectively erase an existing claim or accrued obligation.

25. Liability and Allocation of Responsibility

25.1 PaySolo Responsibility for Its Own Fault

PaySolo is liable to the extent a loss is caused by PaySolo's documented or otherwise established fault, negligence, misconduct, failure to perform its obligations, or breach of applicable law. Relevant conduct includes PaySolo's own platform operations, communications, integration, data handling, security measures, and any Partner selection or oversight duty that applies to PaySolo.

Fault, causation, and loss may be established by transaction records, system logs, correspondence, incident findings, other reliable evidence, or a determination by a competent authority or court. The Client does not need PaySolo's admission of fault or a particular document as a condition for submitting a claim. PaySolo will reasonably cooperate with investigation of evidence within its control, subject to legal confidentiality obligations.

25.2 Client Responsibility

The Client is responsible to the extent a loss is caused by the Client's own acts, omissions, breach, negligence, false information, unlawful activity, unauthorized third-party use, or failure to secure devices, credentials, or external wallets. The Client is responsible for instructions they supply, including wrong recipient details, addresses, networks, memos, or amounts. This allocation does not excuse separate fault by PaySolo or a Partner.

25.3 Partner Responsibility

Responsibility for a Partner's financial services, processing, security, compliance controls, or other acts and omissions lies with that Partner under its own agreement and applicable law. PaySolo is not automatically liable for an independent Partner failure solely because the service is accessed through the System.

PaySolo remains liable for its own established fault relating to a Partner, including a breach of an applicable selection, oversight, integration, or compliance duty. Nothing in these Terms excludes responsibility that applicable law assigns to PaySolo for outsourced activity. These Terms do not impose an obligation on a Partner that has not agreed to them.

25.4 Shared Causes and Evidence

If a loss has more than one cause, each party's responsibility is determined according to its contribution and applicable law. Location of an incident on a device or system does not alone conclusively establish fault. A Client's security lapse does not remove PaySolo's responsibility for its own contribution, and a Partner failure does not remove PaySolo's responsibility for its own breach.

25.5 No Contractual Liability Cap

These Terms impose no contractual monetary cap on PaySolo's liability. The recoverable loss and remedies are determined by established fault, causation, the Agreement, and applicable law. Nothing excludes fraud, willful misconduct, or any other liability or consumer right that cannot lawfully be excluded or transferred to another party. An external event is assessed by its actual cause and does not excuse a party's own established fault.

26. Force Majeure and Operational Resilience

War, civil unrest, natural events, government action, major infrastructure failures, network outages, or other events outside a party's reasonable control may affect performance. The affected party must take reasonable steps to mitigate the effect, resume performance, and provide notice where permitted and practicable. PaySolo may coordinate with the relevant Partner and provide available status information. This Section creates no liability cap or blanket exemption from liability for fault, failure to take required precautions, or a breach of a mandatory duty. Liability remains governed by Section 25.

27. Amendments to Terms and Tariff

PaySolo may amend these Terms or its Tariff. You will be notified of changes by email from an @paysolo.io address or by a notice directed to your Account within the System. The notice will identify the changes or provide access to the revised document, state the effective date, and explain any action required. Publishing a revised document on the website alone does not replace the Client notification required by this Section.

Material changes that adversely affect Clients will normally take effect after at least 15 calendar days' prior notice, or any longer period required by applicable law. If you disagree, you may terminate before the change takes effect. Pending transactions and any Partner-held assets remain subject to their existing processing conditions and applicable law.

Changes may take immediate effect where reasonably necessary for law, a competent authority, sanctions, urgent AML/CFT or security risk, a required Partner change, or urgent network or operational circumstances. PaySolo will notify you as soon as legally permitted and reasonably practicable, stating the effective date. Immediate changes do not authorize retrospective removal of accrued rights or a new liability cap.

Continued use after the notified effective date constitutes acceptance to the extent permitted by applicable law. Where affirmative acceptance is required, PaySolo will obtain it before applying the change. If you do not agree, stop using the affected service and request Account closure. Records of accepted versions may be retained.

28. Termination and Account Closure

28.1 Termination by Client

You may terminate the Agreement at any time by written notice to support@paysolo.io or through the Account closure process. PaySolo holds no Client assets to withdraw or return on closure. Pending transactions or a relationship with a Partner must be resolved under the relevant Partner process. Closing the PaySolo Account does not automatically close an external account or Partner agreement.

28.2 Termination by Paysolo

PaySolo may terminate the Agreement on at least 30 calendar days' notice in ordinary circumstances. PaySolo may suspend or terminate the Account and access to services at any time with immediate effect if an AML/CFT breach is identified or reasonably suspected, or where required or justified by sanctions, a competent authority, material breach, fraud, false verification information, refusal to complete required checks, a serious security risk, or other unlawful use.

This right applies to Clients who have registered but have not passed KYC/KYB and to Clients who have already passed those checks. No prior notice is required where immediate action is needed or notice is prohibited by law. PaySolo will provide notice of the action where lawful and reasonably practicable. Partners may independently reject, restrict, or terminate their own services under their agreements.

28.3 Effects of Termination

Termination ends access to the System and new transaction requests. It does not extinguish accrued rights, lawful fees, complaints, responsibility for prior conduct, or record retention duties. PaySolo may assist with contacting a Partner about a pending request, but any settlement or refund is made directly by that Partner and PaySolo does not take possession of assets.

Provisions concerning liability, prior transactions, confidentiality, record retention, complaints, and dispute resolution survive to the extent needed to give effect to their purpose and applicable law. Immediate closure for an AML/CFT breach does not waive a Client's existing legal claim against PaySolo.

29. Data Protection and Confidentiality

PaySolo processes Client information to administer registration and access, coordinate Partner services, perform or support lawful verification and monitoring, prevent fraud, secure the System, meet legal obligations, and establish or defend claims. KYC/KYB, screening, and monitoring information may be collected or handled by Partners. The Privacy Notice describes PaySolo's role, purposes, applicable legal bases, recipients, transfers, retention, and rights available under applicable data protection law.

Information may be shared with the relevant Partner to perform KYC/KYB, AML/CFT screening, transaction monitoring, transfer information checks, or processing, subject to applicable law and appropriate safeguards. A Partner may act as an independent controller or processor according to its actual role and privacy terms. Subcontracting does not remove PaySolo's own data protection obligations.

29.1 Confidentiality

PaySolo treats Client information as confidential and discloses it only as necessary and lawful for the service, compliance, security, authorized Partner functions, or requests from competent authorities. Appropriate confidentiality and security safeguards apply. You may contact support@paysolo.io about your information or rights under the Privacy Notice.

30. Governing Law, Jurisdiction and Language

30.1 Governing Law

These Terms and the Agreement are governed by the laws of the State of Wyoming and applicable United States federal law. This choice does not deprive a Client of mandatory protections or rights that apply under the law of a jurisdiction that cannot lawfully be excluded by agreement.

30.2 Jurisdiction

Disputes under this Agreement may be brought before the competent state or federal courts in Wyoming, subject to any mandatory jurisdiction or consumer rights under applicable law. These Terms contain no mandatory arbitration provision.

30.3 Hierarchy of Documents

These Terms govern PaySolo's relationship with the Client. The disclosed Tariff governs applicable PaySolo charges, and the Privacy Notice describes data processing without reducing these contractual obligations. A Partner agreement governs the relevant Partner service and does not make PaySolo the holder of Client assets or eliminate its own responsibility. Mandatory law prevails over an inconsistent contractual provision.

30.4 Language

These Terms are issued in English. Account and contractual communications from PaySolo will be in English unless another language is expressly agreed.

Annex 1 — Supported Asset Register

Only the current asset and network pairs expressly shown as available for the relevant Partner service in the System are supported. An entry does not establish custody by PaySolo. Availability is subject to Sections 5 and 6 and may differ by jurisdiction and verification status.

Do not assume that an asset is supported merely because it appeared in an earlier version of a register or document. Check the current service flow before sending assets.

Annex 2 — Tariff and Fee Schedule

The current Tariff and transaction disclosure identify charges before confirmation. No fixed fee amounts are established in this Annex. No PaySolo custody or safeguarding fee applies.

Changes are notified under Section 27. This Tariff contains no aggregate liability cap or other monetary limit on PaySolo's liability; Section 25 applies.

Annex 3 — Risk Disclosure Summary

• Crypto-assets may lose their entire value.

• A stablecoin may lose its peg or become unavailable for redemption.

• Completed blockchain transfers are generally irreversible.

• Wrong addresses, networks, tags, or unsupported assets may result in permanent loss.

• Partners, banks, infrastructure providers, or networks may fail or delay processing.

• Sanctions, AML/CFT, verification, and transfer information requirements may restrict transactions.

• Crypto-assets are not FDIC-insured deposits. Partner fiat protections depend on the actual arrangement.

• You must protect your devices, credentials, email, and external wallet keys and verify @paysolo.io communications.

• PaySolo does not hold Client fiat currency or crypto-assets. This does not remove liability for its own established fault.

This summary supplements Section 18 and does not waive rights under Section 25 or applicable law.

Annex 4 — Complaint Form

Use of this form is optional. Send it to support@paysolo.io or submit the information through the System. Complaints are free of charge. Do not include passwords, seed phrases, private keys, or full authentication codes.

PaySolo will consider its own role and, where appropriate, help identify the Partner responsible for the relevant service. See Section 22.

Annex 5 — Restricted and Prohibited Crypto-Assets

The System prohibits the assets and features described below. The policy applies to Partner transactions submitted through the System and does not mean that PaySolo receives or holds prohibited assets. Check the current supported asset and network information before any transfer.

A5.1 Prohibited Privacy Coins

Monero (XMR), Zcash (ZEC), Dash (DASH), and Xelis (XEL) are excluded under the platform's policy because their privacy or mixing features create screening and transaction transparency risks. This exclusion also applies to wrappers, bridges, and synthetic representations of those assets.

A5.2 Other Prohibited Categories

The following are also prohibited where they obstruct screening, breach applicable restrictions, or fall outside the approved service:

• Assets or transaction features designed to conceal senders, recipients, amounts, balances, or beneficial ownership.

• Assets or services that incorporate mixers, tumblers, or anonymizing transaction mechanisms.

• Assets associated with sanctioned persons, entities, addresses, or prohibited services under applicable sanctions.

• Assets identified as presenting fraud, malicious contract, or AML/CFT risk that cannot be adequately mitigated.

• Unsupported networks, tokens, derivatives, or representations of a prohibited asset.

A5.3 Optional Privacy Features on Supported Assets

Do not use a supported asset's optional mixing or privacy feature to obscure a transaction through the System. Do not use the service to conceal transaction history or beneficial ownership. If Litecoin is supported for the relevant service, MWEB transactions are prohibited. Material exposure to mixers or concealment services may trigger enhanced review, rejection, or a lawful Partner restriction.

A5.4 Consequences of Breach

A prohibited transfer may be rejected, delayed, lawfully restricted by the receiving Partner, reported where required, or become technically unrecoverable. Any permitted return is performed directly by the receiving Partner under its rules and applicable law. PaySolo does not take possession of such assets. Responsibility for loss remains governed by Section 25.

A breach may cause immediate Account suspension or termination, including for an AML/CFT breach. Material changes to this policy are notified under Section 27; urgent legal or security restrictions may take immediate effect as provided there.