Webshop Terms

Operator: Stichting Outpapier, identified by Operator ID b4np (“Operator”, “we”, “us”)
Applies to: purchase, holding, gifting, transfer, and spending of BIT delivered to a Bitcash Wallet
Effective / last updated: 2026-03-25

Trademark notice. Bitcash® is a registered trademark of Roberto Bourgonjen (the “Bitcash Mark”). The Operator uses the Bitcash Mark under license. References to “Bitcash”, “Bitcash Wallet”, and “BIT” in these terms refer only to the official Catalog/Bitcash ecosystem.

These terms apply when you acquire BIT directly from the Operator (including by purchase through the Operator’s webshop) and when you use BIT to access Operator-operated Catalog services and content. If you acquire BIT from a third-party reseller, the reseller’s own webshop terms govern that purchase; however, these terms still apply to your use of BIT on Operator-operated services. These terms supplement the applicable Catalog EULA and Cloud Services Terms, and (if you use catalog.id features) the Catalog.ID Membership Agreement. If there is a conflict, these terms control only for BIT purchase and use.

1) Key definitions

1.1 BIT (BIT tokens)

BIT means prepaid service credits recorded in the Operator’s systems that represent a limited contractual right against the Operator to consume eligible units of the Operator’s Catalog services (for example: uploads, downloads, storage, API usage, publication actions, compute/transcoding tasks, and other metered service units), as described in the Operator’s then-current fee schedule or pricing page (“Fee Schedule”). See Bitcash Whitepaper for a full description of the Bitcash prepaid micropayment system.

  • BIT is prepayment for services (an IOU for service performance), not money.
  • BIT is not a bank account, deposit, e-money, or investment product and does not bear interest.
  • The Operator does not redeem BIT for cash and does not offer cash-out/buyback.

1.2 Bitcash Wallet / Wallet Code (bearer wallet)

A Bitcash Wallet is an official wallet format used in the Catalog/Bitcash ecosystem.
A Bitcash Wallet is identified by a Wallet Code in the format:

{operator_id}-XXXX-XXXX-XXXX-XXXX-XXXX (4-character Operator ID + 20 characters + 5 dashes)
Example for the Operator: b4np-te56-1234-5678-90ab-cdef

A Wallet Code is bearer-style: possession of the Wallet Code is sufficient to use the BIT balance associated with it. The Operator cannot reliably determine the “true owner” of an anonymous wallet.

1.3 Official BIT only; no third-party tokens

The Operator accepts and accounts for only the official BIT delivered through Bitcash Wallets under the Catalog/Bitcash ecosystem. The Operator does not accept substitute tokens, vouchers, or third-party “bits”, and the Operator does not issue its own branded alternative to BIT.

2) Delivery, holding, and spending

2.1 Delivery

BIT purchased from the Operator is delivered to a Bitcash Wallet (Wallet Code) as shown to you at checkout and/or in your purchase confirmation.

2.2 No account required for basic spending

To spend BIT for basic access on supported Operator-operated websites and services, no account is required. Where supported, you may enter your Wallet Code in your browser to load the wallet and spend BIT.

2.3 Automatic spending; phishing warning

Entering a Wallet Code on a website enables automatic spending without per-transaction confirmation.

Treat your Wallet Code like cash. Only enter it on websites you trust and that you intend to authorize. If you enter the code on a phishing or malicious site, the balance may be spent without further confirmation.

2.4 What BIT pays for; no transfer of rights in content

When you spend BIT to access content or files — for example, to view an image, watch a video, listen to audio, download a file, or otherwise consume media made available through Operator-operated services — the BIT you spend is paid solely for the service of making that file accessible to you (e.g., storage, delivery, streaming, transcoding, bandwidth, and related technical services).

Spending BIT does not transfer any ownership, copyright, or other intellectual property rights in the content, and does not grant you any license beyond the limited, personal right to access and consume the content as permitted by the applicable Catalog EULA and Cloud Services Terms, the rights holder's terms, and applicable law. No right of reproduction, redistribution, public performance, modification, or commercial exploitation is granted by the act of spending BIT.

If you wish to use accessed content for any non-personal purpose (for example, redistribution, republication, public performance, commercial use, or incorporation into other works), you must first contact the rights holder — typically via the contact details published on the site where the content was made available — and obtain written permission from the author or rights holder before doing so. Spending BIT does not substitute for, and does not constitute, such permission.

Access may be time-limited, session-limited, or otherwise restricted as described at the point of access. Once BIT is spent to obtain access, the BIT is consumed in exchange for the access service rendered, regardless of whether you actually view, play, or download the content.

