USR-006 Términos de cuenta virtual y datos de cuenta local Virtual Account and Local Account Details Terms
- Versión 1.2 / Version
- 1.2 • Vigentes desde el 8 de septiembre de 2026 / Effective 8 September 2026
Aviso esencial / Essential notice
Los datos de cuenta local o cuenta virtual que Bliim pueda mostrar permiten recibir fondos mediante redes de pago habilitadas. No significan, por sí solos, que Bliim sea un banco, que haya abierto una cuenta bancaria propia a nombre del usuario, que mantenga depósitos del usuario o que toda protección bancaria o de depósitos resulte aplicable. La entidad que proporciona la infraestructura, la titularidad, la red de pago, la protección de fondos y cualquier conversión asociada se identificarán o pondrán a disposición antes de activar el producto cuando corresponda.
Local account details or virtual-account details that Bliim may display allow funds to be received through enabled payment rails. They do not, by themselves, mean that Bliim is a bank, has opened its own bank account in the user's name, holds the user's deposits or that any banking or deposit protection automatically applies. The entity providing the infrastructure, ownership, payment rail, funds protection and any associated conversion will be identified or made available before product activation where applicable.
Entidad contractual / Contracting entity: BLIIM GLOBAL LLC Dirección operativa / Operational address: 1000 N. West Street, Suite 1200, Wilmington, Delaware 19801, United States Legal y privacidad / Legal and privacy: [email protected] • Soporte / Support: [email protected] These Virtual Account and Local Account Details Terms (the “Local Account Terms”) govern access to and use of account details that Bliim enables for receiving funds through certain payment rails. They supplement the Bliim General Terms of Use, the Global Privacy Policy and Notice, the Acceptable Use and Prohibited/Restricted Activities Policy, applicable wallet, conversion, transfer and fee terms, and the terms or notices of any provider involved in the product.
1. Purpose and scope
These Terms apply only to local account details or virtual-account details expressly enabled for the user.
Availability of the Platform, a wallet, card, onboarding process or any other Bliim product does not mean that this functionality is available in the same country or to the same user.
The details may be used to receive funds through the currencies, payment rails and transfer types identified in the application. They must not be used for a purpose, currency or rail other than the one expressly displayed.
2. Nature of the product
Depending on the enabled country and infrastructure, Bliim may display details such as an account number and routing number for USD, an IBAN for EUR/SEPA, a CLABE for MXN/SPEI or other expressly supported local identifiers.
These details allow payments to be directed to infrastructure designated for the user. Their existence does not, by itself, mean that Bliim has opened its own bank account in the user's name, that Bliim is the depositary bank or that the user holds a deposit directly with Bliim.
The legal nature of the details, the entity providing or maintaining them, ownership of the account or subaccount, protection of funds and user rights depend on the actual product structure and applicable jurisdiction.
3. Role of Bliim and providers
BLIIM GLOBAL LLC primarily provides the technology interface, presentation, connectivity and orchestration necessary for the user to access the functionality. Allocation of account details, receipt of funds, maintenance of underlying accounts, settlement, custody, conversion, returns or subsequent movement may be performed by Bridge, banks, financial institutions, payment providers or other enabled third parties, depending on the product.
Bliim does not assume under these Terms obligations that belong exclusively to a bank, payment provider, custodian or other independent entity. This allocation does not limit any mandatory obligations that applicable law directly assigns to Bliim.
4. Provider terms and acceptance
Where the functionality depends on Bridge or another provider requiring a direct contractual relationship with the user, the user must accept the terms, privacy notices, disclosures and other documents required by that provider. Acceptance of these Terms does not replace that acceptance.
Where Bridge requires acceptance of its terms before processing KYC or KYB, Bliim will direct the user to the Bridge-hosted or Bridge-approved acceptance flow and retain or associate the relevant acceptance evidence. Bliim will not replace that process with its own simple checkbox where the provider requires its specific mechanism.
The applicable Bridge entity may vary according to residence, jurisdiction and service and will be determined by the then-current terms presented by Bridge to the user.
5. Eligibility, KYC/KYB and activation
Allocation and activation of local account details are subject to eligibility, identity or business verification, acceptance of required terms, territorial availability, approval for the relevant product or rail, risk and compliance controls, and any provider requirements.
An active Bliim Account, approved KYC/KYB or technical availability of a rail does not guarantee access to this functionality. Bliim may deny, suspend or withdraw access where applicable requirements are no longer satisfied.
6. Product-specific information before activation
Before activating a local-account variant, Bliim will display or make available, where material or legally required, the identity of the relevant provider, the nature of the assigned details, beneficiary name, participating bank or institution where applicable, currency, accepted payment rail, principal use restrictions, applicable funds protections and any associated conversion relationship.
The product screen must reflect the actual structure. Bliim will not describe a feature as a “bank account” , “deposit” , “insured account” or equivalent unless that characterization is accurate for the specific product and supported by the applicable documentation.
7. Account details and ownership
The user must use and share the details exactly as displayed in the application. Beneficiary name, bank, bank address, account number, routing number, IBAN, CLABE or another identifier may be necessary for correct processing.
Where the underlying account or subaccount is not legally owned directly by the user, the interface and applicable notices must not represent otherwise. The user's legal relationship with the infrastructure is determined by the product and the relevant provider terms.
8. Receipt of funds
Funds sent to the account details will be processed only through expressly supported rails, currencies and transfer types. A transfer sent through an unsupported rail, currency, payment type or instruction may be rejected, returned, delayed or require manual handling.
The user must provide third parties only with the current instructions displayed in the application. Bliim does not guarantee recovery of funds sent using outdated, incomplete, modified or incorrect details.
9. Third-party funds and restricted uses
Bliim or the provider may restrict third-party payments, cash, checks, unauthorized debits, transfers made on behalf of other persons, intermediary activity or any use inconsistent with the approved profile or applicable payment rail.
Where the product permits third-party funds, additional information may be requested about the originator, purpose, relationship to the user, source of funds or other information needed for compliance, reconciliation, fraud prevention or investigation.
10. Currencies and payment rails
Each set of details is limited to the currencies and payment rails identified in the application. Depending on the product, routes may include ACH or wire for USD, SEPA for EUR, SPEI for MXN, PIX for BRL, Faster Payments for GBP or other enabled rails.
Technical availability of a rail or provider capability does not mean Bliim lawfully offers it in every country.
Availability is determined for the applicable product, user, jurisdiction and provider.
11. Conversion and subsequent destination
For some products, fiat received through account details may be converted by the provider into USDC or another expressly supported asset and sent to a configured destination. Where this structure applies, Bliim will state that the details form part of a receipt-and-conversion flow and are not necessarily an account intended to hold fiat.
Before a material conversion, the destination asset or currency, relevant network, fees, exchange rate or spread where applicable, and other information required under the conversion terms and applicable law will be displayed or made available.
12. Limits, reserves and controls
Minimum or maximum amounts, frequency limits, aggregate limits, reserves, manual reviews or other restrictions may be imposed by Bliim, the provider, the underlying institution or applicable law. Limits may vary by user, country, currency, rail, source of funds, risk profile or verification status.
Current limits will be communicated where necessary to use the functionality. No displayed limit constitutes a credit line or promise of future capacity.
13. Fees, exchange rates and third-party charges
Fees charged by Bliim to the user, and any applicable spread or exchange rate, will be disclosed in accordance with the Fees, Limits & FX terms and disclosures and, where applicable, before the user confirms a transaction.
Originating banks, intermediaries, networks or other third parties may impose charges that Bliim does not control. Bliim will not present an internal provider cost as though it were automatically a fee charged to the user.
14. Unidentified, pending or unreconciled payments
A payment lacking sufficient information to associate it correctly with the user may remain pending, be returned or require additional information. Technical receipt of funds by a provider does not mean they are immediately available.
The user must reasonably cooperate with requests for identification, reconciliation, receipts or supplementary information where necessary to locate or process a payment.
15. Rejections, returns and reversals
A payment may be rejected, returned or reversed because of incorrect details, unsupported currency or rail, deactivated details, originating or receiving bank restrictions, limits, compliance controls, fraud, technical errors or legal requirements.
A return may be subject to processing time, exchange-rate effects, fees or third-party charges unless applicable law requires different treatment. A return does not necessarily constitute a chargeback or create a general right to reverse any received payment.
16. Funds protection and deposit insurance
Applicable protection depends on the entity receiving the funds, the underlying account structure, the stage of the flow and the jurisdiction. Bliim will not state that funds are covered by FDIC, a European deposit-guarantee scheme, safeguarding, pass-through insurance or another protection unless coverage has been confirmed for the specific product and its conditions and limitations are explained.
The participation of a bank or regulated entity in the chain does not, by itself, mean that all amounts or assets displayed in Bliim receive the same protection.
17. Compliance, fraud, sanctions and source of funds
Bliim and applicable providers may conduct KYC/KYB, AML/CFT, sanctions, fraud, transaction-monitoring, source-of-funds, transaction-purpose and other risk-proportionate controls.
An incoming payment may be held, rejected, returned, blocked or reviewed where legal restrictions, sanctions, fraud risk, inconsistencies, insufficient information, provider requirements or a valid authority order apply. Where law restricts disclosure, Bliim may limit the explanation provided.
18. Security of account details
The user must protect access credentials, verify instructions before sharing them and promptly report suspected misuse, an unrecognized incoming payment or unauthorized access.
Bliim or the provider may replace, migrate or deactivate account details for security, fraud, provider migration, regulatory, maintenance or operational reasons. The user must not continue using details that have been deactivated.
19. Suspension, deactivation and closure
The functionality may be suspended or deactivated, where legally permitted, because of breach, risk, fraud, sanctions, closure of the Bliim Account, provider termination or change, loss of territorial availability or operational necessity.
Suspension or closure does not extinguish obligations, investigations, returns, complaints, rights or pending payments that arose previously.
20. Errors, unrecognized transactions and complaints
The user must promptly report missing payments, incorrect amounts, unrecognized incoming transfers, unexpected returns or any other potential error through channels identified by Bliim.
Investigation, correction, reimbursement, complaint and escalation rights depend on the rail, provider, nature of the service and applicable law. Nothing in these Terms limits mandatory user rights. Where a complaint legally belongs to the underlying provider or bank, Bliim may facilitate routing and retain evidence of that routing.
21. Privacy and personal data
Processing of personal data is governed by Bliim's Global Privacy Policy and Notice and applicable provider notices. To enable or manage the product, Bliim may share with authorised providers the data necessary for identity, ownership, payment instructions, fraud prevention, compliance, reconciliation, support and exercise of rights.
Originator data, bank references, account identifiers, transaction information and risk signals will be subject to applicable purpose limitation, minimisation, security, retention and international-transfer requirements.
22. Jurisdictions and availability
Bliim will enable a local-account variant only after confirming that the applicable product, jurisdiction and provider may be used under the approved architecture. The United States, Colombia, Mexico and Spain/EEA require independent conclusions concerning provider, ownership, currency, rail, treatment of funds, regulation, disclosures and user rights.
Availability of CLABE/SPEI, IBAN/SEPA, USD account/routing, COP or another local detail must not be inferred from its technical presence in an API, prototype or screen. The functionality may be activated only where Bliim has expressly enabled it.
23. Product changes and reacceptance
Bliim may modify, migrate or withdraw account details to reflect changes in provider, bank, rail, currency, law, security or architecture. Where a material change requires a new notice, acceptance or reacceptance, Bliim will implement the relevant mechanism before the user continues using the affected functionality.
The current version of these Terms will be available in the application or Legal Center.
24. Contact and contractual integration
For operational support concerning these account details, the user may contact [email protected] or use the channels available in the Platform. For legal and privacy matters: [email protected]. Specific channels of the underlying provider or bank will be identified where necessary to exercise rights associated with the product.
These Terms are product-specific and form part of the Bliim General Terms of Use together with the terms of the applicable provider. In the event of conflict, mandatory law prevails; then provider terms with respect to obligations directly belonging to the provider; these Terms with respect to the Bliim functionality; and the General Terms with respect to the general Platform relationship.
BLIIM GLOBAL LLC operational address: 1000 N. West Street, Suite 1200, Wilmington, Delaware 19801, United States.