How it works
From link to ledger
Three steps. An agent can do each one from the CLI.
Set the rate, the hold period and the attribution window. Each change is a new version. A payment keeps the terms it was earned under.
Each partner gets their own links. Parka records the click and carries the referral into Stripe Checkout. The first touch in the window wins.
Each collected payment adds a commission entry. Renewals stay with the partner. Refunds and disputes add corrections. Nothing is edited.
Ledger
Every amount has a reason
Parka reads payment facts from Stripe. Each commission points to the payment and the rulebook version behind it.
Attribution stays on the subscription
The referral rides the Stripe checkout into the subscription. Renewals pay the same partner for the period the program sets.
Corrections, never edits
A refund or a dispute adds a correction entry. The original entry stays. The history adds up to the balance.
ce_0003 is unchanged. Replays of the same event add nothing.
Holds, not guesses
When the evidence does not agree, Parka holds the payment and posts nothing. A person looks at it. No partner is paid on a guess.
Workspaces
Each product gets its own workspace. Programs, links and partner records do not cross between them.
Versioned terms
Every rulebook change is a new version. A payment keeps the terms it was earned under.
Net revenue, whole cents
Commission is on collected revenue. Tax and processing fees stay out. Amounts are whole minor units, never floats.
API, CLI and MCP
Your agent runs it. You approve the money.
Every routine task is in the API, the CLI and the MCP server. Steps that move money or change terms wait for a person.
Agent
Create and configure programs
Set up a program in a workspace and read its terms.
ticket4:createProgram
Issue links and coupons
Give each partner links and codes scoped to one program.
ticket5:issueReferralLink
Explain a ledger entry
Show what a partner is owed and the payment behind each line.
ticket7:explainEntries
Draft a new rulebook version
Propose new terms. They do not apply until a person says yes.
ticket6:draftRulebookVersion
Reconcile the window
Compare the ledger against the source and classify every difference.
ticket12:queryReconciliationReport
Read the workspace
Read the configuration the runtime serves for a workspace.
ticket1:getWorkspaceConfig
Person
Activate new terms
A rulebook version takes effect only after a person activates it.
Needs a person
Approve commissions
An entry becomes payable only after approval. Time alone does not do it.
Needs a person
Pay and record the payout
You pay partners outside Parka. A person records the receipt.
Needs a person
Stripe holds the payments. You hold the payouts.
Parka does not move money
Parka calculates what each partner is owed. You pay them with your own rails and record the receipt. The ledger then shows the entry as paid.
- Reads
- payments, refunds, disputes and subscriptions from Stripe
- Writes
- commission entries, corrections and holds
- Never
- charges a card, holds funds or sends a payout