Platform Features

INVSBL offers a set of private payment features for individual use and operational workflows. Each feature can be used on its own or combined into more complex flows.

---

1. Feature Overview

Feature	Best For	Key Privacy Benefit
Private Transfer Links	Direct payments, payouts	No wallet addresses exposed
Private Requests	Invoices, reimbursements	Anonymous payment requests
Batch Transactions	Payroll, grants	Hidden distribution structure
Split Payments	Group payments, distributions	Independent isolated claims
Private Memos	Contextual information	Encrypted end-to-end messages
Dashboard	Activity monitoring	Off-chain visibility without metadata leakage

---

2. Private Transfer Links

Private transfer links allow users to send assets without revealing wallet addresses, balances, or transaction history.

Property	Implementation
Sender privacy	The sender's wallet is never exposed
No address sharing	The recipient does not need to share an address in advance
Transaction isolation	The transfer cannot be linked to prior or future activity

2.1 How It Works

1. Sender creates transfer link for 100 USDC
   → Generates encrypted payment artifact
   → No wallet address in link

2. Sender shares link via any channel
   → Telegram, email, messaging, etc.
   → Link reveals nothing about sender

3. Recipient clicks link and claims
   → Uses their own wallet
   → No connection to sender created
   → Assets received privately

2.2 Use Cases

Use Case	Why It Works
Direct payments	Send money to anyone without knowing their address
Ad-hoc transfers	Quick payments without formal setup
Operational payouts	Distribute funds without exposing recipient list
Gift payments	Send funds anonymously

---

3. Private Requests

Private requests enable users to request funds without publishing an address or revealing identity.

3.1 What It Enables

Capability	Benefit
Anonymous requests	Create payment requests without exposing wallet details
Private fulfillment	Sender pays without revealing their identity
No public association	No on-chain link between requester and payer

3.2 How It Works

1. Requester creates invoice for 5000 USDC
   → Generates private payment request
   → No wallet address exposed

2. Requester shares invoice link
   → Via email, messaging, etc.
   → Invoice shows amount but no identity

3. Payer fulfills request
   → Pays via link
   → Both parties remain anonymous
   → No on-chain connection created

3.3 Use Cases

Use Case	Why It Works
Invoicing	Bill clients without exposing your wallet
Reimbursements	Request payment privately
Peer-to-peer payments	Request funds from friends without address sharing
Donations	Accept anonymous donations

---

4. Batch Transactions

Batch transactions allow a single sender to distribute assets to multiple recipients in one operation, without creating public traceability between recipients or revealing the distribution structure.

Characteristic	Protection
Recipient list	No public list of recipients
Payout amounts	No visible amounts per recipient
Distribution graph	No reconstructable distribution structure
Recipient relationships	Recipients cannot be linked to each other

4.1 How It Works

1. Sender initiates batch payment
   → 10 recipients, varying amounts
   → Creates encrypted payment artifacts for each

2. INVSBL processes batch
   → Each recipient gets individual payment link
   → No public record of batch structure

3. Recipients claim independently
   → Each claim is isolated
   → No way to tell they're part of same batch
   → No recipient knows about others

4.2 Use Cases

Use Case	Why It Works
Payroll	Pay employees without revealing salaries or employee list
Contributor payouts	Distribute payments to multiple contributors privately
Grants	Award grants without exposing recipients or amounts
Incentive programs	Distribute rewards confidentially

---

5. Split Payments

Split payments allow a single deposit to be converted into multiple independent private claims.

5.1 What It Enables

Feature	Description
Flexible allocation	Equal or predefined allocation of funds
Independent claiming	Each recipient claims separately
Hidden structure	No visibility into how funds were split or who claimed them

5.2 How It Works

1. User deposits 10,000 USDC
   → Specifies split: 5 recipients

2. INVSBL creates split
   → 5 independent claims of 2,000 USDC each
   → Or custom amounts per recipient

3. Recipients claim independently
   → Each claim is isolated
   → No connection between claims
   → No way to determine source or other recipients

Use Cases

Use Case	Why It Works
Group payments	Split bills privately among friends
Profit sharing	Distribute earnings to partners
Pool distributions	Split pooled funds confidentially
Multi-recipient gifts	Give to multiple people from one deposit

---

6. Private Memos

Private memos allow senders to attach encrypted messages to transfers or requests.

6.1 Properties

Property	Implementation
End-to-end encryption	Messages are encrypted end-to-end
Recipient-only access	Only the intended recipient can read the memo
Off-chain storage	Memo contents are never published on-chain

6.2 How It Works

1. Sender creates transfer with memo
   → Adds message: "Invoice #12345 - Web design"
   → Message encrypted with recipient's key

2. Recipient claims transfer
   → Decrypts and reads memo
   → Only they can see message content

3. On-chain record
   → No memo content visible
   → No indication memo exists

6.3 Use Cases

---

7. Dashboard

The INVSBL dashboard provides visibility into payment activity without exposing transaction details publicly.

7.1 Dashboard Capabilities

Feature	What It Does
Payment tracking	Track payment and request status
Operational monitoring	Monitor recurring flows and batch operations
Link management	Manage created links, claims, and expiration
Activity history	View your private transaction history

All monitoring occurs off-chain and does not introduce additional metadata to the blockchain.

7.2 What You Can See

Dashboard View:

Recent Activity:
✓ Transfer sent - 1000 USDC - Claimed
✓ Invoice created - 5000 USDC - Pending
✓ Batch payment - 10 recipients - 8 claimed
✓ Recurring payment - Active

Personal visibility without public exposure.

7.3 What Remains Private

Information	Status
Your activity	Visible to you in dashboard
Your balances	Visible to you in dashboard
Your transaction history	Visible to you in dashboard
Public blockchain record	No link to your identity
Third-party observers	Cannot see your activity

---

8. Feature Combinations

8.1 Example: Private Payroll System

1. Use Batch Transactions
   → Distribute to all employees in one operation

2. Add Private Memos
   → Include pay period and any notes

3. Set as Recurring
   → Automate monthly payments

4. Monitor in Dashboard
   → Track claim status without exposing structure

Result: Complete private payroll system

8.2 Example: Freelancer Workflow

1. Create Private Request (Invoice)
   → Client receives payment request

2. Add Private Memo
   → Include project details and invoice number

3. Client pays via link
   → Both parties remain anonymous

4. Track in Dashboard
   → Monitor payment status privately

Result: Professional invoicing with complete privacy