SOURCE_URL: https://majikah.solutions/products/majik-buwiz/docs/buwiz-exchange-receive --- title: "Receiving & Accepting Invoices" id: "buwiz-exchange-receive" group: "majik-buwiz" type: "products" version: "0.1.1" lastUpdated: "2026-05-13T00:00:00.000Z" difficulty: "Beginner" time: "4 minutes" tags: [exchange, receive, inbox, accept, decrypt, countersign, sync, 30-day, muid] --- # Receiving & Accepting Invoices > Receiving invoices via the Exchange inbox — decrypting, accepting, countersigning, and syncing to local storage ## Overview How to receive, decrypt, accept, and optionally countersign invoices sent to you through the Invoice Cloud Exchange. ### How receiving works When another Majik Buwiz user sends you an invoice through the Exchange, it arrives in your Exchange inbox as an encrypted envelope. The invoice is stored on the Majikah relay until you sync it to your local database. All received invoices are encrypted — you need your Majik Key unlocked to decrypt and read the contents. The relay automatically deletes the envelope after 30 days from the sent date, so sync received invoices to your local storage promptly. ### How to receive and accept an invoice 1. **Open the Exchange inbox** *Exchange tab → Inbox* - Navigate to the Exchange tab and select Inbox. - Majik Buwiz fetches any new invoices from the relay addressed to your MUID. - Each inbox entry shows the public summary — sender name, total amount, invoice type, issue date, and sent date — without requiring decryption. 2. **Decrypt the invoice** *Your Majik Key must be unlocked* - Select an invoice from the inbox and choose Decrypt. - Majik Buwiz uses your ML-KEM-768 secret key to recover the shared secret and decrypts the invoice payload with AES-256-GCM. - Once decrypted, the full invoice content — line items, taxes, amounts, references, and notes — is visible. - Verify the sender's signature: Majik Buwiz checks the Ed25519 and ML-DSA-87 signatures against the sender's public keys. A valid signature confirms the invoice came from the stated MUID and has not been modified. 3. **Accept and sync to local storage** *Saves the invoice to your local invoice database* - Select Accept to save the invoice to your local My Invoices database. - Accepting does not send any automatic reply to the issuer — it is a local action only. - Once stored locally, the invoice is accessible offline and is included in your dashboard and CSV exports. - Do this before the 30-day relay window expires — after that, the relay copy is deleted and cannot be recovered from the Exchange. 4. **Optional — Countersign the invoice** *Add your signature to the invoice* - If the issuer has set up an expected signers allowlist that includes your MUID's key fingerprint, you can countersign the invoice. - Select Countersign to add your Ed25519 + ML-DSA-87 signature to the invoice's integrity block. - The countersigned invoice is re-encrypted and transmitted back to the issuer via the Exchange so they can sync your signed version. - Countersigning confirms your review and acceptance of the invoice contents cryptographically. ### Issuer syncing a countersigned invoice After a recipient countersigns an invoice, the issuer can sync the updated version from the Exchange to their local database. This brings in the recipient's signature, making the invoice fully signed by all expected parties. The issuer can then seal the invoice to permanently lock the integrity block. > ⚠️ **WARNING:** Sync received invoices within 30 days. The Majikah relay automatically deletes encrypted invoice envelopes 30 days after they were sent. After deletion, the invoice is no longer accessible via the Exchange. If you have not accepted and saved the invoice to your local database before that window closes, you will need to ask the issuer to resend it. > **NOTE:** Always verify the sender's MUID before accepting an invoice. The Exchange guarantees the invoice was sent from the stated MUID — but you should confirm that MUID belongs to the party you expect. You can check the sender's public MUID profile page to view their verification status and key information.