SOURCE_URL: https://majikah.solutions/products/majik-buwiz/docs/buwiz-exchange-overview

---
title: "How the Invoice Cloud Exchange Works"
id: "buwiz-exchange-overview"
group: "majik-buwiz"
type: "products"
version: "0.1.1"
lastUpdated: "2026-05-13T00:00:00.000Z"
difficulty: "Beginner"
time: "5 minutes"
tags: [exchange, invoice-cloud-exchange, send, receive, muid, online, relay, zero-knowledge, encrypted, 30-day]
---

# How the Invoice Cloud Exchange Works

> What the Exchange is, how it works, and what you need to use it

## Overview
The Invoice Cloud Exchange is Majik Buwiz's built-in encrypted invoice transmission network. It lets you send and receive invoices directly with other Majik Buwiz users — fully end-to-end encrypted, with no payment processing and no permanent cloud storage.

### What is the Invoice Cloud Exchange?

The Invoice Cloud Exchange is a secure, encrypted relay network built into Majik Buwiz for sending and receiving invoices between users. It is strictly a communication layer — Majik Buwiz does not process payments. The Exchange simply ensures that invoices travel securely and privately from sender to recipient. All invoices transmitted through the Exchange are end-to-end encrypted before leaving your device. The relay server stores only ciphertext it cannot read.

### What you need to use the Exchange

The Exchange has two requirements that do not apply to offline use. First, you need an internet connection — the Exchange is the only feature in Majik Buwiz that requires one. Second, both sender and recipient must have a Majik Universal ID (MUID) bound to their Majikah account. This is a strict design requirement: every invoice in the Exchange is permanently tied to the sender's MUID, so recipients can always verify who issued the invoice. There are no anonymous invoices in the Exchange.

### Exchange requirements

| Requirement | Needed for Exchange? | Needed for offline use? |
| --- | --- | --- |
| Majik Key | Yes | Yes — always required |
| Majikah account | Yes | No |
| Majik Universal ID (MUID) | Yes — both sender and recipient | No |
| Internet connection | Yes | No |
| Recipient in Contacts directory | Yes — with full key material | No |
| KYC / Didit verification | No — unverified MUID is sufficient | No |

*Caption: What is needed vs. what is optional for Exchange use.*

### Encryption on the Exchange

All invoices sent through the Exchange are automatically upgraded to encrypted-and-signed mode before transmission, regardless of their local mode. If you have a signed-only invoice locally and publish it to the Exchange, Majik Buwiz re-encrypts it for the recipient before sending. The relay server receives and stores only the encrypted envelope — it cannot read the invoice contents at any point. This is a zero-knowledge relay design.

### 30-day retention window

Encrypted invoice data on the relay is automatically deleted after 30 days from the sent date unless updated by participants. This means recipients must sync and save received invoices to their local database within 30 days. After deletion from the relay, the invoice is no longer accessible via the Exchange. Invoices stored in your local database are not affected by the relay deletion — only the relay copy is removed.

### Exchange invoice states

| State | Meaning |
| --- | --- |
| Published | Invoice has been prepared and is ready to send via the Exchange |
| Sent | Invoice has been transmitted to the recipient via the relay |
| Received | Recipient's app has fetched the invoice from the relay |
| Accepted | Recipient has accepted and stored the invoice locally |
| Countersigned | Recipient has added their own signature to the invoice |
| Void | Invoice has been voided — relay copy may still exist until 30-day window expires |

*Caption: The state of an invoice as it moves through the Exchange.*

> **NOTE:** The Invoice Cloud Exchange is not a payment processor. It transmits invoice documents only — no money moves through Majik Buwiz. Payment is handled separately between the parties by whatever method they agree on.