USR-011 — TÉRMINOS DE BLIIMPAY / PAGOS P2P BliimPay / P2P Terms
- Entidad / Entity
- BLIIM GLOBAL LLC — Delaware, United States
- Documento / Document
- Términos de BliimPay / Pagos P2P / BliimPay / P2P Terms
- ID
- USR-011
- Versión / Version
- V1.1
- Fecha de vigencia / Effective date
- 7 de octubre de 2026 / 7 October 2026
- Estado / Status
- PUBLICATION FINAL — ACTIVATION CONDITIONAL
- Ámbito / Scope
- App, web y funcionalidades P2P expresamente habilitadas / App, web and expressly enabled P2P functionality Soporte / Support [email protected] Legal [email protected]
- PRINCIPIO CENTRAL / CENTRAL PRINCIPLE
- La capacidad técnica de enviar o recibir valor entre usuarios no implica disponibilidad jurídica universal, settlement inmediato, irreversibilidad absoluta ni una asignación automática de responsabilidad a Bliim. Cada flujo P2P depende del producto, país, partner, rail, moneda o activo, límites, controles de seguridad y régimen aplicable.
Technical ability to send or receive value between users does not imply universal legal availability, immediate settlement, absolute irreversibility or automatic allocation of liability to Bliim. Each P2P flow depends on the product, country, partner, rail, currency or asset, limits, security controls and applicable legal regime.
1. Purpose and Scope
These Terms govern access to and use of any user-to-user sending or receiving functionality expressly enabled by Bliim under the BliimPay, P2P or equivalent name.
They apply only to the flow actually enabled for the user, country, product, currency or asset, partner, rail and relevant configuration.
2. Relationship with Other Terms
These Terms supplement the General Terms of Use, Global Privacy Policy, Acceptable Use Policy, applicable wallet/stablecoin, transfer, account or card terms, the Fee, Limits & FX Disclosure and relevant partner terms.
Mandatory law prevails over any incompatible contractual provision.
3. Bliim's Role
Bliim primarily provides the technology layer, interface, orchestration and connectivity allowing a user to initiate, view and manage a P2P instruction when enabled.
The existence of BliimPay/P2P does not by itself mean that Bliim is a bank, electronic-money issuer, money transmitter, remittance transfer provider, custodian, payment institution or regulated financial entity.
4. Third-Party Functions
Where a transaction requires receipt, holding, custody, transmission, conversion, settlement or another regulated activity, that function may be performed by an entity other than Bliim.
The identity and role of the partner may vary by country, product and rail.
5. Eligibility
Access may depend on age, residence, location, account type, KYC/KYB, verification level, currency or asset, history, limits, sanctions, risk and partner availability.
An active Bliim account or completed KYC does not guarantee P2P eligibility.
6. Availability by Country and Product
BliimPay/P2P may be available only in certain countries, states, territories, currencies, assets or user profiles.
Appearance of the feature in an interface does not constitute a universal offer or guarantee permanent availability.
7. P2P Model
The product may use internal transfers, instructions involving wallets or accounts maintained by third parties, payment rails, blockchains or other mechanisms.
Bliim will not describe a transfer as “instant” , “final” , “internal” or “on-chain” unless the actual flow supports that description.
8. Recipient Identification
A recipient may be identified by displayed name, alias, phone number, email, internal identifier, account, wallet address or another enabled identifier.
The identifier used does not by itself constitute absolute proof of legal identity.
9. Sender Verification
Before confirmation, the sender must review the recipient, amount, currency or asset, fee, exchange rate where applicable and any other material information displayed.
Sending value to the wrong person or identifier may result in a transfer that is difficult or impossible to recover.
10. Initiation and Authorization
An instruction is treated as initiated when the user completes the required confirmation mechanism and the corresponding transactional event is created.
Selecting a recipient, entering an amount or viewing a quote does not necessarily constitute an executed order.
11. Authentication
Bliim may require a password, OTP, MFA, biometrics, device verification or other controls before authorizing a transaction.
Authentication level may vary by amount, risk, device, country, rail or partner requirement.
12. Pre-Confirmation Information
Before confirmation, the app may display recipient, amount, currency or asset, fees, FX/spread, total amount, estimated amount received, estimated timing, status and relevant warnings.
Where pricing is dynamic, the quote shown at the decision point is the applicable quote.
13. Fees, FX and Limits
Applicable fees, spreads, exchange rates and limits are governed by the Fee, Limits & FX Disclosure and the information shown in the transaction flow.
Limits may vary by user, country, asset, currency, partner, risk, rail or regulation.
14. Sufficient Funds or Assets
The user must have sufficient and usable funds or assets to complete the transaction, including applicable fees.
A displayed balance may be subject to holds, pending status, settlement, screening or other restrictions.
15. Transaction Status
A transaction may be shown as created, pending, under review, processing, completed, rejected, failed, cancelled, reversed or an equivalent status.
The exact meaning depends on the applicable rail and partner. A visible status should not be interpreted outside its context.
16. Settlement and Finality
Settlement and finality may occur at different times. A transaction may appear processed before all external systems have completed settlement.
On blockchain, technical finality may occur before or after internal crediting.
17. Cancellation
Cancellation capability depends on transaction status, rail, partner and applicable law. Once the point of irrevocability is reached, cancellation may no longer be possible.
Bliim does not guarantee cancellation where the flow no longer permits technical or legal reversal.
18. Reversals and Returns
A reversal may occur because of rejection, technical failure, compliance, invalid account information, partner action or another permitted reason.
A technical reversal is not necessarily the same as a contractual refund or a liability determination.
19. Wrong Recipient
If a user sends value to the wrong recipient, Bliim may attempt to facilitate recovery where reasonably possible, but does not guarantee that the recipient or a third party will return the funds or assets.
Any legal right to a remedy depends on the facts and applicable law.
20. Errors and Unauthorized Transactions
Duplicated, incorrect, unrecognized or allegedly unauthorized transactions are handled under the Unauthorized Transactions & Error Resolution Policy.
Successful authentication does not by itself determine legal liability.
21. Fraud, Scams and Social Engineering
Users should verify payment requests and recipients. Induced scams, impersonation, phishing or social engineering may involve transactions technically authorized by the user under deception.
Bliim may apply anti-fraud controls and restrict or review suspicious activity.
22. AML, Sanctions and Monitoring
Transactions may be subject to sanctions screening, transaction monitoring, source-of-funds review and other AML/KYC controls.
Bliim or a partner may reject, freeze, delay or review a transaction where a legal, contractual or risk basis exists.
23. Privacy and Data
To resolve recipients, execute transactions, prevent fraud or comply with law, Bliim may process and share data with partners, institutions, providers and authorities where appropriate.
Processing is governed by the Global Privacy Policy and applicable law.
24. Stablecoins and Digital Assets
Where P2P uses USDT, USDC or other supported digital assets, the applicable stablecoin, finality, network-fee and unsupported-asset/network disclosures also apply.
Users must use only the asset and network expressly enabled.
25. Blockchain Networks
An on-chain transfer may become irreversible after reaching a certain state. Errors involving wallet address, network, memo/tag or asset representation may cause loss or non-crediting.
Technical recovery, where possible, is not guaranteed.
26. Receipts and Notifications
Bliim may issue receipts, transaction IDs, notifications or tracking statuses. Users should review the information and report inconsistencies promptly.
A processing notification does not always mean final settlement.
27. Support and Complaints
General complaints are handled under the Complaints & Claims Policy; errors and unauthorized transactions are handled under the specialized policy.
The support channel is [email protected].
28. United States
In the United States, certain P2P flows may be subject to electronic-fund-transfer, remittance or money-transmission rules depending on the responsible entity and actual architecture.
Bliim does not automatically hold itself out as a financial institution or money transmitter merely because it provides a P2P interface.
29. Spain and the EEA
In Spain and the EEA, where the flow falls within the applicable payment-services regime, specific rules concerning consent, authentication, unauthorized transactions and irrevocability may apply.
Bliim does not automatically hold itself out as a PSP, electronic-money institution or CASP merely because it integrates a third-party service.
30. Colombia
In Colombia, treatment depends on the product and the entity performing the regulated function.
Consumer-protection, channel-security and unrecognized-transaction rules may be relevant.
Bliim does not hold itself out as supervised by the Colombian Financial Superintendence merely because it integrates a supervised partner.
31. Mexico
In Mexico, the rail, nature of the account or wallet, responsible entity and user rights must be assessed based on the specific flow.
Bliim does not automatically hold itself out as a Financial Institution or ITF merely because it enables P2P.
32. Brazil
In Brazil, P2P functionality may involve payment, Pix, virtual-asset, consumer-protection, AML and responsible-institution rules.
Where Pix is used, Pix participation and execution belong to the applicable participating institutions. Bliim does not hold itself out as a Pix participant, financial institution or payment institution merely because it provides the interface.
33. Changes and Availability
Bliim may modify, suspend or withdraw P2P because of regulatory change, security, fraud, partner changes, risk, maintenance or operational reasons.
Historical support does not create an obligation to maintain the functionality indefinitely.
34. Conditional Activation and Contact
These Terms are ready for publication as a contractual framework. A specific P2P flow will be activated only when the partner, rail, country, currency or asset, fees, limits, error routing, privacy/data sharing and production configuration are enabled.
Support: [email protected]. Legal: [email protected].