Cryptocurrency Payment Terms — Discussion Draft

UplitAU Pty Ltd  —  Door 1 example: DEMI Landing Page issuance / Portal Activation Code

Prepared 21 June 2026

This is a discussion draft, written for you to read and understand — not a published legal document, and not legal or financial advice. Before this goes live anywhere, it should be reviewed by an Australian solicitor or accountant, particularly the AUSTRAC and tax sections below. It is built to be transparent and readable first, polished second.

1. What this document is for

This sets out, in plain terms, what it would mean for UplitAU Pty Ltd to accept cryptocurrency payment from a customer — using CoinSpot as the named example exchange — for a specific, narrow product: issuing a DEMI Landing Page and/or a Portal Activation Code (the “Door 1” example in your plan). It is written so that you, as the responsible human at UplitAU, can read it and genuinely understand what you'd be agreeing to and what obligations follow, before any Russian-toggle bilingual interface goes live.

This document does NOT yet cover UplitPublishing Pty Ltd or any future Door 2 publishing-related crypto arrangement — that is explicitly out of scope here, per your plan, and would need its own version once Door 1 has been tested.

2. Important correction — what CoinSpot actually is

VERIFIED, 21 June 2026 — CoinSpot is a personal/retail cryptocurrency exchange and wallet — it lets a verified individual or business buy, sell, hold, and spend over 500 cryptocurrencies, including via its own prepaid Mastercard. It is registered with an Australian ABN, complies with AUSTRAC AML/CTF requirements, and is a member of the Australian Digital Commerce Association.

VERIFIED, 21 June 2026 — However, CoinSpot does not appear to offer a merchant payment-acceptance product — there is no public evidence of a CoinSpot checkout button, invoicing tool, or API for a business to receive customer payments the way Stripe or PayPal does for card payments. Dedicated crypto merchant-gateway products exist (e.g. CoinPayments, CoinsPaid, CoinGate), but these are separate companies, not CoinSpot, and most are based overseas with their own compliance frameworks.

This matters because it changes what “accepting crypto payment via CoinSpot” actually means in practice for UplitAU:

•       It means a customer sends cryptocurrency directly from their own wallet to a UplitAU-controlled CoinSpot wallet address — a manual transfer, not an automated checkout.

•       It does NOT mean CoinSpot processes the transaction, verifies the buyer, holds funds in escrow, or mediates a dispute — none of that protection exists in this model.

•       UplitAU would be responsible for manually confirming receipt, matching the payment to the correct order, and issuing the Activation Code or Landing Page only once the transfer is confirmed on the blockchain.

This is worth pausing on before drafting public-facing language: a manual wallet-transfer model is legal and workable for a low-volume demo, but it is meaningfully more exposed (no dispute resolution, no fraud protection, no automatic invoice matching) than the phrase “crypto payment via CoinSpot” might suggest to a customer reading it. The Terms below are written to be honest about this rather than to make it sound more automated than it is.

3. Draft Terms — Cryptocurrency Payment (UplitAU Pty Ltd)

3.1 What is being sold

A DEMI Landing Page and/or Portal Activation Code, issued by UplitAU Pty Ltd (ABN 91 680 646 495) on completion of payment, as described on the relevant page of ramsmile.com at the time of purchase.

3.2 Accepted payment method

•       Payment is accepted as a direct cryptocurrency transfer to a wallet address provided by UplitAU Pty Ltd at the time of order.

•       [Specify accepted currencies here — e.g. Bitcoin (BTC) and a stablecoin such as USDC are the most practical starting choices, since stablecoins avoid the price-volatility problem described in Section 3.4 below.]

•       UplitAU Pty Ltd does not control, operate, or guarantee the availability of CoinSpot or any other exchange. The buyer is responsible for the security and correct operation of their own wallet.

3.3 Confirmation and delivery

•       Orders are confirmed manually once the cryptocurrency transfer is visible and sufficiently confirmed on the relevant blockchain. This is not instant — buyers should expect a delay of minutes to hours, not an automatic real-time checkout.

•       The Landing Page / Activation Code will be issued to the email address provided at the time of order, once payment is confirmed.

3.4 Pricing and volatility

