Common rules for funding, instructions, pricing, costs, product-specific obligations, records, errors and closure.
Version 2.0Updated 15 Jan 202612 sections
In this documentexpand_more
1. Services and document hierarchy
Benzig Jwelsg Digital Solutions N.V., registration number 548658, registered address Zuikertuintjeweg Z/N, Willemstad, Curaçao provides the account-based services described in the Legal Center. These common terms apply alongside the Terms of Use and the relevant Wallet, Investor, Loan or Liquidity agreement. The valid individual confirmation identifies its specific financial terms. A marketing summary or screen label does not override mandatory law, a valid accepted schedule or a more specific disclosed transaction condition.
2. Balances, reservations and segregation
An account can show main funds, reserved funds, staking, shares, dedicated loan repayment funds, liquidity balances and pool positions. Their availability and risks differ. Internal accounting separation is not a representation of statutory asset segregation or a bank guarantee. A combined USDT estimate must not be mistaken for cash available to withdraw. Only an authorised product instruction may move or reserve the relevant balance.
3. Instructions, authority and final checks
Review the asset, amount, network, destination, price, fee and product consequences before confirming. Submission authorises the described action, subject to final validation and any mandatory additional acceptance. A preview is not execution. We may reject an instruction for insufficient available funds, stale pricing, invalid details, unsupported assets, lawful restrictions or technical conditions. A rejection must not be represented as a completed transaction.
4. Execution states and receipts
Pending, reserved, partially filled, broadcast, confirmed, cancelled and settled describe different events. Use the relevant transaction, order, loan or operation reference and resulting account history to establish the outcome. A lost response may follow a successful action. Resolve an uncertain existing request before creating another instruction; duplicate protection does not merge independently confirmed transactions. An acknowledged cancellation applies only to the part still cancellable.
5. Prices, estimates and execution differences
Reference market prices, direct-buy prices, pool reserve prices and USDT estimates have different sources. They need not equal an external exchange quote or actual exit proceeds. A price chart contains closing observations for its periods, not every executable bid or ask. Slippage, spread, premium, market depth and processing time can change the total result. An accepted limit or minimum-output condition should be applied as disclosed for that product.
6. Fees, interest and changes in costs
Check Fees and the individual review screen for the current network fee, product charge, direct premium, periodic loan interest or pool fee. A low fee is not a guarantee of a low total cost. Future schedule changes must be communicated before the affected instruction; a general update does not silently reprice an already accepted fixed obligation. Taxes, external-provider costs and any disclosed recovery work are separate where applicable.
7. Product-specific obligations
Wallet users must use supported networks and authorised destinations. Investors accept market and distribution uncertainty under the share terms. Borrowers remain responsible for the agreed borrowed-asset repayment schedule and the disclosed currency restriction. Liquidity providers accept reserve-ratio exposure, quote conditions and possible divergence loss. A gain, referral credit or balance in one product is not a promise to discharge obligations in another.
8. Errors, reconciliation and fair corrections
Report unexpected debits, missing credits, duplicate instructions or inconsistent schedules with supporting references. We must review relevant records and explain a substantiated correction where lawful. A clear mistaken credit may be restricted pending review, but a correction is not an unlimited confiscation power or authority to debit unrelated funds without a legal basis. A user’s reporting delay does not remove a mandatory legal claim period.
9. Networks, service interruptions and force majeure
Network congestion, forks, external-provider failures, attacks, legal measures and events outside reasonable control can impair performance. The affected party should take reasonable mitigation and restoration steps and communicate available information. Such events do not automatically erase ownership records, excuse every preventable internal failure or cancel an already received repayment. Availability notices and Network Status are informative and not guarantees that every transaction will complete immediately.
10. Restrictions, termination and remaining balances
Product suspension or account termination must address open orders, existing loans, reserved amounts, pool units, surplus repayments and legally restricted funds. A lawful return or reconciliation route should be provided for assets available to return, subject to verification, supported networks and legal holds. Existing valid debts and claims survive to the extent required by their agreement and law. Account inactivity alone does not transfer your assets to the Operator.
11. Liability, mandatory rights and legal classification
The responsibility safeguards in the Terms of Use apply. No statement excludes non-waivable rights or liability, promises universal insurance, or treats a corporate registration as financial authorisation. Crypto-assets, profit-participation products, custody and lending may be governed differently in different jurisdictions. Curaçao law applies only so far as a valid choice permits and does not displace mandatory protections, lawful supervisory powers or access to competent courts.
12. Records, changes and complaints
Keep the applicable legal version and individual transaction records. Material changes need clear prospective notice and any required acceptance; historical copies help identify text but are not proof of consent. Contact Support with transaction references and the remedy requested. The Complaints Policy describes review and escalation without requiring surrender of mandatory rights. Service communications should not ask for authentication secrets or payment to an unsolicited recovery intermediary.
