Skip to main content

​
Commission Flow

Rako connects agent recommendations to merchant outcomes. Every recommendation creates attribution context that can later be reconciled into a payable conversion.

​
Three steps

Your agent queries Rako for offers matching user intent: vertical, price, features, provider, contract length, or other structured criteria. Rako returns eligible offers and a session ID.

​
2. Recommend

When the agent recommends a product, it calls the recommendation endpoint. This records the attribution event: the agent influenced the user toward a specific offer.

​
3. Checkout handoff

When the user is ready to buy, the checkout step returns a hosted checkout handoff. The merchant or payment processor handles payment, while Rako keeps attribution context available for later reconciliation. The checkout link or checkout session is not conversion proof; conversion requires later platform-side outcome evidence.

​
How attribution survives

  • No cookies required. Attribution is logged server-side when the recommendation is recorded.
  • Cross-device safe. The session ID ties the recommendation to the eventual purchase or payable milestone.
  • Drop-off recovery. Recommendations can return fallback links that preserve attribution if the user does not buy immediately.
  • Signed offer context. AAP Codes help verify the offer context Rako issued for the recommendation, including merchant, offer, price, currency, and commission basis.

​
Settlement levels

Rako supports multiple evidence models depending on merchant integration depth:
  1. Merchant-reported — the merchant reports payable outcomes.
  2. Payment-observed — payment-processor events confirm transaction status.
  3. Payment-split — commission is split as part of transaction clearing.