USR-005 — TÉRMINOS Y DIVULGACIONES DE TRANSFERENCIAS
TRANSFRONTERIZAS Cross-Border Transfer Terms & Disclosures
- Entidad / Entity
- BLIIM GLOBAL LLC — Delaware, United States
- Documento / Document
- Términos y Divulgaciones de Transferencias Transfronterizas / Cross-Border Transfer Terms & Disclosures
- ID
- USR-005
- Versión / Version
- V1.2
- Fecha de vigencia / Effective date
- 7 de octubre de 2026 / 7 October 2026
- Estado / Status
- PUBLICATION FINAL — ACTIVATION CONDITIONAL
- Ámbito / Scope
- Web, app y corredores transfronterizos expresamente habilitados / Web, app and expressly enabled cross-border corridors
- PRINCIPIO CENTRAL / CENTRAL PRINCIPLE
- Las transferencias transfronterizas pueden involucrar múltiples proveedores, monedas, activos digitales, bancos, redes de pago y etapas de settlement. Bliim opera principalmente como capa tecnológica e interfaz de orquestación. La recepción, custodia, conversión, transmisión, liquidación o pago al beneficiario puede ser realizada por terceros regulados o proveedores independientes según el corredor y la jurisdicción. La disponibilidad técnica no equivale a disponibilidad jurídica o contractual.
Cross-border transfers may involve multiple providers, currencies, digital assets, banks, payment networks and settlement stages. Bliim primarily operates as a technology layer and orchestration interface. Receipt, custody, conversion, transmission, settlement or beneficiary payout may be performed by regulated third parties or independent providers depending on the corridor and jurisdiction. Technical availability does not equal legal or contractual availability.
1. Purpose and Scope
These Terms govern access to and use of cross-border transfer functionality that Bliim expressly enables through its app, website or other interfaces.
They apply together with the General Terms of Use, Privacy Policy, Acceptable Use Policy, applicable provider terms and any product- or jurisdiction-specific disclosure.
2. Nature of the Service
Bliim may allow the user to initiate, view or manage a transfer instruction. Material execution may involve one or more banks, payment providers, infrastructure providers, liquidity providers, custodians, stablecoin issuers or other third parties.
Bliim does not automatically hold itself out as a bank, money transmitter, remittance transfer provider, electronic-money institution, CASP, custodian or financial institution merely because it provides the interface.
3. Corridor Availability
Each corridor is enabled by origin country, destination country, currency or asset, funding method, delivery method, partner, limits and regulatory requirements.
The appearance of a country, currency or method on a screen is not a promise of permanent availability.
4. Product × Country × Partner
Actual availability depends on the specific product, country, partner and responsible entity. Bliim may suspend or restrict a corridor where contractual, technical, regulatory or risk support is insufficient.
A partner used for one corridor may differ from the partner used for another.
5. Sender and Beneficiary Identity
The sender must provide complete and accurate information about themselves and the beneficiary where required by the flow.
Bliim or the applicable provider may request additional information to verify identity, eligibility, ownership, relationship to the beneficiary, transfer purpose or compliance requirements.
6. KYC, KYB, AML and Sanctions
Transfers may be subject to KYC/KYB, sanctions screening, transaction monitoring, source-of-funds checks, risk limits and enhanced review.
A transaction may be held, rejected, cancelled or reviewed where there is a legal, contractual, risk or compliance basis.
7. Funding
Users must use only funding methods expressly enabled. An instruction is not treated as funded until required funds or assets have been received and are usable under the applicable rail.
A pending, reversible or recallable inbound transfer may affect initiation or completion.
8. Beneficiary Payout
Beneficiary payout may be made to a bank account, local account details, wallet or another expressly supported method.
The beneficiary may be subject to verification, limits, banking times, receiving-provider controls and local requirements.
9. Currency and Conversion
Where a transfer involves conversion, Bliim will display or facilitate the applicable exchange rate, quote, spread and fees before confirmation where required.
The exchange rate may change until the transaction is confirmed under the enabled flow.
10. Stablecoins and Digital Assets
Some corridors may use stablecoins or other digital assets as an internal or visible settlement leg. Where USDT, USDC or other supported assets are used, applicable wallet, stablecoin, blockchain-finality, network-fee and supported-network disclosures also apply.
Use of a stablecoin by a partner does not automatically make Bliim the issuer, custodian or regulated provider of the asset.
11. Estimated Timing
Displayed times are estimates unless law requires a specific commitment. Timing may depend on banks, cut-offs, time zones, weekends, holidays, blockchains, partner processing, compliance review and beneficiary availability.
A delay does not necessarily mean that funds have been lost.
12. Instruction Confirmation
Before confirming, the user must review the amount, currency or asset, beneficiary, country, delivery method, exchange rate, fees, bank or wallet details and any visible disclosure.
Once confirmed and transmitted, modification or cancellation may be limited or unavailable.
13. Accuracy of Details
The user is responsible for checking names, account numbers, IBANs, routing numbers, CLABE, references, wallet addresses, network, memo/tag and other required data.
Incorrect data may cause rejection, delay, return, credit to a third party or loss where the rail or network does not allow recovery.
14. Cancellation
Cancellation depends on transfer status, rail, partner and applicable law. Some transactions may be cancelled before transmission or settlement; others may not.
Bliim does not promise cancellation where the transaction is no longer technically or legally reversible.
15. Returns, Recalls and Rejections
A transfer may be returned or rejected because of incorrect data, a closed account, receiving-bank restrictions, compliance, sanctions, limits, technical issues or other legitimate reasons.
Returned amounts may be affected by FX, third-party fees or settlement differences where legally permitted.
16. Errors and Unauthorized Transactions
Errors, duplicates, unrecognized transactions or allegedly unauthorized transactions are handled under the Unauthorized Transactions & Error Resolution Policy and applicable law.
Technical irreversibility of one stage does not automatically eliminate legal rights that may exist.
17. Refunds and Remedies
Where a right to refund, cancellation, recall, reversal or reprocessing exists, the remedy depends on the product, partner, rail, processing status and applicable law.
The Refunds & Chargebacks Procedure supplements these Terms where relevant.
18. Fees
Bliim, partner, bank, network, correspondent, blockchain or other third-party fees may apply. Before confirmation, users will receive material fee information applicable to the flow where required.
A receiving or intermediary bank may impose charges not directly controlled by Bliim where the product structure permits.
19. Limits
Limits may depend on identity, country, currency, product, partner, history, risk, rail, regulation or operational availability.
Bliim may reduce, suspend or change limits where necessary for security, compliance, risk management or partner changes, subject to applicable law.
20. FX and Conversion Risk
Conversions may involve spreads, market movement and differences between quote time and settlement.
Where a quote is temporary, its validity or applicable condition will be displayed.
Users should not assume that a previously displayed rate will remain available.
21. Correspondents and Multiple Intermediaries
A corridor may use correspondent banks, payment processors, liquidity providers, custodians, blockchain providers or other entities.
Each intermediary may have its own controls and timelines without automatically making Bliim responsible for every regulated activity performed by third parties.
22. United States
In the United States, certain transfers may be subject to specific remittance, electronic-fund-transfer, money-transmission or other rules depending on the entity and actual flow.
Where a transaction is a covered remittance transfer, disclosures, cancellation/error rights and other protections applicable to the responsible provider will apply. Bliim does not automatically hold itself out as a remittance transfer provider.
23. Colombia
In Colombia, corridors may be subject to payment, FX, consumer-protection, digital-asset and reserved-activity rules depending on the specific structure.
Availability of COP, local account details or conversion does not mean Bliim is a supervised entity, foreign-exchange intermediary or deposit-taking institution unless expressly confirmed.
24. Mexico
In Mexico, transfers and payments may depend on financial institutions, IFPE/ITF entities, SPEI or other rails and authorized providers.
Bliim does not automatically hold itself out as a Financial Institution or SPEI participant merely because it integrates with a partner.
25. Spain and the EEA
In Spain and the EEA, application of PSD2, MiCA or other regimes depends on the nature of the transfer, the asset, the responsible entity and the service provided.
Bliim does not automatically hold itself out as a PSP, credit institution, electronic-money institution or CASP merely because it integrates third-party services.
26. Brazil
In Brazil, cross-border transfers may be subject to FX, payments, virtual-asset, consumer-protection and responsible-provider requirements. Where a route uses Pix, Pix participation belongs to the applicable authorized or participating institutions.
Bliim does not hold itself out as a Pix participant, financial institution, payment institution or authorized Brazilian virtual-asset service provider merely because it provides an interface or integrates a partner.
27. Blockchain Networks
Where a transfer includes an on-chain leg, users must use only the asset, network and address expressly supported. Blockchain finality may make technical cancellation impossible once the applicable state is reached.
Network, wrong-address, wrong-network and gas risks are also governed by the applicable specific disclosures.
28. Security and Fraud
Bliim may apply MFA, device controls, fraud screening, velocity checks, behavioral monitoring or other reasonable controls.
Users must protect credentials, OTPs, devices and wallets and report suspicious activity promptly.
29. Suspension or Rejection
Bliim or a partner may reject, pause or suspend a transaction because of regulatory restrictions, sanctions, AML, fraud, security, limits, errors, unavailability, missing documentation or breach of terms.
Where legally permitted, Bliim will seek to communicate appropriate status information without disclosing protected compliance information.
30. Complaints and Recourse
Complaints are handled under the Complaints & Claims Policy. The applicable authority, ombudsman, ADR or external route depends on the specific entity and service.
An authority will not be presented as competent where that competence has not been confirmed.
31. Privacy and Data
A cross-border transfer may require sharing data with partners, banks, providers, beneficiaries, networks and authorities where necessary and legally permitted.
Data processing is governed by the Global Privacy Policy and applicable obligations of each participating entity.
32. Evidence and Traceability
Bliim may retain reasonable evidence of the instruction, user identity, beneficiary details, quote, fees, consents, timestamps, transaction IDs, partner routing, status, communications and final outcome in accordance with applicable policies.
33. Updates and Conditional Activation
These Terms are ready for publication as a general framework. A specific corridor will only be available when its partner, responsible entity, rail, limits, fees, rights, disclosures and production configuration are enabled.
The published version and effective date identify the applicable text.
34. Contact
For transfer support, contact [email protected]. For legal questions, contact [email protected].