API first
Partner programs on Stripe,
run by agents
Parka tracks referral links, keeps attribution on the Stripe subscription and records every commission in an append-only ledger. Your agent runs the program. You approve the money.
Built for and used by Crispy.
$ node src/ticket16/cli.mjs ticket4:createProgram '{...}'
created partners workspace acme
$ node src/ticket16/cli.mjs ticket6:draftRulebookVersion '{...}'
drafted v1 rate 20% maturity 30d awaits a person
$ node src/ticket16/cli.mjs ticket5:issueReferralLink '{...}'
issued lnk_k3P9 acme.example/?ref=ana
$ node src/ticket16/cli.mjs ticket7:queryBalances '{}'
5 entries 1 hold unpaid $19.60
$
| Entry | Source | Amount | State |
|---|---|---|---|
| ce_0001commission | inv 1042 first payment | +9.80 | Paid externally |
| ce_0002commission | inv 1187 renewal | +9.80 | Approved |
| ce_0003commission | inv 1203 first payment | +19.80 | Pending |
| ce_0004correction | refund on inv 1203 | -19.80 | Posted |
| ce_0005commission | inv 1311 renewal | +9.80 | Pending |
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
Rulebook
What ships and what is next
Each program has a versioned rulebook. These rules work today. The cards below are on the roadmap. We set no date for them.
Search and discovery
Find creators and partners across the live databases of X and LinkedIn. Save a result to start a relationship.
More rule kinds
A flat amount per paid conversion, tiers, milestones, and per-partner overrides and groups.
Partner view
A partner sees their own links, results and what they are owed. They never see another partner.
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
Access
Is Parka a fit?
Tell us about your product and your partner program. We read every note and reply by email. Plans start at USD 89 a month.
Talk to us- 01
You sell on Stripe
Subscriptions or one-time payments through Stripe Checkout.
- 02
You want partners
Affiliates, creators or agencies who send you customers.
- 03
You work with agents
Or from a terminal. The API, CLI and MCP server come first.
FAQ
Questions
Short answers about attribution, the ledger and access. Ask us if yours is not here.
- What does Parka do?
- Parka runs partner and affiliate programs for SaaS products that sell on Stripe. It issues referral links, records clicks, attributes the Stripe subscription to a partner and keeps an append-only ledger of what each partner is owed.
- Does Parka pay my partners?
- No. Parka calculates the amounts. You pay partners outside Parka. Then a person records the payout receipt and the ledger shows the entry as paid.
- How does attribution work?
- The first qualifying partner touch wins inside the program's window. The default window is 90 days. A direct sale or a CRM opportunity that started before that touch takes precedence. The referral rides the Stripe checkout, so renewals stay with the same partner.
- What happens on a refund or a dispute?
- Parka adds a correction entry. It does not edit the original commission. If the evidence does not agree, for example a refund for a payment Parka has not seen, it holds the event and posts nothing.
- What can an agent do, and what needs a person?
- An agent can create programs, issue links and coupons, read balances and draft new terms through the API, CLI or MCP server. A person activates new terms, approves commissions and records payouts. An agent call to one of those steps creates an approval request and runs nothing.
- Which commission rules work today?
- A percentage of collected net revenue, a hold period before a commission matures and a recurring duration for renewals. Flat amounts per paid conversion, tiers, milestones and per-partner overrides are on the roadmap. A partner view, where partners see their own links and results, is on the roadmap too. We set no date for either.
- Who uses Parka now?
- Parka was built for Crispy and is used by Crispy. Both are Shyft products. Talk to us if you sell on Stripe and want to run your program the same way.
- What does it cost?
- Growth is USD 89 a month and Pro is USD 179 a month. Enterprise starts at USD 449 a month. Annual billing gives you 2 months free. Every plan has a 0% transaction fee. See the pricing page for the revenue bands.