FB Pixel
The Kambria DAOs Framework (KDF)

Receiving Revenue: Creating a Payment Request

Estimated reading: 3 minutes 242 views

When a DAO is about to be paid — for a session, a product, a sponsorship — the Order Handler for that order creates a Payment Request. This gives the customer a clean way to pay, and it lets the framework record the revenue correctly from the start.

To create a payment request:

  1. In the DAO's Revenue Items, open the Payment requests tab and click + New Request. The DAO is already selected.
  2. Choose the Revenue Type / Category (for example, Service or Product) — see Categorisation & Revenue Split for what these are for.
  3. Enter the Amount in USDT.
  4. Add a short Description — the invoice or order text, so the payment is recognisable later. Add an Invoice Number if you have one.
    • Enter the customer's email and how long the link stays valid. The customer signs in with that email to pay.
  1. Create the request. The framework produces a payment request page containing:
    • the DAO's Revenue Vault address,
    • the amount and token (USDT on Polygon),
    • a human-readable reference,
    • and a Connect wallet & pay option for the customer.

If more than one member worked the order, the Order Handler who created it can add co-handlers — the people who will share that order's Order Handler revenue (see Order Handler Revenue Sharing) before the order is marked completed.

The customer then pays by sending USDT to the vault address shown on the request page.

A payment request moves through clear states, so everyone can see where it is:

Payment: Awaiting payment → Confirmed. Order: Open → Pending delivery → Completed

Screenshot: the "Create Payment Request" form (DAO pre-selected, category, amount, description) and the resulting payment request page with vault address + QR. 

 

Confirming what comes in

When the customer pays, the framework detects the USDT transfer to the vault and creates a draft revenue item. The Order Handler checks the category and reference are right and marks the order completed — and the payment is confirmed against the request. An Organizer can also mark it completed. If no one does, the order completes automatically a set number of days after payment — for example CED 60. Each DAO can change this period in its configuration, or set it to 0 to turn automatic completion off.

A few situations need a human eye, and the framework surfaces them rather than guessing: a payment for the wrong amount, a transfer that doesn't match any request, several transfers for one request, or a partial payment. The Order Handler resolves these before marking the order completed.

Screenshot: the "Incoming Revenue" view with a detected transfer awaiting confirmation.