If the Operator's systems fail to deliver a service for which you have already paid with BIT — for example, a stream that terminates unexpectedly, a corrupted download, or an API request that is not served — the spent BIT is not returned to your wallet. BIT refunds are not available as a remedy, because the Operator is not permitted to transfer BIT to end users except by sale (see Bitcash Whitepaper §5.1 and §5.11). Instead, the Operator may record an internal service-level credit against your Wallet Code or account and fulfil a subsequent equivalent request from that credit without issuing a new BIT charge. Where mandatory consumer law requires a monetary refund that an internal service-level credit does not satisfy, the Operator will refund the price paid in EUR through the original payment provider used at the point of sale; contact [email protected] with your order details.

2.5 Ecosystem-scoped spending

BIT acquired from the Operator is spendable on Operator-operated services and content and, under the Catalog/Bitcash ecosystem's mandatory federation arrangement (see Bitcash Whitepaper §8), on the services of every other licensed Operator in the ecosystem, unless a specific cross-operator path is suspended for legal or compliance reasons.

3) Gifting and sending BIT to others

3.1 Do not share your Wallet Code

Your Wallet Code is a bearer instrument: anyone who possesses it can spend the entire balance. The Operator cannot reverse spending or recover bits taken by someone you have shared the code with. Sharing your Wallet Code as a way to "gift" bits is dangerous and is not the intended mechanism. Treat your Wallet Code like a private password.

3.2 Use Gift Vouchers or Demo Wallets to send BIT

If you wish to send BIT to another person, use one of the following mechanisms provided by the official Bitcash Wallet software:

  • Gift Voucher (Bitcash Whitepaper §5.6) — a single-use bearer instrument you create from your own balance. You share only the voucher's code (not your own Wallet Code) with the recipient, and the recipient drains the voucher into a wallet of their own. Gift Vouchers are reclaimable by you at any time before redemption, and any unredeemed balance returns to you automatically after one year.
  • Demo Wallet (Bitcash Whitepaper §5.7) — a single-use bearer instrument bound to one specific (web)site, allowing the recipient to consume services on that site at your expense. You choose the expiration term at creation (from 1 day to 1 year); the Demo Wallet expires at the end of that term regardless of activity, and any unspent bits return to you.

Both mechanisms keep your own Wallet Code private and allow refund of bits the recipient does not consume. Once a Gift Voucher has been redeemed or a Demo Wallet's bits have been consumed at the chosen site, the transaction is final.

3.3 Gift Vouchers and Demo Wallets are free gifts — no charge or obligation permitted

Gift Vouchers and Demo Wallets are strictly gratuitous gifts. You may not sell, offer for purchase, or exchange a Gift Voucher or Demo Wallet for money, services, goods, or any other form of consideration. You may not require or solicit any counter-performance, obligation, or reciprocal commitment from the recipient as a condition of receiving, redeeming, or using a Gift Voucher or Demo Wallet. If a third party demands payment or any form of consideration in exchange for a Gift Voucher or Demo Wallet, that demand is unauthorized and contrary to these terms.

If you wish to sell BIT — for example, so that you can receive BIT back as payment for your own content or services — you must register with the Operator as a reseller. Resellers operate under a separate Reseller Agreement that governs inventory purchase, distribution, pricing, and compliance obligations. Contact [email protected] for more information.

3.4 Non-refundability

Bits sent via a Gift Voucher are reclaimable by you only until the moment of redemption; once the recipient has drained the voucher, the bits belong to them and cannot be reclaimed. Bits consumed from a Demo Wallet at the chosen site are likewise final once spent. Webshop purchases of BIT are non-refundable once delivered to your wallet, except where mandatory consumer law requires otherwise.

4) Expiration

4.1 How expiration works

The expiration term of BIT in a wallet is determined by the source of the most recent dominant top-up to that wallet. The wallet's effective expiration is last_activity + term, so any transaction the wallet participates in (a top-up, a service payment, or a wallet operation) resets the activity timer and extends the effective expiration. Demo Wallets are an exception: a Demo Wallet's expiration is fixed at creation and is not reset by activity — the Demo Wallet expires exactly at the end of the term chosen by the issuer. The full credit policy is described in the Bitcash Whitepaper §5.8.

4.2 Default terms by source

  • BIT credited by the Operator (direct sale): default term 10 years.
  • BIT credited by a reseller (reseller sale): default term 1 year.
  • BIT in a Gift Voucher: default term 1 year.
  • BIT in a Demo Wallet: 1 day to 1 year (chosen by the issuer at creation; fixed from creation, not reset by activity).

The default return wallet is the source of the credit, so expired BIT flows back to the seller (or to the issuer of a voucher / Demo Wallet) via the cascade mechanism described in the Whitepaper §5.8.

