Risk Disclosure

This Disclosure identifies material risks but cannot describe every circumstance. A business should assess its legal duties, treasury needs, loss tolerance, technical capability, customer obligations, and tax position, and obtain independent professional advice. A product preview or demo is not a recommendation to transact or borrow.

A feature may be unavailable or restricted by jurisdiction, customer profile, asset, network, provider, regulation, or operational readiness. Law and regulatory classification can change. A regulator's AML registration, where applicable, is not the same as authorisation of solvency, a lending product, an investment, or the proposed Vault.

• Digital-asset prices may change sharply and liquidity may disappear.
• A stablecoin can lose its reference value, suspend redemption, freeze an address, change terms, or fail.
• Issuer, reserve, governance, smart-contract, bridge, key, and market risks differ by asset and network.
• Digital assets are not Costa Rican legal tender and must not be assumed to carry bank-deposit protection.

Blockchain instructions may be irreversible. A wrong address, asset, network, tag, memo, amount, or beneficiary can cause permanent loss. Confirmation can be delayed or reorganised, network fees may change, and a network can halt, fork, congest, or reject a transaction. Payfux may wait for evidence and reconciliation before credit or release.

The applicable product terms must identify the custody and asset-control arrangement. Loss may arise from an authorised user, compromised credential, service-provider failure, insolvency, legal seizure, operational error, or an unavailable signing or network service. Segregation, reuse, insurance, and recovery rights must not be assumed unless expressly stated in the signed product terms.

Card, bank, conversion, and settlement services can be affected by disputes, reversals, fraud, reserves, scheme or provider rules, exchange-rate movement, reconciliation differences, or delayed review. A displayed state may change when reliable new evidence arrives. Operators remain responsible for truthful customer balances, payouts, refunds, and chargeback handling.

A Bankroll application does not ensure an offer. If financing is later offered, it creates a repayment obligation and may include fees, collateral, covenants, reserve requirements, or consequences of default stated in the separate agreement. Using financing to raise player or customer limits can increase payout, liquidity, concentration, fraud, and responsible-gaming exposure.

Payment volume is not the same as profit or repayment capacity. Currency or digital-asset movement can increase the real cost of a facility. The applicant should model stressed payouts, reduced processing volume, disputes, and loss of a licence or provider before accepting an offer.

The Vault is not currently available. The public preview does not accept funds or create a right to a return. The proposed design refers to eligibility above $10,000, 12% APY, daily credits, and a 48-hour release period. Those are proposed parameters subject to legal, regulatory, financial, and operational approval.

If a lawful version is later launched, risks may include loss of principal, insufficient program revenue, counterparty or borrower default, liquidity constraints, delayed or suspended release, rate change, accounting error, stablecoin loss of value, tax, insolvency, and a change in law. The intended revenue source—realised transaction-fee and financing income—would need documented backing and may be insufficient. Customer principal must not be represented as protected merely because the return is described as revenue-funded.

APY is an annualised figure that assumes compounding under a stated convention. A 12% APY with daily compounding is not calculated as 12% divided by 365; the equivalent daily factor is approximately 0.03105%. Any live product must state the rate version, eligible balance, asset, calculation precision, cutoff timezone, rounding and remainder treatment, credit frequency, whether credits compound, and when a release request becomes available.

Outages, configuration errors, unavailable dependencies, stale data, duplicated requests, misunderstood webhook states, or failed reconciliation can affect an integration. Customers should use idempotency, verify signed instructions where supported, maintain their own records, test failure states, apply role separation, and avoid treating a demo or client display as the sole accounting authority.

The customer is responsible for its licences, consumer and gaming duties, sanctions and AML controls, privacy notices, accounting, tax, and the legality of offering services into each market. Costa Rican terms cannot displace mandatory laws in another jurisdiction. Digital-asset, financing, and return treatment may differ by country and can change.

Payfux product information is general business information, not legal, tax, accounting, investment, credit, or responsible-gaming advice. A customer must make its own decision and should consult qualified advisers before enabling digital-asset payments, accepting financing, or considering any future Vault terms.

Ask product-risk questions or report a suspected loss through [email protected]. Include the relevant reference and a safe contact method. Do not send private keys, passwords, recovery phrases, or identity documents through ordinary email.