Terms of Service

Flowbit Finance L.L.C-FZ Version 1.7 dated 20 October 2026 1. Parties and purpose of the Terms 1.1. These Terms govern the relationship between the user and Flowbit Finance L.L.C-FZ, registered in Meydan Free Zone, Dubai, U.A.E., registration number 2541754, with its address at Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, U.A.E. (the “Company”, “Flowbit”, “we” or “us”). 1.2. Flowbit is a technology service (the “Service”) operated by Flowbit Finance L.L.C-FZ. The Service comprises the website, app and Telegram interfaces. The Company provides access to the Service interfaces, arranges the processing of card issuance and top-up requests, coordinates with partners, displays transactions and provides user support. 1.3. Creating a Flowbit account does not mean opening a bank account. The Service does not provide a separate electronic or cryptocurrency wallet for the user: available balances are recorded against the relevant cards. Flowbit does not provide users with a cryptocurrency trading platform. 1.4. Flowbit does not itself issue cards or perform currency conversion or digital asset exchange. Card issuance, card transaction processing, payment acceptance and actual conversion are carried out by the relevant issuers, card partners, payment partners and cryptocurrency processors within their respective roles. 1.5. Flowbit remains responsible for its own services and obligations under these Terms. The allocation of functions between Flowbit and its partners does not limit the user’s rights under mandatory law. The roles of Flowbit and its partners are described in section 6. The terms and limitations of Flowbit’s liability are set out in section 26. 1.6. These Terms do not restrict the user’s rights under mandatory law and apply subject to the legislation governing the relevant service. 1.7. Available features are determined by the selected product and the terms on which it is activated. 2. Key definitions 2.1. Account means the user’s profile for accessing Flowbit. Creating an account does not, in itself, open a bank account in the user’s name. 2.2. Card programme means the arrangements for issuing, servicing and using a particular product involving the issuer, card provider, payment network and other participants. 2.3. Card provider means a partner providing the infrastructure for a card programme. The provider and the issuer may be different entities. 2.4. Issuer means the legal entity that issues a card under the relevant card programme. 2.5. Card balance means the amount recorded against a card under the programme rules. Available balance means the portion of the card balance available for supported transactions after applicable holds and restrictions. 2.6. Authorisation hold means the reservation of an amount in connection with a card transaction until final settlement or release under the programme rules. A hold is distinct from the deduction of a fee or a debt. 2.7. The user has no separate Flowbit wallet or balance that can be topped up: balances are recorded only against individual cards. A payment being processed is treated as a top-up request under sections 8–10. 2.8. Top-up means an agreed request to credit a specified amount to the selected card once the payment conditions and required checks have been satisfied. 2.9. Prefunding means Flowbit placing liquidity with a card partner before user requests are fulfilled. Master balance means Flowbit’s corporate settlement position with a partner, which is separate from card balances and the corporate reserve. 2.10. Settlement between partners means the discharge of obligations between infrastructure participants, which may take place separately from a card top-up. 2.11. Payment partner means a payment recipient, agent, acquirer, crypto payment processor or other participant in a particular top-up method. 2.12. Digital asset means a supported cryptocurrency or token. USD, USDT and the names of other assets are not interchangeable: the payment asset, unit of account and currency to be credited are specified separately. 2.13. Merchant means the person from whom the user makes a purchase. Dispute means a request concerning a card transaction. Chargeback means a dispute procedure under the rules of the relevant card programme and network; it does not guarantee a refund. 2.14. Tariffs mean the prices and fees for the selected product, provided before its activation or confirmation of a transaction. Transaction terms mean the amount, asset/currency, fee, exchange rate or calculation method, amount to be credited and material restrictions agreed before confirmation. 2.15. BIN sponsor means a card programme participant that enables the use of card infrastructure and issuer identifiers in the role assigned to it under the programme. It may be the issuer or a separate entity. The title of the role does not, in itself, determine who owes an obligation to the user in respect of a particular balance. 2.16. Mandatory law means the applicable requirements of legislation and competent authorities from which the parties may not derogate by agreement. Private rules of a provider or card network do not override such requirements. 3. Documents, consent and priority of terms 3.1. Before accepting the Terms, the user is given an opportunity to review the relevant version. Acceptance is recorded by an express action provided for in the interface, such as ticking a consent box and confirming registration. 3.2. Before ordering a card or confirming a transaction for which a charge applies, the user is provided with these Terms, the applicable tariffs and the material terms of the selected product or transaction. Acceptance of these Terms does not constitute the user’s acceptance of Flowbit’s commercial agreements with partners that have not been provided to the user. If the law requires separate consent or a separate document for a particular service, Flowbit ensures that it is provided and duly obtained or completed before that service is supplied. 3.3. Seeking assistance or requesting information does not, in itself, constitute consent to new fees, changes to a previously confirmed transaction or the activation of a paid service. 3.4. Mandatory law takes precedence. These Terms define Flowbit’s obligations. Additional product terms and the terms of other participants apply to the user within their respective scope if they have been properly brought to the user’s attention and, where required, accepted by the user. 3.5. A confirmed transaction is governed by the amount, fee, exchange rate or method for determining the exchange rate agreed by the user. A subsequent change to tariffs or information in the application does not, in itself, change the terms of that transaction. 3.6. In the event of a technical or arithmetic error, Flowbit provides an explanation and a calculation of the correction. A materially changed transaction requires renewed consent or resolution of the original request, except for corrections and the performance of obligations permitted by law. 4. Eligibility to use the Service 4.1. The Service is intended for adult users with full legal capacity who are at least 18 years old, or any higher age required for a particular service under applicable law. 4.2. The user acts in their own name and uses personal cards for their own lawful purposes unless expressly agreed otherwise for the product. Transferring an account, selling access, using another person’s details and circumventing restrictions through multiple accounts are prohibited. 4.3. Flowbit does not serve residents of the United Arab Emirates or the United States of America. Availability in other countries depends on the selected programme, the top-up method, applicable law and published restrictions, including clause 14.8. The user must provide accurate information about their residency and any material changes to it. 4.4. The user must not circumvent sanctions, territorial or other applicable restrictions. Flowbit and its partners may request information to verify compliance with the access requirements. 4.5. The user checks whether they are permitted to use a particular product under the requirements applicable to them and does not use the Service to circumvent those requirements. This does not release Flowbit from its own obligations to verify availability and provide accurate information. 5. Registration and checks 5.1. The user provides accurate information requested for the selected product and keeps it up to date. The scope of checks may vary by programme, country, transaction type and risk level. 5.2. Flowbit or the relevant partner may request evidence of identity, ownership of a payment instrument or wallet, source of funds, the purpose of a transaction and other information reasonably required. 5.3. Additional checks may be required before a card is issued, when making a top-up, restoring access, transferring a balance, making a refund or reviewing a disputed transaction. The absence of full KYC at one stage does not waive any subsequent checks that may be required. 5.4. If required information is missing or unverified, a transaction may be delayed or declined and access restricted. Any payment received and any balance are dealt with under sections 8–10 and 17–21; failure to provide information does not, in itself, extinguish rights to those amounts. 5.5. The user confirms the lawful origin of funds and digital assets, their right to dispose of them and the accuracy of the information provided. Using another person’s payment instrument or funds without a lawful basis is prohibited. Knowingly false information may result in refusal or restriction of service and other measures provided for by law; the treatment of any amounts received is determined separately. 6. Roles of Flowbit and its partners 6.1. Flowbit receives and handles user requests within the scope of the service provided, sets the commercial terms of its own services, arranges top-ups and interaction with partners, and provides transaction information and support. 6.2. The card provider performs the functions assigned to it under the programme and interacts with the issuer and other participants. The issuer, network and relevant participants determine authorisation, final settlement, restrictions and procedures within their respective areas of responsibility. 6.3. The payment partner receives and processes payments in its assigned role. Flowbit receives transaction information and may issue instructions for transfers and settlements within the authority granted to it. 6.4. The user contacts Flowbit support regarding transactions, restrictions and the card balance. Flowbit reviews the request, checks the available information and, where necessary, refers the matter to the relevant card programme participant. The procedure for resolving matters concerning the balance and the terms of Flowbit’s liability are set out in sections 20 and 26. 6.5. Flowbit does not guarantee that a card will be accepted by every merchant or that every purchase will be approved. Flowbit’s own measures to restrict the Service and the decision to authorise a purchase are separate actions. 6.6. If a partner is replaced, material changes are communicated before a new transaction. Previously accrued rights and obligations remain in force. 7. Prefunding and card balances 7.1. To top up cards, Flowbit may use funds placed in advance with a card partner in the master balance. Settlement with the payment partner may take place later and does not, in itself, alter Flowbit’s obligations under a top-up request for which payment has been made. 7.2. Prefunding does not constitute the provision of credit to the user under these Terms. Obligations in respect of a negative balance, where validly incurred, are considered separately under section 19. 7.3. Balances are recorded against individual cards. The available amount may differ from the total balance because of pending transactions, holds and adjustments. In the event of a discrepancy, Flowbit reconciles the records with programme participants and provides the outcome. 7.4. The user retains the right to fulfilment of a request for which payment has been made and to settlement of the balance due to them by the relevant obligated person. Prefunding and internal settlements do not, in themselves, turn these amounts into fees earned by Flowbit. The allocation of obligations between Flowbit and programme participants is determined by sections 6, 8, 20 and 26 and the applicable product documents. 7.5. The display of a card balance does not, in itself, establish deposit insurance or a bank guarantee. Flowbit does not provide its own insurance of the card balance or a guarantee of the performance of partners’ independent obligations. This does not negate Flowbit’s own obligations or protection under mandatory law. Questions concerning a balance and its settlement are handled through support under section 20. 8. Top-ups: general terms 8.1. Before making payment, the user receives the terms of the specific request: the product, payment amount and currency/asset, agreed amount to be credited, fee, exchange rate or calculation method, payment recipient and restrictions. 8.2. If the exchange rate or calculation is provisional, the conditions for its final determination and the validity period of the request are specified. If the amount needs to change after that period expires, the user receives a new calculation and an opportunity to confirm it or resolve the payment received under the applicable procedure. 8.3. Receipt of payment by the payment partner, the required checks and crediting the card are separate stages. A top-up is completed when the agreed amount has actually been credited to the selected card, as confirmed by the card partner’s records. A notice that payment has been received or a request accepted for processing does not, in itself, confirm completion of the top-up. 8.4. In the event of a technical failure, Flowbit checks the outcome of the previous attempt and, if necessary, repeats the request while preventing a duplicate credit. If payment for the request has already been duly accepted, a technical retry or delay in internal settlement does not require the user to pay again. 8.5. The user must follow the amount, payment details and other parameters of the specific request. Payments using incorrect details, an incorrect asset or network, underpayments, overpayments and payments made after the request expires require separate review. Whether they can be credited or refunded depends on the actual receipt of funds and the nature of the error. 8.6. If review confirms that a top-up for which payment has been made cannot be completed, Flowbit arranges a refund through the payment partner that received the payment. If the agreed completion period has expired, Flowbit checks the outcome of the request and arranges a refund or agrees continued processing with the user. Section 17 applies where a mandatory restriction on transfer is in place. 8.7. Instead of a refund, Flowbit may offer a top-up to another card or another means of fulfilment. Such a solution is implemented with the user’s consent after the amount, costs and other material terms have been agreed. Merely offering an alternative does not constitute fulfilment of the request. 8.8. Flowbit provides the user with the available information on the refund amount, currency or asset, method, costs and expected timescales. If the original refund method is unavailable, Flowbit examines possible alternatives and agrees an available solution with the user. Flowbit handles the request and communicates the confirmed outcome or the reason for the delay and the procedure for further consideration. Initiating a refund does not mean that the user has actually received the funds. 8.9. A delay in settlement between a partner and Flowbit does not, in itself, extinguish Flowbit’s own obligations under a request for which payment has been made. Completion of a top-up does not end Flowbit’s obligations to correct its own errors and review requests. The terms and limitations of liability are set out in section 26. 9. Cryptocurrency top-ups 9.1. Supported assets, networks, confirmation requirements, the address and, where necessary, a memo/tag are displayed in the specific request. The user checks these parameters before sending. 9.2. Cryptocurrency payments are accepted by crypto payment processors engaged by Flowbit using the details provided for the specific top-up request. 9.3. The crypto payment processor receives and records assets and carries out the stipulated transfers and settlements. Flowbit may issue instructions to it within the authority granted to Flowbit. 9.4. A confirmed blockchain transaction is generally irreversible. Where a right to a refund exists, the refund may be made by a separate transfer, subject to technical feasibility, verification of the details and mandatory restrictions. 9.5. Use of an unsupported network or asset, or incorrect details, may result in delay or loss. Flowbit examines the available means of checking and recovery; recovery is not guaranteed. If the error relates to incorrect information provided by Flowbit or its partner, liability is determined by the cause and applicable law. 9.6. A payment may be delayed as a result of source-of-funds, sanctions or risk checks, or provider requirements. The documents required and the actions permitted are communicated to the extent disclosure is allowed. A check does not, in itself, mean that the user has committed a violation. 9.7. A refund for an unfulfilled top-up is made through the crypto payment processor under section 8. The original sending address may belong to an exchange or a pooled wallet and may be unsuitable for refunding the user. The details are verified before transfer; if the original route is unavailable, another address is agreed after verifying ownership and compliance with mandatory requirements. 9.8. Digital assets involve risks of changes in value, a stablecoin losing its currency peg, insufficient liquidity, network delays, changes in network fees and protocol errors. Support for an asset as a top-up method does not guarantee its value or redemption. These risks do not permit the arbitrary recalculation of a credit already confirmed or the extinguishment of the right to resolution of a payment received; sections 8 and 11 apply. 10. Top-ups through the Faster Payments System (SBP) and other fiat methods 10.1. SBP and other fiat methods are available only through the routes offered for the specific product. The user checks the amount, the legal identity of the recipient and the payment purpose in the banking application and payment form before confirmation. 10.2. Under an agency arrangement, payment is received by the agent or a participant engaged by it. Until the funds are transferred, Flowbit has a contractual monetary claim against the agent. The card may be topped up separately using funds placed in advance by Flowbit. 10.3. The specific recipient may vary depending on the route. If the recipient changes before payment, updated information must be provided. The user must not use payment details sent by an unknown person outside the official request. 10.4. Settlement by the payment partner with Flowbit does not discharge the obligation to the user under a request for which payment has been made. If receipt is disputed, Flowbit verifies the payment using the confirmation and transaction identifier, requesting the information needed. 10.5. A refund for an unfulfilled top-up is arranged using the facilities of the original SBP partner or other fiat payment recipient under section 8. The original route and the payer’s details are preferred following the required checks. If that route is unavailable, a permissible solution is agreed. The transfer fee in section 16 does not automatically apply to such a refund. 11. Fees, prepayment and top-up exchange rates 11.1. The user pays for Flowbit’s services and known applicable costs in the amount and manner disclosed before activation of the service or confirmation of the transaction. Prepayment means payment before the relevant service is performed; it does not, in itself, mean that the service has already been fully performed. 11.2. A fee may be deducted from the payment amount or paid in addition to it. The specific method, fee currency and final amount to be credited are displayed before confirmation. The same fee must not be charged twice. 11.3. Flowbit sets the price of its own services and the terms for calculating the top-up amount. The calculation rate may include a commercial markup applied by Flowbit and may differ from official, market and other reference rates. Any actual conversion of currency or a digital asset required to execute the transaction is performed by the relevant partner. The calculation rate offered to the user may differ from the rate at which the partner performs the conversion. 11.4. Before confirming a service order or top-up, the user is shown the amount payable, the applicable exchange rate, separately charged fees and known third-party costs and, for a top-up, the final amount to be credited. For SBP top-ups, the final exchange rate shown in the interface before confirmation applies. No additional fee is charged above the displayed total for the top-up. If any amount is provisional, this is indicated before confirmation together with the circumstances on which the final calculation depends. Additional information is provided where and to the extent required by applicable law. 11.5. A confirmed transaction is governed by the agreed amount, fees and exchange rate or method for determining it. Subsequent changes to tariffs do not alter those terms. New tariffs apply under section 25. An additional fee not provided for in the agreed terms requires the user’s consent, except where expressly provided for by law. 11.6. If a request is cancelled or a service is not performed or is only partly performed, the refund amount is determined by reference to the service actually and properly performed, the agreed price of the completed portion and mandatory law. Receipt of prepayment or acceptance of a request for processing does not, in itself, mean that the service has been performed. A fee deducted in error must be refunded. 11.7. The charge for a card duly issued or another service fully performed is non-refundable if this is permitted by applicable law and was disclosed to the user before ordering. This rule does not apply to the amount of an unfulfilled top-up, a card balance or a fee deducted in error. Third-party costs may be deducted if they relate to the specific transaction, have actually been incurred and are evidenced, and their deduction is provided for in the agreed terms and permitted by law. The same cost is not counted twice. 11.8. A particular merchant’s refusal to accept a card or a card programme participant’s subsequent failure to perform its independent obligations does not, in itself, entitle the user to a refund of the charge for a Flowbit service already properly performed. This rule does not restrict the user’s rights where Flowbit breaches its own obligations, a refund is mandatory or a card must be replaced free of charge. 12. Conversion for top-ups and purchases 12.1. Calculation of the top-up amount, settlement between partners, exchange of digital assets and conversion when paying by card are separate operations. The exchange rates and fees applicable to them may differ. 12.2. Flowbit does not itself exchange digital assets or perform currency conversion. Those operations are performed by the relevant payment and card partners. Flowbit determines the price of its own services and, within the terms of the relevant programme, may set markups and fees that affect the calculation of the top-up amount or the amount debited for a purchase. The terms for calculating a top-up are set out in section 11. 12.3. If a purchase is made in a currency other than the card currency, the amount debited is calculated under the card programme rules. The final exchange rate for the user may include a markup set by Flowbit on the base conversion rate. A separate fee for a transaction in another currency may also apply under the card tariff. The applicable conversion rules and separately charged fees are available in the tariffs and terms of the selected card before it is ordered. The exchange rate and amount debited may depend on the purchase currency, processing date and time, and the terms of the card infrastructure participants. The amount at authorisation may differ from the amount debited at final settlement. Tariff changes apply under section 25 and do not entitle Flowbit to revise confirmed transaction terms retrospectively. Mandatory disclosure requirements remain applicable. 12.4. A merchant or its payment partner may offer the user conversion of the purchase into the card currency at its own exchange rate. If the user chooses that conversion, the exchange rate and costs offered by them apply and may differ from the card programme terms. Consent to conversion by the merchant does not remove the right to dispute an erroneous debit. 12.5. When a purchase is refunded, the amount credited in the card currency may differ from the original debit as a result of the exchange rate and refund processing rules under the card programme. The procedure for refunding fees previously deducted is determined by the terms of the relevant transaction and applicable law. Reversal of an authorisation and refund of a purchase already debited follow different procedures. In the event of a discrepancy, the user may contact Flowbit support to check the calculation. 13. Card issuance and use 13.1. The user orders the selected product after reviewing its price, programme terms and verification requirements. Issuance depends on those requirements being met and on programme availability. If the card is not issued, the request for which payment has been made and the related costs are dealt with under sections 8 and 11. 13.2. The card is personal to the user. The user must not transfer the card, its details or access to it to another person, sell, rent out or publish them. An exception is permitted only for a lawful product that expressly provides for it. 13.3. A purchase may be approved, declined, delayed, adjusted or cancelled under the rules of the issuer, network, merchant and other participants. Flowbit does not guarantee that payment for a particular item or service, or payment to a particular merchant, will be possible. 13.4. Merchant subscriptions, pre-authorisations, late settlements and amounts presented after the usual balance check may lead to adjustments. Their validity, amount and the user’s liability are determined by the actual circumstances and programme rules. 13.5. Freezing or closing a card does not always terminate obligations to a merchant that have already arisen. To cancel a subscription, the user must follow the merchant’s procedure; this does not exclude the right to dispute an unlawful debit. 13.6. The purchase contract is between the user and the merchant. Flowbit is not the seller of the goods or services paid for and does not guarantee their quality, delivery, legality or the merchant’s performance of a refund. The user retains their rights against the merchant and the procedures available under section 15; Flowbit is responsible for its own obligations under those procedures. 13.7. The user complies with the programme rules provided to them and the applicable limits by transaction, period, country and merchant category. The availability of, and limits on, future transactions may change on grounds provided for by law and contract. This does not permit the arbitrary recalculation of a transaction already confirmed or the extinguishment of an obligation that has already arisen. 14. Restrictions and prohibited use 14.1. Illegal transactions, money laundering, fraud and deception, use of another person’s details or funds, testing stolen card details, circumventing sanctions, limits or checks, concealing payment purposes, sham transactions and exploitation of vulnerabilities in payment channels are prohibited. Bad-faith payment disputes and refund abuse are prohibited. A good-faith report of an erroneous or unauthorised transaction does not, in itself, constitute abuse. 14.2. The card must not be used to pay for casinos, gambling, betting or lotteries; adult content, pornography, escort services, sexual services or dating apps; weapons, ammunition or explosives; unlawful transactions involving drugs or controlled substances; counterfeit goods, forged documents, stolen data or other illegal goods or services. 14.3. The card must not be used to purchase or trade cryptocurrency, conduct forex transactions or engage in high-risk financial speculation; fund brokerage, trading or investment accounts; withdraw or obtain cash using the card; purchase prepaid or gift cards; top up electronic wallets; make person-to-person transfers or circular transfers that simulate purchases. These restrictions apply to transactions made using the card and do not prohibit cryptocurrency top-ups of the card itself under section 9, transfers of the user’s own balance under section 16 or settlement of that balance under section 20, as provided for in these Terms. 14.4. Do not use the card to pay for the following services: Adobe, Indigo, Gameforge4D, Shopify and StockX. Such a transaction may result in the card being blocked even if the payment succeeds. Additional restrictions by merchant, transaction type and merchant category code (MCC) may apply to individual cards. Information on restrictions known to Flowbit is provided in the product description, Service notifications or through support. Internal anti-fraud screening criteria are not disclosed. 14.5. Interference with the system, unauthorised access, malicious code, mass extraction of protected data and automation to circumvent the rules are prohibited. Unfounded threats and abuse directed at staff are not permitted; restriction of a particular communication channel does not extinguish the right to submit a legal communication. 14.6. Transactions that breach sanctions or export restrictions binding on Flowbit or participants in the processing of the relevant payment are prohibited. This includes transactions involving persons, organisations, countries and territories where such restrictions prohibit the payment. Territorial restrictions of the specific card programme also apply. Concealing or misrepresenting information about the participants, location or purpose of a transaction to circumvent restrictions is prohibited. 14.7. Payment to certain merchants may be unavailable because of card programme restrictions, the merchant’s own rules, security checks or technical reasons. A declined payment does not, in itself, mean that the user has breached these Terms. A successful payment, or a merchant’s absence from a published list, does not mean that such use is permitted. If you are unsure whether a transaction is permitted, contact support before making the payment. 14.8. Availability of the selected card may be restricted depending on the user’s location, residence, place of registration or principal place of business. Countries and territories to which such restrictions may apply include: Americas and the Caribbean: Cuba, Haiti, Nicaragua, the United States of America and Venezuela. Europe: Albania, Belarus, Bosnia and Herzegovina, Croatia, Kosovo, Montenegro, North Macedonia, Russia, Serbia, Slovenia and Ukraine. Asia and the Middle East: Afghanistan, India, Iran, Iraq, Jordan, Lebanon, mainland China, Myanmar, North Korea, Palestine, Syria, Vietnam and Yemen. Africa: Burkina Faso, Burundi, the Central African Republic, the Republic of the Congo, the Democratic Republic of the Congo, Eritrea, Ethiopia, Guinea-Bissau, Liberia, Libya, Mali, Somalia, South Sudan, Sudan and Zimbabwe. Other territories: Bouvet Island, Guam, the Netherlands Antilles, the Northern Mariana Islands, Puerto Rico, the Turks and Caicos Islands and the US Virgin Islands. This is a list of product eligibility restrictions, not a list of merchant countries in which every purchase is automatically prohibited. It does not mean that all listed countries and territories are subject to the same sanctions prohibitions. The designation “Netherlands Antilles” follows the programme’s list; its application to a specific territory must be clarified before issuance. The restrictions in clause 4.3 and the mandatory prohibitions in clause 14.6 apply independently. Before requesting issuance, contact support to confirm whether the selected card is available in your circumstances. 14.9. A breach of these restrictions may result in the provider freezing or closing the card or restricting access to its service; Flowbit may take measures within its authority under sections 17 and 21. Penalties and costs, including dispute-related costs, may be claimed from the user only where there is a lawful basis and applicable contractual terms disclosed in advance. The basis, amount and connection to the breach must be substantiated; the user is entitled to a calculation and may submit objections under sections 19 and 26. Blocking or closing the card does not, in itself, result in loss of the balance; settlement of the balance is governed by section 20. 14.10. The lists of restrictions are not exhaustive and may be updated in accordance with section 25. A change to the rules does not, in itself, turn a previously permitted transaction into a breach. Successful identity verification, an active Plus subscription or the technical availability of a transaction does not waive applicable restrictions. 15. Purchase refunds and disputed transactions 15.1. A refund by a merchant, cancellation of an authorisation, a refund of an unfulfilled top-up, a challenge to a card transaction through the card programme (chargeback), and settlement of the balance when a card is closed are different procedures. Each is subject to the relevant grounds, time limits and rules. 15.2. If the user discovers an erroneous or unauthorised transaction, they must contact Flowbit support as soon as possible and provide the necessary information. Flowbit records the enquiry, explains the applicable procedure, known time limits and required documents, and forwards the enquiry to the relevant card programme participant within the scope of its authority and with regard to the time limits for the procedure. The user must provide the requested information in a timely manner. 15.3. The availability of a chargeback, the review period and the decision are determined by the rules of the card programme, issuer and payment network, taking into account the circumstances of the transaction. Submitting a claim and paying the fee do not guarantee a refund. Flowbit informs the user of the information it receives on the progress and outcome of the review. These provisions do not limit the user’s mandatory rights in relation to erroneous or unauthorised transactions. 15.4. If the card programme provides for a provisional credit of the disputed amount, that credit does not constitute a final decision in the user’s favour. It may be adjusted or reversed on a ground provided for by the programme rules. The user is given the available information on the grounds for and amount of the adjustment. Adjustments are governed by section 19; the right to dispute them is preserved. 15.5. The fee for a paid chargeback procedure is 45 USD for each disputed card transaction: 30 USD is the card partner’s fee for processing the dispute, and 15 USD is Flowbit’s fee for arranging and supporting the procedure. The fee is charged only where permitted by applicable law and the card programme rules. If several transactions are disputed, the total amount is disclosed before the paid procedure is confirmed. The fee is paid before the paid chargeback procedure begins, after the user has agreed to its cost and conditions. Providing additional documents for the same procedure does not, in itself, justify charging the fee again. Payment and commencement of the procedure do not guarantee recovery of the disputed amount. If the procedure has not been initiated and the card partner has not charged Flowbit the fee, the full 45 USD is refunded to the user. If the partner has charged the fee, Flowbit checks the grounds for the charge and whether it can be refunded. Such an amount may be retained only on a lawful ground disclosed to the user in advance, and only to the extent of costs actually incurred and not reimbursed. Flowbit’s fee for the part of the service not provided is refunded. If the partner subsequently refunds the retained fee, the corresponding amount is refunded to the user. Rejection of the dispute does not, in itself, entitle the user to a refund of fees for services duly provided; mandatory grounds for a refund remain applicable. Merely reporting an erroneous or unauthorised transaction does not constitute an order for a paid chargeback. Acceptance of such a report is not conditional on payment of a fee. Cancellation of an authorisation and an ordinary merchant refund are also not paid chargebacks. The fee does not apply to procedures that must be provided free of charge under mandatory legal requirements or programme rules. 15.6. If a merchant sends a refund after the card has been closed or has expired, Flowbit liaises with the card partner to establish the status of the refund and how the user can receive it. A confirmed amount received is recorded for the benefit of the relevant user and settled in accordance with the programme rules and section 20. Closure of the card does not, in itself, extinguish the user’s right to a refund due to them. 15.7. Knowingly false statements, fabricated evidence, intentional receipt or retention of duplicate compensation for the same amount, and other misuse of refund procedures are prohibited. If the user discovers duplicate compensation, they must notify support; an adjustment is made under section 19. An erroneous duplicate credit does not, in itself, prove fraud by the user. Documented losses and permissible expenses caused by a breach are recoverable under sections 19 and 26. Rejection of a claim made in good faith does not, in itself, constitute evidence of misuse. 16. Transfers of balances between the user’s cards 16.1. The user may contact support to transfer an available balance to another of their own cards. A transfer is carried out if both card programmes support it, after verification of card ownership, the balance, pending transactions and existing restrictions. Transfers to other persons or to external payment details are not provided under this section. 16.2. For a voluntary manual transfer, the fee is 1 USD + 1% of the amount being transferred before deduction of the fee. The fee is deducted from that amount. For example, when transferring 100 USD, the fee is 2 USD and 98 USD is credited to the other card. 16.3. If the user has no suitable card, they may purchase a new one separately or agree to have its issuance cost deducted from the amount being transferred. Before confirmation, Flowbit discloses all costs and the amount to be credited. If there are insufficient funds, the transfer is not carried out; the balance is not reduced to zero and no negative balance is created. 16.4. If a replacement is necessary because the card or programme is closed at the initiative of Flowbit or the provider, the balance transfer and issuance of a replacement card are free of charge. Checks and existing restrictions remain applicable. If the funds are unavailable or a transfer is not possible, the settlement procedure is governed by section 20 and the participants’ liability by section 26. 16.5. If a transfer is not possible or applicable law provides for another method of returning the balance, section 20 applies. The user is not required to purchase a new card to preserve their right to the balance. 16.6. After the transfer, Flowbit provides a calculation of deductions and confirmation of the credit. If the transfer is not completed, any fee deducted for it is refunded. Separate expenses may be retained only if they were agreed in advance, were actually incurred and are permitted by law. 17. Checks, restrictions and blocking 17.1. Access to the Service or individual transactions may be restricted where there is a reasonable suspicion of fraud, account compromise or a breach of the Terms, as well as for mandatory checks, obtaining necessary documents, compliance with sanctions requirements and addressing material technical risks. 17.2. Flowbit may restrict access to its Service, suspend the processing of a request and contact the card or payment partner for measures to be taken within the scope of its authority. Decisions on restrictions imposed by the issuer or partner are made by the relevant participant in accordance with applicable rules and law. 17.3. Flowbit informs the user of the restriction, any action required and the procedure for making an enquiry to the extent permitted by law and security requirements. A restriction may be imposed without prior notice if notice is prohibited, increases the risk of fraud or hinders a check. Information about checks and methods of detecting breaches may be withheld if disclosure is prohibited by law or would enable protective measures to be circumvented. 17.4. Blocking access does not, in itself, mean that the balance is debited or forfeited. Restrictions on the use of funds and deductions towards a confirmed debt require separate grounds. The amount and duration of a restriction must be consistent with its grounds and reviewed in accordance with the prescribed procedure. 17.5. If a refund or transfer of funds is prohibited by law or a binding order of a competent authority, the transaction is not carried out until the prohibition is lifted. Once the restriction is lifted, Flowbit takes the necessary action within the scope of its authority and, where necessary, contacts the relevant partner to settle the balance under section 20. 17.6. Even where access to the account is restricted, the user may contact support about blocking, checks, an erroneous transaction or the balance. Flowbit reviews enquiries concerning its own actions and forwards matters falling within a partner’s authority to the relevant participant. 18. Account and card security 18.1. The user must take reasonable steps to protect their device, Telegram account, email and access to Flowbit. Passwords, PINs and one-time codes must not be disclosed to others. Card details must be protected against unauthorised access and used only for transactions provided for by the card programme. 18.2. If the user loses a device or suspects compromise, disclosure of card details or an unauthorised transaction, they must notify support without undue delay. Support staff are prohibited from requesting passwords, PINs, CVV/CVC, one-time codes, private keys or seed phrases. 18.3. Data concerning the use of the device, account and confirmation codes is taken into account when investigating a disputed transaction. The fact that they were used does not, in itself, rule out compromise or a technical error and does not automatically make the user liable. 18.4. Flowbit takes the technical and organisational measures required by law and contract to protect its systems and the data it processes, responds to identified incidents and issues mandatory notices. Flowbit’s liability for breach of its own security obligations is governed by section 26 and applicable law. 18.5. To the extent permitted by law, Flowbit does not compensate the portion of losses caused by the user’s proven breach of security requirements or failure to report an incident in a timely manner. The connection between the breach and the losses incurred must be taken into account. This provision does not relieve Flowbit of liability for its own breaches or limit the user’s mandatory rights in relation to unauthorised transactions. 19. Adjustments, negative balances and deductions 19.1. The card balance may be adjusted on final settlement of a transaction, deduction of an agreed fee, correction of an erroneous credit or lawful reversal of a provisional credit. Other adjustments are permitted where there is a specific ground under law and the applicable programme terms. The user is provided with the grounds for and calculation of the adjustment to the extent permitted by law. 19.2. The user must repay a negative balance if it arises from a valid and confirmed obligation. A negative amount displayed in the interface does not, in itself, prove the existence of a debt. Flowbit’s debts to partners, the programme’s general reserve and other users’ losses do not, in themselves, create obligations for the user. 19.3. Set-off of mutual claims and deductions, including deductions from a refund to the user, are permitted only where there is a legal and contractual basis and the necessary authority. The same debt is not recovered more than once, and erroneous deductions are corrected. If conversion is required, the calculation method disclosed in advance or the mandatory programme rules apply. The user is provided with a calculation. 19.4. The user may request an explanation and dispute an adjustment or debt, including after a debit has been made. Submitting an enquiry does not, in itself, extinguish a valid debt. If mandatory rules require an amount to be deducted regardless of the review of a dispute, Flowbit informs the user to the extent permitted by law. 19.5. Where there is a confirmed outstanding debt, Flowbit sends a demand stating the grounds, amount, method and deadline for payment, and the procedure for raising objections. The payment period must be reasonable and comply with legal requirements. Checking the calculation does not constitute a separate ground for increasing the debt. 19.6. Outstanding debts may be recovered by lawful means, including proceedings before a competent court. Recovery costs are reimbursable only where there is a legal basis and evidence of their amount. 19.7. Service fees, compensation for losses and mandatory deductions require separate grounds and calculations. These Terms do not impose a fixed penalty for debt or an unlimited investigation or recovery fee. 20. Closure of cards and accounts and settlement of balances 20.1. To close a card or account, the user contacts support. Flowbit checks ownership of the card or account, the balance, pending transactions and restrictions, explains the closure procedure and supports the request. 20.2. A standard withdrawal of the card balance to an external bank account or cryptocurrency wallet is not provided. The absence of this function, previous purchases or closure of the card do not, in themselves, extinguish the user’s right to the remaining balance. Fees for services already provided are considered separately from the balance. 20.3. The user may request a balance transfer under section 16 or use an available card for permitted purchases. The user is not required to make purchases or acquire a new card to preserve their right to the balance. 20.4. On closure, the unsettled balance, known holds and deductions, and pending transactions are recorded. Pending transactions and lawful restrictions may delay final settlement. Closure does not extinguish obligations that have already arisen and does not preclude the recording of late refunds. The balance does not become income of Flowbit or a partner solely because the card is closed. 20.5. If a transfer is not possible or servicing ends, Flowbit checks the amount and restrictions, explains who is responsible for settling the balance and how to submit a claim. Flowbit fulfils its own obligations and supports the enquiry to the relevant partner within the scope of its authority. The technical unavailability of withdrawals does not, in itself, extinguish a claim against the person under the obligation. 20.6. If the issuer or another programme participant becomes insolvent, settlement may take place through liquidation, bankruptcy or another procedure prescribed by law. Flowbit does not guarantee the timing or full payment of that participant’s independent obligations referred to in clause 26.3. Flowbit’s own obligations remain in force. 20.7. Closing an account does not always mean that all data is deleted immediately. Information necessary for settlement and compliance with legal requirements is retained on the grounds and for the periods provided for by law, in accordance with the Privacy Policy. 21. Suspension or termination of services 21.1. Flowbit may suspend or terminate services if the user materially breaches the Terms, mandatory requirements cannot be met, the card programme ends, or on other grounds provided for by law and contract. The user is notified in the manner and within the time limits prescribed by applicable law and the programme rules. 21.2. In the cases specified in section 17, services may be restricted without prior notice. After imposing a restriction, Flowbit provides the available information on its reasons and the procedure for making an enquiry, where disclosure of that information is permitted by law. 21.3. Suspension or termination of services does not cancel obligations of Flowbit, the user or the relevant partners that have already arisen. The balance is settled under section 20, and any required card replacement is carried out on the terms of section 16. 22. Additional products, subscriptions and rewards 22.1. Flowbit may offer subscriptions, referral programmes, cashback, bonuses and other additional products. Their availability and terms are disclosed to the user before activation or participation. 22.2. The terms of the relevant product determine its price, duration, renewal and cancellation procedures, rules for accruing and using rewards, restrictions, adjustments following purchase refunds, and the treatment of accrued rewards when the account is closed or the programme ends. 22.3. Automatic renewal of a paid subscription is permitted with the user’s consent. Before automatic renewal is enabled, the user is informed of the amount and frequency of charges and the cancellation procedure. 22.4. Accrual of a reward does not, in itself, mean that it has actually been credited to the card. Bonuses are recorded separately from funds paid in by the user. Restrictions on the use of bonuses do not, in themselves, apply to those funds. 23. Personal data and electronic communications 23.1. Flowbit processes personal data on lawful grounds to provide services, process transactions, provide support, ensure security and comply with mandatory requirements. 23.2. The Privacy Policy sets out which data is processed, for what purposes, to whom it is disclosed and how long it is retained. It also describes cross-border data transfers and the user’s rights. Data is shared with partners only on a lawful basis and to the extent necessary. 23.3. Flowbit may send service communications and notices on its own behalf through the application, the official Telegram bot linked to the account, a verified email address or another agreed channel. Such communications may concern transactions, cards, security, support enquiries, changes to terms and the operation of activated services. 23.4. Flowbit may also send marketing communications about promotions, new products and special offers through the application and other agreed channels. Such communications are sent with the user’s prior consent, obtained separately from acceptance of these Terms and covering the relevant communication channel. The user may opt out of marketing by the method specified in the communication or through support. Opting out does not prevent use of the Service or receipt of necessary service notices. 23.5. By accepting the Terms, the user agrees to receive contractual documents and notices electronically through the channels specified above, unless the law requires another form. Documents are provided in a manner that allows their contents to be saved. Where an individual notice or separate consent is required, publication on the website does not replace it. 23.6. The user keeps their contact details up to date and checks the agreed communication channels. If Flowbit is aware that an important notice has not been delivered, another available agreed channel is used where necessary. Technical delivery and transaction records may be used as evidence, but the user may challenge their accuracy. A delivery record does not, in itself, confirm that a message has been read. 24. Rights in interfaces and materials 24.1. Rights in the software, interfaces, brand and materials of the Service belong to Flowbit Finance L.L.C-FZ or the relevant rights holders. 24.2. The user is granted a limited, non-exclusive licence to use the Service for its intended purpose and in accordance with these Terms. The licence may not be transferred to another person or sublicensed. The licence remains in force until the right to use the Service ends. 24.3. Copying or distributing protected materials, commercially reselling the software or access to the Service, creating derivative software products, decompiling or reverse engineering is prohibited without the rights holder’s permission. Circumvention of protective measures and unauthorised interference with the operation of the Service are also prohibited. These restrictions do not apply to acts permitted by mandatory provisions of applicable law. 24.4. The user may retain the contracts and transaction confirmations provided to them and use them to make enquiries and protect their rights. This right survives termination of access to the Service. 25. Changes to terms, tariffs and programmes 25.1. New versions of the Terms and changes to tariffs are published in the Service, stating their publication and effective dates. Flowbit gives advance notice of material changes through the channels specified in section 23, observing mandatory notice periods. Urgent changes to comply with legal requirements or prevent an immediate security threat may be introduced without prior notice only where permitted by law. The user is notified of them to the extent permitted by law. 25.2. New tariffs apply to services and transactions after the changes take effect. Transactions that have already been confirmed are settled on the terms agreed at the time of confirmation. 25.3. If separate user consent is required for changes to apply, Flowbit obtains it before applying those changes to the user. Contacting support does not, in itself, constitute such consent. 25.4. If the user does not agree with the changes, they may stop using the Service and contact support to close the card or account. Transfer and settlement of the balance are carried out under sections 16 and 20. 26. Liability and its limitations 26.1. Flowbit is responsible for fulfilling its own obligations under these Terms, including paid services, correct calculation and deduction of its fees, recording of transactions, handling of enquiries, and security of systems and data within its area of responsibility. 26.2. Flowbit takes the technical and organisational measures required by law and contract to operate and protect the Service. Uninterrupted operation, complete freedom from errors and compatibility with every device are not guaranteed unless expressly agreed otherwise. This does not cancel obligations to provide paid services, correct its own errors and comply with mandatory security requirements. Flowbit checks partners on the basis of available information and risk assessments. Such checks do not guarantee their future solvency, uninterrupted operation or freedom from security incidents. 26.3. Flowbit does not act as an insurer, surety or guarantor of the independent obligations of an issuer, BIN sponsor, bank, card partner or payment partner, unless Flowbit expressly undertakes otherwise or the law provides otherwise. An independent obligation is an obligation owed directly by the relevant participant to the user under applicable law or a valid contract, including a contract for the user’s benefit. The mere existence of a contract between Flowbit and a partner does not transfer Flowbit’s own obligations to the user to that partner. Flowbit does not guarantee the absence of failures, cyberattacks, data breaches, fraud, blocking, licence revocation, insolvency or cessation of business by such a participant. If it is established that losses are caused exclusively by circumstances attributable to an independent participant, are unrelated to any breach of Flowbit’s obligations and do not fall within Flowbit’s responsibility under law or contract, they are not compensated by Flowbit. Flowbit is not required to advance funds to discharge such a participant’s independent debt or cover a shortfall in its assets, except where required by law or by obligations expressly undertaken by Flowbit. Receipt of a fee, prefunding and display of a balance do not, in themselves, create such a guarantee. 26.4. Engaging partners does not relieve Flowbit of its own obligations or of liability retained by it under law or contract. This includes obligations provided for by law or contract relating to the selection of partners, transmission of instructions, management of funds, disclosure of information and oversight of delegated functions. Failure to receive funds from a partner, including master balance funds, does not, in itself, extinguish Flowbit’s obligations to the user or constitute performance of a paid service. 26.5. A top-up request is deemed fulfilled after the agreed amount has actually been credited to the selected card, as confirmed by the records of the programme participant servicing it, with the corresponding card balance made available to the user. An entry solely in the Flowbit interface or a notice acknowledging receipt of payment does not, in itself, confirm this. Once duly credited, the amount constitutes a card balance. A subsequent failure, compromise or insolvency of a programme participant does not, in itself, mean that a previously completed top-up was not fulfilled. Obligations concerning continued servicing and settlement of the balance are determined by law, the applicable programme terms, sections 16 and 20, and this section. Flowbit’s own obligations to correct errors and refund unlawfully retained fees and other amounts due from it remain in force. Payment and refund of these amounts are considered separately from compensation for losses; limitations of liability for losses do not reduce Flowbit’s existing debt. 26.6. The grounds for and amount of compensation for losses are determined by applicable law, taking into account the nature of the breach, causation and the circumstances of the case. Flowbit does not guarantee profit or any other commercial outcome from use of the Service. This does not exclude compensation for loss of profit where provided for by applicable law. 26.7. These Terms do not exclude or limit liability for Flowbit’s fraud, wilful misconduct or gross negligence, or liability for causing harm and other breaches which the law prohibits from being excluded or limited. Mandatory consumer rights, rights in relation to unauthorised transactions and mandatory personal data protection requirements remain in force. 26.8. The user compensates documented losses and permissible expenses directly caused by their breach of these Terms or the law, within the limits of liability established by law. Flowbit provides the grounds, calculation and supporting evidence that may lawfully be provided; the user may raise objections. A third-party claim or Flowbit’s voluntary settlement of it does not, in itself, prove that the user owes a debt. Flowbit’s own breaches, the programme’s corporate debts and other users’ losses are not automatically passed on to the user. The same amounts are not recovered twice. The procedure in section 19 applies. 26.9. The consequences of extraordinary circumstances beyond a party’s reasonable control which objectively prevent performance are determined by law. The party relying on them substantiates their existence and effect, notifies the other party without undue delay to the extent permitted, and takes reasonable steps to mitigate the consequences and resume performance. A lack of a party’s own funds or non-payment by a partner does not, in itself, relieve that party of its obligations. Settlements and refunds where performance is impossible are made in accordance with the law. 26.10. In the event of a material failure or non-performance of obligations by a programme participant, Flowbit provides the user with available information, takes reasonable steps within the scope of its authority to reduce losses and supports the enquiry to the responsible person. Mandatory restrictions and established settlement procedures apply. Such support does not constitute a suretyship for a partner’s independent debt and does not guarantee recovery. Flowbit’s own obligations remain in force. 27. Enquiries, complaints and disputes 27.1. The user may submit an enquiry or complaint through the official support channel or to the legal contact specified in section 29. To review it, Flowbit may request the information necessary to identify the user and verify the circumstances of the enquiry. Passwords, PINs, CVV, one-time confirmation codes, private keys and seed phrases are not required. 27.2. Flowbit explains the procedure for reviewing an enquiry and specifies any additional information needed for verification. If the decision depends on the issuer or another partner, Flowbit forwards the enquiry within the scope of its authority and provides available status information. A partner’s procedures may affect the time required for a final outcome, but do not cancel Flowbit’s own obligations to review and support the enquiry. 27.3. These Terms are governed by the laws of the United Arab Emirates. Mandatory law applicable to the particular user, service and dispute nevertheless remains applicable, including consumer rights that cannot be excluded by agreement between the parties. The choice of UAE law does not override such rights in another applicable jurisdiction. 27.4. Disputes may be referred to the competent courts of Dubai unless mandatory provisions of applicable law prescribe another procedure or give the user the right to bring proceedings in another court. Contacting support does not limit the right to legal remedies and must not cause the user to miss applicable time limits for bringing a claim. 27.5. Either party may seek urgent interim or other protective relief from another competent court where permitted by applicable law. This section does not limit the user’s mandatory right to have a dispute heard in the place prescribed by law. 28. Miscellaneous provisions 28.1. The user may not transfer the contract, access rights or obligations to another person without Flowbit’s prior written consent, except where expressly provided for by law. Flowbit may assign rights and claims and transfer the contract to a successor or another person in accordance with the procedure established by law. If the user’s consent is required to transfer the contract or obligations, Flowbit obtains it; notice does not replace such consent. A transfer does not extinguish the user’s accrued claims or reduce their mandatory rights. Engaging contractors does not relieve Flowbit of liability retained by it under law or contract. 28.2. If any provision of the Terms is held invalid, the remaining provisions remain in force if the contract can operate without it. The consequences of invalidity are determined by law. 28.3. The contract consists of these Terms and the documents for the particular product that have been provided to the user and expressly incorporated into the agreement. A new version applies once it takes effect in accordance with section 25 and governs subsequent use of the Service. Accrued claims and the agreed terms of confirmed transactions are preserved. In the event of discrepancies with informational or promotional materials, the procedure in section 3 applies. This does not relieve Flowbit of liability for inaccurate material information or cancel obligations it has expressly undertaken. 28.4. The material financial terms of a transaction must be clear to the user before confirmation. Ambiguities are resolved before confirmation; the agreed terms of a transaction already paid for are preserved. 28.5. The Service’s informational materials do not constitute individual investment, tax or legal advice. The user is responsible for complying with their applicable tax declaration and payment obligations. Flowbit’s obligations concerning tax withholding, reporting and provision of mandatory information remain in force. 28.6. Failure or delay in exercising a right does not, in itself, constitute a waiver of that right. A waiver is effective only to the extent confirmed by the relevant party and within the limits permitted by law. Statutory time limits for enforcing rights remain applicable. 28.7. After the account is closed, provisions necessary for settling pending transactions, card balances and debts, protecting personal data and intellectual property rights, determining liability and resolving disputes remain in force. These provisions apply to the extent necessary and subject to the time limits prescribed by law. 29. Contact details Flowbit Finance L.L.C-FZ Registration number: 2541754. Address: Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, U.A.E. Legal enquiries: company@flowbitfinance.com. Support: the official channel specified in the Flowbit application and the user’s profile.