•       The price for the product is set and displayed in Australian Dollars (AUD). The buyer pays the equivalent amount in the chosen cryptocurrency, calculated at the exchange rate at the time of order.

•       Because cryptocurrency values can change significantly within minutes, a payment window will apply [e.g. 15–30 minutes from order to completed transfer]. Payments received outside this window may be under- or over-paid relative to the AUD price at confirmation time, and UplitAU reserves the right to request the difference or issue a partial refund accordingly.

3.5 No chargebacks, limited dispute process

•       Cryptocurrency transfers are irreversible once confirmed on the blockchain. There is no bank or card-network chargeback mechanism available for this payment method.

•       If a buyer believes a transaction was made in error (wrong amount, wrong currency, non-delivery after confirmed payment), they should contact UplitAU directly at [contact email]. UplitAU will make reasonable efforts to resolve genuine errors but cannot reverse a completed blockchain transaction.

•       Refunds, where agreed, will be issued in AUD to a bank account nominated by the buyer, or in the original cryptocurrency at UplitAU's discretion — not automatically in the original currency, since exchange rates may have moved.

3.6 Buyer eligibility and regional restrictions

•       [Open question for you to decide before publishing: will this be open to international buyers, or restricted to certain regions? CoinSpot itself requires the account holder — i.e. UplitAU — to be an Australian resident/entity with an Australian bank account, but this does not by itself restrict who can SEND a buyer-side wallet transfer to you. Regional restriction, if any, would need to be a deliberate choice stated here, not an automatic consequence of using CoinSpot.]

4. Regulatory and tax position — what UplitAU is actually subject to

This section is the one most worth taking to an accountant before relying on it, but here is the accurate starting picture:

Area

Current position

AUSTRAC / AML-CTF

CoinSpot itself is the regulated entity for AML/CTF purposes as the exchange you hold an account with. UplitAU, as a business merely receiving payment into its own wallet, is not automatically a regulated “digital currency exchange provider” under AUSTRAC — but if volume or structure changes (e.g. UplitAU starts converting crypto on behalf of others, not just itself), this status should be re-checked, not assumed.

Income tax

Cryptocurrency received as payment for goods/services is ordinary business income to UplitAU, valued in AUD at the market rate at the time of receipt — regardless of whether it is later converted to AUD or held.

GST

If UplitAU is GST-registered (or required to be, once turnover thresholds are met), GST treatment of a crypto-paid digital sale generally follows the same rules as any other digital sale — the fact that payment was made in crypto does not itself change whether GST applies.

Record-keeping

Each transaction's AUD-equivalent value at time of receipt, the wallet addresses involved, and the corresponding order should be recorded and retained — this is both an ATO requirement and the only practical way to reconcile a manual transfer-based system.

5. “Door 1” vs “Door 2” — keeping the demo properly scoped

As you set out: Door 1 is UplitAU issuing a DEMI Landing Page / Activation Code, used here as the safe, small-scale example. Door 2 — a UplitPublishing crypto account for publishing-related payments — is explicitly later, and explicitly separate.

•       Keep Door 1 small and clearly labelled as a demo/example on any page where it appears, so it reads as a proof of concept rather than a mature payment system — which is also an accurate description of what it currently is.

•       Door 2 should not reuse this document directly once it's time — a publishing entity selling to a broader, more international customer base for book-related products has a different risk profile (more buyers, more jurisdictions, potentially Uplitpublishing's existing app-store payment terms to reconcile with) and deserves its own version, built the same way: starting from what's actually true about the payment method, not from assumed features.

6. Before this goes anywhere public

•       Confirm which specific cryptocurrencies you'll actually accept, and fill in Section 3.2 and 3.4 brackets accordingly.

•       Decide the buyer-eligibility question in Section 3.6 deliberately, rather than leaving it open by default.

•       Take this document, once you've read and adjusted it, to an accountant for the tax/GST confirmation in Section 4 — this is the one section where getting it wrong has real cost, and it's a much smaller, cheaper question to ask than a full legal review.

•       Consider a visible, short version of Section 2's honesty — “payments are manual wallet transfers, not instant checkout” — directly on the page where a buyer sees the price, so no one is surprised by the confirmation delay.