Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rako.sh/llms.txt

Use this file to discover all available pages before exploring further.

​
Merchant Integration Guide

A merchant integration gives agents a safe way to recommend products and gives Rako enough evidence to attribute payable outcomes.

​
Integration checklist

  1. Publish eligible offers — expose products, services, or campaigns that agents may recommend.
  2. Accept AAP context — carry the signed offer and recommendation context into checkout or the relevant conversion flow.
  3. Report outcomes — send payment, order, activation, or milestone status back to Rako.
  4. Reconcile commission — let the conversion ledger calculate merchant commission, Rako network fee, and builder payout.

​
Checkout and conversion paths

For instant checkout products, conversion can happen when payment status is confirmed. For delayed-service verticals such as broadband, energy, insurance, or finance, the payable conversion may be a later milestone such as approval, activation, policy start, or first bill paid. Rako keeps attribution and the conversion ledger authoritative while payment orchestration and payment status flow through the merchant’s payment processor.

​
What not to include

Do not place API keys, webhook secrets, private PSP configuration, or environment-specific deployment URLs in docs or examples.