4.3 Dominance rule

When a wallet receives a top-up from a different source, the new term and return wallet take effect only if the new top-up is dominant — that is, the credited amount is at least three times the wallet's existing balance. A smaller top-up adds to your balance and resets the activity timer but does not change the term or return destination. This means a small top-up from a reseller does not displace an existing 10-year Operator term, and a small top-up from the Operator does not extend an existing 1-year reseller term. Only a dominant top-up (3x or more of the existing balance) rewrites the term and return destination.

4.4 Regulatory override

If the Operator is required by law or a competent authority to apply a different treatment (for example, a longer minimum validity period), the Operator will publish notice on its website where permitted.

5) Loss, theft, and recovery (important)

Because Wallet Codes are bearer-style, anyone with the Wallet Code can spend the balance.

  • If you lose the Wallet Code, you may lose access permanently.
  • If someone else obtains your Wallet Code and spends BIT, the Operator may be unable to prove misuse or restore the balance.
  • The Operator does not guarantee recovery of anonymous wallets or reversal of spending.

The Operator may investigate credible fraud reports, but you acknowledge that the bearer design limits what the Operator can do.

5.2) Wallet ownership and payment records

If you purchase BIT via the Operator’s webshop, payment processing may be handled by a third-party payment provider (such as Mollie). The Operator may retain order records and transaction references and may be able to make a reasonable assessment that a particular Bitcash Wallet Code was delivered as part of a specific purchase.

However, Bitcash Wallets are bearer-style: the person who controls and uses a Wallet Code may be different from the person who paid for it (for example, due to gifting, sharing, resale, or compromise). The Operator therefore cannot guarantee definitive determination of the current owner/controller of a Wallet Code based on payment records alone.

5.3) Anonymous spending

Where you spend BIT by entering a Wallet Code without logging in, the Operator does not associate the accessed content to your personal identity in the same way as an account-based session. The Operator may still process technical/operational logs for security, abuse prevention, and service delivery, but such logs may not identify you as an individual unless you provide identifying information.

6) Fees, pricing, and changes

6.1 Purchase price and Fee Schedule

The price you pay for BIT is displayed at checkout. The service consumption rate (what actions cost in BIT) is set out in the Operator’s Fee Schedule and may vary by service, content type, and plan.

6.2 Platform fee and network fee

Distribution is fee-free. No fees are charged when you purchase BIT — whether from the Operator or from a reseller. The full amount is delivered to your wallet.

Usage incurs fees. When you spend BIT on services or content, or transfer BIT to another wallet, the following fees apply:

  • A platform fee of 0.1% is deducted and permanently destroyed (burned).
  • A network fee of 2% is deducted from transactions in which the Operator is not a party (for example, content payments to a reseller) and is credited to the Operator's pool to fund network infrastructure.

Whether a fee is deducted from the transferred amount or added on top depends on the transaction type and is specified in the Fee Schedule. See the Bitcash Whitepaper §§6.4–6.6 for full details.

6.3 Changes

The Operator may change the Fee Schedule with reasonable notice, except where urgent changes are required for security, fraud prevention, or legal compliance.

7) Refunds and right of withdrawal (EU/Netherlands)

7.1 General rule

Where you are a consumer, you may have a statutory right of withdrawal for online purchases.

7.2 Digital delivery acknowledgement

BIT is delivered digitally and can be spent immediately. Where lawful, the Operator may ask you at checkout to:

  • request immediate delivery of BIT, and
  • acknowledge that your right of withdrawal may be limited or lost once delivery/performance begins.

7.3 Refund policy

BIT is delivered digitally and can be spent immediately. By consenting to immediate delivery at checkout (see §7.2), you acknowledge that your right of withdrawal is lost once BIT is delivered to your wallet.

Unless mandatory consumer law requires otherwise, BIT purchases are non-refundable once delivered.

If you believe a refund is legally required in your circumstances, contact [email protected] with your order details.

8) Prohibited use and enforcement

You must not use BIT or Wallet Codes to:

The Operator may restrict, freeze, or refuse spending of BIT associated with a wallet where required by law, court order, or where the Operator reasonably suspects fraud, theft, or abuse of the services.

9) Liability and governing law

The limitation of liability and disclaimer provisions in the Catalog EULA and Cloud Services Terms §§15–16 apply to BIT purchases and use under these terms. These terms are governed by the laws of the Netherlands (excluding conflict-of-law rules). The dispute resolution procedure in the Catalog EULA and Cloud Services Terms §21 applies to disputes arising from these terms, unless mandatory consumer law requires otherwise.

10) Contact

Support: [email protected] (Stichting Outpapier)

End of Webshop Terms.