Bituce · Legal

Cross Import & Existing Debt Terms

Import an approved external asset and debt record, review a repayment schedule, and retain a copy of your acceptance.

Version 1.4Updated 3 Nov 20269 sections

In this document

1. Purpose and parties

These terms supplement the platform, wallet and loan terms for Cross Import provided by Benzig Jwelsg Digital Solutions N.V., registration number 548658, Zuikertuintjeweg Z/N, Willemstad, Curaçao (Operator). Cross Import records an existing external debt and separately identified transferable assets. It is not a new cash advance, an on-chain bridge or a second payout of the borrowed principal.

2. Approved source record

An import is available only for a source record entered and enabled by the Operator. The record identifies the external platform, source reference, contact details, debt asset and outstanding amount, credited assets, available periodic rates and permitted repayment terms. The Operator must establish its authority to administer the record and the applicable transfer basis before making it available. A matching key alone does not establish legal ownership, assignment or identity.

3. External platform key and contact details

Use only the import key supplied for the external platform record. Never submit a blockchain private key, seed phrase, exchange API secret or unrelated password. The email must match the approved record. You must provide a contact phone number, but the Operator may leave the source phone blank and your number is not matched against it or verified by SMS or call. Providing contact details is not an identity check or a replacement for any applicable identity checks. Keep the key confidential; each source record can be imported once.

4. Review and disputed information

Read the source details, credited assets and outstanding debt before confirming their accuracy. If any information, source authority or balance is disputed, stop and contact support with the source reference. Do not confirm a record you do not recognize. Confirmation does not waive mandatory rights, existing legal defenses or the right to report an error, and does not by itself prove that an external creditor has discharged its claim.

5. Chosen repayment plan

One import may contain several separate loans. For every loan the accepted quote identifies its borrowed currency, opening principal, credited collateral currency and quantity, separately chosen weekly or monthly frequency, installment count, periodic rate, dates, total interest and total repayment. Several loans may share one collateral asset; its quantity is credited once, not once per loan. Different currencies are not added or converted. Existing debt is not credited again. Only disclosed future interest is added; no undisclosed historical penalty or collection fee is introduced. The final installment absorbs rounding to eight decimals.

6. Single-use import and failure handling

Final confirmation creates every loan and schedule, collateral linkage, the single set of wallet credits and history entries, and the acceptance record in one transaction. Different-currency loans also receive their own external repayment address. A loan in the same currency as its collateral uses the main-wallet payment exception and does not require a new external repayment address. No new loan payout occurs. Repeated confirmation does not duplicate credits or loans. Failure of any required loan, address or credit rolls back the entire import. Changed source data, agreements or expired quotes require fresh review.

7. Repayment and account restrictions

For Cross Import, each loan is backed by the imported collateral identified in its accepted summary. Only that collateral currency is restricted for withdrawals and main-wallet liquidity funding until all loans backed by it, including applicable interest, are fully repaid. A different borrowed currency does not independently restrict that main wallet. Main-wallet installment payment is permitted only when the loan and its actual imported collateral use the same currency. A matching balance in an unrelated main wallet does not qualify; other-currency loans must be repaid externally in their borrowed currency. Wallet payments require an explicit instruction for the earliest unpaid installment and create linked ledger and account-history records without conversion or a blockchain transfer. External payments must reach the loan's displayed address in the borrowed currency and supported network. Prepared early-payment reductions remain applicable. Partial payment or closing one of several loans backed by the same collateral does not release its lock; unrelated holds can remain after full repayment. No automatic liquidation or undisclosed late fee is introduced.

8. Electronic records and corrections

The Operator retains the source record, accepted quote, contract texts and their versions and hashes, time of acceptance, wallet credit ledger and related loan identifiers. Imported assets appear as completed internal deposits in the relevant currency history and account History, identified by a Cross Import reference. An internal credit has no blockchain transaction hash. Repayment deposits appear separately under the loan’s repayment account. Authorized corrections or refunds create separate history entries and do not overwrite the original records. Report suspected mistakes through support; corrections preserve an audit trail and cannot justify reusing a source record.

9. Relationship with other terms

For this import, these terms and the accepted individual quote govern the existing-debt nature, absence of payout and import-specific rates and term. Wallet custody and operation follow the Wallet and Asset Management Terms; remaining loan rules apply where consistent. No statement here represents that the Operator holds a financial-services license, that funds are insured, or that every external platform obligation has been assumed. Mandatory law and non-waivable rights remain unaffected.

Document copy

Benzig Jwelsg Digital Solutions N.V. · 548658

Zuikertuintjeweg Z/N, Willemstad, Curaçao

Version 1.4 · Updated 3 Nov 2026

Document identifier (SHA-256): 42737948251d65ca10d2dcebc92a95fa0a93ee259095047c1289f9a9ea9bd45e